[SOLVED] kill HUP crashes logger

[d_clark]

I'm running 5.0.16 on Mac 10.5, and still having the same child PID issue. Terminal ouput below.


OSBA-SVR-Zimbra:~ zimbra$ zmswatchctl start
Starting swatch...done.
OSBA-SVR-Zimbra:~ zimbra$ ps ax | grep swatch
33443 s000 S 0:00.07 /usr/bin/perl /opt/zimbra/libexec/swatch --config-fil e=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/z imbra.log
33447 s000 S 0:00.08 /usr/bin/perl /tmp/.swatch_script.33443
33529 s000 R+ 0:00.00 grep swatch
OSBA-SVR-Zimbra:~ zimbra$ ps ax | grep swatch
33443 s000 S 0:00.07 /usr/bin/perl /opt/zimbra/libexec/swatch --config-file=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/zimbra.log
33447 s000 S 0:00.09 /usr/bin/perl /tmp/.swatch_script.33443
33706 s000 R+ 0:00.00 grep swatch
OSBA-SVR-Zimbra:~ zimbra$ cat /opt/zimbra/log/swatch.pid
33443
OSBA-SVR-Zimbra:~ zimbra$ zmlogswatchctl start
Starting logswatch...done.
OSBA-SVR-Zimbra:~ zimbra$ ps ax | grep swatch
33443 s000 S 0:00.07 /usr/bin/perl /opt/zimbra/libexec/swatch --config-file=/opt/zimbra/conf/swatchrc --use-cpan-file-tail --script-dir=/tmp -t /var/log/zimbra.log
33447 s000 S 0:00.11 /usr/bin/perl /tmp/.swatch_script.33443
33730 s000 S 0:00.06 /usr/bin/perl /opt/zimbra/libexec/logswatch --config-file=/opt/zimbra/conf/logswatchrc --use-cpan-file-tail --pid-file=/opt/zimbra/log/logswatch.pid --script-dir=/tmp -t /var/log/zimbra.log
33732 s000 R 0:00.07 /usr/bin/perl /tmp/.swatch_script.33730
33775 s000 R+ 0:00.00 grep swatch
OSBA-SVR-Zimbra:~ zimbra$ cat /opt/zimbra/log/logswatch.pid
33732

I've posted this in the bug that said this was verified fixed in 5.0.16.

[phoenix]

Originally Posted by d_clark

I'm running 5.0.16 on Mac 10.5, and still having the same child PID issue.

As you're a Network Edition customer please open a support case and reference the bug report (and your comments).

[rs232c]

I also updated to 5.0.16 this week, the zmlogswatchctl script was not corrected. You can reapply the patch I posted 03-36-2009 in this thread to fix the script.

[d_clark]

Thanks, rs232c, for verifying. I'll try the patch - if all else fails, setup a cron job to start the log services everyday.

This seems like a major issue to have - I'm hoping they'll reopen the bug and it'll be gone in 6.0.