Subject: Re: [monit] Service starting on boot - msg#00078

Previous Message by Date: click to view message preview

RE: [monit] Service starting on boot

Thanks, it looks like it's exiting becuase of the binddir. +++ AUTOSWAP=no ++ '[' pty = serial ']' ++ '[' color '!=' verbose ']' ++ INITLOG_ARGS=-q ++ __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d' + CONFIG='%{_sysconfdir}/monit.conf' + prog=monit + desc='process monitor' + '[' -x '%{_bindir}/monit' ']' + exit 1 --- David Campbell <dave@xxxxxxxx> wrote: > sh -x /etc/init.d/monit start > > Dave > > > -----Original Message----- > From: "John" <jharitos@xxxxxxxxx> > To: "This is the general mailing list for monit" > <monit-general@xxxxxxxxxx> > Sent: 16/11/07 17:43 > Subject: Re: [monit] Service starting on boot > > I have SELinux disabled. I disabled this when I did > the F8 install. > > I did some testing on the monit file in init.d > > CONFIG="%{_sysconfdir}/monit.conf" > prog="monit" > desc="process monitor" > > # Check if requirements are met > [ -x %{_bindir}/monit ] || exit 1 > [ -r "$CONFIG" ] || exit 1 > > I commented out these lines. > > [ -x %{_bindir}/monit ] || exit 1 > [ -r "$CONFIG" ] || exit 1 > > And it came back and said couldn't find > "%{_sysconfdir}/monit.conf" so I wonder if I have a > path problem. > > > > --- Pablo Iranzo Gómez <Pablo.Iranzo@xxxxxxxxxx> > wrote: > > > > > Have you checked any SELinux message at log > files? > > > > Regards > > Pablo > > > > > > -- > > Pablo Iranzo Gómez > > (http://Alufis35.uv.es/~iranzo/) > > (PGPKey Available on > > http://www.uv.es/~iranzop/PGPKey.pgp) > > -- > > Postulado de Boling sobre la Ley de Murphy: > > > > Si se encuentra bien, no se preocupe. Se le > pasará > > > > On Fri, 16 Nov 2007, John wrote: > > > > > I've never messed with the inittab file so I'm > not > > > sure what to look for. Here it is. I can start > and > > > stop other non-monit services though. > > > > > > # > > > # inittab This file describes how the INIT > > > process should set up > > > # the system in a certain > run-level. > > > # > > > # Author: Miquel van Smoorenburg, > > > <miquels@xxxxxxxxxxxxxxxxxxxxx> > > > # Modified for RHS Linux by Marc > > Ewing > > > and Donnie Barnes > > > # > > > > > > # Default runlevel. The runlevels used by RHS > are: > > > # 0 - halt (Do NOT set initdefault to this) > > > # 1 - Single user mode > > > # 2 - Multiuser, without NFS (The same as 3, > if > > you > > > do not have networking) > > > # 3 - Full multiuser mode > > > # 4 - unused > > > # 5 - X11 > > > # 6 - reboot (Do NOT set initdefault to this) > > > # > > > id:5:initdefault: > > > > > > # System initialization. > > > si::sysinit:/etc/rc.d/rc.sysinit > > > > > > l0:0:wait:/etc/rc.d/rc 0 > > > l1:1:wait:/etc/rc.d/rc 1 > > > l2:2:wait:/etc/rc.d/rc 2 > > > l3:3:wait:/etc/rc.d/rc 3 > > > l4:4:wait:/etc/rc.d/rc 4 > > > l5:5:wait:/etc/rc.d/rc 5 > > > l6:6:wait:/etc/rc.d/rc 6 > > > > > > # Trap CTRL-ALT-DELETE > > > ca::ctrlaltdel:/sbin/shutdown -t3 -r now > > > > > > # When our UPS tells us power has failed, assume > > we > > > have a few minutes > > > # of power left. Schedule a shutdown for 2 > > minutes > > > from now. > > > # This does, of course, assume you have powerd > > > installed and your > > > # UPS connected and working correctly. > > > pf::powerfail:/sbin/shutdown -f -h +2 "Power > > Failure; > > > System Shutting Down" > > > > > > # If power was restored before the shutdown > kicked > > in, > > > cancel it. > > > pr:12345:powerokwait:/sbin/shutdown -c "Power > > > Restored; Shutdown Cancelled" > > > > > > > > > # Run gettys in standard runlevels > > > 1:2345:respawn:/sbin/mingetty tty1 > > > 2:2345:respawn:/sbin/mingetty tty2 > > > 3:2345:respawn:/sbin/mingetty tty3 > > > 4:2345:respawn:/sbin/mingetty tty4 > > > 5:2345:respawn:/sbin/mingetty tty5 > > > 6:2345:respawn:/sbin/mingetty tty6 > > > > > > # Run xdm in runlevel 5 > > > x:5:respawn:/etc/X11/prefdm -nodaemon > > > > > > --- Nick Upson <nick.upson@xxxxxxxxx> wrote: > > > > > > > is the monit entry still in /etc/inittab or > did > > the > > > > F7 to F8 install wipe it? > > > > > > > > On 16/11/2007, John <jharitos@xxxxxxxxx> > wrote: > > > > > I'm using Fedora 8 x86_64 and I was using a > > Fedora > > > > 7 > > > > > i386 package of monit. A newer package came > > out > > > > and I > > > > > upgraded to the f8 x86_64 package. Now I > can't > > get > > > > the > > > > > system to start on boot nor does service > monit > > > > start > > > > > work. I can do a monit -vI and it works. I'd > > like > > > > to > > > > > be able to start monit on boot. When typing > > > > service > > > > > monit start it doesn't give me any errors > but > > just > > > > > dumps me back to the command prompt. > > > > > > > > > > Anyone know how to fix this? > > > > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > > > Be a better sports nut! Let your teams > follow > > you > > > > > with Yahoo Mobile. Try it now. > > > > > > > > > > http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ > > > > > > > > > > > > > > > -- > > > > > To unsubscribe: > > > > > > > > > > > > > > > http://lists.nongnu.org/mailman/listinfo/monit-general > > > > > > > > > > > > > > > > > -- > === message truncated === ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general

