Information: Forum is in read-only mode
For details and other support options see https://www.adiscon.com/news/support-forum-set-to-read-only-mode/

Rsyslog as a service causing omfile issues

General discussions here

Moderator: alorbach

Google Ads


Rsyslog as a service causing omfile issues

Postby packland » Tue Nov 07, 2017 5:37 am

Hi all,

I'm running the rsyslog 8.24.0 daemon because when running as a service it will accept a couple of logs from the hosts I have configured to send logs to it and then break, writing the same message to /var/log/messages indefinitely:

rsyslogd: action 'write_to_remote.log' resumed (module 'builtin:omfile') [v8.24.0 try http://www.rsyslog.com/e/2359]

and occasionally:

rsyslogd: action 'write_to_remote.log' suspended, next retry is Sun Nov 5 03:15:54 2017 [v8.24.0 try http://www.rsyslog.com/e/2007 ]

here is my config:

Code: Select all
#### MODULES ####

# The imjournal module bellow is now used as a message source instead of imuxsock.
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal

# Include all config files in /etc/rsyslog.d/
$IncludeConfig /etc/rsyslog.d/*.conf


#### GLOBAL DIRECTIVES ####
$WorkDirectory /var/lib/rsyslog

$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat


# Turn off message reception via local log socket;
# local messages are retrieved through imjournal now.
$OmitLocalLogging off

# File to store the position in the journal
$IMJournalStateFile imjournal.state


#### RULES ####

# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.*                                                 /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none                /var/log/messages

# The authpriv file has restricted access.
authpriv.*                                              /var/log/secure

# Log all the mail messages in one place.
mail.*                                                  -/var/log/maillog

# Log cron stuff
cron.*                                                  /var/log/cron

# Everybody gets emergency messages
*.emerg                                                 :omusrmsg:*

# Save news errors of level crit and higher in a special file.
uucp,news.crit                                          /var/log/spooler

# Save boot messages also to boot.log
local7.*                                                /var/log/boot.log



and here's the config containing the offending action:

Code: Select all
ruleset(name="remote") {
        if $msg contains 'xxxxx' then {
                action(name="write_to_xxxxx.log" type="omfile" file="/path/xxxxx.log")
                stop
        }

        action(name="write_to_remote.log" type="omfile" file="/path/remote.log")
}

module(load="imudp")
input(type="imudp" port="xxxxx" ruleset="remote")


Any ideas?
packland
New
 
Posts: 1
Joined: Tue Nov 07, 2017 5:11 am

Urgent Question?

  • Pulling out your Hair?
  • Wasting Time and Money?
  • Deadline Approaching?

Google Ads


Return to General

Who is online

Users browsing this forum: No registered users and 0 guests

cron