ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0014851ClearOSapp-base - Base Systempublic2017-05-08 18:502017-05-08 18:50
Reporterbchambers 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version7.3.0 
Target VersionFixed in Version 
Summary0014851: Servicewatch polluting logs
Descriptionapp-base's servicewatch scripts pollutes log files with entries like, but only when run from cron...when running the script as root, log file does not get polluted. Wha? I've hacked my server up a lot...is this something I've done??

May 8 20:45:02 chambers systemctl[20811]: Failed to get unit file state for vpnwatchd.service: No such file or directory
May 8 20:45:02 chambers systemctl[20826]: syswatch.service is not a native service, redirecting to /sbin/chkconfig.
May 8 20:45:02 chambers systemctl[20826]: Executing /sbin/chkconfig syswatch --level=5
May 8 20:45:02 chambers systemctl[20848]: snortsam.service is not a native service, redirecting to /sbin/chkconfig.
May 8 20:45:02 chambers systemctl[20848]: Executing /sbin/chkconfig snortsam --level=5
May 8 20:45:02 chambers systemctl[20866]: snort.service is not a native service, redirecting to /sbin/chkconfig.
May 8 20:45:02 chambers systemctl[20866]: Executing /sbin/chkconfig snort --level=5
May 8 20:45:02 chambers systemctl[20884]: Failed to get unit file state for eziod.service: No such file or directory
May 8 20:45:02 chambers systemctl[20910]: Failed to get unit file state for zarafa-dagent.service: No such file or directory
May 8 20:45:02 chambers systemctl[20924]: Failed to get unit file state for zarafa-gateway.service: No such file or directory
May 8 20:45:02 chambers systemctl[20933]: Failed to get unit file state for zarafa-ical.service: No such file or directory
May 8 20:45:02 chambers systemctl[20949]: Failed to get unit file state for zarafa-licensed.service: No such file or directory
May 8 20:45:02 chambers systemctl[20961]: Failed to get unit file state for zarafa-monitor.service: No such file or directory
May 8 20:45:02 chambers systemctl[20975]: Failed to get unit file state for zarafa-presence.service: No such file or directory
May 8 20:45:02 chambers systemctl[20989]: Failed to get unit file state for zarafa-server.service: No such file or directory
May 8 20:45:02 chambers systemctl[21004]: Failed to get unit file state for zarafa-spooler.service: No such file or directory


TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-05-08 18:50 bchambers New Issue