Digging into this a little more, it looks like there may be something problematic in the database. Looking at what config diagnostics I can and searching for answers, there's a reported fix for vBulletin 5 that *might* work if it's not a database corruption issue - increasing the execution time and the memory limit in config.php. (The recommended values were 2880 and -1, respectively). But when I go into the language manager and look at any language's phrases, they all appear in Polish rather than the actual language they should be (I checked English, the attempted Spanish import, and French). A "rebuild all languages" might help, but I don't want to do that until I know both (a) we have the xml files for all languages for recovery, and (b) that we have a good backup of the database in case things go really off the rails. I'm trying to remember who it was who helped with the migration from the Provo data center (Per, was it you?).
Jim Henderson wrote:
I'm trying to remember who it was who helped with the migration from the Provo data center (Per, was it you?).
Yeah, I was certainly involved in that. -- Per Jessen, Zürich (9.6°C) Member, openSUSE Heroes
On Sun, Oct 24, 2021 at 2:59 AM Per Jessen <per@opensuse.org> wrote:
Jim Henderson wrote:
I'm trying to remember who it was who helped with the migration from the Provo data center (Per, was it you?).
Yeah, I was certainly involved in that.
Cool, is this issue something you can assist with? I don't have access to the system in question, nor am I familiar with how the project performs database backups and the like.
Jim Henderson wrote:
On Sun, Oct 24, 2021 at 2:59 AM Per Jessen <per@opensuse.org> wrote:
Jim Henderson wrote:
I'm trying to remember who it was who helped with the migration from the Provo data center (Per, was it you?).
Yeah, I was certainly involved in that.
Cool, is this issue something you can assist with? I don't have access to the system in question, nor am I familiar with how the project performs database backups and the like.
Me neither :-( It might take a while, I really can't say when I'll have enough time to dig into it again. Updating config.php is easy though, if you think that'll help, with those settings you mentioned. -- Per Jessen, Zürich (7.0°C) Member, openSUSE Heroes
Per Jessen wrote:
Jim Henderson wrote:
On Sun, Oct 24, 2021 at 2:59 AM Per Jessen <per@opensuse.org> wrote:
Jim Henderson wrote:
I'm trying to remember who it was who helped with the migration from the Provo data center (Per, was it you?).
Yeah, I was certainly involved in that.
Cool, is this issue something you can assist with? I don't have access to the system in question, nor am I familiar with how the project performs database backups and the like.
Me neither :-(
It might take a while, I really can't say when I'll have enough time to dig into it again.
Jim, are the forums otherwise working? I mean, how urgent is this? -- Per Jessen, Zürich (7.9°C) Member, openSUSE Heroes
Apologies for the couple of off-list replies (one to you, one to Lars). I just attempted again, and while it seemed to hang while uploading the XML files, I let it sit for a couple of minutes after each file, and then did a language rebuild, and it seems to have worked. I think we're good. There's still some sort of issue that causes it to hang, but I'm now wondering if it might be something in my browser interfering. Either way, seems like it's OK now. (Still weird that it shows all the language phrases as Polish phrases in the phrase editor, but I confirmed that the languages are being used properly in the UI). Jim
Am Sat, 23 Oct 2021 12:01:34 -0700 schrieb Jim Henderson <hendersj@gmail.com>:
Digging into this a little more, it looks like there may be something problematic in the database. Looking at what config diagnostics I can and searching for answers, there's a reported fix for vBulletin 5 that *might* work if it's not a database corruption issue - increasing the execution time and the memory limit in config.php. (The recommended values were 2880 and -1, respectively).
As I'm not a fan of "unlimited resources", but on the other hand found some memory left unused on the machine: max_execution_time = 240 memory_limit = 3072M I hope this helps you already.
(b) that we have a good backup of the database in case things go really off the rails.
The latest DB backup is: 465360152 Oct 25 09:35 webforums.sql.xz (triggered manually). Usually, the backup job runs at 05:00 UTC every day. Regards, Lars
participants (3)
-
Jim Henderson -
Lars Vogdt -
Per Jessen