-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade from version 3.0 to version 3.1 fails #1435
Comments
Hi, could you check out 'syspass.log' file within '.../app/config' directory?. There should be some error messages. Regards |
Hi Nuxmin, here is the log: #16 /home/vault/public_html/index.php(28): require(String)","caller":"N/A"} Many thanks |
It seems you're trying to try to upgrade over a failed upgrade?: If so please restore a previous backup and then perform the upgrade again. http://doc.syspass.org/en/3.1/updating/v3.1.html Regards |
Hello Nuxmin, as far as i know, this installation was not upgraded before. Anyway, i manually removed the column versionLevel from the Plugin table and now i get this log: [2019-08-23 18:13:29] syspass.DEBUG: upgrade.db.start {"message":"Update DB","user":"N/A","address":"181.52.65.114","caller":"SP\Services\Upgrade\UpgradeDatabaseService::upgrade"} [] any idea? is it possible to make a clean installation of 3.1 and migrate the credentials already saved in the database of the 3.0 installation? Many thanks for your time and help |
Hi. We are using 3.1 rc5 - I noted that 3.1 was released.. so.. I cloned the repo into a new directory: /var/www/html/sysPass I installed php composer and dependencies, chown'd the sysPass dir to the www-data user and chmod 750 on app and config directories.. I also copied the OLD config.xml and the 2 .pem files from OLD syspass to new directory... my old was in /var/www/html/ssap123/ - once this was done I renamed the ssap123 directory to ssap123.OLD and then renamed the new directory (sysPass) to ssap123 and then pointed my browser at the location expecting the upgrade page - I didn't get one. I got a login page - also there is no upgrade key in my config.xml AND from the new login page my existing admin password does not work anymore. For the time being I have reverted to 3.1 rc5 - but, I would like to know is there an upgrade path to 3.1 or do I have to install from scratch again? Can I import the sql backup I made into a fresh install of 3.1? Will I have issues with admin passwords doing this? Please advise on the best way forward. Regards And thanks for the software. It is very good. |
@dstyles-jg Hello, could you check out 'app/config/syspass.log' file for any error messages? Updating from RC5 to 3.1 doesn't require an upgrade key, since no database structure changes need to be performed. Regards |
It seems that syspass reports "Wrong login" every time I attempt to login. I have checked the password and it is the same one I use for the "old" installation. Basically, when I revert to the 3.1 rc5 directory - the admin pass works. When I use the 3.1 release directory sysPass reports "wrong login". Also in the syspass.log I see this: it is worth noting that I set the same permissions on the "new" installation - as I followed on the "old" installation and copied the config, key and pubkey files across... they SHOULD be readable so I don't see why the new syspass cannot read them. |
meh... file owner on those files was NOT www-data. I missed that... when I copied them across i forgot to chown them back to apache2 user. MY APOLOGIES @nuxsmin. the upgrade process would have been seamless if i didn't forget to change the permissions on those. |
Hi @nuxsmin I rolled back to the backup and trying again, without any upgrade failure or mistake, and I get the error of the database update, but in this case, the error is not longer about the duplicate column. In this case it says Here is the full log
|
it may be related with this migration https://github.com/nuxsmin/sysPass/blob/master/schemas/31019012201.sql |
@dstyles-jg no worries. I was wondering about the permission of certificate files, since there should be an error when encrypting the password field... |
Also reading about the DB schema, Plugin has not defined name as Primary Key then it may be creating a problem with PluginData Foreign Key constraint look here https://github.com/nuxsmin/sysPass/blob/master/schemas/dbstructure.sql#L443 |
@alebeta90 I'm not sure about that, since a clean install works fine. I think it would be so because the "itemId" definition, that should be "int(11)" under some engine versions. There is a closed issue about that (#1428) Thanks for the feedback! |
I got this log output from MariaDB Using command ```2019-08-28 17:16:22 0x7fa0983c7700 Error in foreign key constraint of table foreign key (name) references Plugin (name) |
@alebeta90 hmm, it seems an index issue, I'll fix it shortly. Thanks for the feedback! |
@nuxsmin thanks to you, let me know if I could provide more useful information. all the best |
Hi !
Hope this helps ! |
@devops-tc thanks for your contribution!! |
Hola, Same issue here with
Bye ! |
I have the same problem but this solution don't work for me. |
Solved in latest release |
I ran into the same issue while updating from 3.0 to the latest release - so it does not seem to be fixed. |
Hi,
I tried to upgrade my current installation of syspass 3.0 to version 3.1 and got the error message "error while updating the database" Image attached
I had the same issue upgrading to 3.1.0-rc1 and 3.1.0-rc5 but expected it would work with the final stable release.
How can i upgrade my installation?
Thanks in advance for your help
The text was updated successfully, but these errors were encountered: