Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
3ec61c80
Unverified
Commit
3ec61c80
authored
5 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
show how to restart services without rebooting
parent
b287aae4
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tsa/howto/upgrades.mdwn
+42
-0
42 additions, 0 deletions
tsa/howto/upgrades.mdwn
with
42 additions
and
0 deletions
tsa/howto/upgrades.mdwn
+
42
−
0
View file @
3ec61c80
...
...
@@ -21,6 +21,48 @@ done with the `torproject-upgrade-prepare` command, which is available
in the `admin/tor-misc.git` project in git-rw, followed by the
`tor-project-upgrade` script.
### Restarting services
After upgrades, there's a Nagios check that might trigger and tell you
that some services are running with outdated libraries. For example,
after a Bacula upgrade:
The following processes have libs linked that were upgraded: bacula: bacula-fd (1787)
While the entire host can be rebooted (using the procedure below) to
fix this problem, it's sometimes less disruptive to just restart that
one process.
For this purpose, `needrestart` is installed on all machines, but it's
currently not setup to automatically restart services while we test
the service. It can still be useful to restart services manually, for
example with:
ssh root@cupani.torproject.org needrestart -u NeedRestart::UI::stdio -r a
(Note that earlier versions of needrestart showed spurious warnings in
this mode, see [bug #859387](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859387), fixed in buster.)
If you cannot figure out why the warning happens, you might want to
run the check by hand:
/usr/lib/nagios/plugins/dsa-check-libs
The `--verbose` flag also shows which file trigger the warning.
Some services will have `cron` as a parent, and will make
`needrestart` want to restart cron which is, of course,
ineffective. The only "proper" way to restart those services is to
reboot the host.
Services setup with the new systemd-based startup system documented in
[[doc/services]] can be restarted with:
systemctl restart user@1504.service
There's a feature request ([bug #843778](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843778)) to implement support for
those services directly in needrestart.
### Kernel upgrades and reboots
Sometimes it is necessary to perform a reboot on the hosts, when the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment