-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neil,
Neil Wilson wrote: > Christopher Schultz wrote: >> Okay. Using RPM, you ought to be able to figure out version numbers and >> stuff, though. I'd bet that mod_jk has its own RPM package, but I >> couldn't tell you what it's called. Try listing all packages and search >> for "jk" or something. Another thing you can do is find the mod_jk.so >> binary and run this on it: >> >> $ strings /path/to/mod_jk.so | grep mod_jk/ > > OK, couldn't get the info using rpm so with strings I go the following. > > mod_jk/1.2.14 You probably ought to upgrade. 1.2.14 is pretty old: the current version is 1.2.25. You can look at the changelog at http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html to see if anything important changed for you (and might break a delicate configuration). You can find out which package included mod_jk.so by using rpm to search for it. I don't have any systems handy that have RPM on them anymore, so you'll have to poke around the man page to find out how you can say "which package owns this file?". You might have to upgrade Tomcat (d'oh!) in order to get the upgraded mod_jk. You could always compile it yourself if necessary. >>> I've checked and this file does NOT exist, should I touch it with the >>> correct ownership/permissions? >> >> Not yet. Does the directory exist, and just not the file? If so, maybe >> you should create the file. > > Ok, the directory does exist, but the file doesn't, I'm not using SSL, > so I'm guessing that this won't affect it much. Well, the error you're getting is from mod_jk and doesn't have anything to do with SSL. mod_jk uses shared memory (I think) for it's status worker. It's not really necessary to get it working (mine was giving me the same startup error, but with no other adverse effects). > I've searched through all the files in that directory and can't find > anything relating to shared memory, the only thing that slightly > resembles it is "cachesize=10" No, that's a worker-specific setting (which has been deprecated in newer versions of the library, btw). Unless you are using threaded Apache (worker, not pre-fork), this setting is useless (see the docs). The docs suggest that setting this higher than 1 on Apache 1.3 or Apache 2.x prefork is a bad idea. It's possible that this could be affecting you. You might want to remove this setting for now. > JkWorkerProperty worker.mail.lbfactor=50 Are you using a load-balanced configuration? If not, remove this directive. > JkWorkerProperty worker.mail.cache_timeout=600 Like cacheize, this directive has been deprecated (with a replacement) in newer versions of the library. > JkWorkerProperty worker.mail.recycle_timeout=300 Like cacheize, this directive has been deprecated (with a replacement) in newer versions of the library. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHHfyA9CaO5/Lv0PARAnXxAJ9+gzxkRbDOfNl3yGgThyIpF8ik/ACcCCRW LMJz17a/w2fe/M7cZ293C5Q= =sRsp -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
