topic Re: Problems logging in after changing to MySQL, Labs3Final in Alfresco Archive

Problems logging in after changing to MySQL, Labs3Final

sorca — Fri, 23 Jan 2009 09:54:48 GMT

Hi,This will be a long reading, and I hope it is ok as it is. If not, please contact me via mail. /OscarI am having problems with my Alfresco after I have changed database from Derby to MySQL."Failed to Login - The remote server may be unavailable or your authentication details have not been recogni

Re: Problems logging in after changing to MySQL, Labs3Final

sorca — Fri, 23 Jan 2009 10:10:33 GMT

Hi,

I've searched other threads and found something about OpenOffice. A user xtine writes of his file

/opt/Alfresco/tomcat/shared/classes/alfresco/extension/bootstrap/openoffice-startup-context.xml‍

. He adds(?) this:

<value><![CDATA[/usr/lib/openoffice/program/soffice "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" "-env:UserInstallation=file:///usr/lib/openoffice" -nologo -headless -nofirststartwizard -nocrashrep -norestore]]></value>[/code]

Mi file looks like this:

[code]<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>

<beans>

   <bean id="openOfficeStartupBootstrap" class="org.alfresco.util.exec.RuntimeExecBootstrapBean" >
      <property name="startupCommands">
         <list>
            <ref bean="openOfficeStartupCommand" />
         </list>
      </property>
      <property name="failOnError">
         <value>false</value>
      </property>
   </bean>

   <bean id="openOfficeStartupCommand" class="org.alfresco.util.exec.RuntimeExec">
      <property name="commandsAndArguments">
          <map>
              <entry key=".*">
                  <list>
                      <value>${ooo.exe}</value>
                      <value>-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager</value>
                      <value>-env:UserInstallation=file:///${ooo.user}</value>
                      <value>-nologo</value>
                      <value>-headless</value>
                      <value>-nofirststartwizard</value>
                      <value>-nocrashrep</value>
                      <value>-norestore</value>
                  </list>
              </entry>
          </map>
      </property>
      <property name="waitForCompletion">
         <value>false</value>
      </property>
      <property name="errorCodes">
         <value>2</value>
      </property>
   </bean>

</beans>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Should I add that line, and id so - where?

/Oscar

Re: Problems logging in after changing to MySQL, Labs3Final

mikeh — Fri, 23 Jan 2009 10:22:52 GMT

You shouldn't need to reboot each time, just make sure the java process has been killed off if it doesn't shut down correctly.

What's currently in the /opt/Alfresco/alf_data folder?

Also, for the avoidance of doubt, can you post the contents of the custom-repository.properties file please (remove any passwords if you like)

Thanks,
Mike

Re: Problems logging in after changing to MySQL, Labs3Final

sorca — Fri, 23 Jan 2009 13:04:30 GMT

Hi,

Ok, just killall java

In the /opt/Alfresco/alf_data are the following:

drwxr-xr-x  6 root root 4096 2009-01-23 09:33 ./
drwxr-xr-x 12 root root 4096 2009-01-23 10:37 ../
drwxr-xr-x  2 root root 4096 2009-01-23 09:33 audit.contentstore/
drwxr-xr-x  2 root root 4096 2009-01-23 09:33 contentstore/
drwxr-xr-x  2 root root 4096 2009-01-23 09:33 contentstore.deleted/
drwxr-xr-x  8 root root 4096 2009-01-23 09:34 lucene-indexes/‍‍‍‍‍‍

root@alfresco-test:/opt/Alfresco# tree alf_data/

