Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ SMAUG
➜ Running the server
➜ Alarm clock; cause?
It is now over 60 days since the last post. This thread is closed.
Refresh page
Posted by
| Zeno
USA (2,871 posts) Bio
|
Date
| Wed 21 Dec 2005 05:59 PM (UTC) Amended on Wed 21 Dec 2005 07:56 PM (UTC) by Zeno
|
Message
| About 20 minutes ago, this error appeared:
Log: [*****] BUG:ALARM CLOCK! In section new_descriptor: after accept
Alas, the hideous malevalent entity known only as 'Lag' rises once more!
Log: clearing newdesc
And it kept happening over and over. Doesn't seem to stop. I have no clue what is going on. Anyone have any idea?
[EDIT] A reboot didn't fix it.
Seems like when someone connects, this happens. But why it's happening or how to fix it, I have no idea.
[EDIT 2] I disabled DNS lookups, and it seems fine now. What would cause this all of a sudden? There have been no code changes. No server move. |
Zeno McDohl,
Owner of Bleached InuYasha Galaxy
http://www.biyg.org | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #1 on Wed 21 Dec 2005 10:11 PM (UTC) |
Message
| You have tracked it down as a DNS problem. I would try doing DNS lookups manually to see if that shows the problem. It is actually reverse DNS you are after (resolving an IP address to a name). |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Zeno
USA (2,871 posts) Bio
|
Date
| Reply #2 on Wed 21 Dec 2005 11:56 PM (UTC) |
Message
| I'd have to do that from the host; how would I? |
Zeno McDohl,
Owner of Bleached InuYasha Galaxy
http://www.biyg.org | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #3 on Thu 22 Dec 2005 04:20 AM (UTC) |
Message
| Well you can type something like:
nslookup (address)
or
dig (address)
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Nick Gammon
Australia (23,133 posts) Bio
Forum Administrator |
Date
| Reply #4 on Thu 22 Dec 2005 04:22 AM (UTC) |
Message
| Maybe a DNS server that should be up, is down, and the DNS system times out on the bad server.
If you have access, you could try traceroute to the address in question. Does it happen on all connections or certain ones? |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | Top |
|
Posted by
| Zeno
USA (2,871 posts) Bio
|
Date
| Reply #5 on Thu 22 Dec 2005 10:43 AM (UTC) Amended on Thu 22 Dec 2005 10:53 AM (UTC) by Zeno
|
Message
| Seems like all connections.
(nslookup edited out)
I noticed that in the shell after "Last login: Wed Dec 21 11:00:01 2005 from" now shows my IP when (I think) it used to show my hostname. I've already contacted the host though.
[EDIT] Well, it seems fine now. No more alarm clocks when I turned name resolving on. |
Zeno McDohl,
Owner of Bleached InuYasha Galaxy
http://www.biyg.org | Top |
|
Posted by
| Samson
USA (683 posts) Bio
|
Date
| Reply #6 on Fri 23 Dec 2005 02:45 AM (UTC) |
Message
| Just to put this baby to bed, there was in fact some kind of problem with the recursive DNS lookup process on the server. The kind that do just like muds - crash but leave no core, no log hints, nothing, and then just stay dead. Resulting in any DNS lookup process on the box to fail after the normal timeout period. Generally not fun :/ | Top |
|
Posted by
| Zeno
USA (2,871 posts) Bio
|
Date
| Reply #7 on Sun 25 Dec 2005 09:35 PM (UTC) |
Message
| Well it's happening again. In case this helps to find out what the cause is Samson, here's the error when using nslookup:
;; connection timed out; no servers could be reached
|
Zeno McDohl,
Owner of Bleached InuYasha Galaxy
http://www.biyg.org | Top |
|
Posted by
| Samson
USA (683 posts) Bio
|
Date
| Reply #8 on Mon 26 Dec 2005 12:49 AM (UTC) |
Message
| Yes, that's because it crashed on that box again. I still have not figured out why and there's really not alot of help to be found for PowerDNS, but at least when something breaks it's easier to fix. Trying to keep things running using Bind turned into more of a nightmare than it was worth. | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
21,056 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
top