Git pull broke Redis.

a_5mith

How do I go back?

Cannot read property 'Store' of undefined. Is Redis installed etc... Sites down, won't come back up.

Worked out how to roll back, made no difference.

a_5mith

Gah, was meant to tag someone and can't edit... @baris or @julian

Rescue mee.

a_5mith

Reran npm install on the nodebb folder, now have.

Cannot find module 'redis'

This is not going well for me.

frissdiegurke

same here:
error: Unable to initialize Redis! Is Redis installed? Error :Cannot read property 'Store' of undefined message while ./nodebb upgrade after copyright-notice

frissdiegurke

submitted PR: gh#1780

a_5mith

Any idea on what I need to do for the issue in post 3? Something in node_modules is missing.

I say missing, I reinstalled all dependencies to make sure it wasn't that. So the error changed.

a_5mith

npm install didn't install redis or connect-redis. Good job I took a screenshot of my node_modules folder.

<baris>

These problems might be due to the express 4 update. Did you try the following

git pull
npm install
node app --setup

That should install all required dependencies. Let me know what happens when you do those.

julian

@a_5mith Redis isn't included in our list of dependencies. They are installed on-demand when the NodeBB setup is run, and you select Redis as the database. No need for Redis drivers if you're using Mongo, for example...

a_5mith

@julian Hey guys, my steps to get this working again were, have a beer, rm the node_modules folder and rerun npm install, at this point it said it couldn't find redis. Drink another beer. Remember that I took a screenshot of everything in my node_modules folder prior to beer #1. Match them up and realised that both redis-connect and redis were missing from node_modules, a quick npm install on both of those and I'm up and running again.

However I also went back a few commits, but I will try a pull and an update while you're all about, to see if I can't troubleshoot anything going wrong.

I must admit, I didn't think to run setup again.

nik

Ran into the same issue with this week's pull and npm install fixed it.

./nodebb upgrade is what appears to be breaking it.

manuel

same issue after upgrading from 0.4.2 to 0.5.x (and already fixed with setup)

julian

You guys will need to run ./nodebb setup once again to install the proper database dependencies