AssertException: path at src/socket.c:370
/usr1/app/monit/current/bin/monit -V This is Monit version 5.12.1 Copyright (C) 2001-2015 Tildeslash Ltd. All Rights Reserved.
/usr1/app/monit/current/bin/monit status AssertException: path at src/socket.c:370 aborting.. Aborted (core dumped)
/usr1/app/monit/current/bin/monit -v Runtime constants: Control file = /etc/monitrc Log file = /var/log/monit.log Pid file = /var/run/monit.pid Id file = /var/.monit.id State file = /var/.monit.state Debug = True Log = True Use syslog = False Is Daemon = True Use process engine = True Poll time = 30 seconds with start delay 0 seconds Expect buffer = 256 bytes Event queue = base directory /var/monit with 100 slots Mail from = (not defined) Mail subject = (not defined) Mail message = (not defined) Start monit httpd = False
The service list contains the following entries:
Program Name = port7999 Path = /usr1/app/scripts/monit_scripts/port7999.sh Monitoring mode = active Program timeout = terminate the program if not finished within 300 seconds Status = if exit value > 40 for 3 times within 5 cycles then exec '/usr1/app/scripts/monit_scripts/alert40.sh' Status = if exit value > 30 for 3 times within 5 cycles then exec '/usr1/app/scripts/monit_scripts/alert30.sh' Timeout = If restarted 5 times within 25 cycle(s) then unmonitor
System Name = somehost.localhost.com Monitoring mode = active
Monit daemon with PID 21238 awakened
I thought maybe the binary download was a little out of date so I cloned the git repo today and still get the same error.
Comments (4)
-
-
I just resolved my own problem, in the monitrc I had commented out the http stuff since I had no intention of accessing it myself. I didn't realize certain monit cli commands communicate this way. Once I uncommented out the following and -HUP'd monit it worked
set httpd port 2812 and use address localhost # only accept connection from localhost allow localhost # allow localhost to connect to the server and allow admin:monit # require user 'admin' with password 'monit'
-
repo owner - changed status to resolved
Fixed Issue
#170If monit was started with no http interface, the CLI commands crashed.→ <<cset 9c113ec1ba6a>>
-
repo owner Hello, thank you for report.
Yes, the CLI commands like status, summary, start/stop/restart/monitor/unmonitor require the http interface support so the CLI can communicate with the monit daemon.
If no http interface is enabled, the CLI would log error anyway, as it has no access to the daemon in such case, but it shouldn't crash.
Fixed in the development version
- Log in to comment
Same issue with version 5.12.2
./monit -V This is Monit version 5.12.2 Copyright (C) 2001-2015 Tildeslash Ltd. All Rights Reserved.
./monit status AssertException: path at src/socket.c:370 aborting.. Aborted (core dumped)