From apwww@hyperreal.org Tue Sep 2 02:41:50 1997 Received: (from apwww@localhost) by hyperreal.org (8.8.5/8.8.5) id CAA00985; Tue, 2 Sep 1997 02:41:50 -0700 (PDT) Message-Id: <199709020941.CAA00985@hyperreal.org> Date: Tue, 2 Sep 1997 02:41:50 -0700 (PDT) From: Hans-Juergen Seekamp Reply-To: sir@map_1.iae.tu-berlin.de To: apbugs@hyperreal.org Subject: start-problem X-Send-Pr-Version: 3.2 >Number: 1084 >Category: suexec >Synopsis: start-problem >Confidential: no >Severity: critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Tue Sep 2 02:50:01 1997 >Originator: sir@map_1.iae.tu-berlin.de >Organization: >Release: 1.3.a1 >Environment: Linux 2.0.27 >Description: httpd <-the start open: No such file or directory <-?? Cannot open lcok file <-?? I think I have destroy a link that I can not make executable... (the httpd is compiled only an error) thanks, I think is not a bug but what is the "lcok file". (I found also this name in the binarys from httpd) >How-To-Repeat: Sorry, You must have su-permissions on the system : map_1.iae.tu-berlin.de >Fix: e.g. an output-message :" lcok file ! have You make this or this ?%2 >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: marc State-Changed-When: Tue Sep 2 07:51:58 PDT 1997 State-Changed-Why: It is trying to open a file in the logs directory under ServerRoot. If you don't have such a directory, use somethine like: LockFile /tmp/accept.lock to move it to a different directory. The ommission of the filename it had trouble opening was accidental and, as mentioned _numerous_ times in the bugdb has been corrected. From: Marc Slemko To: Apache bugs database Subject: Re: suexec/1084: start-problem (fwd) Date: Wed, 3 Sep 1997 10:39:57 -0600 (MDT) ---------- Forwarded message ---------- Date: Wed, 3 Sep 1997 11:03:18 +0200 (MET DST) From: Hans-Juergen Seekamp To: Marc Slemko Subject: Re: suexec/1084: start-problem thank you , sorry, but my error: ("Cannot open lcok file") is not demaged by for now hans /'\__\ ~~~~~~~~~~~~~~~ h.-j.seekamp /__\__|o|__ /__\ ( o o ) sir@map_1.iae.tu-berlin.de |__| |=| |__| \ - / root@map_1.iae.tu-berlin.de -P R O AGRAR U N I- BERLIN http://map_1.iae.tu-berlin.de/~sir/ "'ne freundschaft aus biergaerten" taugt mehr als 'ne freundschaft aus dem internet" (roman herzog) On Tue, 2 Sep 1997, Marc Slemko wrote: > Synopsis: start-problem > > State-Changed-From-To: open-closed > State-Changed-By: marc > State-Changed-When: Tue Sep 2 07:51:58 PDT 1997 > State-Changed-Why: > It is trying to open a file in the logs directory under > ServerRoot. If you don't have such a directory, use somethine like: > > LockFile /tmp/accept.lock > > to move it to a different directory. The ommission of > the filename it had trouble opening was accidental and, > as mentioned _numerous_ times in the bugdb has been corrected. > From: Marc Slemko To: Hans-Juergen Seekamp Subject: Re: suexec/1084: start-problem (fwd) Date: Thu, 4 Sep 1997 15:38:53 -0600 (MDT) > ---------- Forwarded message ---------- > Date: Wed, 3 Sep 1997 11:03:18 +0200 (MET DST) > From: Hans-Juergen Seekamp > To: Marc Slemko > Subject: Re: suexec/1084: start-problem > > thank you , sorry, but my error: ("Cannot open lcok file") is not demaged Hmm? Do you mean you still have the problem? Looking further, if you are getting lcok instead of lock then I don't think you are using version 1.3a1 as you reported. Please confirm what version of Apache you are using. Run "httpd -v" to get the version number. In any case, please try 1.2.4. From: Marc Slemko To: Apache bugs database Subject: Re: suexec/1084: start-problem (fwd) Date: Fri, 5 Sep 1997 07:35:00 -0600 (MDT) ---------- Forwarded message ---------- Date: Fri, 5 Sep 1997 09:18:16 +0200 (MET DST) From: Hans-Juergen Seekamp To: Marc Slemko Subject: Re: suexec/1084: start-problem (fwd) Many thank for your helps, the backround of my problems was : I have destroyed any dynamic links in an update-work from linux 2.0.27 to 2.030 and now the httpd from apache is running under http://map_1.iae.tu-berlin.de To first i have: Server version Apache/1.0.0. and i have not found the "lcok" -file over all harddisks then i get the apache src from www.apache.com and compiled this. (./apache_1.3a1/src/httpd).. As i see the same error-message, i think "lcok"-file is "lock".. please make this correct in the source-code or binarys... (sorry my language is bad) by for now hans /'\__\ ~~~~~~~~~~~~~~~ h.-j.seekamp /__\__|o|__ /__\ ( o o ) sir@map_1.iae.tu-berlin.de |__| |=| |__| \ - / root@map_1.iae.tu-berlin.de -P R O AGRAR U N I- BERLIN http://map_1.iae.tu-berlin.de/~sir/ "'ne freundschaft aus biergaerten" taugt mehr als 'ne freundschaft aus dem internet" (roman herzog) On Thu, 4 Sep 1997, Marc Slemko wrote: > > > ---------- Forwarded message ---------- > > Date: Wed, 3 Sep 1997 11:03:18 +0200 (MET DST) > > From: Hans-Juergen Seekamp > > To: Marc Slemko > > Subject: Re: suexec/1084: start-problem > > > > thank you , sorry, but my error: ("Cannot open lcok file") is not demaged > > Hmm? Do you mean you still have the problem? > > Looking further, if you are getting lcok instead of lock then I > don't think you are using version 1.3a1 as you reported. Please > confirm what version of Apache you are using. Run "httpd -v" to > get the version number. > > In any case, please try 1.2.4. > From: Marc Slemko To: Hans-Juergen Seekamp Subject: Re: suexec/1084: start-problem (fwd) Date: Fri, 5 Sep 1997 22:01:02 -0600 (MDT) > Many thank for your helps, > the backround of my problems was : > I have destroyed any dynamic links in an update-work from > linux 2.0.27 to 2.030 and now the httpd from apache is running > under http://map_1.iae.tu-berlin.de > To first i have: > Server version Apache/1.0.0. > and i have not found the "lcok" -file over all harddisks > then i get the apache src from www.apache.com and compiled this. > (./apache_1.3a1/src/httpd).. > As i see the same error-message, i think "lcok"-file is "lock".. > please make this correct in the source-code or binarys... > (sorry my language is bad) > by for now hans If you are still getting the error about the "lcok" file in 1.3a1, then you are not running 1.3a1. You probably have another binary in your path that you are running. The "lcok" misspelling of lock was removed a long time ago, well before 1.2. Please try 1.2.4. It is more recent than 1.3a1. Be sure you are running the correct version. The version you are running may be looking for a /usr/tmp/ or /var/tmp/ directory; one may be missing. However, you should upgrade to 1.2.4 since it has a better error message. From: Marc Slemko To: Apache bugs database Subject: Re: suexec/1084: start-problem (fwd) Date: Sun, 7 Sep 1997 09:42:17 -0600 (MDT) ---------- Forwarded message ---------- Date: Sun, 7 Sep 1997 11:59:34 +0200 (MET DST) From: Hans-Juergen Seekamp To: Marc Slemko Subject: Re: suexec/1084: start-problem (fwd) Many thanks , i make it so... bye for now hans /'\__\ ~~~~~~~~~~~~~~~ h.-j.seekamp /__\__|o|__ /__\ ( o o ) sir@map_1.iae.tu-berlin.de |__| |=| |__| \ - / root@map_1.iae.tu-berlin.de -P R O AGRAR U N I- BERLIN http://map_1.iae.tu-berlin.de/~sir/ "'ne freundschaft aus biergaerten" taugt mehr als 'ne freundschaft aus dem internet" (roman herzog) On Fri, 5 Sep 1997, Marc Slemko wrote: > > > Many thank for your helps, > > the backround of my problems was : > > I have destroyed any dynamic links in an update-work from > > linux 2.0.27 to 2.030 and now the httpd from apache is running > > under http://map_1.iae.tu-berlin.de > > To first i have: > > Server version Apache/1.0.0. > > and i have not found the "lcok" -file over all harddisks > > then i get the apache src from www.apache.com and compiled this. > > (./apache_1.3a1/src/httpd).. > > As i see the same error-message, i think "lcok"-file is "lock".. > > please make this correct in the source-code or binarys... > > (sorry my language is bad) > > by for now hans > > If you are still getting the error about the "lcok" file in 1.3a1, > then you are not running 1.3a1. You probably have another binary > in your path that you are running. The "lcok" misspelling of lock was > removed a long time ago, well before 1.2. > > Please try 1.2.4. It is more recent than 1.3a1. Be sure you are running > the correct version. > > The version you are running may be looking for a /usr/tmp/ or /var/tmp/ > directory; one may be missing. However, you should upgrade to 1.2.4 > since it has a better error message. > >Unformatted: >Last-Modified: Tue Sep 2 07:51:58 PDT 1997