Has Anyone seen this in their error.log

kim

New member
Joined
Jun 21, 2004
Messages
1
I wonder if anyone has ever seen messages like this appear in the error log of DirectAdmin:

2004:06:20-15:51:40: Timeout from from 65.95.114.138 : last flagged: Request::readAndProcess(*skt, 65.95.114.138, 65.95.114.138)
2004:06:20-15:51:40: *** Segmentation fault *** Send::sendData(/HTM_TEMPLATE) : User: (null) : 65.95.114.138 : (null) : (null) : (null)

2004:05:25-13:02:41: Timeout from from 213.82.84.161 : last flagged: Command::doCommand(/CMD_SYSTEM_INFO)

2004:06:20-18:24:56: Timeout from from 213.127.147.5 : last flagged: Authentication::authenticated(*enc, (null), rXzAcbkY3yGz4sh9cIH
5MGlfA79xfLhVrefRFOzIMEFR6uYiCplW3UBBbI8HbnmS, 212.127.146.6)

Has anyone any idea what these might mean? Is this a system configuration problem or a software problem?
 
Last edited:
*** Segmentation fault ***
That ain't good...

Segfaults usually mean a problem in the software (bug or error of somekind), I thought DA's updater would take care of a segfault in the DNS settings for BSD in the next version, but i have no clue if this is the same thing.
 
Hello,

That's a new one. Have you noticed anything not working? It might be someone poking around with invalid data ... or a weird permission issue with the skins.. hard to say. Possibly even just a bad build. I'll take a look at the code around there to see if I can find anything.

John
 
Support did you find a clue about error.log

Has anyone found a clue about the messages?:confused:
 
I'm not sure about the /HTM_TEMPLATE error. I looked through the code, but there is probably too much to go through without a more specific error. I've added more program flags so if it happens again, it will point more specifically to where it's happening (next release though). If anyone is seeing this on their system, take a look at the time that it happens, then go through the access logs (same directory).. eg: 2004-Jun-24.log and scroll down to the time it happens (just a bit before) and let me know what command was run that generated the error. The one case I've seen, it was CMD_LOGIN.

If you notice anything specific not working, also let me know.

John
 
Back
Top