Upgrading from 2.0.17 to 2.1.14 not going through

Started by StarredSkies, December 12, 2023, 12:04:15 AM

Previous topic - Next topic

Kindred

Well, if you are coming out of 2.0.x, you need to remove all Themes except the default anyway,  since 2.0 Themes won't work on 2.1... and all mods  ARE removed as part of the upgrade.


So, with that timeout, it does that for me too... just click try again.  It took me 6 or more to complete a big forum upgrade (2.5 million posts)
Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

StarredSkies

I did remove the themes as you said. There was no change. (And I will keep the mod thing in mind.)

The issue is that I have waited. Hours. It's been over 24 with the first rendition of this and then 13 for he second attempt. Should it really take this long?

Something isn't right and I'm not sure where to go from here (nor does the host).

Doug Heffernan

Quote from: StarredSkies on December 13, 2023, 03:11:08 PMThe issue is that I have waited. Hours. It's been over 24 with the first rendition of this and then 13 for he second attempt. Should it really take this long?

No, it shouldn't take that long unless you have a very very big forum and not a decent host. Something is causing the delay but without seeing any message pertaining to that is difficult to diagnose the problem.

Kindred

Слaва
Украинi

Please do not PM, IM or Email me with support questions.  You will get better and faster responses in the support boards.  Thank you.

"Loki is not evil, although he is certainly not a force for good. Loki is... complicated."

StarredSkies

Quote from: Doug Heffernan on December 13, 2023, 05:02:47 PM
Quote from: StarredSkies on December 13, 2023, 03:11:08 PMThe issue is that I have waited. Hours. It's been over 24 with the first rendition of this and then 13 for he second attempt. Should it really take this long?

No, it shouldn't take that long unless you have a very very big forum and not a decent host. Something is causing the delay but without seeing any message pertaining to that is difficult to diagnose the problem.

My forum is almost 100k posts, so it's not huge. It's very strange that there's been no error shown. Checked again in Apache error logs and the upgrade. No changes whatsoever.

Quote from: Kindred on December 13, 2023, 05:06:42 PMdid you click the button or just wait?
Both. I have been waiting a bit and then every now and then, clicking it to see if a connection has formed.

What else could I try to look at? Could the database be corrupted in some way?

Sesquipedalian

If you have command line access, you could try running the upgrade that way. The command line can produce much more verbose logging and error reporting.
I promise you nothing.

Sesqu... Sesqui... what?
Sesquipedalian, the best word in the English language.

StarredSkies

Well, lord almighty, that worked on the second test subdomain and is functioning just fine. Not the first.

I suppose we could call this solved for now, even if the root of the issue is not known.

shawnb61

If using a subdomain - and especially if using multiple subdomains - look at the cookie settings. 

You may need to specify subdomain independent cookies.  And also specify the primary domain.

Under Admin | Server Settings | Cookies and Sessions.
A question worth asking is born in experience & driven by necessity. - Fripp

StarredSkies

I will 100% check on that in the future. Thank you so much everyone! As always, you guys are helpful.

Andres08

Is here someone upgrading manualy from 2.0.17 to new version? Somehow I am not that good in it, and lack of trust to overwrite something important. 

Aleksi "Lex" Kilpinen

If you for some reason need to test on a copy, make sure the copy actually works before anything related to the upgrade.
ALWAYS start with a working forum. So, first copy the exact same install - files and database, then edit DB settings for the copy or run repair_settings.php to do that and save, then run repair_settings.php (again) and fix all paths and urls, lastly verify everything works correctly. Only then, start with the upgrade.
But you do not need to do this, you should be safe just making a backup and directly working on your live forum. 

The actual upgrade is described in the wiki in fairly good detail https://wiki.simplemachines.org/smf/Upgrading
Slava
Ukraini!
"Before you allow people access to your forum, especially in an administrative position, you must be aware that that person can seriously damage your forum. Therefore, you should only allow people that you trust, implicitly, to have such access." -Douglas

How you can help SMF

Andres08

Quote from: Aleksi "Lex" Kilpinen on August 13, 2024, 12:15:24 AMIf you for some reason need to test on a copy, make sure the copy actually works before anything related to the upgrade.
ALWAYS start with a working forum. So, first copy the exact same install - files and database, then edit DB settings for the copy or run repair_settings.php to do that and save, then run repair_settings.php (again) and fix all paths and urls, lastly verify everything works correctly. Only then, start with the upgrade.
But you do not need to do this, you should be safe just making a backup and directly working on your live forum. 

The actual upgrade is described in the wiki in fairly good detail https://wiki.simplemachines.org/smf/Upgrading

Thank you for that.  I would most likely need some support. 

Andres

Aleksi "Lex" Kilpinen

Most commonly it really is as simple as uploading the contents of the upgrade package, overwriting old files with the new ones, and then running upgrade.php.
Slava
Ukraini!
"Before you allow people access to your forum, especially in an administrative position, you must be aware that that person can seriously damage your forum. Therefore, you should only allow people that you trust, implicitly, to have such access." -Douglas

How you can help SMF

Advertisement: