How do i enable pulse as a service?

[cardinal808]

I cannot manage to enable pulse as a service on a proxmox lxc. what am i missing?

root@pulse:~# systemctl status pulse
Unit pulse.service could not be found.
root@pulse:~# systemctl enable pulse
Failed to enable unit: Unit file pulse.service does not exist.

I now start the application by re-installing pulse.

[INFO] Pulse v4.14.0 is installed but not running

What would you like to do?
1) Update to v4.15.0-rc.4 (release candidate)
2) Reinstall current version
3) Remove Pulse
4) Cancel
Select option [1-4]: 2
[INFO] Backing up existing configuration...
Failed to stop pulse.service: Unit pulse.service not loaded.
[INFO] Downloading Pulse...
[INFO] Latest version: v4.14.0
[INFO] Detected architecture: x86_64 (amd64)
[INFO] Downloading from: https://github.com/rcourtman/Pulse/releases/download/v4.14.0/pulse-v4.14.0-linux-amd64.tar.gz
[SUCCESS] Pulse binary installed to /opt/pulse/bin/pulse
[SUCCESS] Symlink created at /usr/local/bin/pulse
[SUCCESS] Version verified: v4.14.0
[INFO] Setting up directories...
[INFO] Installing systemd service...
[INFO] Using existing service name: pulse-backend
[INFO] Starting Pulse...
[SUCCESS] Pulse started successfully

[rcourtman]

hey @swtrse,

the service is installed as pulse-backend not pulse on your container (legacy naming from older installs).

you could use systemctl status pulse-backend to manage it, but honestly i'd recommend just recreating the container using the install script's option 1:

curl -sSL https://raw.githubusercontent.com/rcourtman/Pulse/main/install.sh | bash

choose option 1 to create a new proxmox lxc. this will give you a fresh container with the correct pulse service name and latest configuration. it's cleaner than trying to fix the existing one.

the new container will have everything set up properly and you can just delete the old one once it's working.