- changed status to resolved
Clamd not running
Issue #760
resolved
My install has a “unhealthy” status.
underneath the output of docker inspect
{"Status":"unhealthy","FailingStreak":1542,"Log":[{"Start":"2020-05-28T23:02:42.925864726+02:00","End":"2020-05-28T23:02:43.000252312+02:00","ExitCode":1,"Output":"pgrep: cannot allocate 4611686018427387903 bytes\nClamd not running\n"},{"Start":"2020-05-28T23:03:43.094862676+02:00","End":"2020-05-28T23:03:43.182570117+02:00","ExitCode":1,"Output":"pgrep: cannot allocate 4611686018427387903 bytes\nClamd not running\n"},{"Start":"2020-05-28T23:04:43.300536118+02:00","End":"2020-05-28T23:04:43.395944565+02:00","ExitCode":1,"Output":"pgrep: cannot allocate 4611686018427387903 bytes\nClamd not running\n"},{"Start":"2020-05-28T23:05:43.549088937+02:00","End":"2020-05-28T23:05:43.663986457+02:00","ExitCode":1,"Output":"pgrep: cannot allocate 4611686018427387903 bytes\nClamd not running\n"},{"Start":"2020-05-28T23:06:43.796570558+02:00","End":"2020-05-28T23:06:43.88131696+02:00","ExitCode":1,"Output":"pgrep: cannot allocate 4611686018427387903 bytes\nClamd not running\n"}]}
anybody an idea how to fix this?
Comments (1)
-
repo owner - Log in to comment
fix
#760replace pgrep with more basic ps | grep, due bug in procps-ng→ <<cset b7ae4bb98d05>>