Next Message by Date: click to view message preview

Re: [monit] Re: started twice

Hmm, this is strange. Can you please post the full monit configuration, startup script for bs4 (/opt/unb/bin/bs.sh) and full monit verbose log from the start till the problem occurrence? Maybe there's some problem with how the the /opt/unb/bin/bs.sh creates the pidfile vs. how the bs4 service is started and monitored. Martin Nick Upson wrote: set daemon 120 in the file On 15/11/2007, Martin Pala <martinp@xxxxxxxxxxxxxx> wrote: How long is the testing cycle? (this is set using either "set daemon ..." option in monitrc or -d option on command line). It seems that it is most probably very short ... 1 second? Thanks, Martin Nick Upson wrote: I've attempted to remove entries that relate to other processes to keep the size down, please let me know if you need the full version. The process in question is called bs4, the config is check process bs4 with pidfile "/var/run/bs4.pid" start program = "/opt/unb/bin/bs.sh 4 restart" stop program = "/opt/unb/bin/bs.sh 4 stop" if totalmem > 1000 Mb then exec "/bin/bash -c '/bin/echo bs4: memory alert >> /tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'" if cpu usage > 95% for 3 cycles then exec "/bin/bash -c '/bin/echo bs4: cpu usage alert >> /tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'" group ntpd_dependant the original problem occurred before the last line was added [GMT Nov 13 13:42:57] debug : monit: pidfile '/var/run/monit.pid' does not exist [GMT Nov 13 13:42:57] info : Starting monit daemon with http interface at [*:2812] [GMT Nov 13 13:42:57] info : Starting monit HTTP server at [*:2812] [GMT Nov 13 13:42:57] info : monit HTTP server started [GMT Nov 13 13:42:57] info : Monit started [GMT Nov 13 13:43:55] info : monit daemon at 2040 awakened [GMT Nov 13 13:43:55] info : Awakened by User defined signal 1 [GMT Nov 13 13:43:55] info : Monit has not changed [GMT Nov 13 13:43:55] info : monit daemon at 2040 awakened [GMT Nov 13 13:43:55] info : start service 'bs4' on user request [GMT Nov 13 13:43:55] info : monit daemon at 2040 awakened [GMT Nov 13 13:43:55] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:55] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:55] info : 'bs4' start: /opt/unb/bin/bs.sh [GMT Nov 13 13:43:55] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:55] debug : Monitoring enabled -- service bs4 [GMT Nov 13 13:43:55] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:55] debug : 'bs4' check skipped -- service already handled in a dependency chain [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:56] error : 'bs4' process is not running [GMT Nov 13 13:43:56] info : 'bs4' trying to restart [GMT Nov 13 13:43:56] debug : Monitoring disabled -- service bs4 [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:56] info : 'bs4' start: /opt/unb/bin/bs.sh [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:56] debug : Monitoring enabled -- service bs4 [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:56] debug : monit: pidfile '/var/run/bs4.pid' does not exist [GMT Nov 13 13:43:57] debug : 'bs4' Error testing process id [2531] -- No such process [GMT Nov 13 13:43:58] info : 'bs4' process is running with pid 2641 [GMT Nov 13 13:43:58] debug : 'bs4' zombie check passed [status_flag=0000] [GMT Nov 13 13:43:58] debug : 'bs4' cpu usage check passed [current cpu usage=0.0%] [GMT Nov 13 13:43:58] debug : 'bs4' total mem amount check passed [current total mem amount=792kB] On 14/11/2007, Martin Pala <martinp@xxxxxxxxxxxxxx> wrote: You can use either the bug-tracing system: https://savannah.nongnu.org/bugs/?group=monit Or the mailing list. Thanks, Martin Nick Upson wrote: I now have a verbose log showing the problem, this is now using 4.10, where should I send it On 11/10/2007, Martin Pala <martinp@xxxxxxxxxxxxxx> wrote: Can you run monit in verbose mode (-v option) and provide logs? Which monit version is it? Thanks, Martin Nick Upson wrote: I have monitoring a process called bs1, yesterday I had a problem which I traced back to having 2 copies running at the same time (as it talks down a serial line that caused problems). The monit log shows it starting one copy at 16:58 and starting it again at 17:00. Normally monit looks after everything fine on this system which has been used for several weeks, the config entry is below check process bs1 with pidfile "/var/run/bs1.pid" start program = "/opt/unb/bin/bs.sh 1 restart" stop program = "/opt/unb/bin/bs.sh 1 stop" if totalmem > 1000 Mb then exec "/bin/bash -c '/bin/echo bs1: memory alert >> /tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'" if cpu usage > 95% for 3 cycles then exec "/bin/bash -c '/bin/echo bs1: cpu usage alert >> /tmp/monit;/opt/unb/bin/dblog_put.sh monit /tmp/monit'" -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general

