Bug#742381: Remove warning message in monit init script in Debian Wheezy

2014-03-22 Thread Volker Theile

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: monit
Version: 1:5.4-2

When using /etc/monit/monit_delay file in Debian Wheezy no warning
should be displayed. Using the suggested start delay in the config file
results in a different behaviour of monit than using the monit_delay file.

When using start delay in config file monit can not
start/stop/restart/... services during this start delay (see
https://lists.gnu.org/archive/html/monit-general/2010-03/msg2.html).
But some systems need to use monit right after it has been restarted to
handle the services.
Assume the following workflow when delay is done via config file:

1. Modify monit configuration
2. Restart monit via 'service monit restart'
3. Restart a monitored service via 'monit restart xyz' = The error
'Cannot connect to the monit daemon Did you start it with http support?'
appears.

To prevent this error you have to use the monit_delay file to start
monitoring services after a given delay AND the ability to manipulate
services via monit CLI right after it has been restarted. But in this
case the current init script will throw an notification message which
should be removed because the suggested replacement will result in a
different and sometimes unwanted behaviour of monit.

- --- /etc/init.d/monit.orig  2014-03-22 23:45:09.37042 +0100
+++ /etc/init.d/monit   2014-03-22 23:45:30.598810357 +0100
@@ -92,9 +92,6 @@
 monit_delayed_monitoring () {
   if [ -f $DELAY ]
   then
- -printf Warning: Please, set start delay for $NAME in config file\n
- -printf  and delete $DELAY file.\n
- -
 if [ ! -x $DELAY ]
 then
   printf Warning: A delayed start file exists ($DELAY)\n

Regards
Volker
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTLhfLAAoJEAHVpGGDJluMbB8QALNrTPei2czgrrpnd60+LTUA
4OK7axPi4zGvJ1sK2Uwi9rlKtK8oX3TEHFtUlCUkY3jkTCgGMbFrN4BjN4bF5jcQ
q7Y0HzRdkx4cBKpF2stP5ZDWPigQK/V/lnNDLJnGCrukOWe9xEqZ400ZTDM4bPtm
1zIp2nwnt6WtoTKYC6LpstWeImLckCk7F2aJPYG2NkjNQW6zjD6nppUY+kXJtiRT
O/jOZeQLbpN18Qk8ZvbFfMVICW4VObeSiUr2+9OD5gMXd36+GKglPKqCmw0ipeBI
blpcjH0K1OUK/ZYmUNlQ9K7v/rawqjZ+q+fziXEvwbWr1tlwKVzYLrzfQ+6QKLC1
hxCS4HQUz63QpLcxkQjO8ljn0U6VGM+SQjLvFy30x3D+eg/ZguVqRjwgJ7GtdqY4
mes2+wNNnjfCTSBlnjVIoUzeaks3vk+f/nwjYWKO/Fmnm/ro+L2zk4WiqUiz1SW4
gvo0N0DaI4F6LBVPfMXgPhOyyknlaxSCmxplbXJ5BnfRIfddMitCtwcnKqK8SH8Q
Tl1FVdxmM91f1pvljFisy8wziwvdBm/TWUUz2gYykCGgd++gHPXZQ3lnjmxHTUEy
X70V8j6Y0QRRYCTycx3yiqs8KzlE/ituuR2zgh80JYJtm1vCDABSxHUAeMYs0YQn
L0DHeqv2GoWvmCVoYvCy
=CBHO
-END PGP SIGNATURE-



Bug#742381: Remove warning message in monit init script in Debian Wheezy

2014-03-22 Thread Sergey B Kirpichev
Hello,

On Sun, Mar 23, 2014 at 12:07:57AM +0100, Volker Theile wrote:
When using /etc/monit/monit_delay file in Debian Wheezy no warning should
be displayed.

It's displayed, because monit_delay was deprecated and will be removed in 
wheezy+.

Using the suggested start delay in the config file results
in a different behaviour of monit than using the monit_delay file.

Yes, that's slightly different things.

When using start delay in config file monit can not start/stop/restart/...
services during this start delay (see
[1]https://lists.gnu.org/archive/html/monit-general/2010-03/msg2.html).

Do you think that monit CLI would work with /etc/monit/monit_delay?!

But some systems need to use monit right after it has been restarted to
handle the services.

Lets examine the reasons for this below...

Assume the following workflow when delay is done via config file:
 
1. Modify monit configuration
2. Restart monit via 'service monit restart'

Why you are doing this?  Why you can't just do monit reload,
instead of restart?

To prevent this error you have to use the monit_delay file to start
monitoring services

I'm sorry, but my point of view: to prevent this error you should read
the monit's manpage.  That's all.

Feel free to reopen this bugreport (with wishlist severity), but please
prepare a better argumentation.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org