Re: Obscure rsyslog question on remote logging

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have seen syslog messages over 4096 chars have the first part go to the right file and the overflow go to the default.  Is smart sending a large message?  The other file would have a long smart message at the same time and this would be overflow.

On Thu, Nov 16, 2023, 6:51 PM Tom Horsley <horsley1953@xxxxxxxxx> wrote:
I've got an old PC running Truenas as a local server for backups,
videos, etc.

I've got another PC I consider my "main" system running rsyslog.
On this PC I have tried (mostly successfully) to direct remote
syslog messages from the Truenas system to logfiles in a subdirectory
on my main system. This gibberish in my main system's rsyslog.conf
seems to do the trick:

# Log incoming message from remote systems here
$template DynamicFile,"/var/log/loghost/%HOSTNAME%/%syslogfacility-text%.log"
:hostname, contains, "nast"
*.*    -?DynamicFile

Most remote log message do indeed get redirected to the subdirectory
as expected, but SMART messages like these still wind up in
/var/log/messages on my main system rather than in the subdirectory.

Example:

Nov 16 16:16:51 nast 1 2023-11-16T16:16:51.564170-05:00 nast.my.lan smartd 1501 - - Device: /dev/ada0, SMART Usage Attribute: 194 Temperature_Celsius changed from 58 to 57

Most other messages wind up down in the subdirectory as expected, like this:

Nov 16 19:15:00 nast 1 2023-11-16T19:15:00.012359-05:00 nast.my.lan /usr/sbin/cron 16239 - - (root) CMD (/usr/libexec/atrun)

Anyone understand remote logging enough to provide any hints why this
is happening? It is clearly not all that critical, but it confuses me.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux