Hi,
We got a problem trying to upgrade from v.6.1.3 to the v. 6.3.6 - After upgrade log-in as admin, system doing database upgrade for about 30 minutes as usual but after that it coming with the message "Invalid login credentials".
Any suggestions?
Log file attached.
Actually it still running - the second log file added
Regards,
Evgueni
Clean browser cache, delete cookies and try again.
Hi,
Logs show that upgrade has been run at least twice.
I guess that you started upgrade that did not finish (seems to be quite long)
Today's upgrade has been run on restored instance/DB, so it been run only once.
I suspect the problem is there:
2017-09-13 08:37:17.656 ===== TRACE ===== Login error for user '< +•Å{4'
Hi,
Logs show that upgrade has been run at least twice.
I guess that you started upgrade that did not finish (seems to be quite long) and tried to reconnect as admin. This started a new upgrade while first one was still in progress.
The upgrade to V6.3 can be a bit long depending on number of notes : we added required fields on notes and need to update every note.
What in unexpected is duration of operation : about 100 notes every 2 minute.
It seems quite slow (was much quicker on my server, about 1000 notes updates per minute) ... and you avec 37000 notes to update.
So, in your case, migration may long about 12 hours.
My advise :
- stop php to end all ongoing process (possibly you have several pmigration process still ongoing) and restart it
- if you can, retreive last backup of database
- launch upgrade in the evening or before week-end and let it run until it ends (about 12 hours in your case)
- do not reconnect as admin before the end
We recorded a ticket to block double migration process (block any connection during process, even for admin)
Actually we have found that the process completed despite problem with credentials - after process completed the same credentials are accepted.
Still there are a few problems:
1. Download of attachments from pre-existing issues and tickets fails (works for new issues)
2. Issues export to PDF failing intermittently with message: ERROR : An error occurred on 2017-09-14 at xx xx (for some issues only)
1) possibly because you did not migrate overwriting exixting code with previous one, so directory for attachments may have changed or is empty
2) please post log file with error
Thank you very much!
We have found error in the script that been moving attachments - so, now it is fixed and PDF works as well