From apwww@hyperreal.org Wed Oct 8 00:55:22 1997 Received: (from apwww@localhost) by hyperreal.org (8.8.5/8.8.5) id AAA09764; Wed, 8 Oct 1997 00:55:22 -0700 (PDT) Message-Id: <199710080755.AAA09764@hyperreal.org> Date: Wed, 8 Oct 1997 00:55:22 -0700 (PDT) From: Jeanette Leitner Reply-To: jeanette.leitner@lfstad.bayern.de To: apbugs@hyperreal.org Subject: socket error in error_log X-Send-Pr-Version: 3.2 >Number: 1210 >Category: general >Synopsis: socket error in error_log >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: support >Submitter-Id: apache >Arrival-Date: Wed Oct 8 01:00:03 1997 >Last-Modified: Wed Oct 8 03:50:57 PDT 1997 >Originator: jeanette.leitner@lfstad.bayern.de >Organization: >Release: 1.0.5 >Environment: OS Linux 5 >Description: Got complaints from a user who can't acces our server , but doesnt't get any messages on his browser. Whenever he tries to access, there occurs a line in the error_log which sais: socket error: accept failed This is all, there is no IP-number or any name of the sender. This problem must be situated in the server itself, because the request shows up in the firewall documentation how any other request. He even gets three packages back, but that's it. So we're afraid that more users might have this problem and we have no idea why and how to fix it. Further, the same user who complained reported that he did browse on our server some weeks ago without any problems. Apart from that, we have quite a lot of error messages in the error_log which say: access to /usr/local/etc failed for ..... reason: file doesn't exist I don't know if this is severe, but I wonder why some keep trying to access this file ..? Thanks a lot in advance for your help ! >How-To-Repeat: >Fix: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: Lars.Eilebrecht@unix-ag.org State-Changed-When: Wed Oct 8 03:50:57 PDT 1997 State-Changed-Why: You mention that you use Apache 1.05 which is an ancient version. I'm afraid we cannot support such an outdated version of Apache any longer. Please upgrade to a recent version (eg. Apache 1.2.4) which likely will solve your problems. Release-Changed-From-To: 105-1.0.5 Release-Changed-By: Lars.Eilebrecht@unix-ag.org Release-Changed-When: Wed Oct 8 03:50:57 PDT 1997 >Unformatted: