Stuck at "Delete Sessions".
-
@Haitch can you take a screenshot? Are you using mongo+redis, or just redis?
-
@Haitch if it literally says
Deleting
instead ofDelete
then you aren't on v1.5.0 -
@Haitch try counting the number of session keys by doing this:
./redis-cli KEYS "sess:*" | wc -l
-
@PitaJ said in Stuck at "Delete Sessions".:
./redis-cli KEYS "sess:*" | wc -l
The clone finally did completely process the upgrade - so I guess I'm just going to have to bite the bullet and take my site down for as long as it takes.
As for the "redis-cli KEYS "sess:*" | wc -l" command: 5,379,194
What the heck could have caused that many "long-lived" sessions?
-
@Haitch there was a bug which caused the sessions to be stored for 1000x the time they were supposed to be. That's why we're clearing the sessions in the first place.
-
@PitaJ said in Stuck at "Delete Sessions".:
@Haitch there was a bug which caused the sessions to be stored for 1000x the time they were supposed to be. That's why we're clearing the sessions in the first place.
that's definitely an oops - but been, there done that in my own code.
Guess it's just bite the bullet and do it. I imagine not having to track over 5 million phantom sessions should make the site more responsive .....
-
@Haitch it is possible to run the upgrade script while your forum is running, I think
-
okay, upgrade completed - took almost 3 hours to delete the sessions, took the site down to do it, now running at 1.5.0.
New problem, when uploading images my users are getting: "something went wrong trying to parse the server response" - the upload URL appears in the post, but no pic. eg:
-
@Haitch open an issue here: https://github.com/nodebb/nodebb/issues
-
Also, make sure you check the upload related ACP settings. Also, this is an expected behavior if a category is not selected when the topic is being written. Make sure they're selecting a category.