Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

notify_push could not be started via systemd at boot time #358

Open
particeps1 opened this issue Nov 12, 2023 · 5 comments · May be fixed by #496
Open

notify_push could not be started via systemd at boot time #358

particeps1 opened this issue Nov 12, 2023 · 5 comments · May be fixed by #496

Comments

@particeps1
Copy link

particeps1 commented Nov 12, 2023 •
edited
Loading

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
@joshtrichards
Copy link
Member

Environment = PORT=7867.

Does that period at the end of your port actually exist in your startup script?

@particeps1
Copy link
Author

No, that was a space, which my editor displays as a dimmed dot.
So unfortunately a copy/paste error. I've corrected my post.
Thanks for the feedback.

@nursoda
Copy link

nursoda commented Dec 3, 2023 •
edited
Loading

Please check the execution rights on your push service binary /mypath/apps/notify_push/bin/x86_64/notify_push – that must be executable by www-data as stated in your .service file for Apache above (user http in my NGINX case).

In my case, I am sure that I once made it executable, and after some past update, the eXecute bit was missing. chmod ug+x …/apps/notify_push/bin/x86_64/notify_push and systemctl restart …/notify_push.service were sufficient to solve the issue in my case.

@particeps1 If that solves it for you, too – then the question is whether the app can set an eXecute bit when installing that binary. If it can, then this is the issue to be solved @joshtrichards .

@particeps1
Copy link
Author

Thanks for the tip. That also worked for me.
No more errors when booting, I will check the file permissions with the next update.
This issue has been resolved for me.

@smorkgl
Copy link

smorkgl commented Dec 7, 2023

hello i have the same problem with certificate

@joshtrichards joshtrichards added bug Something isn't working and removed needs info labels Feb 9, 2024
@solracsf solracsf removed the bug Something isn't working label Jul 30, 2024
@solracsf solracsf linked a pull request Jul 30, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make sure binary is executable nextcloud/notify_push
5 participants
@joshtrichards @nursoda @solracsf @particeps1 @smorkgl