Project

General

Profile

Actions

action #114397

closed

glibc regression causes cron to crash

Added by favogt almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2022-07-20
Due date:
% Done:

0%

Estimated time:

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.


Related issues 1 (0 open1 closed)

Related to openQA Infrastructure - action #111869: Upgrade o3 webUI host to openSUSE Leap 15.4 size:SResolvedmkittler

Actions
Actions #1

Updated by okurz almost 2 years ago

  • Target version set to Ready
Actions #2

Updated by okurz almost 2 years ago

  • Related to action #111869: Upgrade o3 webUI host to openSUSE Leap 15.4 size:S added
Actions #3

Updated by mkittler almost 2 years ago

  • 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.

Actions #4

Updated by mkittler over 1 year ago

  • Status changed from Blocked to New
  • Assignee deleted (mkittler)

o3 is on Leap 15.4 but glibc is still locked.

Actions #5

Updated by okurz over 1 year ago

  • Description updated (diff)

both https://bugzilla.suse.com/show_bug.cgi?id=1201560 https://bugzilla.suse.com/show_bug.cgi?id=1200855 mention a glibc update ready to be installed. We should ensure that we have that version installed and confirm the problem gone or reopen the bug.

Actions #6

Updated by mkittler over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to mkittler
Actions #7

Updated by mkittler over 1 year ago

  • 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.

Actions #8

Updated by mkittler over 1 year ago

  • 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.

Actions

Also available in: Atom PDF