View Issue Details

IDProjectCategoryView StatusLast Update
0016803CentOS-6rsyslogpublic2019-12-06 11:38
Reporterfwilliamson 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
Product Version6.10 
Target VersionFixed in Version 
Summary0016803: Rsyslog8 fails on startup with "Ohhhh jeeee: Assertion `pool_is_locked' failed (random-csprng.c:1075:add_randomness)"
DescriptionOS:
CentOS 6.10
LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 6.10 (Final)
Release: 6.10
Codename: Final

Rsyslog version/packages:
rsyslog-gnutls-8.1905.0-2.el6.x86_64
rsyslog-8.1905.0-2.el6.x86_64



Steps To Reproduce1) Start rsyslog:

service rsyslog start
Starting system logger: [ OK ]

2) ps -aux | grep rsyslog shows no rsyslog running.

3) Display rsyslog status:
rsyslogd dead but pid file exists

4) Removed /var/run/syslog.pid and /var/lock/subsys/rsyslog

5) Run rsyslog from console, in debug mode:

/sbin/rsyslog -dn
Additional InformationGzipped rsyslog debug messages file attached.
TagsNo tags attached.

Activities

fwilliamson

fwilliamson

2019-12-06 09:51

reporter  

rsyslog_debug.txt.gz (1,052,086 bytes)
fwilliamson

fwilliamson

2019-12-06 11:38

reporter   ~0035806

My apologies, I sincerely hope this issue didn't waste anybody's valuable time.

After deeper investigation, it looks like this issue was caused by a badly configured client.conf file.

Opening a can of whoopass on the guilty party. :/


Please close this issue.

Issue History

Date Modified Username Field Change
2019-12-06 09:51 fwilliamson New Issue
2019-12-06 09:51 fwilliamson File Added: rsyslog_debug.txt.gz
2019-12-06 11:38 fwilliamson Note Added: 0035806