This errors occurs when setting up an AWS RDS MySQL datasource in Lucee Administator. It occurs when the database is deleted and re-created. The endpoints stay the same, all AWS settings remain the same. If I use a fresh Lucee instance… it will setup a new connection just fine. Every time a database is recreated, Lucee will no longer make a db connection and gives the following error.
Cannot open file:/opt/lucee/tomcat/lucee-server/context/security/cacerts [Keystore was tampered with, or password was incorrect]
I have restarted the server. It appears that once a datasource connection is made, that authorization or verification to the db domain is saved somewhere. When the database is deleted and recreated… for example, I changed from MySQL 5.6 to 5.7… it will not authorize anymore.
I’m able to go to a fresh install of Lucee and create a new datasource connection to the new database.
Even when I went from 5.7 back to 5.6… same thing… a previously connected Lucee will not connect to a new database.
This is the complete stacktrace from the error as logged in application.log (web-inf).
It implies that the keystore password authentication failed. Found that its default password is “changeit” and never changed it .
I had this same issue the other day. It was because MySQL changed the authentication mechanism. I had to go with the “Legacy” authentication rather than the more “Secure” method they auto select on install. I can’t remember the exact terms used off the top of my head right now but if you re-install MySQL just pay attention to the steps and make sure to go with the older authentication method.
I just re-read your problem and it sounds like it is slightly different than the one I was experiencing but I was receiving the same error as you. A fresh Lucee install wasn’t working for me. Hope you get it figured out.
I got it fixed by manually adding the data-source to the lucee\tomcat\lucee-server\context\lucee-server.xml file Then restarted lucee and it was working. I’m on the cfml:lucee Slack channel if you have any questions.
I just tried adding the datasource in application.cfc and providing a bunch of extra params found here, but that didn’t work.
I managed to add the datasource in de server.cfm interface by unchecking ‘verify connection’, and then as you suggested edited lucee-server.xml. The datasource will be defined there after it is added in the server.cfm interface, so all i had to do is add 2 values to the “custom” attribute:
Im am having (what i think is the same problem) with connecting Lucee 5.2.7.063 datasource to MySQL 8.0…
I’m having to use windows 7(6.1) 64bit (I know not my choice)
I have aslo updated my lucee extensions and also downloaded the “Oracle 12c 12.1.0.2 (release 1)” (tested before and after) because MySQL is an oracle product.
I have also gone to “lucee\tomcat\lucee-server\context\lucee-server.xml” and updated my datasource tag by adding
&useSSL=false&requireSSL=false
to the end of custom var within the tag shown below
To clarify i am getting the error message “Cannot open file:/opt/lucee/tomcat/lucee-server/context/security/cacerts [Keystore was tampered with, or password was incorrect]”
I’ve also inputed the datasource without verifying, then manually edited the lucee-server.xml file restarted lucee without success.
Your edits to <data-source> seem good. Your error message is exactly the same as i got, and you’ve restarted. Your case looks a lot like what i had.
The only minor difference i can spot is that I’m not using mysql root user in the datasource. I had authentication issues before with mysql and root user, so it could be related, but it’s a long shot.
I also didn’t bother with an oracle download and running on ubuntu …
Thank you Jan i’ll shall be trying this tomorrow and ill let you guys know how i get on. I think it’s probably old windows and i’m going to have to get my client onto a newer version…
Again thanks for looking at this.
Hi guys, I’ve seen this come up a number of times now in CFML Slack, here (obviously!) and in other Slack channels. I haven’t followed it super close but it sure sounds like something needs addressed in Lucee for this. I don’t see an issue in the JIRA tracker after searching for the error message. Can someone spearhead getting this into the Lucee issue tracker if there is indeed an issue here? For instance, turning off SSL may get it working as a workaround, but that sounds like work needs done in Lucee to support SSL correctly.
Just a quick note in case anyone else is hitting this…
I couldn’t get the work around to work until I deleted the datasource in Lucee admin, created it again and DID NOT click on Verify Connection. Just save it without verifying. I stopped lucee and then added the extra config (as noted in earlier comments) to lucee-server.xml. Restart lucee and verify from the main Services -Datasource page. Tested on Lucee 5.2.80 / MySQL 5.7.23
In other words do not verify when setting up the datasource in lucee admin.
Running Lucee 5.2.9.31 with Tomcat 8 and MySQL 8 (legacy authentication)
OK, working from gusjohnson’s input, I tried the following several times:
o deleted the data source from the Server Admin page
o created the data source from the Server Admin page without verification
o stopped the Lucee service
o edited the lucee-server.xml file and saved the file
o started the Lucee service
o from the Server Admin page, verified the data source
ERROR! - every time. Strangely, there is no output added to data source.log or any other log in the Lucee logs folder.
EDIT: testing with Lucee 5.3.1.87, Tomcat 8, MySQL 8 under CommandBox, I get a similar result of a verification error with no output to log files.
In lucee-server.xml look for the data source element for your database connection and then edit the custom attribute, ie append: &useSSL=false&requireSSL=false
.