Previous Message by Thread: click to view message preview

RE: [monit] Service starting on boot

Thanks, it looks like it's exiting becuase of the binddir. +++ AUTOSWAP=no ++ '[' pty = serial ']' ++ '[' color '!=' verbose ']' ++ INITLOG_ARGS=-q ++ __sed_discard_ignored_files='/\(~\|\.bak\|\.orig\|\.rpmnew\|\.rpmorig\|\.rpmsave\)$/d' + CONFIG='%{_sysconfdir}/monit.conf' + prog=monit + desc='process monitor' + '[' -x '%{_bindir}/monit' ']' + exit 1 --- David Campbell <dave@xxxxxxxx> wrote: > sh -x /etc/init.d/monit start > > Dave > > > -----Original Message----- > From: "John" <jharitos@xxxxxxxxx> > To: "This is the general mailing list for monit" > <monit-general@xxxxxxxxxx> > Sent: 16/11/07 17:43 > Subject: Re: [monit] Service starting on boot > > I have SELinux disabled. I disabled this when I did > the F8 install. > > I did some testing on the monit file in init.d > > CONFIG="%{_sysconfdir}/monit.conf" > prog="monit" > desc="process monitor" > > # Check if requirements are met > [ -x %{_bindir}/monit ] || exit 1 > [ -r "$CONFIG" ] || exit 1 > > I commented out these lines. > > [ -x %{_bindir}/monit ] || exit 1 > [ -r "$CONFIG" ] || exit 1 > > And it came back and said couldn't find > "%{_sysconfdir}/monit.conf" so I wonder if I have a > path problem. > > > > --- Pablo Iranzo Gómez <Pablo.Iranzo@xxxxxxxxxx> > wrote: > > > > > Have you checked any SELinux message at log > files? > > > > Regards > > Pablo > > > > > > -- > > Pablo Iranzo Gómez > > (http://Alufis35.uv.es/~iranzo/) > > (PGPKey Available on > > http://www.uv.es/~iranzop/PGPKey.pgp) > > -- > > Postulado de Boling sobre la Ley de Murphy: > > > > Si se encuentra bien, no se preocupe. Se le > pasará > > > > On Fri, 16 Nov 2007, John wrote: > > > > > I've never messed with the inittab file so I'm > not > > > sure what to look for. Here it is. I can start > and > > > stop other non-monit services though. > > > > > > # > > > # inittab This file describes how the INIT > > > process should set up > > > # the system in a certain > run-level. > > > # > > > # Author: Miquel van Smoorenburg, > > > <miquels@xxxxxxxxxxxxxxxxxxxxx> > > > # Modified for RHS Linux by Marc > > Ewing > > > and Donnie Barnes > > > # > > > > > > # Default runlevel. The runlevels used by RHS > are: > > > # 0 - halt (Do NOT set initdefault to this) > > > # 1 - Single user mode > > > # 2 - Multiuser, without NFS (The same as 3, > if > > you > > > do not have networking) > > > # 3 - Full multiuser mode > > > # 4 - unused > > > # 5 - X11 > > > # 6 - reboot (Do NOT set initdefault to this) > > > # > > > id:5:initdefault: > > > > > > # System initialization. > > > si::sysinit:/etc/rc.d/rc.sysinit > > > > > > l0:0:wait:/etc/rc.d/rc 0 > > > l1:1:wait:/etc/rc.d/rc 1 > > > l2:2:wait:/etc/rc.d/rc 2 > > > l3:3:wait:/etc/rc.d/rc 3 > > > l4:4:wait:/etc/rc.d/rc 4 > > > l5:5:wait:/etc/rc.d/rc 5 > > > l6:6:wait:/etc/rc.d/rc 6 > > > > > > # Trap CTRL-ALT-DELETE > > > ca::ctrlaltdel:/sbin/shutdown -t3 -r now > > > > > > # When our UPS tells us power has failed, assume > > we > > > have a few minutes > > > # of power left. Schedule a shutdown for 2 > > minutes > > > from now. > > > # This does, of course, assume you have powerd > > > installed and your > > > # UPS connected and working correctly. > > > pf::powerfail:/sbin/shutdown -f -h +2 "Power > > Failure; > > > System Shutting Down" > > > > > > # If power was restored before the shutdown > kicked > > in, > > > cancel it. > > > pr:12345:powerokwait:/sbin/shutdown -c "Power > > > Restored; Shutdown Cancelled" > > > > > > > > > # Run gettys in standard runlevels > > > 1:2345:respawn:/sbin/mingetty tty1 > > > 2:2345:respawn:/sbin/mingetty tty2 > > > 3:2345:respawn:/sbin/mingetty tty3 > > > 4:2345:respawn:/sbin/mingetty tty4 > > > 5:2345:respawn:/sbin/mingetty tty5 > > > 6:2345:respawn:/sbin/mingetty tty6 > > > > > > # Run xdm in runlevel 5 > > > x:5:respawn:/etc/X11/prefdm -nodaemon > > > > > > --- Nick Upson <nick.upson@xxxxxxxxx> wrote: > > > > > > > is the monit entry still in /etc/inittab or > did > > the > > > > F7 to F8 install wipe it? > > > > > > > > On 16/11/2007, John <jharitos@xxxxxxxxx> > wrote: > > > > > I'm using Fedora 8 x86_64 and I was using a > > Fedora > > > > 7 > > > > > i386 package of monit. A newer package came > > out > > > > and I > > > > > upgraded to the f8 x86_64 package. Now I > can't > > get > > > > the > > > > > system to start on boot nor does service > monit > > > > start > > > > > work. I can do a monit -vI and it works. I'd > > like > > > > to > > > > > be able to start monit on boot. When typing > > > > service > > > > > monit start it doesn't give me any errors > but > > just > > > > > dumps me back to the command prompt. > > > > > > > > > > Anyone know how to fix this? > > > > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > > > Be a better sports nut! Let your teams > follow > > you > > > > > with Yahoo Mobile. Try it now. > > > > > > > > > > http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ > > > > > > > > > > > > > > > -- > > > > > To unsubscribe: > > > > > > > > > > > > > > > http://lists.nongnu.org/mailman/listinfo/monit-general > > > > > > > > > > > > > > > > > -- > === message truncated === ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general

Next Message by Thread: click to view message preview

[monit] restart service if swap or real ram is below a thresgold

Can anyone show me how they restart a service if the overall system memory or swap falls below a threshold? Thanks Dave -- To unsubscribe: http://lists.nongnu.org/mailman/listinfo/monit-general