We have some updates for the linux installer
Firstly, we have improved lucee_ctl behaviour, thanks to @kenricashe
https://luceeserver.atlassian.net/browse/LDEV-5945
I made a bunch of improvements to lucee_ctl which I’ve been running in production for more than a year, and I’m sure everyone would benefit from this enhanced version.
@Zackster let me know if it’s okay for me to submit a pull request?
Secondly, we now support service name also on linux, so side by side installs don’t conflict with lucee_ctl
thanks to @MiniFireDragon for raising this
https://luceeserver.atlassian.net/browse/LDEV-5944
I am running out of tinker space, so before I destroy a perfectly good working install of Lucee 6 to test, I thought I would just query those who may know better.
If I use the Lucee 7 Installer, will Lucee 6 (current release) still work?
My method of installing is to take the war folder and drop it into the webapps folder, and do some binds to merge the web-inf into a public_html folder and use ajp. And since the installer takes care of the Tomcat setup mumbo jumbo, I now prefer using it (spo…
In addition, the install scripts now fail fast, rather than silently failing and then waiting 30s for tomcat to start
I spent a lot of time getting the whole test CI for these installers, makes improving this a lot easier!
There are sample Lucee 7.0.0.395 installers here for testing at the bottom of the page
Build Lucee Installer #377
These improvements will be part of the upcoming 6.2.4 and 7.0.1 releases
3 Likes
So, for example, the service names could be lucee6_ctl and lucee7_ctl?
Just finally also updated the Linux installer to support systemd by default
https://luceeserver.atlassian.net/browse/LDEV-5948
Test 7.0.0.395 builds at the bottom of this page
Build Lucee Installer #392
1 Like
I’ve noticed how systemctl doesn’t have the verbose output provided by lucee_ctl, which is why I generally still prefer the latter, not only for manual control, but also I have a cron job that checks the running status of Lucee every minute.
I now realize that with the new systemd support, I could update my bash script to get the running status as a boolean via:
systemctl is-active --quiet lucee_ctl
But the verbose output from the lucee_ctl script is still preferred for the manual start, stop, and restart options.
With that in mind, I see that the new service file from LDEV-5948 does not include:
SuccessExitStatus=143
In my October post about systemd and SELinux , my example service file has a comment with a link to a fascinating blog post by PJB:
I wonder if that could be related to the issue of systemd losing track of the Lucee service when using the lucee_ctl script directly?
yeah, that’s what I encountered with the extended CI tests for this
hence my github actions, walk of shame
