You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Lodrö Sangpo Joergen Larsen <ni...@tdcspace.dk> on 2003/12/07 19:02:32 UTC
[users@httpd] upgrade startup-errors third try
This is the third time I post this request for help!!! AND STILL NO REPLIES!!!!
Help why upgrade??
I recently downloaded and installed the newest version Apache 1.3.29. I am using windows98.
After start-up, a bunch of messages can be seen in the console window.
The error messages on launch:
"[warn] (2)No such file or directory: exec() may not be safe"
It appears eleven times(at least) and at the end it says that the server is running.
They were not there with my version 1.3.27. And if I use that version's files(you know the 4 important ones) on top of the new install there is no problem.
Only with the new 1.3.29 files.
The server IS running. Everything works. But why the messages?
And how to get rid of them. ? Since I din't like error messages I have gone back to the old version until I get some reply - if ever - sigh.
OmManiPemeHung
Many Greetings Viele Gruesse Mange Hilsener
Lodrö Sangpo Joergen Larsen
www.nimmersoft.com www.nimmersoft.dk
Karmapa Chenno
OmManiPemeHung
Re: [users@httpd] upgrade startup-errors third try
Posted by Lodrö Sangpo Joergen Larsen <ni...@tdcspace.dk>.
Thanks to "Hunter"
thank you ever so much for troubling to answer.
Really appreciate it.
OmManiPemeHung
Many Greetings Viele Gruesse Mange Hilsener
Lodrö Sangpo Joergen Larsen
www.nimmersoft.com www.nimmersoft.dk
Karmapa Chenno
OmManiPemeHung
----- Original Message -----
From: "hunter" <th...@sympatico.ca>
To: <us...@httpd.apache.org>
Sent: Sunday, December 07, 2003 11:48 PM
Subject: Re: [users@httpd] upgrade startup-errors third try
> On Sun, 2003-12-07 at 13:02, Lodrö Sangpo Joergen Larsen wrote:
> > This is the third time I post this request for help!!! AND STILL NO
> > REPLIES!!!!
> >
> > Help why upgrade??
> > I recently downloaded and installed the newest version Apache 1.3.29.
> > I am using windows98.
> > After start-up, a bunch of messages can be seen in the console window.
> > The error messages on launch:
> > "[warn] (2)No such file or directory: exec() may not be safe"
> > It appears eleven times(at least) and at the end it says that the
> > server is running.
> >
> > They were not there with my version 1.3.27. And if I use that
> > version's files(you know the 4 important ones) on top of the new
> > install there is no problem.
> > Only with the new 1.3.29 files.
> >
> > The server IS running. Everything works. But why the messages?
> > And how to get rid of them. ? Since I din't like error messages I have
> > gone back to the old version until I get some reply - if ever - sigh.
> >
> >
> > OmManiPemeHung
> > Many Greetings Viele Gruesse Mange Hilsener
> > Lodrö Sangpo Joergen Larsen
> > www.nimmersoft.com www.nimmersoft.dk
> > Karmapa Chenno
> > OmManiPemeHung
>
> I have done some thinking since my last post. There may be an
> explanation in the Apache 1.3.29 release notes below.
>
> This comes back to unsupported function but it may simply be something
> that was added that is not fully supported in Windows 98 - refer to to
> the last paragraph below.
>
> IMHO: I think you can safely ignore the warning.
>
> And, I am no longer convinced that a file is actually missing - I think
> this is a artifict of the missing functionality.
>
> -Chris
>
> Apache 1.3.29 Major changes
> Security vulnerabilities
> The main security vulnerabilities addressed in 1.3.29 are:
>
> CAN-2003-0542 (cve.mitre.org): Fix buffer overflows in mod_alias and
> mod_rewrite which occurred if one configured a regular expression with
> more than 9 captures.
>
> New features
> New features that relate to specific platforms:
>
> Enabled RFC1413 ident functionality for both Win32 and NetWare
> platforms. This also included an alternate thread safe implementation of
> the socket timout functionality when querying the identd daemon.
>
> Bugs fixed
> The following bugs were found in Apache 1.3.28 (or earlier) and have
> been fixed in Apache 1.3.29:
>
> Within ap_bclose(), ap_pclosesocket() is now called consistently for
> sockets and ap_pclosef() for files. Also, closesocket() is used
> consistenly to close socket fd's. The previous confusion between socket
> and file fd's would cause problems with some applications now that we
> proactively close fd's to prevent leakage. PR 22805.
> Fixed mod_usertrack to not get false positive matches on the
> user-tracking cookie's name. PR 16661.
> Prevent creation of subprocess Zombies when using CGI wrappers such as
> suEXEC and cgiwrap. PR 21737.
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] upgrade startup-errors third try
Posted by hunter <th...@sympatico.ca>.
On Sun, 2003-12-07 at 13:02, Lodrö Sangpo Joergen Larsen wrote:
> This is the third time I post this request for help!!! AND STILL NO
> REPLIES!!!!
>
> Help why upgrade??
> I recently downloaded and installed the newest version Apache 1.3.29.
> I am using windows98.
> After start-up, a bunch of messages can be seen in the console window.
> The error messages on launch:
> "[warn] (2)No such file or directory: exec() may not be safe"
> It appears eleven times(at least) and at the end it says that the
> server is running.
>
> They were not there with my version 1.3.27. And if I use that
> version's files(you know the 4 important ones) on top of the new
> install there is no problem.
> Only with the new 1.3.29 files.
>
> The server IS running. Everything works. But why the messages?
> And how to get rid of them. ? Since I din't like error messages I have
> gone back to the old version until I get some reply - if ever - sigh.
>
>
> OmManiPemeHung
> Many Greetings Viele Gruesse Mange Hilsener
> Lodrö Sangpo Joergen Larsen
> www.nimmersoft.com www.nimmersoft.dk
> Karmapa Chenno
> OmManiPemeHung
I have done some thinking since my last post. There may be an
explanation in the Apache 1.3.29 release notes below.
This comes back to unsupported function but it may simply be something
that was added that is not fully supported in Windows 98 - refer to to
the last paragraph below.
IMHO: I think you can safely ignore the warning.
And, I am no longer convinced that a file is actually missing - I think
this is a artifict of the missing functionality.
-Chris
Apache 1.3.29 Major changes
Security vulnerabilities
The main security vulnerabilities addressed in 1.3.29 are:
CAN-2003-0542 (cve.mitre.org): Fix buffer overflows in mod_alias and
mod_rewrite which occurred if one configured a regular expression with
more than 9 captures.
New features
New features that relate to specific platforms:
Enabled RFC1413 ident functionality for both Win32 and NetWare
platforms. This also included an alternate thread safe implementation of
the socket timout functionality when querying the identd daemon.
Bugs fixed
The following bugs were found in Apache 1.3.28 (or earlier) and have
been fixed in Apache 1.3.29:
Within ap_bclose(), ap_pclosesocket() is now called consistently for
sockets and ap_pclosef() for files. Also, closesocket() is used
consistenly to close socket fd's. The previous confusion between socket
and file fd's would cause problems with some applications now that we
proactively close fd's to prevent leakage. PR 22805.
Fixed mod_usertrack to not get false positive matches on the
user-tracking cookie's name. PR 16661.
Prevent creation of subprocess Zombies when using CGI wrappers such as
suEXEC and cgiwrap. PR 21737.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] upgrade startup-errors third try
Posted by hunter <th...@sympatico.ca>.
On Sun, 2003-12-07 at 13:02, Lodrö Sangpo Joergen Larsen wrote:
> This is the third time I post this request for help!!! AND STILL NO
> REPLIES!!!!
>
> Help why upgrade??
> I recently downloaded and installed the newest version Apache 1.3.29.
> I am using windows98.
> After start-up, a bunch of messages can be seen in the console window.
> The error messages on launch:
> "[warn] (2)No such file or directory: exec() may not be safe"
> It appears eleven times(at least) and at the end it says that the
> server is running.
>
> They were not there with my version 1.3.27. And if I use that
> version's files(you know the 4 important ones) on top of the new
> install there is no problem.
> Only with the new 1.3.29 files.
>
> The server IS running. Everything works. But why the messages?
> And how to get rid of them. ? Since I din't like error messages I have
> gone back to the old version until I get some reply - if ever - sigh.
>
>
> OmManiPemeHung
> Many Greetings Viele Gruesse Mange Hilsener
> Lodrö Sangpo Joergen Larsen
> www.nimmersoft.com www.nimmersoft.dk
> Karmapa Chenno
> OmManiPemeHung
>
1. It is hard to take anyone serious who is using Windows 98.
2. You are getting a warning, not an error message.
3. The probable cause is (a missing file that leads to) unsupported
functionality with Windows 98.
4. It may have something to do with a file that is missing and the
'exec() may not be safe' is a symptom of the unsupported function -
exec() is not used for Win32 in anycase.
5. I could not recreate this error on Windows XP by deleting various
files.
Disclaimer:
1. I am not an Apache developer.
2. I do not use Windows 98.
IMHO: You should look for a file that is not there that should be. But
if your Apache starts and works you should accept that your OS is not
fully compliant and continue.
I have extracted the functions that are relevant - as and attachment.
Here is a quick summary:
This is where the function is exported and called by many modules.
.\main\http_log.c:API_EXPORT(piped_log *) ap_open_piped_log(pool *p, const char *program)
.\main\http_log.c:API_EXPORT(piped_log *) ap_open_piped_log(pool *p, const char *program)
One of the following modules attempts to call 'ap_open_piped_log' and
this eventually leads to the unsupported function.
.\modules\ssl\ssl_engine_log.c: if ((pl = ap_open_piped_log(p, szLogFile)) == NULL) {
.\modules\standard\mod_log_agent.c: pl = ap_open_piped_log(p, cls->fname + 1);
.\modules\standard\mod_log_config.c: pl = ap_open_piped_log(p, cls->fname + 1);
.\modules\standard\mod_log_referer.c: pl = ap_open_piped_log(p, cls->fname + 1);
.\modules\standard\mod_rewrite.c: if ((pl = ap_open_piped_log(p, conf->rewritelogfile+1)) == NULL){
else /* Win9x */ {
/* XXX: This API doesn't work... you can't change the handle by just
* 'touching' it... you must duplicat to a second handle and close
* the original.
*/
return 0;
}
Feel free to examine the attached code. Perhaps if you know which
modules you are using this will lead you to the missing file.
This is about the best I can offer, unless someone else jumps in with a
better suggestion or someone has some first hand experience with Windows
98.
Chris