Cascade 7 failing to initialize
Hey, Cascade 7 was running well on our test server, until I made some changes and restarted the server. Now it seems to start but has some errors marked SEVERE and gives a 404 on access.
The only change made was an update to the database to make it match our live version of Cascade, which may be at issue here, the logs show problems with the database.
I've attached the catalina.out
- catalina.out 49.4 KB
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Mike on 09 May, 2012 05:29 PM
Hello,
It sounds/looks like you may have upgraded a database that was already upgraded with a beta version of Cascade. If this is the case, you will have to start with a fresh database dump from your production instance (or any instance that is running a production release of Cascade) as we do not support upgrading from a beta version of Cascade to a production version. Let me know if that resolves your issue. Thanks!
3 Posted by cpayan on 09 May, 2012 05:50 PM
No, the upgrade was from 6.10.5. Should I make a new mysqldump from our production server, then reinstall Cascade 7? And what does this mean for upgrading our production from 6.10.5 to 7?
Support Staff 4 Posted by Mike on 09 May, 2012 05:59 PM
Yes, I would start over with a fresh database dump. I'm not sure if maybe the database was partially upgraded or not. This can happen if you shut down the server before it has finished applying database updates. Usually when we see messages like "Table 'xyz' already exists", it means that a database update is being applied for a second time when it should not be. In rarer cases, this can happen when the account used to connect to the database is not configured correctly.
You shouldn't have to reinstall Cascade 7 as long as your context.xml file (found in /<cascade install directory>/tomcat/conf) is pointing to the correct test database. If you're not sure, then I would go ahead and do a fresh install. Make sure that there are no other Cascade instances running against the database you are trying to upgrade.
Upgrading your production instance should be as simple as installing Cascade 7 and pointing it to your existing production database (after having shut down the other version of Cascade, 6.10.5 in your case). Remember to always back up your database before doing a production upgrade.
5 Posted by cpayan on 09 May, 2012 06:26 PM
So... how would I be able to make sure that the production database is inactive before getting a dump from it? Wait until low-use time, shut down the server, and get a mysqldump?
Support Staff 6 Posted by Mike on 09 May, 2012 07:20 PM
As long as Cascade is not running, the database should be inactive.
7 Posted by cpayan on 10 May, 2012 07:16 PM
Hmm, I don't know, after making sure the database was not being molested and taking the mysqldump at that point, then using that copy for the dev environment, I still get the same errors about cxml_unpublishable and so on.
I suppose I'm going to try reinstalling Cascade without changing the database and seeing what that gives.
8 Posted by cpayan on 10 May, 2012 07:27 PM
The reinstall over the existing DB didn't help. The current database it's using was dumped when cascade wasn't running, so it couldn't be in the process of changes.
Support Staff 9 Posted by Tim on 10 May, 2012 07:54 PM
Can you please attach your most recent cascade.log file? We'll want to see if the error message is the same as the one that appeared previously.
Also, can you attach the results of the following query (run against a copy of the database on which the upgrade has not been attempted):
Thanks
10 Posted by cpayan on 11 May, 2012 05:23 PM
All right, here are the results. The query results are in query.out
Support Staff 11 Posted by Bradley Wagner on 11 May, 2012 06:07 PM
Hi, this is odd. Your query results tell us that your database should have been running Cascade 6.10 prior to the upgrade but your log is saying that the database already contains a table (cxml_unpublishable) that is new to 7.0 and that it is trying to add during the upgrade.
Can you try:
show tablesagainst your MySQL databaseSupport Staff 12 Posted by Bradley Wagner on 11 May, 2012 06:14 PM
Also, your log indicates that Cascade is only attempting to apply database update 7_0_010 during the upgrade which would indicate that updates 7_0_001 to 7_0_009 had already been applied. Yet, your query of your DATABASECHANGELOG table shows that no 7_0_x updates have been applied yet.
Is it possible your server is pointed at a different database than the one you're examining? Can you include your tomcat/conf/context.xml file and a brief overview of the names and locations of the databases you're using?
13 Posted by cpayan on 11 May, 2012 07:28 PM
All right, I've completely scrubbed everything out from the database in the dev site and gave it a fresh backup from our live server and it's worked fine. I think the problem was that I didn't delete everything in the database before giving it the db from the live server, which had the 6.10 tables.
So here's what happened:
I guess I should have known better, but this hasn't been a problem the last few upgrades in the 6.10.x series, so live and learn.
cpayan closed this discussion on 11 May, 2012 07:28 PM.