Incredibly stupid user error, so I don't think this is actionable on your side.

Accidentally erased a part of the redis database while trying to find ways to speed it up. Found a webpage talking about memory optimization saying that you can set the order in which "cache keys are invalidated" by setting maxmemory-policy to allkeys-lru through the cli. So I did that, only after a quarter of the forum went away did I read the actual manual which didn't talk about invalidation of cache keys but deletion of database keys...

The backup we had was a few months old (as I wasn't planning to do anything to the database here), so I couldn't restore it, but I could calculate the diff of keys and import all the keys in the diff.

Doing the first (updating tid:<tid>:posts to len(topic:<tid>)+1) already fixed the problems it seems, thanks!

Thanks! The post numbers are also clearly borked, so I'd need to update those as well. I guess I can write a script that counts tid:<tid>:posts and then updates topic:<tid> and tid:<tid>:bookmarks?

We lost a bunch of, but not all, recent keys in the database. The result is that clicking on a thread tries to lead you to a post that isn't there and thus you land at the first post of a potentially 20k post thread. Is there a way of sanitizing this and removing links that link to posts that don't exist? If not, how do I do it manually? Go over all notifications and remove those that link to a non-existing post?
Thanks!

Nevermind. Fixed by repo reset..

Only error I see is:

2019-11-24T11:47:32.340Z [4567/1551] - error: db.initSessionStore is not a function

on trying to run it, but I presume this is caused by incomplete build..

And I seem to have this hanging on multiple commands:

./nodebb build
[benchpressjs] Unable to build or find a suitable native module, falling back to JS version
  started

(hangs)

I'm trying to upgrade nodebb to 1.13 from 1.6 and the update process updates schema (yay!) but then gets stuck on assets:

Updating NodeBB...

1. Updating package.json file with defaults...  OK

2. Bringing base dependencies up to date...  started
npm WARN [email protected] requires a peer of nodebb-plugin-emoji@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of textcomplete@^0.14.2 but none is installed. You must install peer dependencies yourself.

audited 4084 packages in 9.988s
found 15 vulnerabilities (4 low, 2 moderate, 9 high)
  run `npm audit fix` to fix them, or `npm audit` for details

3. Checking installed plugins for updates...  OK
4. Updating NodeBB data store schema...[benchpressjs] Unable to build or find a suitable native module, falling back to JS version

Parsing upgrade scripts... 
OK | 0 script(s) found, 82 skipped
Schema update complete!


5. Rebuilding assets...  started

Is there any way to ask for more logs to understand what is going on?
Thanks!

Did you by any chance have another look at the discord widget?

@HolyPhoenix

I'd be still super interested in a discord plug-in that works sort of like the site chat (in a drop-bar from the menu).

No chance you had a look at it meanwhile? Or at integrating?

@PitaJ said in v1.4.0 startup error:

@MJ try this sequence of commands:

./nodebb stop
npm install [email protected]
./nodebb build
./nodebb start

For me this results in:
4/12 04:11 [14399] - warn: One or more of NodeBB's dependent packages are out-of-date. Please run the following command to update them:
4/12 04:11 [14399] - warn: ./nodebb upgrade

After running nodebb upgrade, I'm back to 4.3.0.

1.4.0 at least appears to just work.

Yes, it's an upgrade blocker for us but then we don't really need upgrading.

... and it was our issue (broken css). Deleting the comments to keep the thread clean.