Kill EPERM error in dev

Unsolved Technical Support
  • I've just refreshed by DEV instance so that it is a replica of production, and when I attempt to start it, I get

    Error: kill EPERM
        at process.kill (node:internal/process/per_thread:221:13)
        at /home/sudonix.dev/nodebb/loader.js:215:14
        at /home/sudonix.dev/nodebb/node_modules/graceful-fs/graceful-fs.js:362:16
        at FSReqCallback.oncomplete (node:fs:197:23) {
      errno: -1,
      code: 'EPERM',
      syscall: 'kill'
    }
    

    ./nodebb dev works fine, but I can't access once I kill the dev console. Production doesn't seem to have this issue, and works without problems.

    Thanks

  • Is that a v3 issue, or just an oddity you're seeing now on v2.x?

    Check the running instances to see which user is running ps aux | grep node

    Both loader.js and app.js should be running under the same user.


Suggested Topics


  • Invalid CSRF on dev install

    Solved Technical Support
    0 Votes
    2 Posts
    326 Views
  • 0 Votes
    4 Posts
    226 Views
  • 0 Votes
    14 Posts
    867 Views
  • 0 Votes
    1 Posts
    548 Views
  • 0 Votes
    3 Posts
    1229 Views