FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update #461

simonlock · 2020-01-11T12:15:12Z

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.

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

The text was updated successfully, but these errors were encountered:

oznu · 2020-01-11T12:23:49Z

I'll check this out soon. I haven't tested shells - you're in fact the first person I've come across who's setup Homebridge this way.

You can roll back to 4.6.7 for now.

sudo npm install -g --unsafe-perm [email protected]

Does your version of FreeNAS support Docker?

simonlock · 2020-01-11T12:32:12Z

Thank you for your quick reply and for letting me know how to roll back. I'm up and running for now. Freenas does support docker after first installing a linux vm so not very elegant. I look forward to hearing back from you.

oznu · 2020-01-11T12:34:28Z

I'll push an update soon to not crash on cpu stats failure / add the ability to turn it off.

You might not get CPU usage info on your dashboard anymore, but we'll see what I can do.

oznu · 2020-01-11T12:55:44Z

@simonlock can you let me know what platform Node.js reports you as being on?

You can do this at an interactive Node prompt.

node
os.platform()

simonlock · 2020-01-11T13:04:02Z

It displays 'freebsd'.

…

On Sat, 11 Jan 2020 at 12:55, oznu ***@***.***> wrote: @simonlock <https://github.com/simonlock> can you let me know what platform Node.js reports you as being on? You can do this at an interactive Node prompt. node os.platform() — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#461>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUGGG3ZYUO5KUJSZ2ESTI3Q5G6VBANCNFSM4KFRWY4Q> .

oznu · 2020-01-11T13:14:54Z

Perfect, thanks. The systeminformation module I'm now using does not support the "current load" command on FreeBSD. I'll find an alternative.

oznu · 2020-01-12T04:33:19Z

FreeBSD 12 seems to be ok.

oznu · 2020-01-12T04:51:26Z

Same with 11.2:

oznu · 2020-01-12T04:57:07Z

I couldn't replicate this in FreeBSD, I wasn't using a jailed shell though so that may have been the difference.

Either way, I've published a @test version for you to try that uses the same method to get CPU load as v4.6.7 did on freebsd only.

You can install it like this:

sudo npm install -g --unsafe-perm homebridge-config-ui-x@test

Let me know if that works for you.

simonlock · 2020-01-12T23:36:14Z

Thanks for your excellent support on this. I've installed your latest test update but Homebridge still continually restarts and I never get to see the status page.

The logs report:

I've now moved on to using Homebridge on a Raspberry PI running docker and I'm finding it to be a big improvement over the FreeNAS jail version with great visible logging; which was something that was very much lacking using pm2 on freeNAS. I'm happy to continue testing freeNAS if this is something you'd like to solve?

oznu · 2020-01-13T06:55:50Z

Thanks @simonlock,

If you could try one more time with the latest @test I think I have found all the issues:

sudo npm install -g --unsafe-perm homebridge-config-ui-x@test

Let me know if that works for you.

simonlock · 2020-01-13T07:30:01Z

I've just tried it out and yes you've solved it. Thanks for your support. The Raspberry Pi version is more feature-rich but this version now works and functions correctly.

oznu · 2020-01-13T09:36:58Z

Great; thanks for testing this out. It saves me having to setup and figure out FreeNAS 😄!

sidbena · 2020-01-13T14:03:47Z

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.

simonlock · 2020-01-13T22:43:26Z

Thank you Ted. I did struggle trying to get these pm2 logs to show up in Homebridge within a FreeNAS jail. However, I've now moved onto using Homebridge running on docker within a Raspberry Pi along with my other IOT related containers. Your instructions will certainly help if I decide to return to using Homebridge in a FreeNAS jail again in the future. Moreover, hopefully, your example given above will help others who might stumble across this.

…

On Mon, 13 Jan 2020 at 14:03, Ted Jangius ***@***.***> wrote: I don't mean to reopen the issue itself, more to point out to @simonlock <https://github.com/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. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#461>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUGGGZJTN4VTSH3SN4PPGLQ5RYEJANCNFSM4KFRWY4Q> .

Grinchii · 2020-01-19T15:58:57Z

It now works on FreeNAS with the newest Version.

But there seems to be a problem with 10GBE Mellanox Cards. While Homebridge is running the system gets flooded with noise from this card.

mlx4_core0: port level mtu is only used for IB ports
mlx4_core0: port level mtu is only used for IB ports
mlx4_core0: port level mtu is only used for IB ports
mlx4_core0: port level mtu is only used for IB ports
mlx4_core0: port level mtu is only used for IB ports

About every 3sec I get this message twice.

It seems like homebridge in the newest version is using something like sysctl quite often. This trys accessing the card and the error occurs.

simonlock added the question label Jan 11, 2020

oznu changed the title ~~Will not start after Homebridge Config UI X v4.7.0 update~~ FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update Jan 11, 2020

oznu closed this as completed Jan 13, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update #461

FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update #461

simonlock commented Jan 11, 2020

oznu commented Jan 11, 2020 •

edited

Loading

simonlock commented Jan 11, 2020

oznu commented Jan 11, 2020

oznu commented Jan 11, 2020

simonlock commented Jan 11, 2020 via email

oznu commented Jan 11, 2020

oznu commented Jan 12, 2020

oznu commented Jan 12, 2020

oznu commented Jan 12, 2020

simonlock commented Jan 12, 2020

oznu commented Jan 13, 2020

simonlock commented Jan 13, 2020

oznu commented Jan 13, 2020

sidbena commented Jan 13, 2020

simonlock commented Jan 13, 2020 via email

Grinchii commented Jan 19, 2020

FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update #461

FreeNAS Jail - Will not start after Homebridge Config UI X v4.7.0 update #461

Comments

simonlock commented Jan 11, 2020

oznu commented Jan 11, 2020 • edited Loading

simonlock commented Jan 11, 2020

oznu commented Jan 11, 2020

oznu commented Jan 11, 2020

simonlock commented Jan 11, 2020 via email

oznu commented Jan 11, 2020

oznu commented Jan 12, 2020

oznu commented Jan 12, 2020

oznu commented Jan 12, 2020

simonlock commented Jan 12, 2020

oznu commented Jan 13, 2020

simonlock commented Jan 13, 2020

oznu commented Jan 13, 2020

sidbena commented Jan 13, 2020

simonlock commented Jan 13, 2020 via email

Grinchii commented Jan 19, 2020

oznu commented Jan 11, 2020 •

edited

Loading