-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
Labels
bug
Something isn't working
Comments
Hi @jbob762 and thanks for your issue. Generally |
Thanks for the fast answer. Agreed it’s odd which made it difficult to troubleshoot. I am using the root user in the VM, the output of echo $HOME is /root and ls -l ~/.ssh shows the expected authorized_keys file. Anything else I can check?
…On Mon, Sep 30, 2024 at 05:14, Daniel Lando ***@***.***(mailto:On Mon, Sep 30, 2024 at 05:14, Daniel Lando <<a href=)> wrote:
Hi ***@***.***(https://github.com/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?
—
Reply to this email directly, [view it on GitHub](#3918 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AM3SNTFDIL34LOOFTKFZHRDZZEI57AVCNFSM6AAAAABPBXQEJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBSGU3TENBXGE).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@jbob762 using the root user isn't unsafe? |
Do you believe root could be causing the difference in operation?
I appreciate the concern. It’s in a VM on an isolated subnet, I’ll let you know if it gets up to any mischief. Rootless is the goal. It’s not obvious to me why that should make a difference with the tilde.
…On Mon, Sep 30, 2024 at 11:00, Daniel Lando < ***@***.***(mailto:On Mon, Sep 30, 2024 at 11:00, Daniel Lando <<a href=)> wrote:
***@***.***(https://github.com/jbob762) using the root user isn't unsafe?
—
Reply to this email directly, [view it on GitHub](#3918 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AM3SNTC2OI6UEIEN7CAO45LZZFRPDAVCNFSM6AAAAABPBXQEJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBTGQ2TKMJTGA).
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
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
Checklist
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.
The text was updated successfully, but these errors were encountered: