tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/1362-trouble-moving-existing-database-from-win-to-linuxCascade CMS: Discussion 2018-10-18T20:36:54Ztag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-09T18:46:46Z2013-07-09T18:46:46Ztrouble moving existing database from Win to Linux<div><p>Hi Eric,</p>
<p>Thanks for attaching those log files. The <em>cascade.log</em>
file, unfortunately, only contains that repeating error that you
mentioned:<br></p>
<pre>
<code>ERROR [MemoryQueueSearchJobScheduler] An error occurred while consuming from the lucene event queue: java.lang.NullPointerException</code>
</pre>
Whenever you see this message it is an indication that some other
problem has caused Cascade Server to not start properly. Usually
I'm able to see the cause further up in the log file. Since I'm not
seeing the initial startup in the cascade.log, I checked the
catalina.log file you attached and noticed this:<br>
<pre>
<code>LifecycleException: service.getName(): "Catalina"; Protocol handler start failed: java.net.BindException: Address already in use <null>:8080</code>
</pre>
which would seem to indicate that port 8080 is already in use by
either another Cascade Server process or some other random system
process. Can you try the following:
<ul>
<li>Make sure there are no Cascade Server (Java) processes running
on the machine. You can do so in Linux with this command:
<pre>
<code>> ps aux | grep java</code>
</pre>
If you see a Cascade process running, use <code>kill -9
<pid></code> to end it.<br></li>
<li>Restore the most recent copy of your database</li>
<li>Remove the file <em>tomcat/logs/cascade.log</em></li>
<li>Start Cascade against the newly restored database</li>
<li>Wait about 5 minutes or so and see if you can get to the login
screen. If you can't, keep the Cascade Server process running and
attach your most recent <em>cascade.log</em> file here</li>
</ul>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-09T20:30:54Z2013-07-09T20:30:54Ztrouble moving existing database from Win to Linux<div><p>Thanks! There were indeed several Cascade processes running.
Here's the new logs.</p></div>Eric L. Eppstag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-10T13:53:57Z2013-07-10T13:53:57Ztrouble moving existing database from Win to Linux<div><p>Hi Eric,</p>
<p>Sorry for the delay here. For some reason I didn't get an email
notification yesterday after your response.</p>
<p>Can you tell me what database you are starting Cascade up
against? The reason I ask is because I can see from the log file
that Cascade is applying <strong>all</strong> updates dating way
back to the 5.5 series. This would seem to indicate that the
<code>DATABASECHANGELOG</code> table in your database is either
non-existent to begin with or doesn't have the appropriate
permissions configured (so Cascade isn't able to see that
table).</p>
<p>Can you check to see if that table exists in your database prior
to attempting the upgrade?</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-10T13:59:56Z2013-07-10T13:59:56Ztrouble moving existing database from Win to Linux<div><p>Ah, I think I see the problem. Looks like it's looking for
<code>DATABASECHANGELOG</code> and not finding it because
everything's in lowercase <code>databasechangelog</code>.</p>
<pre>
<code>+-------------------------------+
| Tables_in_contentxml |
+-------------------------------+
| DATABASECHANGELOG |
| DATABASECHANGELOGLOCK |
| cxml_aclentry |
| cxml_assetfactory |
| cxml_assetfactorycontainer |
| cxml_assetfactoryplugin |
| cxml_assetfactorypluginparam |
| cxml_assetstats |
| cxml_audit |
| cxml_blob |
| cxml_con_page_mapping |
| cxml_condexec |
| cxml_configurationfile |
| cxml_conn_ctype_link_param |
| cxml_connector |
| cxml_connector_ctype_link |
| cxml_connectorcontainer |
| cxml_connectorparameter |
| cxml_contenttype |
| cxml_contenttypecontainer |
| cxml_ct_pageconfig_dest |
| cxml_ct_pageconfiguration |
| cxml_dbpub_entity |
| cxml_dbpub_metadata |
| cxml_dbupdate |
| cxml_destination |
| cxml_dynamicmetadatafield |
| cxml_dynamicmetadatafielddef |
| cxml_entitylock |
| cxml_entitymetadata |
| cxml_entityrelation |
| cxml_foldercontent |
| cxml_folders_wfdefs |
| cxml_group |
| cxml_group_membership |
| cxml_last_modified |
| cxml_lock |
| cxml_login |
| cxml_mail |
| cxml_metadataset |
| cxml_metadatasetcontainer |
| cxml_pageconfigsetcont |
| cxml_pageconfiguration |
| cxml_pageconfigurationset |
| cxml_pageregion |
| cxml_permissions |
| cxml_preferences |
| cxml_publishrequest |
| cxml_publishrequest_config |
| cxml_publishrequest_dest |
| cxml_publishset |
| cxml_publishsetcontainer |
| cxml_publishsetrecord |
| cxml_recyclerecord |
| cxml_role_group_link |
| cxml_role_group_site_link |
| cxml_role_user_link |
| cxml_role_user_site_link |
| cxml_roles |
| cxml_site |
| cxml_site_roles |
| cxml_structureddata |
| cxml_structureddatadefcont |
| cxml_structureddatadefinition |
| cxml_systemproperty |
| cxml_target |
| cxml_transport |
| cxml_transportcontainer |
| cxml_unpublishable |
| cxml_user |
| cxml_userlexicon |
| cxml_workflow |
| cxml_workflowaction |
| cxml_workflowdefcontainer |
| cxml_workflowdefinition |
| cxml_workflowhistory |
| cxml_workflowstep |
| cxml_workflowtrigger |
| cxml_workflowtriggerparameter |
| cxml_xml |
| databasechangelog |
| databasechangeloglock |
| qrtz_blob_triggers |
| qrtz_calendars |
| qrtz_cron_triggers |
| qrtz_fired_triggers |
| qrtz_job_details |
| qrtz_job_listeners |
| qrtz_locks |
| qrtz_paused_trigger_grps |
| qrtz_scheduler_state |
| qrtz_simple_triggers |
| qrtz_trigger_listeners |
| qrtz_triggers |
+-------------------------------+
94 rows in set (0.00 sec)</code>
</pre></div>Eric L. Eppstag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-10T14:33:21Z2013-07-10T14:33:21Ztrouble moving existing database from Win to Linux<div><p>Ah, yep that's it. That seems like it's due to the Windows ->
Linux migration of the database. Looking at the tables in your
database, it seems that the <code>qrtz...</code> tables may also be
an issue. Take a look at the <code>lower-case-tables</code> option
in MySQL and see if configuring that helps:</p>
<p><a href=
"http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html">
http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity....</a></p>
<p>Let me know what you find and I'll be more than happy to help
you investigate further.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/276945122013-07-10T15:08:33Z2013-07-10T15:08:33Ztrouble moving existing database from Win to Linux<div><p>Set <code>lower_case_table_names=1</code>, reimported the
database and it updated fine. Thanks!</p></div>Eric L. Epps