You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Denise Mangano <De...@complusdata.com> on 2003/08/28 18:13:33 UTC
RE: First mod_jk problem - can't start apache with Include statement (revisited)
Not really sure if this is a problem as of yet. I currently cannot test
my configuration ... But I just wanted to write again regarding this
issue. As I followed the how-to, I did things a little out of order.
Before changing Tomcat, and while Tomcat was not running, I added the
LoadModule and Include statements into httpd.conf. I then ran an
apachectl configtest. The configtest executed fine and I was returned
an error message that the file mod_jk.conf could not be found. This was
right, because the file was not generated yet.
I then set up server.xml and created my workers.properties and started
Tomcat, which started no problem.
I then went back to apache and ran another configtest, and surprise...
It hangs... And so does apachectl start ...So we're back to the same
issue. I am having a hard time at this point believing it is an Apache
issue, because the configtest executed fine with the include before
Tomcat was started and before the mod_jk.conf was created.
So what I did next was one at a time, I added in the Jk statements into
the httpd.conf to rule out this being an issue with the mod_jk
module(?). First I added in the JkWorkersFile, then ran a configtest.
Then added in the JkLogFile and ran a configtest. Lastly added in some
JkMount statements and ran a configtest. At each of these points, the
configtest executed and was successful. I can also start and stop
apache no problem.
As I mentioned, I cannot test whether or not mod_jk works just yet
(network issues)... There were no errors when starting either Tomcat or
apache. But I do find it strange that I can't start apache just because
I have the Include statement.
Any further thoughts on this? The output of httpd -l just lists
mod_core and mod_so. I have all other modules added as DSO's.
Thanks :)
DEnise
> -----Original Message-----
> From: John Turner [mailto:tomcat-user@johnturner.com]
> Sent: Wednesday, August 27, 2003 11:08 AM
> To: Tomcat Users List
> Subject: Re: [OFF-TOPIC] Re: First mod_jk problem - can't
> start apache with Include statement
>
>
>
> Cool. My typical Apache build is:
>
> ./configure --enable-so --enable-ssl
> make
> make install
>
> John
>
> Denise Mangano wrote:
>
> > Yes I am. The problem (right now) definitely appears to be some
> > issues with Apache. Unfortunately, the Apache list isn't
> as heavily
> > trafficked, or as quick to response, so I'm still waiting on some
> > replies while I search the archives. I think I have to recompile
> > Apache. I added in a few extra flags when I did this yesterday to
> > make it more "secure" but I think I am better off just
> keeping it as
> > is, then taking out what I don't need later...
> >
> > Won't be able to determine if I have a mod_jk problem at
> all until I
> > get my Apache running properly.
> >
> >
> >>-----Original Message-----
> >>From: John Turner [mailto:tomcat-user@johnturner.com]
> >>Sent: Wednesday, August 27, 2003 10:47 AM
> >>To: Tomcat Users List
> >>Subject: [OFF-TOPIC] Re: First mod_jk problem - can't start
> >>apache with Include statement
> >>
> >>
> >>
> >>Are you loading mod_ssl?
> >>
> >>I'm marking this as off-topic because we haven't determined
> >>that this is
> >>a JK/Tomcat problem yet.
> >>
> >>John
> >>
> >>Denise Mangano wrote:
> >>
> >>
> >>>Yeah, it appears to be my apache. I still get that
> >>
> >>SSLMutex error. I
> >>
> >>>have to work on getting that resolved.
> >>>
> >>>This is the output of httpd -l:
> >>>
> >>> http_core.c
> >>> mod_env.c
> >>> mod_log_config.c
> >>> mod_mime.c
> >>> mod_negotiation.c
> >>> mod_status.c
> >>> mod_include.c
> >>> mod_dir.c
> >>> mod_cgi.c
> >>> mod_asis.c
> >>> mod_imap.c
> >>> mod_actions.c
> >>> mod_alias.c
> >>> mod_access.c
> >>> mod_auth.c
> >>> mod_so.c
> >>> mod_setenvif.c
> >>> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
> >>>
> >>>Denise
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: John Turner [mailto:tomcat-user@johnturner.com]
> >>>>Sent: Wednesday, August 27, 2003 10:25 AM
> >>>>To: Tomcat Users List
> >>>>Subject: Re: First mod_jk problem - can't start apache with
> >>>>Include statement
> >>>>
> >>>>
> >>>>
> >>>>Hate to say it, but it sounds like your Apache is munged up.
> >>>>
> >>>>If you delete the mod_jk.conf Include, and you delete all
> other JK
> >>>>stuff
> >>>
> >>>>from httpd.conf, your Apache starts up properly, with no errors?
> >>>
> >>>>What is the output of "httpd -l"?
> >>>>
> >>>>John
> >>>>
> >>>>Denise Mangano wrote:
> >>>>
> >>>>
> >>>>
> >>>>>OK, I tried adding the Jk directives directly into the
> httpd.conf
> >>>>>file, and apache at least starts. So the problem is the include
> >>>>>statement. Is it possible that I don't have whatever module
> >>>>
> >>>>is needed
> >>>>
> >>>>
> >>>>>to support the "Include" statement?
> >>>>>
> >>>>>So now the problem is that although apache starts, it does
> >>>>
> >>>>not start
> >>>>
> >>>>
> >>>>>properly. When I run ps -aux | grep httpd I get the following:
> >>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
> >>>>>[httpd <defunct>]
> >>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
> >>>>>[httpd <defunct>]
> >>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
> >>>>>[httpd <defunct>]
> >>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
> >>>>>[httpd <defunct>]
> >>>>>
> >>>>>And needless to say I can't get to my web page. Now again I am
> >>>>>getting those error messages in both my error_log and
> >>>>
> >>>>ssl_engine_log:
> >>>>
> >>>>
> >>>>> [error]mod_ssl: Child could not open SSLMutex lockfile
> >>>>>/usr/local/apache/logs/ssl_mutex.30776 (System error follows)
> >>>>> [error]System: Permission denied (errno: 13)
> >>>>>
> >>>>>So apparently I have a problem with mod_ssl, which I
> guess I didn't
> >>>>>resolve yesterday and should post to the apache list. But the
> >>>>>question still remains why using the Include statement
> >>>>
> >>>>would prevent
> >>>>
> >>>>
> >>>>>Apache from starting at all?
> >>>>>
> >>>>>Thanks for your help :)
> >>>>>Denise
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>>------------------------------------------------------------
> >>
> >>---------
> >>
> >>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >>>>For additional commands, e-mail:
> tomcat-user-help@jakarta.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>------------------------------------------------------------
> ---------
> >>
> >>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >>>For additional commands, e-mail:
> tomcat-user-help@jakarta.apache.org
> >>>
> >>
> >>
> >>
> >>------------------------------------------------------------
> ---------
> >>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >>
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
Re: First mod_jk problem - can't start apache with Include statement
(revisited)
Posted by John Turner <to...@johnturner.com>.
A good test would be to create a file called "test.conf" in
APACHE_HOME/conf.
In that file, put the following:
###
### this is an apache comment
###
Change the Include line in httpd.conf to include the file test.conf and
NOT mod_jk.conf.
Then start Apache or run configtest and see what happens. If it hangs,
its definitely an Apache issue.
John
Denise Mangano wrote:
> Not really sure if this is a problem as of yet. I currently cannot test
> my configuration ... But I just wanted to write again regarding this
> issue. As I followed the how-to, I did things a little out of order.
> Before changing Tomcat, and while Tomcat was not running, I added the
> LoadModule and Include statements into httpd.conf. I then ran an
> apachectl configtest. The configtest executed fine and I was returned
> an error message that the file mod_jk.conf could not be found. This was
> right, because the file was not generated yet.
>
> I then set up server.xml and created my workers.properties and started
> Tomcat, which started no problem.
>
> I then went back to apache and ran another configtest, and surprise...
> It hangs... And so does apachectl start ...So we're back to the same
> issue. I am having a hard time at this point believing it is an Apache
> issue, because the configtest executed fine with the include before
> Tomcat was started and before the mod_jk.conf was created.
>
> So what I did next was one at a time, I added in the Jk statements into
> the httpd.conf to rule out this being an issue with the mod_jk
> module(?). First I added in the JkWorkersFile, then ran a configtest.
> Then added in the JkLogFile and ran a configtest. Lastly added in some
> JkMount statements and ran a configtest. At each of these points, the
> configtest executed and was successful. I can also start and stop
> apache no problem.
>
> As I mentioned, I cannot test whether or not mod_jk works just yet
> (network issues)... There were no errors when starting either Tomcat or
> apache. But I do find it strange that I can't start apache just because
> I have the Include statement.
>
> Any further thoughts on this? The output of httpd -l just lists
> mod_core and mod_so. I have all other modules added as DSO's.
>
> Thanks :)
> DEnise
>
>
>>-----Original Message-----
>>From: John Turner [mailto:tomcat-user@johnturner.com]
>>Sent: Wednesday, August 27, 2003 11:08 AM
>>To: Tomcat Users List
>>Subject: Re: [OFF-TOPIC] Re: First mod_jk problem - can't
>>start apache with Include statement
>>
>>
>>
>>Cool. My typical Apache build is:
>>
>>./configure --enable-so --enable-ssl
>>make
>>make install
>>
>>John
>>
>>Denise Mangano wrote:
>>
>>
>>>Yes I am. The problem (right now) definitely appears to be some
>>>issues with Apache. Unfortunately, the Apache list isn't
>>
>>as heavily
>>
>>>trafficked, or as quick to response, so I'm still waiting on some
>>>replies while I search the archives. I think I have to recompile
>>>Apache. I added in a few extra flags when I did this yesterday to
>>>make it more "secure" but I think I am better off just
>>
>>keeping it as
>>
>>>is, then taking out what I don't need later...
>>>
>>>Won't be able to determine if I have a mod_jk problem at
>>
>>all until I
>>
>>>get my Apache running properly.
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: John Turner [mailto:tomcat-user@johnturner.com]
>>>>Sent: Wednesday, August 27, 2003 10:47 AM
>>>>To: Tomcat Users List
>>>>Subject: [OFF-TOPIC] Re: First mod_jk problem - can't start
>>>>apache with Include statement
>>>>
>>>>
>>>>
>>>>Are you loading mod_ssl?
>>>>
>>>>I'm marking this as off-topic because we haven't determined
>>>>that this is
>>>>a JK/Tomcat problem yet.
>>>>
>>>>John
>>>>
>>>>Denise Mangano wrote:
>>>>
>>>>
>>>>
>>>>>Yeah, it appears to be my apache. I still get that
>>>>
>>>>SSLMutex error. I
>>>>
>>>>
>>>>>have to work on getting that resolved.
>>>>>
>>>>>This is the output of httpd -l:
>>>>>
>>>>> http_core.c
>>>>> mod_env.c
>>>>> mod_log_config.c
>>>>> mod_mime.c
>>>>> mod_negotiation.c
>>>>> mod_status.c
>>>>> mod_include.c
>>>>> mod_dir.c
>>>>> mod_cgi.c
>>>>> mod_asis.c
>>>>> mod_imap.c
>>>>> mod_actions.c
>>>>> mod_alias.c
>>>>> mod_access.c
>>>>> mod_auth.c
>>>>> mod_so.c
>>>>> mod_setenvif.c
>>>>> suexec: disabled; invalid wrapper /usr/local/apache/bin/suexec
>>>>>
>>>>>Denise
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: John Turner [mailto:tomcat-user@johnturner.com]
>>>>>>Sent: Wednesday, August 27, 2003 10:25 AM
>>>>>>To: Tomcat Users List
>>>>>>Subject: Re: First mod_jk problem - can't start apache with
>>>>>>Include statement
>>>>>>
>>>>>>
>>>>>>
>>>>>>Hate to say it, but it sounds like your Apache is munged up.
>>>>>>
>>>>>>If you delete the mod_jk.conf Include, and you delete all
>>
>>other JK
>>
>>>>>>stuff
>>>>>
>>>>>>from httpd.conf, your Apache starts up properly, with no errors?
>>>>>
>>>>>
>>>>>>What is the output of "httpd -l"?
>>>>>>
>>>>>>John
>>>>>>
>>>>>>Denise Mangano wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>OK, I tried adding the Jk directives directly into the
>>
>>httpd.conf
>>
>>>>>>>file, and apache at least starts. So the problem is the include
>>>>>>>statement. Is it possible that I don't have whatever module
>>>>>>
>>>>>>is needed
>>>>>>
>>>>>>
>>>>>>
>>>>>>>to support the "Include" statement?
>>>>>>>
>>>>>>>So now the problem is that although apache starts, it does
>>>>>>
>>>>>>not start
>>>>>>
>>>>>>
>>>>>>
>>>>>>>properly. When I run ps -aux | grep httpd I get the following:
>>>>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
>>>>>>>[httpd <defunct>]
>>>>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
>>>>>>>[httpd <defunct>]
>>>>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
>>>>>>>[httpd <defunct>]
>>>>>>> www 8074 0.0 0.0 0 0 ? Z 10:07 0:00
>>>>>>>[httpd <defunct>]
>>>>>>>
>>>>>>>And needless to say I can't get to my web page. Now again I am
>>>>>>>getting those error messages in both my error_log and
>>>>>>
>>>>>>ssl_engine_log:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> [error]mod_ssl: Child could not open SSLMutex lockfile
>>>>>>>/usr/local/apache/logs/ssl_mutex.30776 (System error follows)
>>>>>>> [error]System: Permission denied (errno: 13)
>>>>>>>
>>>>>>>So apparently I have a problem with mod_ssl, which I
>>
>>guess I didn't
>>
>>>>>>>resolve yesterday and should post to the apache list. But the
>>>>>>>question still remains why using the Include statement
>>>>>>
>>>>>>would prevent
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Apache from starting at all?
>>>>>>>
>>>>>>>Thanks for your help :)
>>>>>>>Denise
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>------------------------------------------------------------
>>>>
>>>>---------
>>>>
>>>>
>>>>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>>>>For additional commands, e-mail:
>>
>>tomcat-user-help@jakarta.apache.org
>>
>>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------
>>
>>---------
>>
>>>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>>>For additional commands, e-mail:
>>
>>tomcat-user-help@jakarta.apache.org
>>
>>>>
>>>>
>>>>------------------------------------------------------------
>>
>>---------
>>
>>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
Re: First mod_jk problem - can't start apache with Include statement
(revisited)
Posted by John Turner <to...@johnturner.com>.
I woudl skip the Include statement and modify httpd.conf manually as you
have. For anything but a simple configuration, you have to do it
anyway, so there's no real loss.
John
Denise Mangano wrote:
> Not really sure if this is a problem as of yet. I currently cannot test
> my configuration ... But I just wanted to write again regarding this
> issue. As I followed the how-to, I did things a little out of order.
> Before changing Tomcat, and while Tomcat was not running, I added the
> LoadModule and Include statements into httpd.conf. I then ran an
> apachectl configtest. The configtest executed fine and I was returned
> an error message that the file mod_jk.conf could not be found. This was
> right, because the file was not generated yet.
>