Thanks, Adrian... Syntax error on line 4 of /usr/local/tomcat/conf/auto/mod_jk.conf: Can't locate API module structure `jk_module' in file /usr/local/apache2/modules/mod_jk.so: ld.so.1: /usr/local/apache2/bin/httpd: fatal: jk_module: can't find symbol
Mine's saying mod_jk.so is there, but there's no API structure 'jk_module'? I got this binary from jakarta via John Turner's how-to since I've been having problems compiling it myself and I'm almost positive all of this is related in some way to a root problem with my libraries or something. [ j o h n ] -----Original Message----- From: adrian [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 12:27 PM To: Tomcat Users List Subject: Re: mod_jk tomcat/apache connector issue One more idea, look at mod_jk.conf, I had the same error last night. Line 4 dictates where mod_jk.so is located. I ran apachectl configtest and it told me that mod_jk was not located at /etc/httpd/libexec/ I included the modJk=/usr/lib/apache/mod_jk.so , but it didn`t work until I put mod_jk.so where it was looking. Line 4 is the include for mod_jk.so. Sounds like the same problem. I was wrong about the connector, John said last night the JK2 connectors backwards compatable with jk. John Bullock wrote: >Thanks Adrian... I commented out the JK2 connector in server.xml and >uncommented the JK connector... still got the 'syntax error on line 4' error >message when attempting to start apache. > >I also followed the instructions for trying to build coyote/JK2 on the URL >you posted before I gave up and tried to do mod_jk instead... the mod_jk2 >problems I had were in step 8 where you run 'ant native'... the 'ant' in the >root gave me jtc.jar with no problems, but when I did 'ant native' in the >/jk directory, the build failed with the following: > > [so] StdErr: > [so] ld: warning: option -o appears more than once, first setting >taken > [so] ld: fatal: file mod_jk.so: cannot open file: No such file or >directory > [so] ld: fatal: File processing errors. No output written to >.libs/mod_jk.so > [so] collect2: ld returned 1 exit status > >Tried rebuilding from scratch and all sorts of things before throwing in the >towel and following John Turner's how-to, but I can't seem to get that one >to work either... I must be missing something because I know it can't be >this hard to get it to work. :( > >[ j o h n ] > > > > >>The reason I asked was the default connector on 8009 is for JK2 , right >>below it commented >>out is the jk connector, I had to make the change recently for an >>Apache2 config. >>Also for building mod_jk, check out >>http://www.pubbitch.org/jboss/mod_jk2.html, >>may give a little insight. >> >> > > >-----Original Message----- >From: adrian [mailto:[EMAIL PROTECTED]] >Sent: Monday, January 06, 2003 5:56 PM >To: Tomcat Users List >Subject: Re: mod_jk tomcat/apache connector issue > > >John Bullock wrote: > > > >>I'll try to explain.. :) >> >>For a long time, I've tried to build mod_jk with the 4.1.18 connectors >>package to no avail... it wouldn't give any errors, but I'd wind up with a >>mod_jk.la file (617 bytes) and no .so file whatsoever. >> >>Using a link from John Turner's how-to, I downloaded a pre-compiled binary >>of mod_jk and followed the configuration steps. >> >>Just in case: >>http://www.johnturner.com/howto/apache2-tomcat4112-sol8-howto.html >> >>[ j o h n ] >> >>-----Original Message----- >>From: adrian [mailto:[EMAIL PROTECTED]] >>Sent: Monday, January 06, 2003 5:38 PM >>To: Tomcat Users List >>Subject: Re: mod_jk tomcat/apache connector issue >> >> >>John Bullock wrote: >> >> >> >> >> >>>Haven't seen this anywhere, but when I try to start apache (2.0.43) with >>> >>> >>> >>> >>the >> >> >> >> >>>mod_jk module enabled, I get: >>> >>>#apachectl start >>>Syntax error on line 4 of /usr/local/tomcat/conf/auto/mod_jk.conf: >>>Can't locate API module structure `jk_module' in file >>>/usr/local/apache2/modules/mod_jk.so: ld.so.1: >>> >>> >>> >>> >>/usr/local/apache2/bin/httpd: >> >> >> >> >>>fatal: jk_module: can't find symbol >>># >>> >>>Tomcat starts up correctly with working examples, however. I think this >>> >>> >is > > >>>a library issue, though it seems like it'd happen more often and be in the >>>FAQ? >>> >>>using: >>>Tomcat 4.1.18 >>>Apache 2.0.43 >>>Java 1.4.1_01-b01 >>> >>>[ j o h n ] >>> >>> >>>-- >>>To unsubscribe, e-mail: >>> >>> >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >> >> >>>For additional commands, e-mail: >>> >>> >>> >>> >><mailto:[EMAIL PROTECTED]> >> >> >> >> >>> >>> >>> >>> >>> >>Are you using mod_jk or mod_jk2 ? Tomcat 4.1.18 is setup for jk2 by >> >> >default. > > >> >>-- >>To unsubscribe, e-mail: >><mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: >><mailto:[EMAIL PROTECTED]> >> >> >>-- >>To unsubscribe, e-mail: >> >> ><mailto:[EMAIL PROTECTED]> > > >>For additional commands, e-mail: >> >> ><mailto:[EMAIL PROTECTED]> > > >> >> >> >> >> >The reason I asked was the default connector on 8009 is for JK2 , right >below it commented >out is the jk connector, I had to make the change recently for an >Apache2 config. >Also for building mod_jk, check out >http://www.pubbitch.org/jboss/mod_jk2.html, >may give a little insight. > > > > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
