Remote syslog broken after update/reboot? - Changing it away, then back fixes.
-
Hi,
We use the 'Remote syslog' option with XCP-ng 8.2.1. This has been working well - but recently we patched the pool, rebooted the pool (everything came back ok) - but Remote syslog - doesn't log any more.
If I go into XO and look at the option for the Hosts - on both it's set to the correct IP address.
If I try changing that IP to a different host on the network XO quite correctly said something like "can't use that expect port to be open".
If I change it back to the original host, I've just noticed - it starts working again.
This is a bit annoying (as we've lost days of logs) - anyone else seen similar with that option?
[Before figuring that changing it 'fixes' it - I'd already tested the syslog server was up, and I could send test log entries to it using 'logger' from the XCP-ng's dom0].
Thanks!
-
@Tackyone
You solution fixed it for me. Lost a few days of logs as well and i am on the latest commit of the XO community edition.Theres some bug with syslog clear but your fix works great.