[chef] Chef-Solr logrotate issues

[Ash Berlin < >]

It seems that solr is not coming back up cleanly after logrotate. I'm using 
the opscode provided .deb packages on Ubuntu 10.04.

% cat /var/log/chef/solr.log
[Sun, 22 Aug 2010 06:30:03 +0100] INFO: About to change privilege to chef:chef
[Sun, 22 Aug 2010 06:30:03 +0100] FATAL: Chef is already running pid 11974

Looking back over the log, it seems that its trying to restart it before the 
old one has shutdown:

% sudo kill -0 11974
kill: No such process
% zgrep -e 'Forked, in\|FATAL' /var/log/chef/solr.log*
/var/log/chef/solr.log:[Sun, 22 Aug 2010 06:30:03 +0100] FATAL: Chef is 
already running pid 11974
/var/log/chef/solr.log.1.gz:[Sun, 15 Aug 2010 06:39:00 +0100] FATAL: Chef is 
already running pid 16429
/var/log/chef/solr.log.1.gz:[Mon, 16 Aug 2010 15:12:05 +0100] INFO: Forked, 
in 11923. Priveleges: 111 112
/var/log/chef/solr.log.1.gz:[Mon, 16 Aug 2010 15:12:12 +0100] INFO: Forked, 
in 11974. Priveleges: 111 112
/var/log/chef/solr.log.2.gz:[Tue, 10 Aug 2010 14:01:12 +0100] INFO: Forked, 
in 9285. Priveleges: 111 112
/var/log/chef/solr.log.2.gz:[Tue, 10 Aug 2010 14:08:05 +0100] INFO: Forked, 
in 10231. Priveleges: 111 112
/var/log/chef/solr.log.2.gz:[Tue, 10 Aug 2010 14:11:11 +0100] INFO: Forked, 
in 12761. Priveleges: 111 112
/var/log/chef/solr.log.2.gz:[Tue, 10 Aug 2010 14:17:58 +0100] INFO: Forked, 
in 16429. Priveleges: 111 112


Anyone else noticed this problem? Better yet anyone got a solution?

-ash