Socket errors

Hello,

Since yesterday I keep getting messages that the DA service on the server is down. I can't find any usefull information in de log files execpt this message:

2009:06:21-16:01:50: Socket write error: fd is connected to a pipe or socket whose reading end is closed. When this happens the writing process will also receive a SIG_PIPE signal. (Thus, the write return value is seen only if the program catches, blocks or ignores this signal.)
2009:06:21-16:01:50: Error reading from 213.46.110.66:

Click to expand...

This message is repeating over and over again. What does this mean? I couldn't find out on the internet whaat this message means.

Also a other messages found a few times in the log:

2009:06:18-13:25:48: Timeout from from 217.77.144.150 : last flagged: Request::readAndProcess(*skt, 217.77.144.150, 217.77.144.150)

Click to expand...

What I forgot to report is that despite the fact that I receive messages that DA is down, DA is not down but accessible...

Have you tried restarting DirectAdmin from a root shell? If you do, you should see a specific error message which may be different, and which may help.

Jeff

I didn't try restarting DA.
These messages just starting to show up Saturday night while nobody was working with of on the server.

Try restarting DirectAdmin through the shell to see if you get any errors.

Jeff

Without any problems:

/root$ /etc/init.d/directadmin restart
Stopping DirectAdmin: [ OK ]
Starting DirectAdmin: [ OK ]


What I forgot to report is that despite the fact that I receive messages that DA is down, DA is not down but accessible...

I don't know why you're getting the message. For me to figure it out I'd have to log into your system and our minimum service charge is us$125. So you probably should ask DirectAdmin Support, if your license includes support.

Jeff

Oke thank you.

I will send an E-mail tomorrow morning (local).

Thought i better speak up, I also just got this error yesterday.


I dont know either. This happened to us when a new client signed up with us yesterday.

cheers. your not alone MikeVrind.

I got the same error. what's the solution about this?
Did you solved the error?

Hello,

If you're getting messages that DA is down, but it in fact isn't down, likely either your /proc "procfs" partition isn't mounted right, or you're running binaries compiled for an OS different than your own. Check Admin Level -> Licenses Updates -> Compile on:

I believe some of the FreeBSD versions are slightly different than other FreeBSD vesions. Some get the processes from the kernel directly, while others get them from the /proc directory.

If you're DA is actually down, then use this guide:
http://help.directadmin.com/item.php?id=75
Try running DA manually, eg:
Note that some socket errors are normal (if you can still access DA normally). For example, if ever a transfer is aborted by the User (eg: press esc, or change pages before an image finishes) that would throw a socket errors.

Also if you connect to https on an http connection, or vice versa, those errors might show up.

Also ensure you're not blacklisted.
If the file exists, make sure your IP isn't in it:
/usr/local/directadmin/data/admin/ip_blacklist

You can also run DA in debug mode to see more of what's going on: If you get the message that just means that DA is already running running, so the "killall -9 directadmin" can be run to kill existing processes before starting a new one.

John