action #114397
closed
glibc regression causes cron to crash
Added by favogt over 2 years ago.
Updated over 2 years ago.
Description
git repos on o3 didn't get updated because cron crashes with
Jul 20 08:09:02 ariel cron[3041]: *** stack smashing detected ***: terminated
Jul 20 08:09:02 ariel cron[3040]: *** stack smashing detected ***: terminated
Jul 20 08:09:02 ariel cron[3039]: *** stack smashing detected ***: terminated
This is due to boo#1201560/bsc#1200855. I downgraded glibc to the previous version and added a lock. Once the fixed package is out, the lock should be removed again.
- Target version set to Ready
- Related to action #111869: Upgrade o3 webUI host to openSUSE Leap 15.4 size:S added
- Status changed from New to Blocked
- Assignee set to mkittler
I'll do the update on o3 and check whether the problem persists after a reboot. If it persists, I'll try to downgrade.
- Status changed from Blocked to New
- Assignee deleted (
mkittler)
o3 is on Leap 15.4 but glibc is still locked.
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to mkittler
- Status changed from In Progress to Feedback
Removed the lock on o3, updated and restarted cron. Still looks good so far.
On OSD this wasn't locked so there's nothing to do.
- Status changed from Feedback to Resolved
The last (relevant) error message in o3's journal is Jul 20 08:15:01 ariel cron[5267]: *** stack smashing detected ***: terminated. So we should be good on the new glibc version.
Also available in: Atom
PDF