[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [monit] noob question

From: peter
Subject: Re: [monit] noob question
Date: Thu, 29 Apr 2010 18:16:20 +0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100422 Shredder/3.0.5pre

Thank you very much for your help.

I will be working on this in detail on Saturday ..........  I have your very detailed responses (thank you) but I also feel that I have to read what you have presented together with the user manual since there is a lot of information there and if I work hard at this I will certainly learn something new in addition to solving a problem ........  :)

On 04/29/2010 05:16 PM, Eric Pailleau wrote:
<troll>If pppoe is well written</troll>, the fact that the pppd daemon exit should exit the pppoe clients as well.

Change your monit exec to '/usr/bin/killall -9 pppoe pppd' in such case, that will clean radically the mess.

I'm disappointed that you did not see that my 3rd solution can't work.
If pppd depends on internet, it will never start again, as far pppd create the internet connection !

Use 2nd way.

Sorry for the kinding...

peter a écrit :
yep ....   I have even read that already .......   what it does not tell you is about the connection that remains open in the background and the new connection that is started is then in addition.    The mess does not quite get cleaned up.  Sadly.  I have read quite a lot of the various pppoe documentation and the challenges that people face.

Monit ...  nope not read all of this by any means.  In general terms I do not understand what I have read which is why I posted to the list.  For me to learn it all would take many many months at the minimum ......

But thank you for posting back.

On 04/28/2010 10:50 PM, Eric Pailleau wrote:
pppoe is a client,
you can tell the client to exit when no traffic after a delay, that will clean the mess.

man pppoe,  see the option "-T timeout"

I really recommend you to read the manuals (monit and pppd/pppoe).

nothing can be well monitored if you don't know how it works...

Thank your for your suggestion.   I can see that this is saying if you cannot get through on port 80 then restart.   But ....   I have noticed that pppoe is not very elegant when a connection fails, the old connection stays in the background and a new connection is opened. It seems to get messy.

Is there any way to clean up before the restart?

I am also assuming that this is going to the right tool to open the connection in the first place ....  since the connection will be closed, it will no doubt be detected as failed and then started when the server is first started.  Or did I miss the point?

On 04/28/2010 10:29 PM, Philippe Muller wrote:
if failed host <> port 80 protocol http and request "/" for 2 cycles then restart


To unsubscribe:


To unsubscribe:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]