Login Authentication not working after install with script
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-24-2015 03:49 PM
https://github.com/loftuxab/alfresco-ubuntu-install
Postgres 9.3, pg jdbc, nginx, tomcat 7, swftools, openjdk, imagemagick, share and alfresco war files, share config files, bart, sharepoint connector, gdocs, libreoffice, solr4, etc.
All options, all default settings.
Login to Alfresco Share fails when using admin/admin
The error message displayed is vague:
Message: "Your authentication details have not been recognized or Alfresco may not be available at this time."
Script author cannot reproduce error on his system.
EDIT: Postgres JDBC jar url was outdated, failed to download.
EDIT: Attached is a new /opt/alfresco/logs/alfresco.log file, plus share.log, and catalina.log
Any suggestion on how to find the cause of the login error?
- Labels:
-
Archive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2015 09:07 AM
Also would be good to attach your alfresco-global.properties
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-25-2015 04:33 PM
(The script had an outdated Postgres JDBC URL, so it failed to download the jar, and didn't check…)
Still getting the login fail error!
"Your authentication details have not been recognized or Alfresco may not be available at this time."
Logs and alfresco-global.properties are attached….
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2015 03:47 AM
Looking at catalina.out, the solr4 web application is failing to load because there is a problem with the config file solr.xml.
I'm not sure why solr would be relevant to a log in, but certainly without it Alfresco will not function. Also the fact that it is aborting may be killing some components that Alfresco login relies upon.
First order of business is to adjust the solr config so that it will load & run
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2015 02:55 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2015 03:13 AM
That said, I think solr.war is missing or corrupt or a required jar. This is a bit of a guess but it is based on
SEVERE: Exception fixing docBase for context [/solr4]
java.util.zip.ZipException: error in opening zip file
jar / war files are sip files and I suspect one is missing or broken.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2015 08:39 AM
The login problem ("Your authentication details have not been recognized or Alfresco may not be available at this time.") is still there.
Where does alfresco write its login failure log?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2015 09:31 AM
Usually, when you get that error it means that the alfresco webapp is not running.
First question I would ask is what password did you give the installer when you installed Alfresco because that is your admin password.
Second question is to check alfresco.log / share.log for any kind of errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2015 09:51 PM
02:31:03,538 ERROR [org.alfresco.repo.domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema auto-update failedorg.alfresco.error.AlfrescoRuntimeException: 01280000 More than one Alfresco schema was found when querying the database metadata. Limit the database user's permissions or set the 'hibernate.default_schema' property in 'custom-hibernate-dialect.properties'. at org.alfresco.repo.domain.schema.SchemaBootstrap.countAppliedPatches(SchemaBootstrap.java:644)
Why would it have more than 1 schema?
How to fix?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2015 05:43 AM
Fixing this is not something I have any experience of but I would suggest examining each schema using psql and eiter dropping the duplicates or you could edit tomcat/webapps/alfresco/WEB-INF/classes/alfresco/domain/hibernate-cfg.properties and set hibernate.default_schema={pick one of the schemas}
I would start by limiting the schema via hibernate-cfg.properties and then when you have found one that works, back up your installation (make certain Alfresco is shut down if you use file copy) then drop the redundant schemas and remove the hibernate.default_schema={pick one of the schemas} change.