cancel
Showing results for 
Search instead for 
Did you mean: 

3d does not allow login

m_r_
Champ in-the-making
Champ in-the-making
Given the last 2 times I've tried to get help in this forum I've been unsuccessful - I'll try again because I'm just that way.

Versions in play:
apache-tomcat-6.0.18
postgresql-server-8.2.9
http://dev.alfresco.com/downloads/nightly/dist/alfresco-labs-war-3d-dev.zip
Tomcat says:
Apache Tomcat/6.0.18     1.6.0_07-b02     The FreeBSD Foundation     FreeBSD     6.3-STABLE     i386


Tomcat log looks like this (BTW the best its looked in this effort) :
INFO: HTMLManager: list: Listing contexts for virtual host 'localhost'
Jan 16, 2009 9:24:40 PM org.apache.catalina.core.ApplicationContext log
INFO: HTMLManager: start: Starting web application at '/alfresco'
Jan 16, 2009 9:24:44 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
21:24:53,246  INFO  [web.site.FrameworkHelper] Successfully Initialized Web Framework

Modified WEB-INF/classes/log4j.properties per others comments to a fixed path so this is what I get when the login attempt happens:

21:24:53,246 INFO  [org.alfresco.web.site.FrameworkHelper] Successfully Initialized Web Framework



to admin:admin  and alfresco:alfresco   (the logins that are supposed to work)

Failed to Login
The remote server may be unavailable or your authentication details have not been recognized.
OK


So - what error logging do I need to turn on to figure out why the login is not allowed?


(Oh and have any of you run the install on OpenCMS?   The feedback it gives was nice.   The community might wanna look at what they are doing and ape it.)
18 REPLIES 18

m_r_
Champ in-the-making
Champ in-the-making
Now what about avm-console.properties

# grep ^db. *
avm-console.properties:db.driver=org.gjt.mm.mysql.Driver
avm-console.properties:db.url=jdbc:mysql://127.0.0.1/avm
avm-console.properties:db.username=root
avm-console.properties:db.password=
avm-console.properties:db.pool.initial=4
avm-console.properties:db.pool.max=32
repository.properties:db.schema.update=true
repository.properties:db.username=alfresco
repository.properties:db.password=alfABCcoke
repository.properties:db.pool.initial=10
repository.properties:db.pool.max=100
repository.properties:db.driver=org.postgresql.Driver
repository.properties:db.url=jdbcSmiley Tongueostgresql://localhost:5432/alfresco

Is that needing modification also?

