Caveat: I've recently inherited a bunch of ubuntu systems with very little
historical knowledge available to me. The issue described below has occurred
only since the inline ubuntu upgrade was done. However, Ive no vision of
whether this is solely an issue with ubuntu implementation of rsyslog,
>>Rsyslog tries very hard to not break backwards compatibility, so you should
>>not have needed to change the config. There have been bugs over the years,
>>but in >>general, a config should just keep working.
That of course makes perfect sense. Though as it turned it - come the upgrade
18-> 2
>> Is there any chance that they are getting logged under a different hostname?
I've done an extensive search in the rsyslog server this morning, and the
answer is sadly no.
Confidentiality notice: This email (and any attachment) is intended for the
addressee(s) named above. It may contain in
>> specifically look for 127.0.0.1 or localhost
see previous message . Nothing.
OK, Ive just set this up
local4.* /tmp/Tlocal.log
I created that log and chmod 777 for it to remove any silly potential issues
and restarted rsyslog on the central server
No change. Client logs have new entrie
atefile.directory = "/var/log/node"
or
>> file = "/var/log/node/Tlog.log"
Cheers
ian
On 2024-04-22 10:42, Ian Diddams via rsyslog wrote :
>>> specifically look for 127.0.0.1 or localhost
> see previous message . Nothing.
>
>
> OK, Ive just set t
delete the log file, then delete the state file, then restart rsyslog.
Regards,
> On Apr 22, 2024, at 16:22, Ian Diddams via rsyslog
> wrote:
>
>> Having experienced something similar a few years ago (imfile not seeing new
>> messages added to a certain log file), I
6 matches
Mail list logo
