One of the reasons that jk2 is a beta :-). It looks like it is trying to use the "standard" Apache layout and not handling the "RedHat" layout. My suggestion is to file a bug at: http://nagoya.apache.org/bugzilla/ so that it won't get lost in all of the "I don't understand..." messages.
I'm not a Jk2-native expert, but I believe that you can work-around this by including a directive in your httpd.conf file like: JkSet conf:file etc/httpd/workers2.properties "Theodore A. Jencks" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... I'm getting a strange error when starting apache 2.0.43 running on Redhat Linux 8.0 mod_jk2 version 2.0.2. Here is what apache reports: [Tue Dec 10 18:30:29 2002] [error] config.update(): Can't find config file /etc/httpd/conf/workers2.properties [Tue Dec 10 18:30:29 2002] [error] shm.init(): No file [Tue Dec 10 18:30:29 2002] [notice] Apache configured -- resuming normal operations [Tue Dec 10 18:30:29 2002] [error] shm.init(): No file [Tue Dec 10 18:30:29 2002] [error] mod_jk child init 1 0 [Tue Dec 10 18:30:30 2002] [error] shm.init(): No file [Tue Dec 10 18:30:31 2002] [error] shm.init(): No file [Tue Dec 10 18:30:31 2002] [error] shm.init(): No file [Tue Dec 10 18:30:32 2002] [error] shm.init(): No file [Tue Dec 10 18:30:32 2002] [error] shm.init(): No file [Tue Dec 10 18:30:32 2002] [error] shm.init(): No file [Tue Dec 10 18:30:32 2002] [error] shm.init(): No file This is rather strange since I've got workers2.properties configured like this: [config:] file=/etc/httpd/workers2.properties debug=0 debugEnv=0 [shm:] info=Scoreboard. Required for reconfiguration and status with multiprocess servers file=/opt/tomcat/logs/httpd/jk2.shm size=1000000 debug=0 disabled=0 When I copy workers2.properties to /etc/httpd/conf/workers2.properties it finds the config file. I'm just wondering what causes jk2 to look for the workers2.properties file in /etc/httpd/conf when all my apache conf files are just in /etc/httpd/httpd.conf Regards, Theo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
