systemctl complain about "archipel.pid"

[ikus060]

Starting archipel using system archipel start is not working as expected. systemd is waiting for a pid file.

debian@test-archipel:~$ sudo service archipel start
[sudo] password for debian: 
^C

debian@test-archipel:~$ sudo service archipel status
● archipel.service - LSB: daemon for archipel orchestrator suite
   Loaded: loaded (/etc/init.d/archipel)
   Active: activating (start) since Sun 2016-10-09 08:04:01 EDT; 59s ago
  Process: 954 ExecStart=/etc/init.d/archipel start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/archipel.service
           └─961 /usr/bin/python -W ignore::DeprecationWarning /usr/local/bin/runarchipel --config=/etc/archipel/archipel.conf

Oct 09 08:04:03 test-archipel archipel[954]: [47B blob data]
Oct 09 08:04:03 test-archipel systemd[1]: PID file /var/run/archipel.pid not readable (yet?) after start.

The faulty line seams to be in /etc/init.d/archipel.

# pidfile: /var/run/archipel.pid

[CyrilPeponnet]

I don't have this issue under Centos 7.X. Can you use the systemd unit archipel-agent looks like the legacy init.d is kind of conflicting with the systemd one. systemctl start archipel-agent