ClearFoundation Tracker - ClearOS
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006571ClearOSapp-base - Base Systempublic2015-12-02 09:292016-01-28 09:08
Reporterbchambers 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.1.0 
Target Version7.2.0Fixed in Version7.2.0 
Summary0006571: servicewatch script doesn't catch all services that may not be running
DescriptionIt didn't catch this case:

Nov 22 19:36:08 chambers systemd: Reloading.
Nov 22 19:36:08 chambers systemd: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Nov 22 19:36:08 chambers systemd: [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Nov 22 19:36:08 chambers yum[10809]: Installed: clamav-server-0.98.7-3.v7.3.x86_64
Nov 22 19:36:09 chambers systemd: Reloading.
Nov 22 19:36:09 chambers systemd: [/usr/lib/systemd/system/dm-event.socket:10] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Nov 22 19:36:09 chambers systemd: [/usr/lib/systemd/system/lvm2-lvmetad.socket:9] Unknown lvalue 'RemoveOnStop' in section 'Socket'
Nov 22 19:36:09 chambers systemd: Starting ClamAV daemon...
Nov 22 19:36:09 chambers clamd: LibClamAV Warning: **************************************************
Nov 22 19:36:09 chambers clamd: LibClamAV Warning: *** The virus database is older than 7 days! ***
Nov 22 19:36:09 chambers clamd: LibClamAV Warning: *** Please update it as soon as possible. ***
Nov 22 19:36:09 chambers clamd: LibClamAV Warning: **************************************************
Nov 22 19:36:10 chambers systemd: syswatch.service: main process exited, code=killed, status=61/RTMIN+27
Nov 22 19:36:10 chambers syswatch: /etc/rc.d/init.d/syswatch: line 18: [: =: unary operator expected
Nov 22 19:36:10 chambers syswatch: Stopping syswatch: [FAILED]
Nov 22 19:36:10 chambers systemd: Unit syswatch.service entered failed state.
Nov 22 19:36:23 chambers systemd: Started ClamAV daemon.

Maybe we can reproduce it by installing clam-av-server???
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-12-02 09:29bchambersNew Issue
2015-12-02 10:40user2Assigned To => user2
2015-12-02 10:40user2Statusnew => confirmed
2015-12-02 10:49user2Note Added: 0002311
2015-12-02 10:52user2Note Added: 0002321
2015-12-02 11:02user2Target Version => 7.2.0 Beta 1
2016-01-01 12:44user2Statusconfirmed => resolved
2016-01-01 12:44user2Fixed in Version => 7.2.0 Beta 1
2016-01-01 12:44user2Resolutionopen => fixed
2016-01-01 12:56user2Fixed in Version7.2.0 Beta 1 => 7.2.0
2016-01-01 12:59user2Target Version7.2.0 Beta 1 => 7.2.0
2016-01-28 09:08user2Statusresolved => closed

Notes
(0002311)
user2   
2015-12-02 10:49   
It looks like the SysV library no longer drops a /var/lock/subsys file on start up. This is how the servicewatch daemon knows that the daemon crashed, i.e.:

- init script starts daemon
- init script creates /var/lock/subsys/XYZ to indicate daemon was started successfully

If the daemon gets killed abruptly or crashes, the /var/lock/subsys/XYZ file will still exist. If the daemon is stopped normally, the /var/lock/subsys/XYZ file is cleanly removed.
(0002321)
user2   
2015-12-02 10:52   
Why syswatch was killed is still a bit of an unsolved mystery. ClamAV doesn't interact with syswatch in any direct way. However, ClamAV is certainly one of the big memory hogs, so perhaps it's related to memory usage? We should keep an eye out for this one.