We are also seeing this problem on RHEL5.5, using the RPM from http://jenkins-ci.org/redhat/ (hudson-1.381-1.1 as this writing):
/etc/cron.daily/logrotate:
kill -SIGALRM `cat /var/run/hudson.pid`
: line 1: kill: SIGALRM: invalid signal specification
error: error running postrotate script for /var/log/hudson/hudson.log /var/log/hudson/access_log
The recommendation above (using "kill -s SIGALRM") should fix the problem, but you could also consider calling /bin/kill explicitly and using -ALRM, as in the attached patch. Using "kill [-signal_name] pid" as noted in http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html seems to be the most popular approach on RHEL, at least. Compare /etc/logrotate.d/syslog, for example.
We are also seeing this problem on RHEL5.5, using the RPM from http://jenkins-ci.org/redhat/ (hudson-1.381-1.1 as this writing):
/etc/cron.daily/logrotate:
kill -SIGALRM `cat /var/run/hudson.pid`
: line 1: kill: SIGALRM: invalid signal specification
error: error running postrotate script for /var/log/hudson/hudson.log /var/log/hudson/access_log
The recommendation above (using "kill -s SIGALRM") should fix the problem, but you could also consider calling /bin/kill explicitly and using -ALRM, as in the attached patch. Using "kill [-signal_name] pid" as noted in http://www.opengroup.org/onlinepubs/009695399/utilities/kill.html seems to be the most popular approach on RHEL, at least. Compare /etc/logrotate.d/syslog, for example.