Because I'm now seeing this which makes me think I have to clear something else:
16:53:58,573 UserSmiley Frustratedystem WARN  [remoting.rmi.RmiRegistryFactoryBean] Could not detect RMI registry - creating new one
16:54:10,059 UserSmiley Frustratedystem INFO  [domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.MySQLInnoDBDialect.
16:55:10,163 UserSmiley Frustratedystem ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed
org.alfresco.error.AlfrescoRuntimeException: A previous schema upgrade failed.  Revert to the original database before attempting the upgrade again.
        at org.alfresco.error.AlfrescoRuntimeException.create(AlfrescoRuntimeException.java:46)

sorca
Champ in-the-making
Champ in-the-making
I seem to get the same error (on AlfrescoLab3Final, Ubuntu8.10):

"Failed to Login - The remote server may be unavailable or your authentication details have not been recognized."

I followed the installation instructions in the InstallConfigure_Alfresco_Lab3Final-1.pdf which I got off the Alfresco wiki. I installed and tried to start, not changing database, and it worked like a charm. I then edited to change to MySQL from Derby. After starting Alfresco again I cannot login, I only get the fault above. I then tried to do it all over again, deleting Alfresco from /opt, rebooting and installing and changing to MySQL before I start it. Same fault at logon.

I am deeply puzzled over this, though I am hopeful it is just a minor glitch. The instructions in the pdf relates to the complete install on a RedHat system, but hopefully that wouldn´t change anything. I just followed the guide. It differs from the instruction though, I do not get any question on changing the default database from Derby to MySQL, as it states in the "manual". It goes directly from Setup Type to Location of OpenOffice.

I sincerely hope there is a solution  Smiley Indifferent

/Oscar

m_r_
Champ in-the-making
Champ in-the-making
I sincerely hope there is a solution  Smiley Indifferent

It may be the documentation is out of date/wrong.   Some of the stuff looks to be 2.1 vintage, others talk about modifying files in places they are no longer at. 

I don't have a working version so I can submit changes/a set of instructions/know if the problem is me or the software.

mikeh
Star Contributor
Star Contributor
I seem to get the same error (on AlfrescoLab3Final, Ubuntu8.10):

/Oscar
I suspect your error is actually different to this topic. Could you start a new thread, posting the contents of the log file / Tomcat startup console please?

One quick thing to check is whether the MySQL database looks populated? If not, check the MySQL connector is on the classpath.

Thanks,
Mike

mikeh
Star Contributor
Star Contributor
16:55:10,163 UserSmiley Frustratedystem ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed
org.alfresco.error.AlfrescoRuntimeException: A previous schema upgrade failed.  Revert to the original database before attempting the upgrade again.
        at org.alfresco.error.AlfrescoRuntimeException.create(AlfrescoRuntimeException.java:46)
This means the bootstrap failed part-way through running the db scripts.

Easiest solution is to clear-down the database and alf_data folder and restart the app.

Thanks,
Mike

m_r_
Champ in-the-making
Champ in-the-making
16:55:10,163 UserSmiley Frustratedystem ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed
org.alfresco.error.AlfrescoRuntimeException: A previous schema upgrade failed.  Revert to the original database before attempting the upgrade again.
        at org.alfresco.error.AlfrescoRuntimeException.create(AlfrescoRuntimeException.java:46)
This means the bootstrap failed part-way through running the db scripts.

The title of this thread - 3d no longer reflects that I am trying 2.9B to get PostgreSQL.    And perhaps I was unclear in my postings - mea culpa.

But I've changed the files that various documentation says to change - yet the code is asking for MySQL.   
And, of course, a request for MySQL fails.  Because its never been initialized.    So I'm not sure the re-initialize advice is the correct one.

And my machine is showing the code is talking to PostgreSQL

  889  ??  Ss     2:16.76 postgres: stats collector process    (postgres)
22442  ??  Is     0:00.07 postgres: alfresco alfresco 127.0.0.1(55795) idle (po
22443  ??  Is     0:00.08 postgres: alfresco alfresco 127.0.0.1(58276) idle (po
22445  ??  Is     0:00.08 postgres: alfresco alfresco 127.0.0.1(50398) idle (po
22446  ??  Is     0:00.08 postgres: alfresco alfresco 127.0.0.1(64082) idle (po
22447  ??  Is     0:00.07 postgres: alfresco alfresco 127.0.0.1(63780) idle (po
22448  ??  Is     0:00.07 postgres: alfresco alfresco 127.0.0.1(57890) idle (po
22449  ??  Is     0:00.06 postgres: alfresco alfresco 127.0.0.1(57538) idle (po

Of course these are hung/zombies.   


Now without PostgreSQL running in the log I see these snipits:

21:34:01,996 UserSmiley Frustratedystem ERROR [web.context.ContextLoader] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usageQuotaProtector' defined in class path resource [alfresco/usage-services-context.xml]: Invocation of init method failed; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Cannot open connection
Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.)
Caused by: org.postgresql.util.PSQLException: Connection refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

This is expected.

When I run postgres as below (with silent turned off and log to stderr)
$ ps ax | grep post
66338  ??  Ss     0:00.12 postgres: writer process    (postgres)
66339  ??  Ss     0:00.01 postgres: stats collector process    (postgres)
66347  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(59258) idle (po
66348  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(49561) idle (po
66349  ??  Is     0:00.03 postgres: alfresco alfresco 127.0.0.1(53250) idle (po
66350  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(55724) idle (po
66351  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(61816) idle (po
66352  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(55272) idle (po
66353  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(65039) idle (po
66354  ??  Is     0:00.01 postgres: alfresco alfresco 127.0.0.1(61197) idle (po
66436  p0  S+     0:00.00 grep post
66336  p1  I+     0:00.27 /usr/local/bin/postgres -d 5 -D /mypostgresdata

I see no actual PostgreSQL queries  from the running in foreground postges app.

I do see connections like these:
DEBUG:  forked new backend, pid=66545 socket=7
LOG:  connection received: host=127.0.0.1 port=50099
LOG:  connection authorized: user=alfresco database=alfresco
DEBUG:  postgres child[66545]: starting with (
DEBUG:          postgres
DEBUG:          -v196608
DEBUG:          -y
DEBUG:          alfresco
DEBUG:  )
DEBUG:  InitPostgres
DEBUG:  StartTransaction
DEBUG:  name: unnamed; blockState:       DEFAULT; state: INPROGR, xid/subid/cid: 1778052/1/0, nestlvl: 1, children: <>
DEBUG:  CommitTransaction
DEBUG:  name: unnamed; blockState:       STARTED; state: INPROGR, xid/subid/cid: 1778052/1/0, nestlvl: 1, children: <>
DEBUG:  forked new backend, pid=66546 socket=7

But that is all.

Instead I get this (And the bouncycastle) error:

21:49:00,355 UserSmiley Frustratedystem WARN  [remoting.rmi.RmiRegistryFactoryBean] Could not detect RMI registry - creating new one
21:49:05,801 UserSmiley Frustratedystem INFO  [domain.schema.SchemaBootstrap] Schema managed by database dialect org.hibernate.dialect.MySQLInnoDBDialect.
21:50:06,034 UserSmiley Frustratedystem ERROR [domain.schema.SchemaBootstrap] Schema auto-update failed
org.alfresco.error.AlfrescoRuntimeException: A previous schema upgrade failed.  Revert to the original database before attempting the upgrade again.

Thus back to my question - what OTHER files need to be changed?

When you have regression tested PostgreSQL - do you do that on a machine that has no MySQL loaded (ever) on it?  

I doubt filing bug reports on 2.9B would have a point, given the move to 3.0.   (Not to mention the odds favor me being in error even if my bug reporting to date has been correct.)  I'd be willing to wait for 3.0 SP1 if I had any idea of when that might happen - hence my attempt to use 2.9B.

sorca
Champ in-the-making
Champ in-the-making
I will post a new thread with the contents of the log file and a thorough desciption of what I do. I'll come back to this thread when I have done so to inform you.

Thanks,

Oscar

sorca
Champ in-the-making
Champ in-the-making
Hi,

I have started a new topic, Problems logging in after changing to MySQL, Labs3Final where I have included detailed info on how I have installed, error seeking and log transcripts. Hopefully it will help solve the problem.

/Oscar

joglekar
Champ in-the-making
Champ in-the-making
Should do, yes. We're planning to release patches to the PostgreSQL scripts for v3.0 - I don't have a time for that though. http://wiki.alfresco.com/wiki/Alfresco_Labs_3_Stable_Release_Notes

As you stated you use MySQL for development. So will community version always have patches / scripts for MySQL in future.

At present I am using Labs3.b version with PostgreSQL 8.3 fedora 9.0. How can I migrate to MySQL?

To create scripts for v3.0 postgres which files needs changes. is it only in
alfresco/dbscripts/upgrade/2.2/${db.script.dialect}/upgrade-from-2.2SP1.sql
and which other files? If it is only in sql files I will attemt to change.

I have problem to upgrade to 3 Stble. I had same problems when I tried to upgrade to 3c.

Thanks

Joglekar