Service doesn't work on reboot Topic is solved

[xavierlp]

Hello all.

I just finished to build a new script with the help of this page
https://www.domoticz.com/wiki/Presence_ ... Beacon%29

All is ok if I run the service manually but after every reboot the service is failed!

I built the file check_beacon_presence.service as is

Code: Select all

Description=check_beacon_presence Service
After=multi-user.target

[Service]
User=root
Type=idle
ExecStart=python /usr/local/bin/check_beacon_presence.py

[Install]
WantedBy=multi-user.target

then I activated the service

Code: Select all

 sudo systemctl enable  check_beacon_presence.service

Then start the service like this

Code: Select all

 sudo systemctl start check_beacon_presence.service

All is working

Code: Select all

pi@raspberrypi4:~ $ sudo systemctl status check_beacon_presence.service -l
● check_beacon_presence.service
   Loaded: loaded (/etc/systemd/system/check_beacon_presence.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-04-18 19:30:22 CEST; 1min 7s ago
 Main PID: 7213 (python)
    Tasks: 2 (limit: 3911)
   Memory: 12.0M
   CGroup: /system.slice/check_beacon_presence.service
           └─7213 /usr/bin/python /usr/local/bin/check_beacon_presence.py

avril 18 19:30:22 raspberrypi4 systemd[1]: Started check_beacon_presence.service.
avril 18 19:30:22 raspberrypi4 sudo[7219]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/hciconfig hci1 down
avril 18 19:30:22 raspberrypi4 sudo[7219]: pam_unix(sudo:session): session opened for user root by (uid=0)
avril 18 19:30:22 raspberrypi4 sudo[7219]: pam_unix(sudo:session): session closed for user root
avril 18 19:30:22 raspberrypi4 sudo[7229]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/hciconfig hci1 up
avril 18 19:30:22 raspberrypi4 sudo[7229]: pam_unix(sudo:session): session opened for user root by (uid=0)
avril 18 19:30:22 raspberrypi4 sudo[7229]: pam_unix(sudo:session): session closed for user root
avril 18 19:30:22 raspberrypi4 sudo[7239]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/hciconfig
avril 18 19:30:22 raspberrypi4 sudo[7239]: pam_unix(sudo:session): session opened for user root by (uid=0)
avril 18 19:30:22 raspberrypi4 sudo[7239]: pam_unix(sudo:session): session closed for user root

But after a reboot I can read this

Code: Select all

pi@raspberrypi4:~ $ sudo systemctl status check_beacon_presence.service -l
● check_beacon_presence.service
   Loaded: loaded (/etc/systemd/system/check_beacon_presence.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-04-18 19:25:09 CEST; 1s ago
  Process: 4777 ExecStart=/usr/bin/python /usr/local/bin/check_beacon_presence.py (code=exited, status=1/FAILURE)
 Main PID: 4777 (code=exited, status=1/FAILURE)

avril 18 19:25:09 raspberrypi4 sudo[4803]: pam_unix(sudo:session): session opened for user root by (uid=0)
avril 18 19:25:09 raspberrypi4 sudo[4803]: pam_unix(sudo:session): session closed for user root
avril 18 19:25:09 raspberrypi4 python[4777]: Traceback (most recent call last):
avril 18 19:25:09 raspberrypi4 python[4777]:   File "/usr/local/bin/check_beacon_presence.py", line 182, in <module>
avril 18 19:25:09 raspberrypi4 python[4777]:     hci_toggle_le_scan(sock, 0x01)
avril 18 19:25:09 raspberrypi4 python[4777]:   File "/usr/local/bin/check_beacon_presence.py", line 102, in hci_toggle_le_scan
avril 18 19:25:09 raspberrypi4 python[4777]:     bluez.hci_send_cmd(sock, OGF_LE_CTL, OCF_LE_SET_SCAN_ENABLE, cmd_pkt)
avril 18 19:25:09 raspberrypi4 python[4777]: _bluetooth.error: (1, 'Operation not permitted')
avril 18 19:25:09 raspberrypi4 systemd[1]: check_beacon_presence.service: Main process exited, code=exited, status=1/FAILURE
avril 18 19:25:09 raspberrypi4 systemd[1]: check_beacon_presence.service: Failed with result 'exit-code'.

So my first idea it was because root user
So I ran this command

Code: Select all

pi@raspberrypi4:~ $ sudo su
root@raspberrypi4:/home/pi# python /usr/local/bin/check_beacon_presence.py

And all is ok

So manually od ok but after rebbot no!

I am using RPI4 and buster

I can't understand where is my mistake

Any help or advice very appreciated

Have a good day

[MikeF]

I think your After clause is probably wrong - you want something like

Code: Select all

After=network.target

[xavierlp]

MikeF

Thanks a lot : it's works perfectly now

You made my day ....

[McMelloW]

Dear all.

Since the update to buster,i Have the same kind of problem. I hope some can point me in the right direction to solve it.

This is my service file.

Code: Select all

# This is an example systemd configuration file for using in an systemd environment
# its was written for the archlinux-arm os
# modify User and ExecStart for your needs

[Unit]
Description=iSpindle-genericTCP server and relay
After=multi-user.target

[Service]
Type=idle
User=pi
ExecStart=/usr/bin/python3 /usr/local/bin/iSpindle.py
Restart=always
TimeoutStartSec=10
RestartSec=10

[Install]
WantedBy=multi-user.target

When I enable the service and start it It does work. See the log below.

Code: Select all

pi@mcmellow-pi:~ $ sudo systemctl status ispindle-srv.service
? ispindle-srv.service
   Loaded: loaded (/etc/init.d/ispindle-srv.service; generated)
   Active: failed (Result: exit-code) since Thu 2020-05-14 19:00:49 CEST; 1min 51s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 27666 ExecStart=/etc/init.d/ispindle-srv.service start (code=exited, status=203/EXEC)

May 14 19:00:49 mcmellow-pi systemd[1]: Starting ispindle-srv.service...
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed to execute command: Exec format error
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 14 19:00:49 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

[FireWizard]

Hello @Mcmellow.

You said:

When I enable the service and start it It does work.

However, if I see the file below it displays:

Active: failed

and

May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed to execute command: Exec format error
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 14 19:00:49 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

Does this work? Or are my observations wrong?

Regards

[McMelloW]

Hello @Mcmellow.

You said:

When I enable the service and start it It does work.

However, if I see the file below it displays:

Active: failed

and

May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed to execute command: Exec format error
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 14 19:00:49 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

Does this work? Or are my observations wrong?


Regards

No it does not start. This is what happen.

Code: Select all

pi@mcmellow-pi:~ $ sudo systemctl start ispindle-srv.service
Job for ispindle-srv.service failed because the control process exited with error code.
See "systemctl status ispindle-srv.service" and "journalctl -xe" for details.
pi@mcmellow-pi:~ $

This is the status after the failed start.

Code: Select all

pi@mcmellow-pi:~ $ sudo systemctl status ispindle-srv.service
? ispindle-srv.service
   Loaded: loaded (/etc/init.d/ispindle-srv.service; generated)
   Active: failed (Result: exit-code) since Thu 2020-05-14 19:00:49 CEST; 1min 51s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 27666 ExecStart=/etc/init.d/ispindle-srv.service start (code=exited, status=203/EXEC)

May 14 19:00:49 mcmellow-pi systemd[1]: Starting ispindle-srv.service...
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed to execute command: Exec format error
May 14 19:00:49 mcmellow-pi systemd[27666]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 14 19:00:49 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 14 19:00:49 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

[FireWizard]

Ho @McMelloW,

Can you check a few things?

The error message (code=exited, status=203/EXEC) is often seen when the script itself or its interpreter cannot be executed.

It could have these reasons:

wrong path, (/usr/local/bin/iSpindle.py)

script not executable

no shebang (first line)

wrong path in shebang (e.g. /bin/python3)

internal files in your script might be missing access permissions.

Regards

[McMelloW]

@FireWizard Thanks very much for your checking.

Ho @McMelloW,

Can you check a few things?

The error message (code=exited, status=203/EXEC) is often seen when the script itself or its interpreter cannot be executed.

It could have these reasons:

I will check.

wrong path, (/usr/local/bin/iSpindle.py

script not executable

Script will run OK from command line

Code: Select all

$ /usr/bin/python3 /usr/local/bin/iSpindle.py

So script is executable and does run OK. path is OK

no shebang (first line)

wrong path in shebang (e.g. /bin/python3)

internal files in your script might be missing access permissions.

Regards

shebang line and shebang path are correct. Otherwise it would not run correctly before.

It did run before Buster with insserv. But with Buster you have to remove insserv, because this does not OK. And it is build inin buster.

[FireWizard]

Hi,

@McMellow,

If I try to "google" iSpindle.py I find Python2 scripts.
Are you sure that the script is Python3?
Check the shebang,

Regards

[McMelloW]

Hi,

@McMellow,

If I try to "google" iSpindle.py I find Python2 scripts.
Are you sure that the script is Python3?
Check the shebang,

Regards

Sure it is python3. This is the header:

Code: Select all

#!/usr/bin/env python3
# Version 3.0
# Modified version for Python 3
# Some string handling had to be changed for python3
#  

How can it else work on a command line like this.

Code: Select all

$ /usr/bin/python3 /usr/local/bin/iSpindle.py

[FireWizard]

Hi @McMelloW,

You are right, otherwise the commandline would have failed also.

Can you try the following command:

Code: Select all

journalctl -u ispindle-srv.service

Regards

[McMelloW]

Can you try the following command:

Code: Select all

journalctl -u ispindle-srv.service

Regards

Thanks FireWizard.
Getting a bit frustrated about Buster.It is now asking for user-id password authentication when a service is started interactive.
Below you see what happens after I started the service; then the status and finaly the journalctl

Code: Select all

pi@mcmellow-pi:~ $ systemctl start ispindle-srv.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'ispindle-srv.service'.
Multiple identities can be used for authentication:
 1.  ,,, (pi)
 2.  root
Choose identity to authenticate as (1-2): 1
Password:
==== AUTHENTICATION COMPLETE ===
Job for ispindle-srv.service failed because the control process exited with error code.
See "systemctl status ispindle-srv.service" and "journalctl -xe" for details.

pi@mcmellow-pi:~ $ systemctl status ispindle-srv.service
? ispindle-srv.service
   Loaded: loaded (/etc/init.d/ispindle-srv.service; generated)
   Active: failed (Result: exit-code) since Fri 2020-05-15 15:04:45 CEST; 1min 4s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4845 ExecStart=/etc/init.d/ispindle-srv.service start (code=exited, status=203/EXEC)

May 15 15:04:45 mcmellow-pi systemd[1]: Starting ispindle-srv.service...
May 15 15:04:45 mcmellow-pi systemd[4845]: ispindle-srv.service: Failed to execute command: Exec format error
May 15 15:04:45 mcmellow-pi systemd[4845]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 15 15:04:45 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 15 15:04:45 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 15 15:04:45 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

pi@mcmellow-pi:~ $ sudo journalctl -u ispindle-srv.service
May 15 15:04:45 mcmellow-pi systemd[1]: Starting ispindle-srv.service...
May 15 15:04:45 mcmellow-pi systemd[4845]: ispindle-srv.service: Failed to execute command: Exec format error
May 15 15:04:45 mcmellow-pi systemd[4845]: ispindle-srv.service: Failed at step EXEC spawning /etc/init.d/ispindle-srv.service: Exec format error
May 15 15:04:45 mcmellow-pi systemd[1]: ispindle-srv.service: Control process exited, code=exited, status=203/EXEC
May 15 15:04:45 mcmellow-pi systemd[1]: ispindle-srv.service: Failed with result 'exit-code'.
May 15 15:04:45 mcmellow-pi systemd[1]: Failed to start ispindle-srv.service.

[FireWizard]

Hello @McMellow,

You wrote:

Getting a bit frustrated about Buster.It is now asking for user-id password authentication when a service is started interactive.

This has nothing to do with Buster, but with the fact that you tried to start the service WITHOUT sudo. Previously you started that service with sudo.

Did you also try sudo journalctl -xe, as suggested?

Try to do some research now.

Regards

[McMelloW]

Hello @McMellow,

You wrote:

Getting a bit frustrated about Buster.It is now asking for user-id password authentication when a service is started interactive.

This has nothing to do with Buster, but with the fact that you tried to start the service WITHOUT sudo. Previously you started that service with sudo.

Did you also try sudo journalctl -xe, as suggested?

Try to do some research now.

Regards

Yes you are right, had to use sudo. That is one thing solved

[FireWizard]

Hello @McMellow,

I have a question.

Is the software iSpindle retrieved from:

https://github.com/avollkopf/iSpindel-T ... rv.service

If so, I see that indeed the file iSpindle.py is a Python 3 file:

#!/usr/bin/env python3
# Version 3.0
# Modified version fpor Python 3
# Some string handling had to be changed for python3

But, I see also that the file ispindle-srv is not a python file:

#!/bin/sh

### BEGIN INIT INFO
# Provides: ispindle-srv
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: iSpindle-genericTCP server and relay
# Description: genericTCP backend for iSpindle providing data forwarding to ubidots csv and mysql

The file ispindle-srv.service contains:

# This is an example systemd configuration file for using in an systemd environment
# its was written for the archlinux-arm os
# modify User and ExecStart for your needs

[Unit]
Description=iSpindle-genericTCP server and relay
After=multi-user.target

[Service]
Type=idle
User=alarm
ExecStart=/usr/bin/python2 /home/alarm/iSpindle.py
Restart=always
TimeoutStartSec=10
RestartSec=10

[Install]
WantedBy=multi-user.target


### END INIT INFO

# Change the next 3 lines to suit where you install your script and what you want to call it
DIR=/usr/local/bin
DAEMON=$DIR/iSpindle.py
DAEMON_NAME=ispindle-srv

Isn't that strange, that it indicates python2 or is it just a left-over of the previous version?
Once again, do the environment variables match (see above DIR).

Regards

[McMelloW]

Hello @McMellow,

I have a question.

Is the software iSpindle retrieved from:

https://github.com/avollkopf/iSpindel-T ... rv.service

Isn't that strange, that it indicates python2 or is it just a left-over of the previous version?
Once again, do the environment variables match (see above DIR).

Regards

You did a lot of homework, thanks.
Yes, it from the github link you mentioned. This is a fork from another and in development. The iSpindle.py is changed to python3
Therefore ispindle-srv.service has to be adjusted to python3
This the current /etc/init.d/ispindle-srv.service

Code: Select all

# This is an example systemd configuration file for using in an systemd environment
# its was written for the archlinux-arm os
# modify User and ExecStart for your needs

[Unit]
Description=iSpindle-genericTCP server and relay
After=network.target

[Service]
Type=simple
User=pi
ExecStart=/usr/bin/python3 /usr/local/bin/iSpindle.py
Restart=always
TimeoutStartSec=10
RestartSec=10

[Install]
WantedBy=multi-user.target

I hope it make things clear

[FireWizard]

Hello @McMelloW,

I don't see anything wrong, except that you make a change in the "ispindle-srv.service" file where you changed:

After=multi-user.target

into

After=network.target

Does/Did it really need that the network is up. If not, reverse the change.

In my case I have all the .service files, I use to start, installed in /etc/systemd/system AND they have all set the eXecutable bit.
Can you check/try that.

1. Copy your ispindle-srv.service to /etc/systemd/system
2 sudo chmod +x etc/systemd/system/ispindle-srv.service
3 sudo systemctl start ispindle-srv.service

And for reading: https://www.digitalocean.com/community/ ... -and-units and
https://www.digitalocean.com/community/ ... unit-files.

Regards

[McMelloW]

Hello FireWizard.

Thank you so much. This is exactly what I had to change. It works OK now. Well done.
I will look at the links as well and do some study.

Hello @McMelloW,

I don't see anything wrong, except that you make a change in the "ispindle-srv.service" file where you changed:

After=multi-user.target

into

After=network.target

Does/Did it really need that the network is up. If not, reverse the change.

In my case I have all the . service files, I use to start, installed in /etc/systemd/system AND they have all set the eXecutable bit.
Can you check/try that.

1. Copy your ispindle-srv.service to /etc/systemd/system
2 sudo chmod +x etc/systemd/system/ispindle-srv.service
3 sudo systemctl start ispindle-srv.service

And for reading: https://www.digitalocean.com/community/ ... -and-units and
https://www.digitalocean.com/community/ ... unit-files.

Regards

[FireWizard]

@McMelloW,

Take an extra beer first

Regards

[McMelloW]

@McMelloW,

Take an extra beer first

Regards

Sure, I will