Raspbian: can't start tango-db service due to Debian bug

# 3 years ago
mariocaptain	Hi all, I am using tango 9.2.5 on a Raspberry Pi 4, and there is a problem starting the tango database service at boot. At first, it works fine, but after a while the service doesn't start at boot any more. To make it work I have to restart the service everytime by: `$ sudo /etc/init.d/tango-db restart` Then after a while, it is very hard to restart the server this way. The output of `$ sudo /etc/init.d/tango-db status` is below. `pi@raspberry:~ $ sudo /etc/init.d/tango-db restart [ ok ] Restarting tango-db (via systemctl): tango-db.service. pi@raspberry:~ $ sudo /etc/init.d/tango-db status ● tango-db.service - LSB: Start the tango control system database daemon Loaded: loaded (/etc/init.d/tango-db; generated) Active: active (exited) since Sat 2021-02-13 11:32:40 GMT; 16h ago Docs: man:systemd-sysv-generator(8) Process: 1523 ExecStart=/etc/init.d/tango-db start (code=exited, status=0/SUCCESS)` After some searching, I found that this is due to a bug of Debian as reported here I am not sure how to patch/fix this. I wouldn't want to install a higher version of tango until an installation package for Raspberry Pi is available. Anyone experiencing the same and has some solution? Edited 3 years ago

# 3 years ago

Hi all,

I am using tango 9.2.5 on a Raspberry Pi 4, and there is a problem starting the tango database service at boot.

At first, it works fine, but after a while the service doesn't start at boot any more. To make it work I have to restart the service everytime by:

$ sudo /etc/init.d/tango-db restart

Then after a while, it is very hard to restart the server this way.
The output of

$ sudo /etc/init.d/tango-db status

is below.

pi@raspberry:~ $ sudo /etc/init.d/tango-db restart
[ ok ] Restarting tango-db (via systemctl): tango-db.service.
pi@raspberry:~ $ sudo /etc/init.d/tango-db status
● tango-db.service - LSB: Start the tango control system database daemon
   Loaded: loaded (/etc/init.d/tango-db; generated)
   Active: active (exited) since Sat 2021-02-13 11:32:40 GMT; 16h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1523 ExecStart=/etc/init.d/tango-db start (code=exited, status=0/SUCCESS)

After some searching, I found that this is due to a bug of Debian as reported here

I am not sure how to patch/fix this. I wouldn't want to install a higher version of tango until an installation package for Raspberry Pi is available.

Anyone experiencing the same and has some solution?

Edited 3 years ago

# 3 years ago
t-b	It might be easiest to apply the patch from the bug report, see https://salsa.debian.org/science-team/tango/-/merge_requests/1/diffs yourself. Which exact tango package version are you using?

# 3 years ago
mariocaptain	Thanks. I am using tango-db 9.2.5a+dfsg1-2+b2 Will try the patch now. Dave

# 3 years ago
t-b	Do you know if that tango package is straight from debian? If yes, I know who to ping for an updated package, as 9.3.4 came out recently.

# 3 years ago
mariocaptain	Yes, I install from the Debian repo (apt-get). But maybe it's MY BAD. I didn't install tango-starter from the beginning. I have installed and the problem seems to have gone. If it comes back I will apply the patch. On 9.3.4 I have a couple of months till production and I hope that it would be available on the official Debian repo. Thanks!

# 3 years ago
mariocaptain	It happens again, so I am gonna apply the patch. I understand that to apply the patch is to simply replace line 6 & 7 of the tango-starter file located in /etc/init.d/ from: `# Should-Start: tango-db # Should-Stop: tango-db` to `# Should-Start: tango-db network # Should-Stop: tango-db network` Edited 3 years ago

# 3 years ago

mariocaptain

It happens again, so I am gonna apply the patch. I understand that to apply the patch is to simply replace line 6 & 7 of the tango-starter file located in /etc/init.d/ from:

# Should-Start:      tango-db
# Should-Stop:       tango-db

# Should-Start:      tango-db network
# Should-Stop:       tango-db network

Edited 3 years ago

# 3 years ago
mariocaptain	Still doesn't work when there is no network (internet) connection at boot. Does anyone know how to correctly apply the patch? Thanks!