06-13-2012 02:32 PM - edited 03-16-2019 11:39 AM
Syslog has quit (last log on 6/11) on one of my subscribers. No logs in RTMT or in remote syslog server. Everything else seems to be working fine and 2nd subscriber and publisher both show logging correctly. Is there something to look at or service to restart or am I headed to TAC.
Version 8.6.2a
06-13-2012 02:46 PM
Just to add. Database replication shows good for both subscribers and publisher.
06-13-2012 04:48 PM
Sounds like the file system may have gone into read-only mode so the system cannot write logs. An easy way to check this is to look at the time the syslog stopped writing and check the last CCM trace file, if they both stopped at the same time chances are high you're in a read-only state. It would be best to open a case with us and we can take a look at your server to see if you're running into a known issue.
06-14-2012 06:09 AM
I just checked and trace files are showing current time and date.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide