Update, merge issue..

General Discussion
  • @julian Followed latest instructions in this post, got this.

    Error: Cannot find module './styles'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/errapolis/nodebb/node_modules/colors/lib/colors.js:36:34)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    
  • Seems like the colors module wasn't installed properly... try reinstalling it? npm i colors

  • I knew i'd encountered a problem like that before, that worked, though subsequently I ran upgrade then it was the same issue with "cookie", then upgrade, then "crc", now "debug". Is there a quicker way to find all those needed if more follow?

  • @julian would this bunch be causing the problem now that the dependency requirements are more strict?

    unmet.JPG

    If so, any hints? Stuck on this:

    Capture.JPG

  • @Danny-McWilliams Nope, that should only apply to bundled plugins (mentions, vanilla/lavender/persona theme, markdown, etc).

    If you're getting more of those "cannot find module" errors, then perhaps your dependencies were not completely installed.

    Please run npm install.

  • Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

    Tried to start nodebb, this was in log.

    Capture.JPG

  • @julian i run ./nodebb upgrade after it looks successful npm i command ?

    ./nodebb upgrade
    
    module.js:340
        throw err;
              ^
    Error: Cannot find module 'ini'
        at Function.Module._resolveFilename (module.js:338:15)
        at Function.Module._load (module.js:280:25)
        at Module.require (module.js:364:17)
        at require (module.js:380:17)
        at Object.<anonymous> (/root/nodebb/node_modules/npm/node_modules/config-chain/index.js:4:11)
        at Module._compile (module.js:456:26)
        at Object.Module._extensions..js (module.js:474:10)
        at Module.load (module.js:356:32)
        at Function.Module._load (module.js:312:12)
        at Module.require (module.js:364:17)
    
    21/7 20:21 [25890] - error: Error: Cannot find module './build/Release/magic'
        at Function.Module._resolveFilename (module.js:338:15)
        at Function.Module._load (module.js:280:25)
        at Module.require (module.js:364:17)
        at require (module.js:380:17)
        at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
        at Module._compile (module.js:456:26)
        at Object.Module._extensions..js (module.js:474:10)
        at Module.load (module.js:356:32)
        at Function.Module._load (module.js:312:12)
        at Module.require (module.js:364:17)
    Error: Cannot find module './build/Release/magic'
        at Function.Module._resolveFilename (module.js:338:15)
        at Function.Module._load (module.js:280:25)
        at Module.require (module.js:364:17)
        at require (module.js:380:17)
        at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
        at Module._compile (module.js:456:26)
        at Object.Module._extensions..js (module.js:474:10)
        at Module.load (module.js:356:32)
        at Function.Module._load (module.js:312:12)
        at Module.require (module.js:364:17)
    
    module.js:340
        throw err;
        ^
    Error: Cannot find module './build/Release/magic'
        at Function.Module._resolveFilename (module.js:338:15)
        at Function.Module._load (module.js:280:25)
        at Module.require (module.js:364:17)
        at require (module.js:380:17)
        at Object.<anonymous> (/root/nodebb/node_modules/mmmagic/index.js:3:13)
        at Module._compile (module.js:456:26)
        at Object.Module._extensions..js (module.js:474:10)
        at Module.load (module.js:356:32)
        at Function.Module._load (module.js:312:12)
        at Module.require (module.js:364:17)
    
  • npm i is your phriend

    NodeBB Upgrade Complete!

  • @Danny-McWilliams said:

    Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

    Tried to start nodebb, this was in log.

    Capture.JPG

    Usually when I get issues like this, I have to do an npm cache clean and then an npm install or npm rebuild

  • for some reason my ./nodebb upgrade script after git pull missed a ton of modules

  • trying to update, but npm i shows me that

    npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires async@'~0.2.9' but will load
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/async,
    npm WARN unmet dependency which is version 0.9.2
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires string@'~1.8.0' but will load
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/string,
    npm WARN unmet dependency which is version 3.3.0
    npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@>=0.0.137
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.0.18
    
    npm ERR! System Linux 3.16.0-43-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
    npm ERR! cwd /home/leksar/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! code EPEERINVALID
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR!     /home/leksar/nodebb/npm-debug.log
    npm ERR! not ok code 0
    

    Tried to do npm unlink nodebb-plugin-spam-be-gone and npm unlink nodebb-theme-ifsta-ui, but the result is the same. Any ideas ?

  • try npm uninstall nodebb-theme-vanilla and then reinstall it again, it might install the version that satisfies the dependancy.

    Save changes made to vanilla too if need be 🙂

  • same result

  • @leksar try run ./nodebb upgrade
    paste error from th@ ?

  • leksar@ubuntu:~/nodebb$ sudo ./nodebb upgrade
    [sudo] password for leksar:
    no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
    1. Bringing base dependencies up to date
    
    Error: The package [email protected] does not satisfy its siblings' peerDependencies requirements!
    
  • sounds like unlinking those plugins did nothing.

    I'm out of idea's but that was why it was complaining, maybe uninstall them if they aren't vital

    I dont use shoutbox or that other thingo

  • @Codejet said:

    I dont use shoutbox or that other thingo

    I'm not using them too, just tried for some time. The weird thing is that even uninstalling doesn't help. I would remove them manually, if there is a way.

  • @leksar Remove them from node_modules/ is the most manual way 😄

    Whenever the peer dependency error comes up, I just purge every module it mentions, and then run npm i

  • ok, so i restored my forum from a backup
    removed all unnecessary plugins by ACP (including spam-be-gone and ifsta-ui)
    checked that there was no plugin foldes in node_modules/
    restarted forum and checked it works well

    then:

    sudo git checkout v0.7.x
    sudo git fetch
    sudo git reset --hard origin/v0.7.x
    sudo npm i
    

    there was no more warnings, but the errors still exists

    npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@>=0.0.137
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.0.18
    
    npm ERR! System Linux 3.16.0-43-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
    npm ERR! cwd /home/leksar/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! code EPEERINVALID
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR!     /home/leksar/nodebb/npm-debug.log
    npm ERR! not ok code 0
    

    looks like the "links" are stored somethere else


