Debugging monit

后端 未结 7 2014
迷失自我
迷失自我 2020-12-07 09:04

I find debugging monit to be a major pain. Monit\'s shell environment basically has nothing in it (no paths or other environment variables). Also, there are no log file that

7条回答
  •  囚心锁ツ
    2020-12-07 09:44

    You can start Monit in verbose/debug mode by adding MONIT_OPTS="-v" to /etc/default/monit (don't forget to restart; /etc/init.d/monit restart).

    You can then capture the output using tail -f /var/log/monit.log

    [CEST Jun  4 21:10:42] info     : Starting Monit 5.17.1 daemon with http interface at [*]:2812
    [CEST Jun  4 21:10:42] info     : Starting Monit HTTP server at [*]:2812
    [CEST Jun  4 21:10:42] info     : Monit HTTP server started
    [CEST Jun  4 21:10:42] info     : 'ocean' Monit 5.17.1 started
    [CEST Jun  4 21:10:42] debug    : Sending Monit instance changed notification to monit@example.io
    [CEST Jun  4 21:10:42] debug    : Trying to send mail via smtp.sendgrid.net:587
    [CEST Jun  4 21:10:43] debug    : Processing postponed events queue
    [CEST Jun  4 21:10:43] debug    : 'rootfs' succeeded getting filesystem statistics for '/'
    [CEST Jun  4 21:10:43] debug    : 'rootfs' filesytem flags has not changed
    [CEST Jun  4 21:10:43] debug    : 'rootfs' inode usage test succeeded [current inode usage=8.5%]
    [CEST Jun  4 21:10:43] debug    : 'rootfs' space usage test succeeded [current space usage=59.6%]
    [CEST Jun  4 21:10:43] debug    : 'ws.example.com' succeeded testing protocol [WEBSOCKET] at [ws.example.com]:80/faye [TCP/IP] [response time 114.070 ms]
    [CEST Jun  4 21:10:43] debug    : 'ws.example.com' connection succeeded to [ws.example.com]:80/faye [TCP/IP]
    

提交回复
热议问题