Re: ????: Collector locking config.db

Looks OK from here.  Make sure you have no other cricket processes running,
that could also cause the problem you saw.  Use "ps" and maybe
"lsof config.db" to check.

On Tue, Jul 24, 2007 at 12:01:09PM +0800, Ramanan wrote:
>    Hi Ed Ravin,
> 
>    Thank you for your time and advice. Currently the cricket is executed
>    by user ivan. Below is the permission.
>    I am not the linux pro, so not sure whether the permission for
>    config.db is correct.
>    [ivan@localhost cricket-config]$ ls -la
>    total 1016
>    drwxr-xr-x   7 ivan ivan   4096 Jul 24 10:50 .
>    drwxr-xr-x  55 ivan ivan   4096 Jul 21 09:57 ..
>    -rw-r--r--   1 ivan ivan 983040 Jun  8 09:56 config.db
>    drwxr-xr-x   5 ivan ivan   4096 Jul  7  2004 CRC_error
>    -rw-r--r--   1 ivan ivan      0 Jul 11 09:04 __db.config.db.new.
>    -rw-r--r--   1 ivan ivan   9018 Sep 13  2004 Defaults
>    -rw-r--r--   1 ivan ivan   8982 Jun 21  2004 Defaults~
>    drwxrwxr-x   6 ivan ivan   4096 May  3 13:25 packeteer
>    drwxr-xr-x   5 ivan ivan   4096 Jul 12  2004 performance
>    drwxr-xr-x   4 ivan ivan   4096 Sep 24  2004 responsetime
>    drwxr-xr-x   4 ivan ivan   4096 May  3 13:24 utilization
>    Appreciate your help.
> 
>    Regards,
>    Ramanan
>      __________________________________________________________________
> 
>    From: Ed Ravin [mailto:[email protected]]
>    Sent: 23/7/2007 (ÐÇÆÚÒ») PM 11:18
>    To: Ramanan
>    Cc: [email protected]
>    Subject: Re: [cricket-users] 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.

-- 
Ed Ravin          | "The law, in its majestic equality, forbids the rich as
                  |  well as the poor to sleep under bridges, to beg in the
 eravin@          |  streets, and to steal bread."
 panix.com        |               --Anatole France, Le Lys Rouge [1894]

-------------------------------------------------------------------------
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/

_______________________________________________
cricket-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cricket-users