Bug#581790: libapache2-mod-jk: tomcat auto-configure could be easier

Diederik de Haas didi.debian at cknow.org
Sat May 15 22:40:46 UTC 2010


Apparently I didn't figure it out properly, since /etc/libapache2-mod-jk/mod_jk-auto.conf did not get 
created, despite tomcat6 starting succesfully and webserver_howto/apache.html saying:
"Then restart Tomcat and mod_jk.conf should be generated."
locate didn't find mod_jk.conf or mod_jk-auto.conf

Which resulted in apache2 not (re)starting anymore:
Syntax error on line 1 of /etc/apache2/httpd.conf: Could not open configuration file /etc/libapache2-
mod-jk/mod_jk-auto.conf: No such file or directory

Also looking at the apache2 log files, it seems that that auto-configure 'just' doesn't work, so I'll 
go with the method defined in the README.Debian (Custom mod_jk configuration).

Although the error seems to be on my side, I'm not closing the bug just now since I believe it 
should be mentioned that the auto-configure option doesn't work (properly) on a (standard) debian 
install.





More information about the pkg-java-maintainers mailing list