Re: Collector locking config.db

On Mon, Jul 23, 2007 at 04:50:49PM +0800, Ramanan wrote:
> 
> [23-Jul-2007 15:48:52*] config.db.new could not be renamed to config.db!
> [23-Jul-2007 15:48:52*] Reason is: No such file or directory
> [23-Jul-2007 15:48:52*] This is usually due to collector locking
> config.db.
> [23-Jul-2007 15:48:52*] Your changes won't take effect until this is
> resolved!
> [23-Jul-2007 15:48:52 ] Processed 818 nodes (in 189 files) in 0 seconds.
> 
> Is there any remedy for this. I looked at the script which says "we are
> being asked to do a complete rebuild, so start from scratch "

Perhaps Cricket cron script does not have permissions to rename config.db?
The usual way to fix this is to change the permissions on the
cricket-config directory tree to be owned by the Cricket user that also
runs the cron job.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/