Revision history [back]

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service is running in background, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service is running in background, will be shutdown, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service will be shutdown, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service will be shutdown, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service will be shutdown, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target

After switching from btsync to Syncthing I am using now the systemd approach to keep it running in background as described here in the Syncthing documentation.

The problem now is, that the service gets stopped, when the phone goes into standby. Journalctl -u syncthing delivers this messages:

Jolla systemd[1]: INFO: Paused state detected, possibly woke up from standby
Jolla systemd[1]: INFO: Restarting
Jolla systemd[1]: OK: Exiting
Jolla systemd[1]: syncthing.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jolla systemd[1]: Unit syncthing.service entered failed state.

Q: How can I avoid, that the service will be shutdown, even when the phone goes to standby?

My .service file in /etc/systemd/system/multi-user.target.wants/syncthing.service looks now like this:

 [Unit]
Description=Syncthing service
After=network.target

[Service]
User=nemo
Environment=STNORESTART=yes
ExecStart=/usr/bin/syncthing
Restart=always
#Restart=on-success
RestartSec=1min

[Install]
WantedBy=multi-user.target