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.
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.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...