monit crash

2016-10-16 Thread Thomas Lau
Hi all, we got a crash on monit main process, here is the crash report: ProblemType: Crash Architecture: amd64 Date: Tue Oct 11 13:59:46 2016 DistroRelease: Ubuntu 14.04 ExecutablePath: /usr/bin/monit ExecutableTimestamp: 1384665445 ProcCmdline: /usr/bin/monit -c /etc/monit/monitrc ProcCwd: / Pro

Re: monit crash

2016-10-16 Thread Thomas Lau
mind to explain what's going on? On Mon, Oct 17, 2016 at 2:49 PM, Martin Pala wrote: > Thanks for data. This problem was fixed in monit 5.7, please upgrade monit. > > Best regards, > Martin > > > On 17 Oct 2016, at 08:45, Thomas Lau wrote: > > monit -V > Th

Re: monit crash

2016-10-16 Thread Thomas Lau
I see, okay thanks, I will upgrade and test again. On Mon, Oct 17, 2016 at 2:57 PM, Martin Pala wrote: > It is related to the IOException from your log - it was not catched. > > > On 17 Oct 2016, at 08:51, Thomas Lau wrote: > > mind to explain what's going on? > >

scheduler on Monit

2016-10-30 Thread Thomas Lau
Hi All, I read some documents and found this: The current scheduler is poll cycle based. If a service check is scheduled with the every cron statement, Monit will check if the current time match the cron-string pattern. If it does, then the check is performed otherwise it is skipped. The cron spe

Re: scheduler on Monit

2016-10-31 Thread Thomas Lau
m/monit/documentation/monit. > html#DAEMON-MODE > > Best regards, > Martin > > > On 31 Oct 2016, at 03:48, Thomas Lau wrote: > > Hi All, > > I read some documents and found this: > > The current scheduler is poll cycle based. If a service check is scheduled > with

Re: scheduler on Monit

2016-10-31 Thread Thomas Lau
you want to reduce > overhead, you can poll for example each 30 seconds: "set daemon 30" (or > more) > > > > On 31 Oct 2016, at 08:07, Thomas Lau wrote: > > Thanks, may I know what's the default setting and suggested setting for > scheduler job on Monit? >

missing or invalid Authorization header

2017-07-17 Thread Thomas Lau
error: HttpRequest: access denied -- client 127.0.0.1: missing or invalid Authorization header I keep seeing this on my log, anyone have idea why? -- Thomas Lau Director of Infrastructure Tetrion Capital Limited Direct: +852-3976-8903 Mobile: +852-9323-9670 Address: Suite 2716, Two IFC