Lucee Crashes every week

Hi everyone,

My server is running on Windows. I had Lucee version 6.2 installed. One day, when I opened the Lucee Admin panel, I saw a notification that version 7 was released. I was happy and clicked to upgrade.

Unfortunately, after some time the installation crashed and Lucee did not start anymore. I finally managed to uninstall and delete folders of Lucee and install version 6.2.1.122.

But now I have a strange problem:
Every week, usually on Wednesday morning, and sometimes in the middle of the week, my website (running on Lucee) starts throwing errors saying that the Data Source Names (DSNs) are not defined.

When I try to open the Lucee Admin panel, I get this error:

Page [/lucee/admin/index.cfm] not found
Detail: File not found: C:\lucee\tomcat\lucee-server\context\context\admin\index.cfm

The only way I can fix this is by uninstalling Lucee completely and reinstalling it again, but this is very time-consuming.

Has anyone else experienced this?
What is causing the /context/context/ issue and the disappearing DSNs every week?
How can I fix this permanently?

Any help would be really appreciated.

Thank you!

I had a similar issue, we had multiple servers updating one Lucee servers scheduled tasks, so config got corrupted.

Maybe you can check if .CFConfig.json was changed (backup and then compare)?

Thank you for the tip.
Today is Wednesday and the problem happened again. I checked and it was exactly the .CFConfig.json file that got changed. I restored it from backup and everything worked again.

The only extra thing I had to do was reinstall the cfimage extension in the applications, otherwise they were throwing errors.

Do you have any idea how I can prevent this from happening again? Is there a way to stop Lucee (or some other process) from overwriting .CFConfig.json every week?

Glad that it helped. As a temp fix, we locked all cfschedule calls in our code. I already filed a bug report and hope that it will be fixed with the next version.

Do you have any code which updates the config file, like mentioned: cfschedule…

1 Like

there’s a much better approach I’ve just written up

1 Like