A few error.log errors

Xuru

Verified User
Joined
Nov 10, 2003
Messages
71
While I have seen no direct error, I checked the DA error.log and found these. Not sure what all of them mean.

2004:01:13-02:41:48: 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.)
2004:01:13-02:47:35: cpuinfo didn't exist, mounting the filesystem: /sbin/mount_linprocfs linprocfs /compat/linux/proc
2004:01:13-03:04:50: cpuinfo didn't exist, mounting the filesystem: /sbin/mount_linprocfs linprocfs /compat/linux/proc
2004:01:13-03:58:48: 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.)
2004:01:13-03:58:48: Error while sending ./data/skins/default/images/complete_usage.gif
2004:01:13-04:04:02: cpuinfo didn't exist, mounting the filesystem: /sbin/mount_linprocfs linprocfs /compat/linux/proc
2004:01:13-04:11:38: 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.)
2004:01:13-04:11:38: Error while sending ./data/skins/default/images/sys_services.gif
2004:01:13-04:29:33: Domin::deleteFile:Could not find ip for deletetion of (null)
2004:01:14-01:54:16: Didn't find two eols on the header from 4.65.163.1

2004:01:14-01:54:16: Error reading from 4.65.163.1:
2004:01:14-01:58:02: cpuinfo didn't exist, mounting the filesystem: /sbin/mount_linprocfs linprocfs /compat/linux/proc
2004:01:14-05:45:28: 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.)
2004:01:14-05:46:00: Didn't find two eols on the header from 4.65.163.1

2004:01:14-05:46:00: Error reading from 4.65.163.1:
2004:01:14-23:52:54: Domin::deleteFile:Could not find ip for deletetion of (null)
2004:01:14-23:53:54: Domin::deleteFile:Could not find ip for deletetion of (null)
2004:01:14-23:53:54: Domin::deleteFile:Could not find ip or deletetion of (null)

Looks like multiple issues with one thing or another. Any ideas what the different ones mean? The one that really confuses me is the ip ones. I don't have that IP.
 
Hello,

Socket write error: fd is connected to a pipe or socket whose reading end is closed
Means the user pressed "escape" in their browser. Not a problem.


cpuinfo didn't exist, mounting the filesystem: /sbin/mount_linprocfs
This is used for the system information. What it does is tries to get info from the cpuinfo file (from redhat).. if it doesn't exist on FreeBSD, it will try to mount the /compat/linux/proc filesystem. If that doesn't work or do anything, it will then just get the info using other means. Basically just a trial and error method to get the system information.

Error while sending ./data/skins/default/images/complete_usage.gif
Again, just a cancelled transfer, no biggie.

Domin::deleteFile:Could not find ip for deletetion of (null)
If you can forgive the spelling errors ;), that just means that no domain existed when the user account was deleted. There are many places where several things are checked, even tho they are valid occurences. They sometime help with things DO go wrong.

Didn't find two eols on the header from 4.65.163.1
Means during the HTTP request, the full headers wern't sent. This can happen when someone telnets to the port to checkout if it's running.. or if the connection was cancelled by the user half way through the request.

John
 
Back
Top