[Bug 473553] New: amavis does not restart
https://bugzilla.novell.com/show_bug.cgi?id=473553 Summary: amavis does not restart Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: f.de.kruijf@hetnet.nl QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux; nl, en_US) KHTML/3.5.10 (like Gecko) SUSE Somehow amavis did crash. After that a "rcamavis restart" could not restart the amivis process. In /var/log/mail.warn I found the following messages: Jan 29 23:18:57 eik110 amavis[2496]: (!)Net::Server: 2009/01/29-23:18:57 Pid_file already exists for running process (2520)... aborting\n\n at line 277 in file /usr/lib/perl5/vendor_perl/5.10.0/Net/Server.pm Feb 5 22:58:11 eik110 amavis[3110]: (!)Net::Server: 2009/02/05-22:58:11 Pid_file already exists for running process (2520)... aborting\n\n at line 277 in file /usr/lib/perl5/vendor_perl/5.10.0/Net/Server.pm Feb 5 23:00:29 eik110 amavis[3177]: (!)Net::Server: 2009/02/05-23:00:29 Pid_file already exists for running process (2520)... aborting\n\n at line 277 in file /usr/lib/perl5/vendor_perl/5.10.0/Net/Server.pm Feb 6 00:28:13 eik110 amavis[2546]: (!)Net::Server: 2009/02/06-00:28:13 Pid_file already exists for running process (2583)... aborting\n\n at line 277 in file /usr/lib/perl5/vendor_perl/5.10.0/Net/Server.pm Feb 6 10:23:38 eik110 amavis[7572]: (!)Net::Server: 2009/02/06-10:23:38 Pid_file already exists for running process (2583)... aborting\n\n at line 277 in file /usr/lib/perl5/vendor_perl/5.10.0/Net/Server.pm At first the only solution I found was to reboot. However a few hours later the same problem occured. Studying the above messages more carefully I found the file /var/spool/amavis/amavisd.pid to contain the mentioned pid number. However this pid was active and did belong to the .... courier authdaemon! After deleting the file /var/spool/amavis/amavisd.pid, there was no active amavis process, I could restart this process. Now things are running as it should. Reproducible: Sometimes Steps to Reproduce: 1. Create the file /var/spool/amavis/amavisd.pid with an active process nummber in it. 2.Give the command "rcamavis restart"; this will not succeed. Error message: eik110:~ # rcamavis restart Shutting down virus-scanner (amavisd-new): done Starting virus-scanner (amavisd-new):The amavisd daemon is already running, PID: [2583] failed eik110:~ # ps aux | grep 2583 root 2583 0.0 0.0 29352 788 ? S 00:28 0:00 /usr/lib/courier-authlib/authdaemond 3. Remove the above created file Actual Results: I have no idea how amavis stopped and left a pid file behind with the wrong process number. The software should check wether the pid belongs to an amavis process. If not it should ignore the pid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473553 Katarina Machalkova <kmachalkova@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |varkoly@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=473553 User varkoly@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=473553#c1 Peter Varkoly <varkoly@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WORKSFORME --- Comment #1 from Peter Varkoly <varkoly@novell.com> 2009-03-27 01:13:08 MST --- On openSUSE 11.1 it works please update your system -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com