alf_data/
|– audit.contentstore
|– contentstore
|– contentstore.deleted
`– lucene-indexes
    |– archive
    |   `– SpacesStore
    |       |– IndexInfo
    |       `– IndexInfoBackup
    |– avm
    |   `– sitestore
    |       |– IndexInfo
    |       `– IndexInfoBackup
    |– locks
    |– system
    |   `– system
    |       |– 4518e9ac-8931-4021-b971-bd8b96bafc8e
    |       |   |– IndexInfoDeletions
    |       |   |– _0.cfs
    |       |   |– segments.gen
    |       |   `– segments_3
    |       |– IndexInfo
    |       |– IndexInfoBackup
    |       |– b4ca4a7f-b1f3-4415-9a3a-a1c86085354f
    |       |   |– IndexInfoDeletions
    |       |   |– _0.cfs
    |       |   |– segments.gen
    |       |   `– segments_3
    |       `– d4596774-ce50-40c1-b857-4df9193c1ca4
    |           |– IndexInfoDeletions
    |           |– _0.cfs
    |           |– segments.gen
    |           `– segments_3
    |– user
    |   `– alfrescoUserStore
    |       |– IndexInfo
    |       `– IndexInfoBackup
    `– workspace
        |– SpacesStore
        |   |– IndexInfo
        |   `– IndexInfoBackup
        |– lightWeightVersionStore
        |   |– IndexInfo
        |   `– IndexInfoBackup
        `– version2Store
            |– IndexInfo
            `– IndexInfoBackup

20 directories, 26 files‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

And here's the content of custom-repository.properties:

###############################
## Common Alfresco Properties #
###############################

#
# Sample custom content and index data location
#
dir.root=/opt/Alfresco/alf_data
dir.indexes=/opt/Alfresco/alf_data/lucene-indexes

#
# Sample database connection properties
#
db.name=alfresco
db.username=alfresco
db.password=alfresco
#db.pool.initial=10
#db.pool.max=100

#
# External locations
#
ooo.exe=/opt/Alfresco/program/soffice
ooo.user=${dir.root}/oouser
img.root=/usr/local
swf.exe=/opt/Alfresco/pdf2swf

#
# Property to control whether schema updates are performed automatically.
# Updates must be enabled during upgrades as, apart from the static upgrade scripts,
# there are also auto-generated update scripts that will need to be executed.  After
# upgrading to a new version, this can be disabled.
#
#db.schema.update=true

#
# Derby connection
#
#db.driver=org.apache.derby.jdbc.EmbeddedDriver
#db.url=jdbc:derby:/opt/Alfresco/alf_data/derby_data/alfresco;create=true

#
# HSQL connection
#
#hsql#db.driver=org.hsqldb.jdbcDriver
#hsql#db.url=jdbc:hsqldb:file:/opt/Alfresco/alf_data/hsql_data/alfresco;ifexists=true;shutdown=true;

#
# MySQL connection (This is default and requires mysql-connector-java-5.0.3-bin.jar, which ships with the Alfresco server)
#
#mysql#
db.driver=org.gjt.mm.mysql.Driver
#mysql#
db.url=jdbc:mysql://localhost:3306/alfresco

#
# PostgreSQL connection (requires postgresql-8.2-504.jdbc3.jar or equivalent)
#
#postgresql#db.driver=org.postgresql.Driver
#postgresql#db.url=jdbc:postgresql://localhost:3306/alfresco
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

For this test I use the default passwords, so I don't feel a need to remove them. How would I change them for future use on a "production" server?

/Oscar

Re: Problems logging in after changing to MySQL, Labs3Final

mikeh — Fri, 23 Jan 2009 13:38:40 GMT

The config looks ok, so I'd suggest making sure everything is shutdown, clearing out the contents of alf_data, drop and recreate the db and finally restart Tomcat.

Thanks,
Mike

Re: Problems logging in after changing to MySQL, Labs3Final

sorca — Fri, 23 Jan 2009 13:56:03 GMT

So, I should stop Alfresco, stop tomcat, stop java and do a rm -rf on alf_data and stop-and-restart on MySQL?

Should I manually add alfresco as user in my MySQL, like:

grant all privileges on *.* to 'alfresco'@'%' identified by 'alfresco' with grant option;

Can I manually create db alfresco, empty, and give privileges on alfresco.* in that case?

Thanks,

Oscar

Re: Problems logging in after changing to MySQL, Labs3Final

mikeh — Fri, 23 Jan 2009 14:43:44 GMT

Stopping Tomcat will stop Alfresco. Make sure the java process has gone afterwards. Yes, rm -rf *under* alf_data (keep the alf_data folder itself). No need to stop and restart MySQL.

Run this sql script:

drop database alfresco;
create database alfresco;
grant all on alfresco.* to 'alfresco'@'localhost' identified by 'alfresco' with grant option;
grant all on alfresco.* to 'alfresco'@'localhost.localdomain' identified by 'alfresco' with grant option;‍‍‍‍

Thanks,
Mike

Re: Problems logging in after changing to MySQL, Labs3Final

sorca — Sun, 25 Jan 2009 13:57:14 GMT

Thnx, I will give it a try in a moment I'll let you know how it goes.

Thanks,

Oscar

Re: Problems logging in after changing to MySQL, Labs3Final

clive — Wed, 28 Jan 2009 15:20:44 GMT

I had the exact same problems as was able to resolve all except for the soffice error:
   os:         Linux
   command:    "/usr/lib/openoffice/program/soffice.bin" "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" "-env:UserInstallation=file:////opt/Alfresco" -nologo -headless -nofirststartwizard -nocrashrep -norestore
   succeeded: false
   exit code: 2
   out:
   err:        Cannot run program ""/usr/lib/openoffice/program/soffice.bin"": java.io.IOException: error=2, No such file or directory

I had partial success by performing the following. I think that office needs to run a 1st time to perform some setup of the user config:

- Installed headless openoffice
$ sudo apt-get install openoffice.org-headless

- Ran the soffice with the same command as in the log file from the command line, BUT less the -nofirststartwizard switch
$ export JAVA_HOME="/usr/lib/jvm/java-6-sun-1.6.0.07/"; "/usr/lib/openoffice/program/soffice.bin" "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" "-env:UserInstallation=file:////opt/Alfresco" -nologo -headless -nocrashrep -norestore &

- Notice that in the log file the following:
3:17:00,073 INFO [org.alfresco.util.OpenOfficeConnectionTester] The OpenOffice connection was re-established.

Re: Problems logging in after changing to MySQL, Labs3Final

mikeh — Wed, 28 Jan 2009 16:29:45 GMT

Please see my post here: http://forums.alfresco.com/en/viewtopic.php?p=54455#p54455

Thanks,
Mike