Replication Details:
Device: Pod 5
Branch: main - v1.8.1 (I think?)
Problem:
I installed SleepyPod (main branch) for the first time on my Pod 5 and it installed successfully. However, it was continuously failing to start the service:
root@eight-pod:~# sp-logs
Apr 28 19:55:04 eight-pod systemd[1]: Started SleepyPod Core Service.
Apr 28 19:55:04 eight-pod sh[6331]: /bin/sh: line 1: /usr/local/bin/node: No such file or directory
Apr 28 19:55:05 eight-pod systemd[1]: sleepypod.service: Main process exited, code=exited, status=127/n/a
Apr 28 19:55:05 eight-pod systemd[1]: sleepypod.service: Failed with result 'exit-code'.
Apr 28 19:55:15 eight-pod systemd[1]: sleepypod.service: Scheduled restart job, restart counter is at 15.
Apr 28 19:55:15 eight-pod systemd[1]: Stopped SleepyPod Core Service.
Apr 28 19:55:15 eight-pod systemd[1]: Starting SleepyPod Core Service...
Apr 28 19:55:15 eight-pod sp-maintenance[6358]: === SleepyPod Maintenance ===
Apr 28 19:55:15 eight-pod sp-maintenance[6358]: Vacuuming journal (58MB → 50MB)...
Apr 28 19:55:16 eight-pod sp-maintenance[6358]: Pruning pnpm store (1520MB)...
Apr 28 19:55:19 eight-pod sp-maintenance[6371]: Removed all cached metadata files
Apr 28 19:55:19 eight-pod sp-maintenance[6371]: Removed 0 files
Apr 28 19:55:19 eight-pod sp-maintenance[6371]: Removed 0 packages
Apr 28 19:55:19 eight-pod sp-maintenance[6358]: Maintenance complete. 844MB free.
Apr 28 19:55:19 eight-pod systemd[1]: Started SleepyPod Core Service.
Apr 28 19:55:19 eight-pod sh[6387]: /bin/sh: line 1: /usr/local/bin/node: No such file or directory
Apr 28 19:55:20 eight-pod systemd[1]: sleepypod.service: Main process exited, code=exited, status=127/n/a
Apr 28 19:55:20 eight-pod systemd[1]: sleepypod.service: Failed with result 'exit-code'.
Apr 28 19:55:30 eight-pod systemd[1]: sleepypod.service: Scheduled restart job, restart counter is at 16.
Apr 28 19:55:30 eight-pod systemd[1]: Stopped SleepyPod Core Service.
Apr 28 19:55:30 eight-pod systemd[1]: Starting SleepyPod Core Service...
Apr 28 19:55:30 eight-pod sp-maintenance[6419]: === SleepyPod Maintenance ===
Apr 28 19:55:30 eight-pod sp-maintenance[6419]: Vacuuming journal (58MB → 50MB)...
Apr 28 19:55:31 eight-pod sp-maintenance[6419]: Pruning pnpm store (1520MB)...
Apr 28 19:55:34 eight-pod sp-maintenance[6432]: Removed all cached metadata files
Apr 28 19:55:34 eight-pod sp-maintenance[6432]: Removed 0 files
Apr 28 19:55:34 eight-pod sp-maintenance[6432]: Removed 0 packages
Apr 28 19:55:34 eight-pod sp-maintenance[6419]: Maintenance complete. 844MB free.
Apr 28 19:55:34 eight-pod systemd[1]: Started SleepyPod Core Service.
Apr 28 19:55:34 eight-pod sh[6448]: /bin/sh: line 1: /usr/local/bin/node: No such file or directory
...
...
...
SleepyPod is looking for the node directory located at /usr/local/bin/node. On my Pod 5, it is installed at this directory:
root@eight-pod:~# which node
/usr/bin/node
To fix this, I just created a symlink between these two directories:
mkdir -p /usr/local/bin
ln -sf /usr/bin/node /usr/local/bin/node
ln -sf /usr/bin/npm /usr/local/bin/npm
Potential Solution:
We could just include these symlink creation lines in the install script for SleepyPod. Other pods seem to have Node installed at /usr/local/bin/node, but it is in /usr/bin/node on my Pod.
Replication Details:
Device: Pod 5
Branch:
main - v1.8.1 (I think?)Problem:
I installed SleepyPod (
mainbranch) for the first time on my Pod 5 and it installed successfully. However, it was continuously failing to start the service:SleepyPod is looking for the
nodedirectory located at/usr/local/bin/node. On my Pod 5, it is installed at this directory:To fix this, I just created a symlink between these two directories:
Potential Solution:
We could just include these symlink creation lines in the install script for SleepyPod. Other pods seem to have Node installed at
/usr/local/bin/node, but it is in/usr/bin/nodeon my Pod.