Home / ubuntu / Questions / 1373179
In Process
mevers303
Asked: 2021-11-03 12:58:50 +0800 CST

Upgraded to 21.10, now getting socket error `Error: Command failed: cat /sys/fs/cgroup/memory/memory.stat` using Node.js

  • 772

Last night I upgraded my Ubuntu to version 21.10 using the automatic installer. Now I am unable to execute my Node.js application I am working on for my job. I'm getting two different errors:

Error: Command failed: cat /sys/fs/cgroup/memory/memory.limit_in_bytes 
cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory

    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:486:12)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:486:12)
    at Pipe.<anonymous> (net.js:673:12)
    at Pipe.callbackTrampoline (internal/async_hooks.js:129:14) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'cat /sys/fs/cgroup/memory/memory.limit_in_bytes '
}
Error: Command failed: cat /sys/fs/cgroup/memory/memory.stat 
cat: /sys/fs/cgroup/memory/memory.stat: No such file or directory

    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:315:20)
    at ChildProcess.EventEmitter.emit (domain.js:486:12)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:486:12)
    at Pipe.<anonymous> (net.js:673:12)
    at Pipe.callbackTrampoline (internal/async_hooks.js:129:14) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'cat /sys/fs/cgroup/memory/memory.stat '
}

Obviously those two files, /sys/fs/cgroup/memory/memory.stat and /sys/fs/cgroup/memory/memory.limit_in_bytes no longer exist and the Node.js framework needs them to open a socket. I haven't been able to find a solution on Google. I have tried reinstalling Node and the npm package.

Can anyone help?

nodejs

0 Answers