Suggested Topics


  • 0 Votes
    4 Posts
    803 Views

    @PitaJ

    Thank you, will try it.

  • 0 Votes
    2 Posts
    685 Views

    That link is generated using the value of url in your config.json file. Change the url and remove the 4567 and set up nginx to reverse proxy.

  • upgrade to 0.6.x issue

    General Discussion
    15
    0 Votes
    15 Posts
    9k Views

    @julian said:

    @priapo Keep in mind putting a socket.io section in config.json doesn't do anything 😄

    We had just talked about this configuration option short time ago in the issue 😄 so obviously it does affect. But "transports": ["polling","websocket"] is now the Standard.

    @priapo if you can't use the websockets you can set also "transports": ["polling"], then you will only get the failures for the long polling request which throws errors.

    I just tested by connecting directly without any proxy before NodeBB. The timeout disappears.

    So one failure source is that the timeout is higher than what is allowed by the proxy e.g. cloudflare. So an option to adjust the timeout would be great!

    The failure throwing which are left now are:

    GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766084670-12&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766094756-13&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766096635-23&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766106720-24&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766108697-34&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766118775-35&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766120692-45&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766130783-46&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)
  • 0 Votes
    7 Posts
    3k Views

    @a_5mith I have a new issue now but it could be because I am running the rc version but I installed the latest version available (v0.5.0-2) but I am getting huge CPU spikes randomly from the forum that makes the server sluggish for up to 5 minutes.

  • 0 Votes
    18 Posts
    4k Views

    I was editing them in plain document mode. That was my bad. It didn't seem to make a difference. The endquote worked fine when we had the ip in the base url.

    And yeah! of course! I'm glad you like it.