I am still seeing BOARDBUSY messages in my logs like the following: larrd-status.log: 2005-03-04 11:36:11 Tried to down BOARDBUSY: Invalid argument
I've narrowed it down to the following code in hobbitd_channel.c, but I don't know how to fix it. My log files don't seem to be getting updated properly and I'm wondering if this has anything to do with it. I'm on Fedora.
/*
* Let master know we got it by downing BOARDBUSY.
* This should not block, since BOARDBUSY is upped
* by the master just before he ups GOCLIENT.
*/
do {
s.sem_num = BOARDBUSY; s.sem_op = -1;
s.sem_flg = IPC_NOWAIT; n = semop(channel->semid, &s, 1); } while ((n == -1) && (errno == EINTR)); if (n == -1) { errprintf("Tried to down BOARDBUSY: %s\n", strerror(errno)); }
Can anyone provide any assistance?
Thanks
David Stuffle
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
On Fri, Mar 04, 2005 at 12:00:22PM -0500, Stuffle, David wrote:
I am still seeing BOARDBUSY messages in my logs like the following: larrd-status.log: 2005-03-04 11:36:11 Tried to down BOARDBUSY: Invalid argument
This one is harmless, and happens when Hobbit shuts down. The master daemon (hobbitd) sends a shutdown-message to all of the hobbitd_channel worker modules, then marks the shared memory segments used for communication with the modules for deletion. Depending on how fast the workers respond, they may try to access the shared memory segment when it has been deleted, and you'll get this message.
My log files don't seem to be getting updated properly and I'm wondering if this has anything to do with it. I'm on Fedora.
Which log files, specifically ? The only files that Hobbit normally updates while running are the historical logs in the data/hist/ and data/histlogs/ directories - and they only get updated when there are status changes.
Regards, Henrik
participants (2)
-
dstuffle@deltafaucet.com
-
henrik@hswn.dk