Monday, January 07, 2019

Re: amavisd-new stuck: computer doesn't shutdown

El 07/01/2019 14:03, Stuart Henderson escribió:
> Moving to ports@ because ports-bugs@ isn't listed on the mailing
> lists page so isn't likely to be very widely read.
>
> On 2019/01/07 13:48, SyYExroNZ@cajaume.org wrote:
>> El 07/01/2019 08:21, Giovanni Bechis escribió:
>> > On Sat, Jan 05, 2019 at 11:00:00PM +0100, SyYExroNZ@cajaume.org wrote:
>> > > Hello,
>> > >
>> > > When turning off the computer by pressing the power button it never
>> > > shuts down because
>> > > the amavisd daemon doesn't stop.
>> > >
>> > > pkg_info:
>> > >
>> > > amavisd-new-2.11.0p3
>> > > amavisd-new-utils-2.11.0p2
>> > >
>> > can you provide your rc.conf.local(8) ?
>> > Cheers
>> > Giovanni
>>
>> Hi,
>>
>> Here it is:
>>
>> apmd_flags=
>> cron_flags=
>> ntpd_flags=
>> smtpd_flags=NO
>> sshd_flags=
>> unbound_flags=
>> xenodm_flags=NO
>> pkg_scripts=vnstatd clamd freshclam amavisd spamassassin mysqld
>> courier_authdaemond dovecot postfix apache2 squid
>>
>> Other computers i've used as mail servers have the same problem.
>
> Anything in logs?

This is all i get (/var/log/maillog)

Jan 7 14:34:44 router postfix/postfix-script[20510]: stopping the
Postfix mail system
Jan 7 14:34:44 router postfix/master[51997]: terminating on signal 15
Jan 7 14:34:44 router dovecot: master: Warning: Killed with signal 15
(by pid=0 uid=0 code=kill)
Jan 7 14:34:45 router authdaemond: stopping authdaemond children
Jan 07 14:34:48 router spamd[22160]: spamd: server killed by SIGTERM,
shutting down
Jan 7 14:34:55 router amavis[68340]: logging initialized, log level 2,
syslog: amavis.mail
Jan 7 14:34:55 router amavis[68340]: sd_notify (no socket):
STATUS=Config files have been read, modules loaded.
Jan 7 14:34:55 router amavis[68340]: Valid PID file
/var/amavisd/amavisd.pid (younger than sys uptime 0 7:49:00)
Jan 7 14:34:55 router amavis[28355]: sd_notify (no socket):
STOPPING=1\\nSTATUS=Server rundown, notifying child processes.
Jan 7 14:34:55 router amavis[28355]: Net::Server: 2019/01/07-14:34:55
Server closing!
Jan 7 14:34:55 router amavis[28355]: sd_notify (no socket):
STATUS=Child processes have been stopped.
Jan 7 14:34:56 router amavis[68340]: Waiting for the process [28355] to
terminate
Jan 7 14:35:11 router last message repeated 3 times

>
> What do you see if you run "rcctl -d stop amavisd" from the shell?

rcctl -d stop amavisd

doing _rc_parse_conf
doing _rc_quirks
amavisd_flags empty, using default ><
doing _rc_parse_conf /var/run/rc.d/amavisd
doing _rc_quirks
doing rc_check
amavisd
doing rc_stop
Waiting for the process [54915] to terminate
Daemon [54915] terminated by SIGTERM
doing _rc_wait stop
doing rc_check
doing _rc_rm_runfile
(ok)

When you run "shutdown" or reboot the computer there is no problem.

>
> [Perhaps rc_stop() needs the same 'alarm clock' mechanism as
> rc_start() ...]

Not aware of that.

No comments:

Post a Comment