Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation PM2 ecosystem file. #3918

Open
3 tasks done
jbob762 opened this issue Sep 29, 2024 · 5 comments
Open
3 tasks done

Documentation PM2 ecosystem file. #3918

jbob762 opened this issue Sep 29, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@jbob762
Copy link

jbob762 commented Sep 29, 2024

Checklist

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Deploy method

NPM

Z-Wave JS UI version

9.21.0

ZwaveJS version

13.4.0

Describe the bug

zwavejsui shows up in 'pm2 list' as a running service, but it is not running and not accessible via the web UI. There are errors in the logs about invalid PID.

To Reproduce

Hardware config: a Debian VM in Proxmox with USB passthrough of a Zooz ZST10 USB stick (/dev/ttyACM0)
Software config: installed in the VM using NPM method with PM2 to run as a service per "other-methods" in the docs, including copy->paste the ecosystem config

Expected behavior

zwave-js-ui running and accessible from the web UI

Additional context

It appears PM2 is unhappy with the relative paths (tilde) in ecosystem.config.js
When converted to direct paths it works as expected, the web UI comes up, and the service survives reboot.

Thanks and really appreciate zwave-js-ui! I'm (finally) migrating from zwave2mqtt and doing some testing with it running in a VM. Hopefully helps someone else if they run into the same thing.

@jbob762 jbob762 added the bug Something isn't working label Sep 29, 2024
@robertsLando
Copy link
Member

Hi @jbob762 and thanks for your issue. Generally ~ is used to refer to the user home directory path, I tried it on my side and it's working, could it be that the user you are using doesn't have one?

@jbob762
Copy link
Author

jbob762 commented Sep 30, 2024 via email

@robertsLando
Copy link
Member

@jbob762 using the root user isn't unsafe?

@jbob762
Copy link
Author

jbob762 commented Oct 1, 2024 via email

@robertsLando
Copy link
Member

It’s not obvious to me why that should make a difference with the tilde.

It doesn't make sense to me nwighter but it's the only thing that's "unusual" in your setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants