Agent not starting on Debian - but service restart helps!?

[mensa]

Hello,

I successfully installed the Linux veeam by that command:

Code: Select all

apt install veeam

Code: Select all

root@Server:~# uname -a
Linux Server 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux

When I want to start veeam agent I get that errors:

Code: Select all

root@Server:~# veeam
Connection refused
Failed to connect: /var/tmp/veeam/socket/veeam.sock.
Failed to connect to veeamservice daemon.

Service is not running:

Code: Select all

root@Server:~# service veeamservice status
● veeamservice.service - Veeam Agent for Linux service daemon
   Loaded: loaded (/usr/lib/systemd/system/veeamservice.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

May 28 13:01:48 Server systemd[1]: /usr/lib/systemd/system/veeamservice.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/veeamservice.pid → /run/veeamservice.pid; please update the unit file accordingly.
May 28 13:03:59 Server systemd[1]: /usr/lib/systemd/system/veeamservice.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/veeamservice.pid → /run/veeamservice.pid; please update the unit file accordingly.
May 28 13:07:43 Server systemd[1]: /usr/lib/systemd/system/veeamservice.service:6: PIDFile= references path below legacy directory /var/run/, updating /var/run/veeamservice.pid → /run/veeamservice.pid; please update the unit file accordingly.

But when I do a restart of the service it is working and I can use the veeam program:

Code: Select all

root@Server:~#service veeamservice restart
root@Server:~#service veeamservice status
● veeamservice.service - Veeam Agent for Linux service daemon
   Loaded: loaded (/usr/lib/systemd/system/veeamservice.service; disabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-05-28 13:09:21 CEST; 27s ago
  Process: 7438 ExecStart=/usr/sbin/veeamservice --daemonize --pidfile=${PIDFILE} (code=exited, status=0/SUCCESS)
 Main PID: 7442 (veeamservice)
    Tasks: 5 (limit: 2355)
   Memory: 5.4M
   CGroup: /system.slice/veeamservice.service
           └─7442 /usr/sbin/veeamservice --daemonize --pidfile=/var/run/veeamservice.pid

May 28 13:09:21 Server systemd[1]: Starting Veeam Agent for Linux service daemon...
May 28 13:09:21 Server systemd[1]: veeamservice.service: Failed to parse PID from file /run/veeamservice.pid: Invalid argument
May 28 13:09:21 Server systemd[1]: veeamservice.service: Supervising process 7442 which is not our child. We'll most likely not notice when it exits.
May 28 13:09:21 Server veeamservice[7442]: Service started.
May 28 13:09:21 Server veeamservice[7442]: Initializing log file [/var/log/veeam/veeamsvc.log].
May 28 13:09:21 Server systemd[1]: Started Veeam Agent for Linux service daemon.

But after a reboot of that debian machine, the veeam service is dead again. How can one fix that please?

[PTide]

Hi,

Loaded: loaded (/usr/lib/systemd/system/veeamservice.service; disabled; vendor preset: enabled)

It seems that autostart is not enabled for veeamservice.
Kindly run

Code: Select all

sudo systemctl enable veeamservice

and see if the issue is resolved.

I'll check with QC whether it's a known bug or just a glitch.

Thanks!

[mensa]

That worked, thank you!
Would be good if that is done automatically by the installer, or?

[PTide]

Actually, it is supposed to be done automatically by the installer. If you could open a case and upload logs (/var/log/dpkg.log and /var/log/apt/history.log) and post your case ID that would be great.

Thanks!

[Capt.Skoomer]

Hello mensa,

thanks for this "solution". It seeams that this is a general problem of the agent. Now our Backup is running fine again.

Kinde Regards

[PTide]

@@Capt.Skoomer ,

Would you submit logs for troubleshooting via support case then, please?

Thanks!