HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Search
-
Re: Upgrade from 2.0.18.11 to 2.1 failed bad
Strange.... I see now the Admin user is listed 5 times in the GDN_UserRole table, which was causing the issue. Deleted the 5 rows, and re-inserted a single row. The /dashboard/utility/structure now completed with a success status THEN, the /utility/update, also completed with a success status. YES!!! I suspect the 5 rows… -
Re: Upgrade from 2.0.18.11 to 2.1 failed bad
Really... weird, here is the last bit of SQL that needs to execute: alter table GDN_UserRole add primary key (UserID, RoleID); But it throws the error: ERROR 1062 (23000): Duplicate entry '5-8' for key 'PRIMARY' However, show create table, shows the table currently has no PRIMARY key.... Hmmmmm..... mysql> show create… -
Re: Upgrade from 2.0.18.11 to 2.1 failed bad
Also.... a web page based update is just a bad idea. I have a 300 meg database. There is no way the upgrade can run within the confines of a gateway timeout. It timed out... then I ran TOP in unix and waited until MYSQL dropped from 100% usage, indicating the upgrade finally finished before I continued. But thats a guess.…
3 results