rsyslog crash with "double free or corruption (out)" #5343
Milestone
Comments
gaaf
changed the title
|
8.35 is very old, you would need to update to a current version for the
community to be able to support you (or reach out to your distro for support if
you don't want to upgrade to a version they don't provide to you)
If you do update to a current version, we would need your full config
(rsyslog.conf and any included files) to begin to figure out what's going on.
David Lang
…On Tue, 5 Mar 2024, Alex Hermann wrote:
### Expected behavior
No crash
### Actual behavior
Crash.
### Steps to reproduce the behavior
This has ever happened only a single time.
### Environment
- rsyslog version: <!-- e.g. 8.35.0 - use "rsyslogd -v" to obtain the version number -->
- platform: <!-- e.g. Ubuntu 16.04 -->
- for configuration questions/issues, include rsyslog.conf and included config files
<!-- Note: rsyslog documentation is available here:
- current stable release: http://www.rsyslog.com/doc/v8-stable/
- pre-release: http://www.rsyslog.com/doc/master/
-->
|
|
You only saw a half filled report that github found necessary to submit on a yet unknown key(-combo?) I apparently hit while typing. The report is complete now. My rsyslog version is 8.2312.0 (aka 2023.12) which is not the newest, but also not very old. Config: |
|
On Tue, 5 Mar 2024, Alex Hermann wrote:
You only saw a half filled report that github found necessary to submit on a yet unknown key(-combo?) I apparently hit while typing. The report is complete now.
sorry about that
My rsyslog version is 8.2312.0 (aka 2023.12) which is not the newest, but also not very old.
yep, that's current enough
Config:
If this is the full config, I don't see anything odd or likely to trigger a
problem
did the crash create a core file?
David Lang
… ```
# grep -h -v ^# /etc/rsyslog.conf /etc/rsyslog.d/*.conf | grep \\S
module(load="imuxsock") # provides support for local system logging
module(load="imklog") # provides kernel logging support
module(load="imudp")
input(type="imudp" port="514")
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$FileOwner root
$FileGroup adm
$FileCreateMode 0640
$DirCreateMode 0755
$Umask 0022
$WorkDirectory /var/spool/rsyslog
$IncludeConfig /etc/rsyslog.d/*.conf
auth,authpriv.* /var/log/auth.log
*.* -/var/log/syslog
*.emerg :omusrmsg:*
template (name="VoipFile" type="string" string="/var/log/voip-%timestamp:::date-year%-%timestamp:::date-month%-%timestamp:::date-day%.log")
$fileGroup www-data
local0.* -?VoipFile;RSYSLOG_FileFormat
&stop
:programname, isequal, "asterisk" -?VoipFile;RSYSLOG_FileFormat
&stop
:programname, isequal, "kamailio" -?VoipFile;RSYSLOG_FileFormat
&stop
```
|
|
Please take a look at the issue on github. Because of the submitted unfinished report, the emails don't have all information, including a full backtrace. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
No crash
Actual behavior
Crash. The only correlation I could find is that the systems resumed from boot a few minutes (~4) before.
The crash was triggered by this message:
I've had these multiple times after resume, but I've ever noticed a crash before.
Steps to reproduce the behavior
This has ever happened only a single time. This config has been running trouble free for years, including several supend-resume cycles.
Environment
Backtrace
The text was updated successfully, but these errors were encountered: