Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rsyslog aborts if errmsg is generated in early startup #1783

Closed
rgerhards opened this issue Sep 21, 2017 · 1 comment · Fixed by #1784
Closed

rsyslog aborts if errmsg is generated in early startup #1783

rgerhards opened this issue Sep 21, 2017 · 1 comment · Fixed by #1784
Assignees
Labels
Milestone

Comments

@rgerhards
Copy link
Member

if the errmsg subsystem is used during startup, rsyslog aborts due to "deadly signal". This most probably means that the internal signaling is not properly initialized (too late in the process).

@rgerhards rgerhards self-assigned this Sep 21, 2017
@rgerhards rgerhards added the bug label Sep 21, 2017
@rgerhards rgerhards added this to the v8.30 milestone Sep 21, 2017
rgerhards added a commit to rgerhards/rsyslog that referenced this issue Sep 21, 2017
Note that the segfault can occur only during early startup. Once
rsyslog has started, everything works reliably.

closes rsyslog#1783
@lock
Copy link

lock bot commented Dec 26, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant