Closed OyvindLGjesdal closed 3 years ago
I am also seeing this issue. It may make sense to make the AJP section in the template an optional section, so that when not using AJP, this error does not occur.
I can try and put together a PR for this.
Hi,
I'll try to reproduce the issue and write a fix. Back later!
Thanks for reporting and replying to the issue.
Hi and thanks for the fix.
I added the same change as 22c72f in a fork of the repo, but was a bit unsure of PRing it, since it reintroduces the old default behaviour of tomcat. Could @williampiv's suggestion of having AJP be an optional block, and then requiring a secret by default if enabled be an option? I may also just be overthinking the problem.
I've made a suggestion in the last version (4.7.0).
Have a look, see if this works for you. I'll close this issue, but feel free to open it when changes are required.
Regards, Robert de Bock.
Describe the bug
Tomcat systemd service refuses to start, due to mandatory secret missing from server.xml (template.)
This was introduced in; Tomcat 7.0.100, Tomcat 8.5.59, and tomcat 9.0.31, according to the logs, which is less than the default version for tomcat 7 and 9 values.
From the changelog:
I don't know what would be the best way to solve in the server.yml template. Having a
instance.ajp_secret
variable on the ajp Connector element, with a default secret generated, or should the default requiredSecret attribute be set to false?I added a secret attribute manually on the box, and the service then started.
--
Playbook
Output
Play does not report error, but
sudo systemctl status tomcat-version-9
shows:Environment