Installing nodebb-plugin-spam-be-gone crashes server

[Guiri]

Below is some output of ./nodebb log. Child processes continually spawn and crash.

NodeBB: 0.5.4
Redis: 2.8.9

[cluster] Child Process (6996) has disconnected
[cluster] Child Process (6996) has exited (code: 1, signal: null)
[cluster] Spinning up another process...
2014-11-22T14:33:00.501Z - info: Enabling 'trust proxy'
[cluster] Child Process (7004) listening for connections.

2014-11-22T14:33:00.736Z - warn: [plugins/nodebb-plugin-markdown] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
2014-11-22T14:33:00.736Z - warn: [plugins/nodebb-plugin-markdown] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-markdown".


2014-11-22T14:33:00.738Z - warn: [plugins/nodebb-plugin-mentions] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
2014-11-22T14:33:00.738Z - warn: [plugins/nodebb-plugin-mentions] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-mentions".


2014-11-22T14:33:00.739Z - warn: [plugins/nodebb-plugin-solr] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
2014-11-22T14:33:00.739Z - warn: [plugins/nodebb-plugin-solr] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-plugin-solr".


2014-11-22T14:33:00.740Z - warn: [plugins/nodebb-widget-essentials] This plugin may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing.
2014-11-22T14:33:00.740Z - warn: [plugins/nodebb-widget-essentials] In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset plugin="nodebb-widget-essentials".

{ tasks: 
   { pokeclient: 
      { action: 'poke',
        actionvalue: '{{message}}',
        target: 'client',
        targetvalue: '{{client}}',
        trigger: 'chatcommand',
        triggervalue: '!poke {{client}} {{message}}' } } }
{ pokeclient: 
   { action: 'poke',
     actionvalue: '{{message}}',
     target: 'client',
     targetvalue: '{{client}}',
     trigger: 'chatcommand',
     triggervalue: '!poke {{client}} {{message}}' } }
{ tasks: 
   { pokeclient: 
      { action: 'poke',
        actionvalue: '{{message}}',
        target: 'client',
        targetvalue: '{{client}}',
        trigger: 'chatcommand',
        triggervalue: '!poke {{client}} {{message}}' } } }
No serverinfo
2014-11-22T14:33:01.386Z - info: [plugins/spam-be-gone] Settings loaded
2014-11-22T14:33:01.392Z - error: TypeError: Cannot read property 'admin' of undefined
    at /home/user/node5/node_modules/nodebb-plugin-spam-be-gone/library.js:91:82
    at /home/user/node5/src/meta/settings.js:12:4
    at try_callback (/home/user/node5/node_modules/redis/index.js:573:9)
    at RedisClient.return_reply (/home/user/node5/node_modules/redis/index.js:661:13)
    at ReplyParser.<anonymous> (/home/user/node5/node_modules/redis/index.js:309:14)
    at ReplyParser.emit (events.js:95:17)
    at ReplyParser.send_reply (/home/user/node5/node_modules/redis/lib/parser/javascript.js:300:10)
    at ReplyParser.execute (/home/user/node5/node_modules/redis/lib/parser/javascript.js:211:22)
    at RedisClient.on_data (/home/user/node5/node_modules/redis/index.js:534:27)
    at Socket.<anonymous> (/home/user/node5/node_modules/redis/index.js:91:14)
[cluster] Child Process (7004) has disconnected
[cluster] Child Process (7004) has exited (code: 1, signal: null)
[cluster] Spinning up another process...

[a_5mith]

Run npm install [email protected], then try again.

[Guiri]

Problem solved. Any idea how I overshot the compatible release? I thought version restrictions were added to NodeBB plugins a few months ago.

[a_5mith]

@Guiri Not sure, i suspected it might be an issue with the dependency, but it's not even a dependency of 0.5.x. So only thing I can think of is it's just downloaded @latest, rather than the correct one. But, don't know how.

[Scuzz]

I have the same issue.

[a_5mith]

@Scuzz Exactly the same error code? What version of NodeBB & SBG plugin you running?

[bentael]

@Guiri actually, use [email protected] instead of [email protected] I backported a critical fix not too long ago.

What happened was that you installed the latest, [email protected] which is compatible with [email protected], if you are on NodeBB\@0.5.x you should use the [email protected]

NodeBB dependency enforcement has been updated and improved much more in for 0.6, but not sure what exactly happened with you.

Maybe I should take the [email protected] down from npm till [email protected] actually gets released, which is in a week or so

[Guiri]

@bentael Thanks for the tip!

[Scuzz]

@a_5mith said:

npm install [email protected]

Laters version of the plugin but after npm install [email protected] its working ok.

Same issues i am having with all the other plugins not being compatible with the stable version.

[a_5mith]

@Scuzz Look on Github for the version number prior to 0.6.0 changes. Or post the plugins here and I'll take a look, also read bentaels post two above this one, 0.2.52 contains a fix for something in 0.2.51. So that should work too.

[julian]

@Scuzz @Schamper @a_5mith v0.5.5 was released, with an update to the plugin compatibility detection so that NodeBB will actively refuse to upgrade past the suggested version, and installation will throw a warning with instructions on fixing NodeBB in the event an incompatible plugin is installed. The warning also acts as a confirmation dialog.

[a_5mith]

Sounds good.

[Guiri]

@julian Awesome, thank you.