View previous topic :: View next topic |
Author |
Message |
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9657 Location: almost Mile High in the USA
|
Posted: Wed Dec 06, 2017 9:01 pm Post subject: Warning to vixie-cron users... |
|
|
Today I tried emerge --update @world after about almost 3 weeks.
It came out CLEAN, no updates. That can't be right, have the Gentoo dev team been slacking?
No! I then noticed I had not gotten an emerge --sync for over two weeks, despite having a cron job to do this every other day.
I recently pulled an update and something got updated, might be glibc or pam along with gcc. Anyway, vixie-cron had been running fine in the background or at least I thought it was as the process was still running. Turns out that it was trying to run but coughing up errors when it couldn't dynamically link modules to pam.
A simple restart of vixie-cron was sufficient to restore operation.
Just a word of warning to anyone depending on cron syncs... restart your daemons and ensure they're still running after any update, and sometimes rebooting is not a bad idea (no wonder M$ wants a reboot!) _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Thu Dec 07, 2017 5:54 am Post subject: |
|
|
Ah, thanks for the reminder why I run all my systems USE=-pam ;) |
|
Back to top |
|
|
joanandk Apprentice
Joined: 12 Feb 2017 Posts: 169
|
Posted: Thu Dec 07, 2017 6:41 am Post subject: Re: Warning to vixie-cron users... |
|
|
eccerr0r wrote: | No! I then noticed I had not gotten an emerge --sync for over two weeks, despite having a cron job to do this every other day.
...
A simple restart of vixie-cron was sufficient to restore operation. |
I have seen that too, but in my case there was an entry in the syslog. I have seen that such issues are very seldom and there are ways to check (for example, for each sync done by cron, I get an E-Mail).
Did you change your profile prior to updating cron? If so, this was the cause for the failure.
eccerr0r wrote: | and sometimes rebooting is not a bad idea (no wonder M$ wants a reboot!) |
On MS Windows you reboot even for no reason I think MS would even like to reboot after you have saved your Word document (just to sure that the cache has been committed)
BR |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9657 Location: almost Mile High in the USA
|
Posted: Thu Dec 07, 2017 7:03 am Post subject: |
|
|
For me it was an unexpected failure, I didn't change the profile - normally it wouldn't fail like this. The link error was in syslog but was quite cryptic... _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
cboldt Veteran
Joined: 24 Aug 2005 Posts: 1046
|
Posted: Thu Dec 07, 2017 10:35 am Post subject: |
|
|
FWIW, I run "lib_users" after doing updates, and restart services to get that report cleaned up. Not sure it would have caught the mismatch you describe, but I think it would have.
I try to reboot rarely, just out of principle, no practical reason, but did reboot after profile change and emerge -e @world, just to make sure it would (reboot). |
|
Back to top |
|
|
krinn Watchman
Joined: 02 May 2003 Posts: 7470
|
Posted: Thu Dec 07, 2017 3:50 pm Post subject: |
|
|
Just to prove my memory is gold, here's Naib code that would had saved you...
Thanks goes to Naib so (but i'm not against a little pic of you praising my memory!) |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9657 Location: almost Mile High in the USA
|
Posted: Thu Dec 07, 2017 5:55 pm Post subject: |
|
|
Actually I don't think it would help in this case, because it's a link on demand - the problem library isn't actually loaded in memory until needed, and at that point the failure is detected.
Granted that searching for programs that require restarts that way is helpful (it may have hinted that vixie-cron may have other programs that other libraries indeed does need a restart), most programs don't need immediate restarts because these libraries are saved in memory even if you delete the binaries -- which is why people get the false impression a restart isn't necessary after updates. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Zucca Moderator
Joined: 14 Jun 2007 Posts: 3313 Location: Rasi, Finland
|
Posted: Thu Dec 07, 2017 6:51 pm Post subject: |
|
|
I use metalog to send alerts if it sees something fishy. Simplest thing could probably be to just to run beep (PC-speaker), but to reach further a mail should be sent for example. _________________ ..: Zucca :..
Gentoo IRC channels reside on Libera.Chat.
--
Quote: | I am NaN! I am a man! |
|
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21522
|
Posted: Fri Dec 08, 2017 2:22 am Post subject: |
|
|
I hit this failure recently on a system that had received a sys-libs/glibc update, but no recent PAM updates. Therefore, I think it was the libc upgrade which provoked the problem, so anything that flagged programs running an old libc (which unfortunately is almost all of them) probably would have reported the need for intervention just on the basis that a deleted libc was in use, independent of whether that broke PAM. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6095 Location: Dallas area
|
Posted: Fri Dec 08, 2017 10:29 am Post subject: |
|
|
I always bounce the box after a libc update. _________________ PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
|