Unable to login to Confluence (even with recovery_admin) on the new server

[SEBtheSaviour]

Hello guys,

I've moved Confluence VM to the new server, in order to do "staging" and test it before upgrade to the Data-Center. Copied database, connected it and so on.
I had LDAP directory on the top and "Internal" as a second.

Confluence is started, I can't log into because of LDAP, but when I created properties in order to log in using recovery_admin I got into but I'm seeing. blank screen with:

"Error occurred during template rendering. Contact your administrator for assistance."

So what the logs are saying:

ERROR [http-nio-8090-exec-4] [engine.jdbc.spi.SqlExceptionHelper] logExceptions TRIGGER command denied to user 'jirauser'@'192.168.0.22' for table 'CONTENT'
-- referer: https://[confluence-url]/authenticate.action?destination=/admin/editdecorator.action?decoratorName=decorators/main.vmd | url: /admin/editdecorator.action | traceId: 5bcd330982bf28a4 | userName: recovery_admin

ERROR [http-nio-8090-exec-4] [core.persistence.hibernate.HibernateObjectDao] reIndex Unable to reIndex object: userinfo: recovery_admin v.1 (143196169) -- Failed to add entry to queue
-- referer: https://[confluence-url]/authenticate.action?destination=/admin/editdecorator.action?decoratorName=decorators/main.vmd | url: /admin/editdecorator.action | traceId: 5bcd330982bf28a4 | userName: recovery_admin

There are also some errors with internal admin (I see the healthcheck).

It seems that:

ERROR [http-nio-8090-exec-4] [engine.jdbc.spi.SqlExceptionHelper] logExceptions TRIGGER command denied to user 'jirauser'@'192.168.0.22' for table 'CONTENT'
-- referer: https://[confluence-url]/authenticate.action?destination=/admin/editdecorator.action?decoratorName=decorators/main.vmd | url: /admin/editdecorator.action | traceId: 5bcd330982bf28a4 | userName: recovery_admin

the "jirauser@192.168.0.22" is the "previous JIRA server".

So my questions are:

• if there's any way to log in via recovery_admin?
• does anybody faced the same situation before?
• could you give me any tips how to get out of this? :) 

Thanx in advance!

[SEBtheSaviour · Accepted solution]

Okay guys, there were many related issues.
Actually the /etc/hosts file is the first where you should pay attention to. 
JIRA/Confluence may produce some non-related warnings (XRSF, CORS etc) because of /etc/hosts conf.
I thrown out this instance and set up the fresh one so the problem can be marked as resolved though

[Fabio Racobaldo _Herzum_]

Hi @SEBtheSaviour ,

welcome to the atlassian community!

Is  192.168.0.22 the IP address of your prod dbms? If so, try to update db link in the <confluence_home>/confluence.cfg.xml. Morevover please verify that db user ("jirauser") has grants to access the db in preprod.

Let me know,

Fabio

[SEBtheSaviour]

Hello @Fabio Racobaldo _Herzum_ !

Yup, I verified it. Everything in the confluence.cfg.xml is set up now to the new DB but somehow I see that something is trying to "write" to the old DB, so that's why I posted it.

Moreover, I tried to set up internal admin user using this:
https://confluence.atlassian.com/conf64/restore-passwords-to-recover-admin-user-rights-936511358.html and it seems that internal admin is showing up but I still cannot log into getting "unable to log in".

The recovery_admin should be "agnostic" from any user IMO, but I got the blank screen and I have:

[confluence.util.profiling.ConfluenceSitemeshDecorator] renderToResponse Error occurred rendering template: /decorators/main.vmd

 While It's only a "default" template installed.


Confluence has for sure in my case Crowd Directory set on top, but even if I'm trying to resolve this issue I cannot get in.

Using the new created admin causes something like "permission violation" in logs.