nextcloud / nextcloud/notify_push

notify_push could not be started via systemd at boot time

Open
#358 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
344
Forks
64
Avg merge
2d 10h
Merged PRs (30d)
5

Description

Hello,

Sadly, I did not succeed in starting notify_push automatically at boot time

systemd log:

Nov 12 19:57:49 obfuscated systemd[1]: Started notify_push.service - Push daemon for Nextcloud clients.
Nov 12 19:57:49 obfuscated systemd[1]: Stopping notify_push.service - Push daemon for Nextcloud clients...
Nov 12 19:57:49 obfuscated systemd[1]: notify_push.service: Deactivated successfully.
                                      *** the previous 3 protocol lines are repeated 5 times ***
Nov 12 19:57:49 obfuscated systemd[1]: notify_push.service: Start request repeated too quickly.
Nov 12 19:57:49 obfuscated systemd[1]: notify_push.service: Failed with result 'start-limit-hit'.
Nov 12 19:57:49 obfuscated systemd[1]: Failed to start notify_push.service - Push daemon for Nextcloud clients.

Setting debug for logging does not provide any further information either.
The content of my notify_push.service:

[Unit]
Description = Push daemon for Nextcloud clients
Documentation = https://github.com/nextcloud/notify_push
Wants = network-online.target apache2.service redis-server.service
After=network-online.target redis-server.service mariadb.service apache2.service php8.2-fpm.service

[Service]
Environment = PORT=7867
ExecStart = /mypath/apps/notify_push/bin/x86_64/notify_push /mypath/config/config.php
User=www-data

[Install]
WantedBy = multi-user.target

ubuntu 23.10

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the boot-time failure with the shown notify_push.service on Ubuntu 23.10, then inspect its systemd journal and the configured ExecStart command. Determine why the service exits and hits start-limit-hit; done means notify_push remains running after boot without repeated start failures.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, ubuntu
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.