| Anonymous | Login | 2024-04-19 12:58 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0006571 | ClearOS | app-base - Base System | public | 2015-12-02 09:29 | 2016-01-28 09:08 | ||||
| Reporter | bchambers | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | minor | Reproducibility | sometimes | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.1.0 | ||||||||
| Target Version | 7.2.0 | Fixed in Version | 7.2.0 | ||||||
| Summary | 0006571: servicewatch script doesn't catch all services that may not be running | ||||||||
| Description | It 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??? | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-12-02 09:29 | bchambers | New Issue | |
| 2015-12-02 10:40 | user2 | Assigned To | => user2 |
| 2015-12-02 10:40 | user2 | Status | new => confirmed |
| 2015-12-02 10:49 | user2 | Note Added: 0002311 | |
| 2015-12-02 10:52 | user2 | Note Added: 0002321 | |
| 2015-12-02 11:02 | user2 | Target Version | => 7.2.0 Beta 1 |
| 2016-01-01 12:44 | user2 | Status | confirmed => resolved |
| 2016-01-01 12:44 | user2 | Fixed in Version | => 7.2.0 Beta 1 |
| 2016-01-01 12:44 | user2 | Resolution | open => fixed |
| 2016-01-01 12:56 | user2 | Fixed in Version | 7.2.0 Beta 1 => 7.2.0 |
| 2016-01-01 12:59 | user2 | Target Version | 7.2.0 Beta 1 => 7.2.0 |
| 2016-01-28 09:08 | user2 | Status | resolved => closed |
|
Issue History |