Mailing List Archive: RSyslog: users

5.8.5 Upgrade Issue

Index | Next | Previous | View Threaded

jpoling at moody

Sep 8, 2011, 9:02 PM

Post #1 of 3 (204 views)
Permalink

5.8.5 Upgrade Issue

I installed rsyslog 5.8.5 on a system that already had 5.4.x on it. A symbolic link was used previously to point to the rsyslog install directory. After installing the new version, I adjusted to link to point to the new version. Here is what the file system looks like:

drwxr-xr-x 2 root root 1024 Sep 14 2010 etc
drwxr-xr-x 4 root root 1024 Sep 14 2010 relp
lrwxrwxrwx 1 root root 26 Sep 8 13:27 rsyslog -> /opt/rsyslog/rsyslog-5.8.5
drwxr-xr-x 5 root root 1024 Sep 14 2010 rsyslog-5.4.0
drwxr-xr-x 5 root root 1024 Sep 8 13:24 rsyslog-5.8.5
drwxr-xr-x 2 root root 1024 Sep 14 2010 spool

When I try to start rsyslog with the start script that was used previously (/etc/init.d/rsyslog), it hangs. After a reboot, rsyslog simply does not start.

So, I am missing something :) Is there a way to debug this? Is there a local log that rsyslog creates with info that will help me determine what is wrong?

Any insight is greatly appreciated. If I did not explain it well, please let me know that also.

Thanks,

Jeff

Jeffrey Poling
System Administrator | Information Systems
Moody Bible Institute
820 N. LaSalle Blvd., Chicago, IL 60610
312-329-8968
www.moodyministries.net<http://www.moodyministries.net>
From the Word. To Life.

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

jpoling at moody

Sep 9, 2011, 8:06 AM

Post #2 of 3 (198 views)
Permalink

Re: 5.8.5 Upgrade Issue [In reply to]

I posted last night about an issue with rsyslog hanging after I started using the 5.8.5 version. Today I have some more info. The startup process actually fails and produces the following error:

"Starting system logger (rsyslog): rsyslogd: $AbortOnUncleanConfig is set, and config is not clean.
Check error log for details, fix errors and restart. As a last resort, you may want to remove $AbortOnUncleanConfig to permit a startup with a dirty config."

I am using the same config file from the previous version of rsyslog. Is there something that I need to change in the config file to get it to work with 5.8.5? Below is the config we are using:

##
$ModLoad immark # provides --MARK-- message capability
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imklog # kernel logging (formerly provided by rklogd)

####
$ModLoad imfile # Input module for text files
#$ModLoad imrelp # Input RELP protocol
#$InputRELPServerRun 1514
$ModLoad omrelp

$WorkDirectory /opt/rsyslog/spool
$MarkMessagePeriod 600
$MaxMessageSize 64k
#$OptimizeForUniprocessor on
$RepeatedMsgReduction off

#$MainMsgQueueFileName mailQ_
#$MainMsgQueueSaveOnShutdown on
#$MainMsgQueueType LinkedList
#$MainMsgQueueWorkerThreads 8

$ActionWriteAllMarkMessages on
$ActionQueueFileName actionQ_
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList
$ActionResumeRetryCount -1
#$ActionQueueWorkerThreads 8
#$ActionQueueDequeueBatchSize 32
#$ActionQueueHighWaterMark 12000

$AbortOnUncleanConfig on
#$template HostFile,"/opt/var/log/messages.%FROMHOST%.%%%%%%%%"
#$template TraditionalFormat,"%% %timegenerated:::date-rfc3164% %HOSTNAME% [%syslogfacility-text%.%syslogpriority-text%] %syslogtag%%msg%\n"

*.* :omrelp:mysyslogserver.myorg.com:601

Thanks for any insight.

Jeff
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

rgerhards at hq

Sep 11, 2011, 8:16 AM

Post #3 of 3 (196 views)
Permalink

Re: 5.8.5 Upgrade Issue [In reply to]

Can you pls provide a debug log of the startup? One reason may be that the work directory does not exist. This was previously undetected.

Rainer

Jeff Poling <jpoling [at] moody> hat geschrieben:I posted last night about an issue with rsyslog hanging after I started using the 5.8.5 version. Today I have some more info. The startup process actually fails and produces the following error:

"Starting system logger (rsyslog): rsyslogd: $AbortOnUncleanConfig is set, and config is not clean.
Check error log for details, fix errors and restart. As a last resort, you may want to remove $AbortOnUncleanConfig to permit a startup with a dirty config."

I am using the same config file from the previous version of rsyslog. Is there something that I need to change in the config file to get it to work with 5.8.5? Below is the config we are using:

##
$ModLoad immark # provides --MARK-- message capability
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imklog # kernel logging (formerly provided by rklogd)

####
$ModLoad imfile # Input module for text files
#$ModLoad imrelp # Input RELP protocol
#$InputRELPServerRun 1514
$ModLoad omrelp

$WorkDirectory /opt/rsyslog/spool
$MarkMessagePeriod 600
$MaxMessageSize 64k
#$OptimizeForUniprocessor on
$RepeatedMsgReduction off

#$MainMsgQueueFileName mailQ_
#$MainMsgQueueSaveOnShutdown on
#$MainMsgQueueType LinkedList
#$MainMsgQueueWorkerThreads 8

$ActionWriteAllMarkMessages on
$ActionQueueFileName actionQ_
$ActionQueueSaveOnShutdown on
$ActionQueueType LinkedList
$ActionResumeRetryCount -1
#$ActionQueueWorkerThreads 8
#$ActionQueueDequeueBatchSize 32
#$ActionQueueHighWaterMark 12000

$AbortOnUncleanConfig on
#$template HostFile,"/opt/var/log/messages.%FROMHOST%.%%%%%%%%"
#$template TraditionalFormat,"%% %timegenerated:::date-rfc3164% %HOSTNAME% [%syslogfacility-text%.%syslogpriority-text%] %syslogtag%%msg%\n"

*.* :omrelp:mysyslogserver.myorg.com:601

Thanks for any insight.

Jeff
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads