![]() ![]() ![]() # local messages are retrieved through imjournal now. # Turn off message reception via local log socket # Include all config files in /etc/rsyslog.d/ # not useful and an extreme performance hit # File syncing capability is disabled by default. $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat #$ModLoad immark # provides -MARK- message capability #$ModLoad imklog # reads kernel messages (the same are read from journald) $ModLoad imjournal # provides access to the systemd journal $ModLoad imuxsock # provides support for local system logging (e.g. # The imjournal module bellow is now used as a message source instead of imuxsock. # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html I am at a total loss here for ideas, I can providemore information if needed, but, please remember I am no more that an advanced novice with Linux. I know the syslogs are being sent to the server, I can see them while doing a tcpdump for the proper port. Out of total frustration, I uninstalled rsysyslog, and installed syslog-ng since the configuration seemed easier, still nothing. When that did not work, I uninstalled rsyslog, booted, reinstalled and reconfigured, still nothing. Opens a new window for the setup options. In researching, I found that some configurations changed between versions, so I made those changes, still not functioning, I followed the instructions here: The best I can make out is that rsyslog was updated from a prior version 7, to a newer version 8.024? I believe. I am a Linux, novice, but do have a general understanding of it.Īnyway I updated Observium and all dependencies last Friday, now syslog is no longer functioning. I have an instance of Observium up and running, or at least it has been for the past 18-24 Months. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |