homebridge-config-ui-x: FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update

Describe Your Problem: After installing the Homebridge Config UI X v4.7.0 update homebridge fails to start and continually tries to restart unsuccessfully. I am running homebridge in a Freenas Jail as detailed https://github.com/nfarina/homebridge/wiki/FreeNAS-11-Installation-using-a-Jail. and using pm2.

I’ve tried reinstalling Homebridge. Resetting Homebridge and using just a very simple default json.config and the problem still persists. Perhaps thsi problem is now related to the new UI displaying the cpu usage because the logs mention cpu.js?

Logs:

Show the Homebridge / Homebridge Config UI X logs here.

0|homebridge | [1/11/2020, 11:18:34 AM] [Config] Homebridge Config UI X v4.7.0 is listening on :: port 8080 0|homebridge | TypeError: Cannot read property ‘replace’ of undefined 0|homebridge | at /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/systeminformation/lib/cpu.js:817:50 0|homebridge | at Array.forEach (<anonymous>) 0|homebridge | at /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/systeminformation/lib/cpu.js:814:19 0|homebridge | at ChildProcess.exithandler (child_process.js:292:7) 0|homebridge | at ChildProcess.emit (events.js:219:5) 0|homebridge | at maybeClose (internal/child_process.js:1027:16) 0|homebridge | at Socket.<anonymous> (internal/child_process.js:442:11) 0|homebridge | at Socket.emit (events.js:219:5) 0|homebridge | at Pipe.<anonymous> (net.js:666:12)

Homebridge Config:

    "platforms": [
        {
            "name": "Config",
            "port": 8080,
            "auth": "form",
            "theme": "auto",
            "tempUnits": "c",
            "sudo": true,
            "ssl": {
                "key": "/usr/local/etc/letsencrypt/live/xxx/privkey.pem",
                "cert": "/usr/local/etc/letsencrypt/live/xxx/cert.pem"
            },
            "platform": "config"
        },

Screenshots:

Environment:

  • Node.js Version: Node.js v13.3.0
  • NPM Version: 6.13.6
  • Homebridge Version: 0.4.50
  • Homebridge Config UI X Version:v4.7.0
  • Operating System: FreeNAS-11.2-U7
  • Process Supervisor: freeBSD jail

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 16 (9 by maintainers)

Most upvoted comments

I don’t mean to reopen the issue itself, more to point out to @simonlock that there are logs when running homebridge (and homebridge-config-ui-x), managed with pm2, through a FreeNAS jail too. The logs are, what I believe, automatically created at /<user pm2 is run as>/.pm2/logs/<pm2 service name>/ as <service name>-[out|error].log so in my case I’ve got two logs at:

/root/.pm2/logs/homebridge-out.log
/root/.pm2/logs/homebridge-error.log

I’ve chosen to show the logs within homebridge-config-ui-x by going into the settings for the plugin and under Log Viewer Setup I’ve chosen Custom Command and for the command:

tail -f /root/.pm2/logs/homebridge-out.log /root/.pm2/logs/homebridge-error.log

This solution makes new log entries show up through the logging web interface that homebridge-config-ui-x provides. Sorry for the long explanation (and possible reopening) of the issue.