[MGNLBACKUP-26] After restoring a backup, unable to login to restored instance Created: 24/Sep/09 Updated: 29/Mar/22 Resolved: 24/Sep/09 |
|
| Status: | Closed |
| Project: | Backup |
| Component/s: | None |
| Affects Version/s: | 1.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jon Holmes | Assignee: | Jan Haderka |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | backup, restore | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Vista, mg4.1 Enterprise, m-m-backup1.1, MySQL5.1 (5.0 driver)., vanilla mg install |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: | |
| Team: |
| Description |
|
After backup of a vanilla mg author instance, after running the restore script, I am unable to login to the restored author instance. Before I even attempt to login, this exception is thrown as the login screen is rendered. Extra information, - On both the backup and the restore I get a number of 'Unclosed session detected' being logged - is this expected. 2009-09-24 15:39:56,652 ERROR info.magnolia.cms.security.SystemUserManager : Failed to login as anonymous user |
| Comments |
| Comment by Jan Haderka [ 24/Sep/09 ] |
Seems like indexing was not finished when the restored repo was shut down. Try to delete all repositories/magnolia/*/index folders and startup again .. the issue should go away then. |
| Comment by Jan Haderka [ 24/Jun/11 ] |
|
Closing all previously resolved and released issues. |
| Comment by Edgar Vonk [ 08/May/12 ] |
|
Hi Jan, just a quick note: I also ran into this issue. I think it would be a very worthwhile addition to the Magnolia Backup Module's documentation page. It cost me a lot of time before I found this solution (which is also causes by the fact that searching is quite hard in JIRA in my opinion..). |