| View previous topic :: View next topic |
| Author |
Message |
treble33
n00b
Joined: 19 Oct 2012
Posts: 4
|
 Posted: Fri Oct 19, 2012 6:13 pm Post subject: [solved] could updating software rarely cause problems |
 |
|
Hello! I own gentoo server for like 2 or 3 years. Server uptime is almost year. And I install updates really rarely. I don't have physical access to server because it's located pretty far away in data center. So i'm a bit worried about installing critical updates. First thing is that I have many kernel versions:
[1] linux-2.6.34-gentoo-r6 *
[2] linux-2.6.39-gentoo-r3
[3] linux-3.2.12-gentoo
[4] linux-3.4.9-gentoo
Could swtiching to latest version cause any problems? Because I can't risk getting server offline after failed boot.
Also there are many python versions:
[1] python2.6
[2] python2.7 *
[3] python3.1
[4] python3.2
Can I safetly switch to latest python and delete others with depclean?
Should I fear any other startup problems related to emerging many updates after long time?
Last edited by treble33 on Sun Oct 21, 2012 9:10 pm; edited 1 time in total |
|
| Back to top |
|
 |
gentoo_ram
Guru
Joined: 25 Oct 2007
Posts: 474
Location: San Diego, California USA
|
| Posted: Fri Oct 19, 2012 6:24 pm Post subject: |
|
|
| Any Gentoo box that sits around without updates for that long should probably be re-installed from scratch. Would be less painful. Gentoo is more of a "live" distribution. |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Fri Oct 19, 2012 6:53 pm Post subject: |
|
|
| Perhaps a bigger problem than your server going offline, is that it's online, in a public datacentre, and an entire year behind on security updates. Have you run a rootkit checker recently? |
|
| Back to top |
|
|
piedar
Tux's lil' helper
Joined: 09 Aug 2010
Posts: 82
|
| Posted: Fri Oct 19, 2012 7:24 pm Post subject: |
|
|
Are you up to date other than kernel and python?
For python you'll be fine sticking with 2.7. Depclean should want to remove 2.6 and 3.1 unless something depends directly on them. Then again, I use 3.2 and it's rare to find something in the tree that doesn't work with it. Most packages that require a specific version use what they need instead of the system default. If you do switch python versions, make sure to run python-updater after.
For the kernel, as long as you configure it carefully and consistently with the old one, you should be fine. Just in case, have a look at Grub's fallback feature, which can boot the old kernel if the new one fails.
Oh, and make sure you read emerge output. There's lots of important information there, especially if you're doing a lot of major updates. |
|
| Back to top |
|
|
treble33
n00b
Joined: 19 Oct 2012
Posts: 4
|
| Posted: Fri Oct 19, 2012 8:10 pm Post subject: |
|
|
Everything else is up to date. There usually aren't any huge problems with blocking or anything like that.
My boot partition is not mounted after boot, so i guess it stays untouched thus can't cause any issues with booting?
I think everything will be fine anyway. Usually I do read emerge log, and there haven't been any problems. |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Sat Oct 20, 2012 1:46 am Post subject: |
|
|
| treble33 wrote: | | Everything else is up to date. |
What does `lsof -n | egrep '/(bin|lib).*\(deleted\)'` print out? |
|
| Back to top |
|
|
treble33
n00b
Joined: 19 Oct 2012
Posts: 4
|
| Posted: Sat Oct 20, 2012 7:45 am Post subject: |
|
|
| Code: | screen 2625 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
bash 2626 root txt REG 8,3 847992 1075620 /var/tmp/portage/app-shells/bash-4.2_p20/image/bin/bash (deleted)
screen 3958 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
cs 3960 root txt REG 8,3 692536 814510729 /var/tmp/portage/app-shells/bash-4.2_p37/image/bin/bash (deleted)
screen 12297 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
cs 12298 root txt REG 8,3 692536 814510729 /var/tmp/portage/app-shells/bash-4.2_p37/image/bin/bash (deleted)
screen 13655 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
bash 13656 root txt REG 8,3 847992 1075620 /var/tmp/portage/app-shells/bash-4.2_p20/image/bin/bash (deleted)
screen 15299 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
cs 15300 root txt REG 8,3 692536 814510729 /var/tmp/portage/app-shells/bash-4.2_p37/image/bin/bash (deleted)
screen 27780 root txt REG 8,3 342368 769627 /var/tmp/portage/app-misc/screen-4.0.3-r5/image/usr/bin/screen (deleted)
bash 27781 root txt REG 8,3 847992 1075620 /var/tmp/portage/app-shells/bash-4.2_p20/image/bin/bash (deleted) |
I guess thats because i have 6 screen sessions open for long time. It also showed up dovecot and postfix but they disappeared after restarting them. |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Sat Oct 20, 2012 3:05 pm Post subject: |
|
|
OK, that's not a bad sign.
The longer you leave it though, the more chance there is that something in the boot process will change in incompatible ways. That's already happened for other people with devtmpfs (and new udev requires it). |
|
| Back to top |
|
|
treble33
n00b
Joined: 19 Oct 2012
Posts: 4
|
| Posted: Sun Oct 21, 2012 9:13 pm Post subject: |
|
|
| ok, so i did restart server, everything went well, only thing that booting took 20min`s because of filesystem check. |
|
| Back to top |
|
|
|
Portage & Programming
