Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 913123 - app-admin/syslog-ng 4.2.0 logging repeated "general protection fault ... in libsyslog-ng-4.0.so.0.0.0", high CPU
Summary: app-admin/syslog-ng 4.2.0 logging repeated "general protection fault ... in l...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tomáš Mózes
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-27 22:26 UTC by John Hardin
Modified: 2023-09-04 22:10 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Hardin 2023-08-27 22:26:12 UTC
syslog-ng is spinning on one CPU logging this:

> Aug 27 14:45:39 davinci kernel: traps: syslog-ng[14142] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:42 davinci kernel: show_signal: 10 callbacks suppressed
> Aug 27 14:45:42 davinci kernel: traps: syslog-ng[14201] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:42 davinci kernel: traps: syslog-ng[14212] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:42 davinci kernel: traps: syslog-ng[14213] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:43 davinci kernel: traps: syslog-ng[14214] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:43 davinci kernel: traps: syslog-ng[14215] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:43 davinci kernel: traps: syslog-ng[14231] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:43 davinci kernel: traps: syslog-ng[14232] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:44 davinci kernel: traps: syslog-ng[14233] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:45 davinci kernel: traps: syslog-ng[14259] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:45 davinci kernel: traps: syslog-ng[14260] general protection fault ip:7efeb17726fc sp:7ffd9ae8aad8 error:0 in libsyslog-ng-4.0.so.0.0.0 (deleted)[7efeb174b000+78000]
> Aug 27 14:45:47 davinci kernel: show_signal: 6 callbacks suppressed


Downgrading to 4.0.1 works.



Reproducible: Always

Steps to Reproduce:
1. Install syslog-ng 4.2.0
Comment 1 John Hardin 2023-08-27 22:42:27 UTC
It looks like there were several instances of syslog-ng running. Perhaps the upgrade didn't properly stop the 4.0.1 version and that is causing a conflict?
Comment 2 snIP3r 2023-09-01 06:23:05 UTC
had the same error. but after disabling python use flag as suggested here https://bugs.gentoo.org/907550 and restarting syslog-ng everything runs as it should
Comment 3 John Hardin 2023-09-01 19:03:51 UTC
Disable python globally, or just for syslog-ng?
Comment 4 John Hardin 2023-09-02 22:39:18 UTC
Confirmed, disabling python for just app-admin/syslog-ng in package.use avoids the problem. Something python-related is broken. Potentially virtualenv? (see bug 907550)
Comment 5 Jan Sembera 2023-09-04 22:10:30 UTC
The comment about extra running instances helped in my case. After several unsuccessful runs of /etc/init.d/syslog-ng restart, I read the note here, tried /etc/init.d/syslog-ng stop, then kill -9 the remaining running instances and then manually starting seems to have helped. There was still some whining about python venv:

[2023-09-05T00:06:06.185906] python: private virtualenv is not initialized, use the `syslog-ng-update-virtualenv' script to initialize it or make sure all required Python dependencies are available in the system Python installation; path='/var/lib/syslog-ng/python-venv'                          [ ok ]

but otherwise I have one instance that isn't crashing. So it may be a problem of the upgrade path. That said, I haven't rebooted since then, so I'm not sure if I'll get multiple instances again once I reboot.