Problem on dcc 1.3.30 - Continue Not Asking DCC...

Breno Moiana breno@haxent.com.br
Thu Mar 9 17:46:14 UTC 2006


Hello, Gary. Thanks for the quick answer :)

My problem is very similar to yours, however I seem to be running into 
it for hours at a time, and nearly every other day.

I could identify in my log situations similar to the ones you describe:

1. At least one time, the server stopped responding at the time of the 
database cleanup. However, it remained that way for about 8 hours. Then 
it came back to life again with no apparent reason. I had manually 
triggered the cron-dccd, but that was about 30 minutes before the 
service actually got back online.

2. Sometimes (not always) I also have the system coming back up after 
the reopening of the database.

I still couldn't replicate the error nor the solution. It's all still misty.

Today it is unstable, and I am poking around it to see if I can find the 
weak spot.
If I find something, I will post back.

Best Regards,

Breno  Moiana.
===============
Haxent Consulting





Gary Mills wrote:

>On Thu, Mar 09, 2006 at 12:00:40PM -0300, Breno Moiana wrote:
>  
>
>>I am having a problem that is very similar to the one reported by Gary 
>>Mills[1] on January 26th 2006.
>>    
>>
>
>  
>
>>: Mar  9 09:29:38 dcc dccifd[4782]: no DCC answer from 127.0.0.1,6277 
>>after 18264 ms
>>: Mar  9 09:29:38 dcc dccifd[4782]: continue not asking DCC 64 seconds 
>>after failure
>>    
>>
>
>I've been seeing this problem for a long time, but it doesn't happen
>every day.  It did this morning, though.  It seems to begin with
>database cleaning:
>
>  Mar  9 03:48:59 electra dccd grey[4622]: [ID 287260 mail.notice] database cleaning begun
>  Mar  9 03:49:16 electra dccd grey[4622]: [ID 308828 mail.notice] 1.3.30 database /usr/local/dcc/grey_db reopened with 2037 MByte window
>  Mar  9 03:49:17 electra dccd[4603]: [ID 287260 mail.notice] database cleaning begun
>  Mar  9 03:54:23 electra dccm[4639]: [ID 702911 mail.error] no DCC answer from electra.cc.umanitoba.ca (130.179.16.23,6277) after 7237 ms
>  Mar  9 03:54:23 electra dccm[4639]: [ID 702911 mail.error] continue not asking DCC 64 seconds after failure
>
>I've omitted some here.  It ends when the database is reopened:
>
>  Mar  9 03:54:30 electra dccm[4639]: [ID 702911 mail.error] continue not asking DCC 2045 seconds after failure
>  Mar  9 03:54:33 electra dccm[4639]: [ID 702911 mail.error] continue not asking DCC 2042 seconds after failure
>  Mar  9 03:54:34 electra dccd[4603]: [ID 308828 mail.notice] 1.3.30 database /usr/local/dcc/dcc_db reopened with 2037 MByte window
>  Mar  9 03:54:36 electra dccm[4639]: [ID 702911 mail.error] fcntl(F_SETLKW F_WRLCK resolve lock /usr/local/dcc/map 3): Deadlock situation detected/avoided
>
>The other piece of the puzzle is:
>
>  $ cdcc info
>  # 03/09/06 09:23:06 CST  /usr/local/dcc/map
>  # Re-resolve names after 09:54:36
>  # 3340.05 ms threshold, 6879.11 ms average    2 total, 2 working servers
>
>Note that the minutes of the re-resolve time corresponds to that of
>the last error message.
>
>  
>




More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.