Print  
Gray star Gray star Gray star Gray star Gray star --Not rated--
776 Visits 10 Comments
Created
Mark Behrens Mark Behrens
Kablink Component
  • Teaming

I am trying to move ma Kablink 2.0.1 system to a new server bu am encountering problems.

Initial installation was icecore/liferay version upgraded to 2.0.1 on Windows 2K Server. Directory structure is icecore/ home etc... Working perfectly. did a mysqldump -u root -p sitescape >sitescape.sql of the database and copied file to new server.

New server is W2K3. I did a fresh installation of Kablink 2.0.1. and tested working fine after installation. used default directories of Novell/Teaming etc...

Copied data from W2K icecoredata to new server Novell/Teaming folder

After running the mysql --user=root --password -vvf sitescape < sitescape.sql command and sucessfully inporting the data I continually get (in Firefox) a "The page isn't redirecting properly" error when trying to link to the new site. There are no errors in the catalina logs.

I have tried all sorts of combinations of copying the filerepository data across, and have even tried the installation with the W2K installer.xml file, creating the icecore and home directories on the W2K3 server. I  still get the same result after restoring the sitescape.sql file and restarting the server.

Any ideas on what config files or methods I need to modify, please

Workflow
Process State Action
Discussion workflow Active
This entry is currently active
Attachments(0)
Entry History
Tags
 
Replies
Thumbnail Image
Jong Kim Jong Kim

Have you tried to look at the ssf*.log files in the <tomcat>/webapps/ssf/WEB-INF/logs directory on the "target" (W2K3) system?

Thumbnail Image
Mark Behrens Mark Behrens

Thanks for the prompt response. thee ssf.log has the following errors

NUMBER_OF_PROCESSORS=1
ComSpec=C:\WINDOWS\system32\cmd.exe}
2009-09-14 13:54:19,014 WARN  [main] [org.hibernate.cfg.SettingsFactory] - Could not obtain connection metadata
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at org.kablink.util.dao.hibernate.DSConnectionProvider.getConnection(DSConnectionProvider.java:61)
at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2073)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1298)
at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:814)
at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:732)
at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:211)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1369)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:423)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:627)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Caused by: java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: YES)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:812)
at com.mysql.jdbc.MysqlIO.secureAuth411(MysqlIO.java:3269)
at com.mysql.jdbc.MysqlIO.doHandshake(MysqlIO.java:1182)
at com.mysql.jdbc.Connection.createNewIO(Connection.java:2670)
at com.mysql.jdbc.Connection.<init>(Connection.java:1531)
at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266)
at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221)
... 49 more
2009-09-14 13:54:19,092 ERROR [main] [org.kablink.util.dao.hibernate.DynamicDialect] - org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Access denied for user 'root'@'localhost' (using password: YES))
2009-09-14 13:54:19,092 ERROR [main] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Could not instantiate dialect class
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1338)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)

Thumbnail Image
Jong Kim Jong Kim

The log message indicates that Teaming could not connect to the database using the credentials provided. Try double checking that you're using correct username/password for the database. Re-run Teaming installer (with configuration option) and double check the connection URL that you specified for the database.

Thumbnail Image
Mark Behrens Mark Behrens

I found an incorrect root password in the ssf.xml file (i changed the mysql root password to the same as the W2K server). This has solved the ssf.log issue, but not the fundamental problem which still persists.

When I go to the site http://kablinkserver:8080/. the url changes to ;

http://kablinkserver:8080/ssf/a/c/p_name/ss_forum/p_action/1/operation/view_error_message/value/No+such+workspace+by+the+name+%27kablink%27/action/__ajax_request

This may be the cause of the problem. As mentioned previously the W2K version has a directory structure;

  • home
    • icecoredata
      • filrerepository
        • liferay.com
        • etc...

The W2K3 installation has a structure;

  • Novell
    • Teaming
      • filerepository
        • kablink
        • etc

How should I copy across the data from W2K to W2K3. I used the default directories when installing in W2K3. Does this have an effect on the sitescape database that I restore?

Appreciate your assistance

Thumbnail Image
Jong Kim Jong Kim

The default zone name has changed between Teaming 1.0 and 2.0, and I bet that your W2K system (which was upgraded from Teaming 1.0) still uses (rightly) the old zone name while the brand new system on W2K3 uses the new name. There are a couple of approaches to fix this discrepency, but let's try the easier one and see if it can get you past the trouble.

First, make sure to continue using the old zone name (liferay.com) in the various directory names on the new system. For instance, to do this, you should have copied /home/icecoredata/filerepository/liferay.com to /Novell/Teaming/filerepository/liferay.com. Note that the leaf directory name "liferay.com" should be preserved here. It must not be changed to "kablink".

Second, open up <tomcat>/webapps/ssf/WEB-INF/classes/config/zone-ext.cfg.xml file in a text editor, and add the following line (IF it is not already there). Note that the value of the defaultZone element must be "liferay.com". For more info on syntax, take a look at zone.cfg.xml file in the same directory.

<defaultZone name="liferay.com"/>

Save the file, re-start Teaming, and give it a try.

Thumbnail Image
Mark Behrens Mark Behrens

Thanks... that almost did the trick. Although I now get the home page the login screen I could not log in using any of the admin accounts and get authentication errors in the catalina.log. I eventually managed to get it working by doing the following

  • Copy the home/icecoredata file structure complete and not use Novell/Teaming at all. Thus the new folder structure is identical to the old one
  • Copy the <tomcat>/webapps/ssf/WEB-INF/classes/config/zone-ext.cfg.xml and the ssf-ext.proporties from the old system.

This now functions correctly. I would ultimately like to change the directory structure to the new format Novell/Teaming/Kablink, but at least I am able to use the system as is. My concern is with future upgrades/moves and this old file/security structure.

I appreciate your help.

Thumbnail Image
Roy Klein Roy Klein

Did you remember to reindex the entire tree after starting up the new Teaming server?  (I didn't notice any mention of it)

Thumbnail Image
Mark Behrens Mark Behrens

Roy,

Yes I did reindex the entire Workplace tree. I have picked up another issue with files.

I can add files, edit and view them in the new server, but when I try to delete or copy any file loaded into the system, I get a general error and the database (mysql) crashes.

There is a lot of data on the tomcat screen, by nothing in the catalina logfile.

To get the system running again I have to restore the database and /home/icecore folders and restart mysql. All other functions seem to be ok.

Hopefully it is a setting in one of the xml files

Thumbnail Image
Jong Kim Jong Kim

1. In order for your custom settings (eg. data directory location, etc.) to survive future Teaming upgrades, you MUST ensure that all of the custom settings are recorded in the installer.xml which is located in the directory from which you installed the new system. Teaming uses the information in this file to learn about the settings of the existing installation, and it will try to preserve those settings across system upgrades.

2. For the delete error - It sounds like to me that you're running into the same problem reported in another discussion entry (http://community.kablink.org:8080/ssf/a/c/p_name/ss_forum/p_action/1/action/view_permalink/entityType/folderEntry/entryId/2813).

Thumbnail Image
Mark Behrens Mark Behrens

Thanks for the link... which was the problem. The old server had MYSQL 5.0.77 and the W2K3 had 5.1.36. I uninstalled 5.1.36 and installed 5.0.77 and all is working as expected and the delete problem is no more!!

I think that Kablink/Novell should specify the MYSQL versions known to work (or not to work) so that users don't run into these problems.

Thanks for all the assistance

Skip Footer Toolbar