Re: mod_perl crashes after apache upgraded

Wow apache 2.0.x to 2.2.x upgrade is quite a jump ! :)

May I suggest checking the apache configuration to make sure all log locations exist and are writable at start time? Crashing with "No such file or directory" on "ap_run_open_logs" suggests that something related to this might be a problem.

Comment on Re: mod_perl crashes after apache upgraded

Replies are listed 'Best First'.
Re^2: mod_perl crashes after apache upgraded by ysmartnet (Initiate) on Jan 17, 2011 at 04:38 UTC
Hi hsinclai, Yes, it is a huge jump. but I think "No such file or directory" from config.c only shows the apache source code is not found. Thanks for your reply ysmartnet	[reply]
Re^3: mod_perl crashes after apache upgraded by hsinclai (Deacon) on Jan 17, 2011 at 04:52 UTC
> I think "No such file or directory" from config.c only shows the apache source code is not found. Actually, no, I don't believe it means the source code is not found -- it is telling you which line in config.c is generating the error "No such file or directory".. so if you consulted line 148 in the source code of config.c you would see the source code that threw that particular exception.	[reply]
Re^2: mod_perl crashes after apache upgraded by Anonymous Monk on Jan 18, 2011 at 02:41 UTC
"No such file or directory" is print only when I jumped to the 31 stack frame. Thanks for your comments.	[reply]