> Nov 21 18:32:37 server2 httpd[24339]: Invalid command 'JkWorkersFile',
> perhaps misspelled or defined by a module not included in the server
> configuration
That means that there was no LoadModule line for mod_jk before that
config line. You originally posted the first config line "LoadModule
jk_module modules/mod_jk.so" bus either the module was located somewhere
else, or - more likely - during this attempt here the LoadModule line wa
sno longer in place.
[Wed Nov 21 15:54:19.916294 2018] [jk:warn] [pid 11957] No JkShmFile
defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Wed Nov 21 15:54:19.916632 2018] [jk:emerg] [pid 11957] Initializing
shm:/etc/httpd/logs/jk-runtime-status.11957 errno=13. Unable to start due
to shared memory failure.
[Wed Nov 21 15:54:19.916639 2018] [jk:emerg] [pid 11957] Initializing
shm:/etc/httpd/logs/jk-runtime-status.11957 errno=13. Unable to start due
to shared memory failure.
errno=13 means access error, so the user who runs the httpd server does
not have rights to create a shared memory file at
/etc/httpd/logs/jk-runtime-status.11957. Have a look at
/etc/httpd/logs/, check whether it exists and whether the httpd runtime
user has full rights on the directory. If you can not get rights there,
choose another path where you have rights and set it using
JkShmFile "/path/to/my/jk-runtime-status"
[Wed Nov 21 15:54:19 2018] [11957:140478724515968] [warn]
jk_map_handle_duplicates::jk_map.c (456): Duplicate key $
That is weired and doesn't match the config you posted. Especially since
you didn't use either a worker mapping properties file not any JkMount
directive. So either with the above problems fixed, i would not expect
you mod_jk to get any requests passed over from httpd to handle them.
Also the config in your workers.properties doesn't look really good. i
suggest you look at the exaple config you received inside
tomcat-connectors-1.2.46-src.tar.gz and start form there. But first fix
the above first two errors.
Regards,
Rainer
Am 21.11.2018 um 19:41 schrieb Lou Wallace:
Hey Greg,
Thanks for the info. I changed both httpd.conf and workers.properties to
your settings. Got the same error msg when I restarted httpd.
When I checked journalist I get
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-11-21 18:32:37 UTC;
3min 51s ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 24340 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited,
status=1/FAILURE)
Process: 24339 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND
(code=exited, status=1/FAILURE)
Main PID: 24339 (code=exited, status=1/FAILURE)
Nov 21 18:32:37 server2 systemd[1]: Starting The Apache HTTP Server...
Nov 21 18:32:37 server2 httpd[24339]: AH00526: Syntax error on line 63 of
/etc/httpd/conf/httpd.conf:
Nov 21 18:32:37 server2 httpd[24339]: Invalid command 'JkWorkersFile',
perhaps misspelled or defined by a module not included in the server
configuration
Nov 21 18:32:37 server2 systemd[1]: httpd.service: main process exited,
code=exited, status=1/FAILURE
Nov 21 18:32:37 server2 kill[24340]: kill: cannot find process ""
Nov 21 18:32:37 server2 systemd[1]: httpd.service: control process exited,
code=exited status=1
Nov 21 18:32:37 server2 systemd[1]: Failed to start The Apache HTTP Server.
Nov 21 18:32:37 server2 systemd[1]: Unit httpd.service entered failed state.
Nov 21 18:32:37 server2 systemd[1]: httpd.service failed.
On Wed, Nov 21, 2018 at 11:31 AM Greg Huber <gregh3...@gmail.com> wrote:
For my centos/mod._jk I use :
/etc/httpd/conf.d/my.conf :
...
JkWorkersFile "/etc/httpd/conf.d/workers.properties"
JkLogFile "/etc/httpd/logs/mod_jk.log"
JkShmFile "/etc/httpd/logs/jk-runtime-status.log"
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
....
JkMount / worker1
JkMount /* worker1
....
workers.properties :
# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
worker.worker1.socket_keepalive=1
On Wed, 21 Nov 2018 at 16:19, Lou Wallace <mrlouwall...@gmail.com> wrote:
Hi Everyone,
So still having issues with mod_jk. I have downloaded
wget
http://www.eu.apache.org/dist/tomcat/tomcat-connectors/jk/tomcat-connectors-1.2.46-src.tar.gz
wget
http://www.eu.apache.org/dist/tomcat/tomcat-connectors/jk/tomcat-connectors-1.2.46-src.tar.gz.sha1
and make install, and everything seems fine
I then edited the httpd.conf file and added
LoadModule jk_module modules/mod_jk.so
JkWorkersFile "/etc/httpd/conf/workers.properties"
JkLogFile "/var/log/mod_jk.log"
JkLogLevel info
JkLogStampFormat "[%a %b %d %H:%M:%S %Y] "
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
JkRequestLogFormat "%w %V %T"
then I edited workers.properties and added
worker.list=app1,app2
worker.app1.type=ajp13
worker.app1.host=app1.example.com
worker.app1.port=8201
worker.app1.socket_timeout=10
worker.app2.type=ajp13
worker.app2.host=app2.example.com
worker.app2.port=8201
worker.app1.socket_timeout=10
Then when I restart Apache using systemctl restart httpd I get
Job for httpd.service failed because the control process exited with
error
code. See "systemctl status httpd.servic
e" and "journalctl -xe" for details.
So checking mod_jk log I see
[Wed Nov 21 15:54:19 2018] [11957:140478724515968] [warn]
jk_map_handle_duplicates::jk_map.c (456): Duplicate key $
and the httpd log last entries are
[Wed Nov 21 15:54:13.789384 2018] [mpm_prefork:notice] [pid 7569]
AH00170:
caught SIGWINCH, shutting down gracefully
[Wed Nov 21 15:54:19.910325 2018] [core:notice] [pid 11957] SELinux
policy
enabled; httpd running as context system_u:system_r:httpd_t:s0
[Wed Nov 21 15:54:19.911278 2018] [suexec:notice] [pid 11957] AH01232:
suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Nov 21 15:54:19.916294 2018] [jk:warn] [pid 11957] No JkShmFile
defined in httpd.conf. Using default /etc/httpd/logs/jk-runtime-status
[Wed Nov 21 15:54:19.916632 2018] [jk:emerg] [pid 11957] Initializing
shm:/etc/httpd/logs/jk-runtime-status.11957 errno=13. Unable to start due
to shared memory failure.
[Wed Nov 21 15:54:19.916639 2018] [jk:emerg] [pid 11957] Initializing
shm:/etc/httpd/logs/jk-runtime-status.11957 errno=13. Unable to start due
to shared memory failure.
I am not sure if the first 3 are connected to mod_jk, I included them for
those who know far more then me (almost everyone I suspect) just in case
And ideas, hints or thoughts?
Thanks!
Lou
On Fri, Nov 16, 2018 at 9:56 AM Lou Wallace <mrlouwall...@gmail.com>
wrote:
Hi All,
I am in need of some help in getting mod_jk installed on a new google
cloud server.
Right now it has Apache, Tomcat, Java, mysql, perl and python
installed.
But mod_jk isn't there.
When I try yum install mod_jk it isn't found in any of the mirrors.
I've been to the Tomcat site and when I try and get binaries or source
it
sees I am on a windows pc and forces me to those directories.
So, if someone can give me a simple set of commands to do this it would
be
awesome. Also is there other tomcat connectors needed with java?
Preferable it will be done from the ssh client on the cloud server.
Thanks!
Lou
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
