SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0004165: amavsid is not running after gui changes - MantisBT Endian Bugtracker
Endian Issue Tracker





Please see now our new Bugtracker system: JIRA








View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004165Endian FirewallProxy SMTPpublic2011-09-23 15:572011-09-23 16:18
Reporterluca-endian 
Assigned To 
PrioritynormalSeveritymajorReproducibilitysometimes
StatusfeedbackResolutionopen 
PlatformOSOS Version
Product Version2.4.1 
Target VersionFixed in Version 
Summary0004165: amavsid is not running after gui changes
DescriptionAfter a change on webgui smtp proxy amavis doesn't start..

no process:
ps -e | grep amavis

no socket:
netstat -ntpl | grep amavis

monit summary | grep amavis
Process 'amavisd' not monitored

If you run resrtarsmtpscan.py -fd it start back working..

Then everything goes back working..
I think there is something wrong on monit because after restarting amaivis is monitored..
Additional InformationThis is the log when you save gui settings:

Sep 23 17:40:16 xxx sudo: nobody : TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/restartsmtpscan.py --force
Sep 23 17:41:55 xxx saslauthd[4368]: server_exit : master exited: 4368
Sep 23 17:41:56 xxx saslauthd[14061]: detach_tty : master pid is: 14061
Sep 23 17:41:56 xxx saslauthd[14061]: ipc_init : listening on socket: /var/spool/postfix/var/run/saslauthd/mux

This is the mail log when amavis is not running (of course it gets connection refused..)
Sep 16 00:59:15 postfix/smtp[2727]: connect to 127.0.0.1[127.0.0.1]:
Connection refused (port 10024)
Sep 16 00:59:15 postfix/smtp[2726]: 9AE252FE86: to=, relay=none, delay=23653,
delays=23653/0.22/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1
[127.0.0.1]: Connection refused)
Sep 16 00:59:15 postfix/smtp[2727]: CA3232FE82: to=, relay=none,
delay=425514, delays=425513/0.21/0.01/0, dsn=4.4.1, status=deferred (connect to
127.0.0.1[127.0.0.1]: Connection refused)


monit log:

Sep 23 17:40:20 xxx monit[3566]: unmonitor service 'pyzord' on user request
Sep 23 17:40:20 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:40:20 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:40:23 xxx monit[3566]: monitor service 'pyzord' on user request
Sep 23 17:40:23 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:40:23 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:40:24 xxx monit[3566]: unmonitor service 'clamd' on user request
Sep 23 17:40:24 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:40:25 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:41:32 xxx monit[3566]: monitor service 'clamd' on user request
Sep 23 17:41:32 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:41:33 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:41:43 xxx monit[3566]: unmonitor service 'amavisd' on user request
Sep 23 17:41:43 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:41:43 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:41:51 xxx monit[3566]: unmonitor service 'postfix' on user request
Sep 23 17:41:51 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:41:51 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:41:52 xxx monit[3566]: unmonitor service 'mailgraph' on user request
Sep 23 17:41:52 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:41:53 xxx monit[3566]: unmonitor service 'mailgraph' on user request
Sep 23 17:41:53 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:41:53 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:42:02 xxx monit[3566]: monitor service 'postfix' on user request
Sep 23 17:42:02 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:42:02 xxx monit[3566]: monit daemon at 3566 awakened
Sep 23 17:42:05 xxx monit[3566]: monitor service 'mailgraph' on user request
Sep 23 17:42:05 xxx monit[3566]: Awakened by User defined signal 1
Sep 23 17:42:05 xxx monit[3566]: monit daemon at 3566 awakened
Tagssupport
Attached Files

- Relationships

-  Notes
(0007438)
luca-endian (developer)
2011-09-23 16:18

** POSSIBLE FIX **

this is the amavis configuration for monit which actually doesn't really make sense:

root@kenny:/etc/monit.d # cat amavisd.conf
 check process amavisd with pidfile /var/run/amavisd/amavisd.pid
   group mail
   start program = "/etc/init.d/amavisd start"
   stop program = "/etc/init.d/amavisd stop"
   every 2 cycles
   if 5 restarts within 5 cycles then timeout
   mode manual


Every 2 cycles do what?!? just remove that line and it starts working!
On a system worked, please drop feedbacks!

- Issue History
Date Modified Username Field Change
2011-09-23 15:57 luca-endian New Issue
2011-09-23 15:57 luca-endian Tag Attached: support
2011-09-23 16:18 luca-endian Note Added: 0007438
2011-09-23 16:18 luca-endian Status new => feedback

Copyright © 2005-2008 Endian, SRL. All rights reserved.


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker