Hide Forgot
rsyslogd fails to start during the boot sequence. rsyslogd segfaults when run from the command line with "-d -m 0" options. See attached log file. -Joseph
Created attachment 160186 [details] output from "/sbin/rsyslogd -d -m 0"
(gdb) bt #0 0x0fee60e4 in __atomic_writev_replacement () from /lib/libc.so.6 #1 0x10014d1c in writeFile (f=0x1002f4c8) at omfile.c:361 #2 0x10015134 in doActionFile (f=0x7) at omfile.c:433 #3 0x10004cc0 in fprintlog (f=0x1002f4c8) at syslogd.c:3297 #4 0x10005ed8 in processMsg (pMsg=0x1002f358) at syslogd.c:2424 #5 0x10004e34 in logmsg (pri=<value optimized out>, pMsg=0x1002f358, flags=5) at syslogd.c:2611 #6 0x10005938 in logmsgInternal (pri=46, msg=0x7fa672fe " [origin software=\"rsyslogd\" swVersion=\"1.17.2\" x-pid=\"6221\"][x-configInfo udpReception=\"No\" udpPort=\"514\" tcpReception=\"No\" tcpPort=\"0\"] restart", flags=4) at syslogd.c:2172 #7 0x100091c0 in init () at syslogd.c:4495 #8 0x1000b410 in main (argc=<value optimized out>, argv=<value optimized out>) at syslogd.c:6405 #9 0x0fe1de0c in generic_start_main () from /lib/libc.so.6 #10 0x0fe1e060 in __libc_start_main () from /lib/libc.so.6 #11 0x00000000 in ?? ()
Could you test it with rsyslog-1.17.5-1, please. I wasn't able to reproduce it with the newest(-5) release on ppc64. http://people.redhat.com/pvrabec/rpms/rsyslog/rsyslog-1.17.5-1.src.rpm
Peter, Version 1.17.5-1, fetched from Koji today, starts up immediately and runs on my 32-bit PPC. -Joseph