Server mode on Gentoo: TypeError in logger.js
I’ve tried to perform a fresh install of MM2 on a Gentoo system, intended to run as a headless server system. There was no previous working installation of MM2 on that system - in fact, this is my very first installation of MM2. I’m using the Node.js version supplied via the Gentoo package management system portage, which is
Other than that, I’ve followed the steps in the installation instructions exactly. Running the application with
npm run startvia a SSH connection with X11 tunneling works (slow, but that was to be expected), so there’s nothing obviously wrong with the config or the installation. Now I want to use the server-only feature, which does not work:
~/MagicMirror $ npm run server > email@example.com server /home/magicmirror/MagicMirror > node ./serveronly /home/magicmirror/MagicMirror/js/logger.js:32 timeStamp: Function.prototype.bind.call(console.timeStamp, console) ^ TypeError: Bind must be called on a function at bind (<anonymous>) at /home/magicmirror/MagicMirror/js/logger.js:32:38 at /home/magicmirror/MagicMirror/js/logger.js:16:20 at Object.<anonymous> (/home/magicmirror/MagicMirror/js/logger.js:21:3) at Module._compile (internal/modules/cjs/loader.js:1200:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10) at Module.load (internal/modules/cjs/loader.js:1049:32) at Function.Module._load (internal/modules/cjs/loader.js:937:14) at Module.require (internal/modules/cjs/loader.js:1089:19) at require (internal/modules/cjs/helpers.js:73:18) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! firstname.lastname@example.org server: `node ./serveronly` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the email@example.com server script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /home/magicmirror/.npm/_logs/2020-09-26T06_38_24_702Z-debug.log
Is this a bug I should report or is there something else I’m missing?
…commenting out the offending line in logger.js appears to resolve the issue, and I can find no other reference to timeStamp - is this line needed for anything…?