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
074bef45
Unverified
Commit
074bef45
authored
5 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
document kernel upgrade procedure
parent
74d03155
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
+30
-0
30 additions, 0 deletions
tsa/howto/upgrades.mdwn
with
30 additions
and
0 deletions
tsa/howto/upgrades.mdwn
+
30
−
0
View file @
074bef45
...
...
@@ -20,6 +20,36 @@ When a few pending upgrades have piled up, a batch of upgrades can be
done with the `torproject-upgrade-prepare` command, which is available
in the `admin/tor-misc.git` project in git-rw.
### Kernel upgrades and reboots
Sometimes it is necessary to perform a reboot on the hosts, when the
kernel is updated. Nagios will warn about this, with something like
this:
WARNING: Kernel needs upgrade [linux-image-4.9.0-9-amd64 != linux-image-4.9.0-8-amd64]
If this is only a virtual machine, and the only one affected, it can
be rebooted directly. If it has an encrypted filesystem and is hooked
up with Mandos, it will return automatically. Otherwise it might need
a password to be entered at boot time, either through the initramfs
(if it has the `profile::fde` class in Puppet) or manually, after the
boot.
Generally, KVM hosts are the latter and need special attention, as the
guests need to be individually rebooted. The `tor-libvirt-reboot`
takes care of the hand-holding necessary here. When the server
returns, the encrypted partitions need to be unlocked as well, with
the `tor-libvirt-luks-start` command. A full reboot procedure will
look something like this:
host=unifolium.torproject.org
ssh -tt root@$host tor-libvirt-reboot &&
echo "waiting 2 minutes for host to come back" &&
ping -c 10 -w 120 $host &&
ssh -tt root@$host tor-libvirt-luks-start
### Example run
Here's an example run of the tool:
weasel@orinoco:~$ torproject-upgrade-prepare
...
...
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