nextcloud / nextcloud/notify_push
After update from 0.7 to 1.0.0 systemd service does not start anymore error is “bundled binary not working on your system"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
Corresponding to my question on help.nextcloud
-> https://help.nextcloud.com/t/update-notify-push-to-1-0-0-leads-to-bundled-binary-not-working-on-your-system/215417
i can no longer start the notify_push service on ubuntu server 24.04.1 with Nextcloud Server 30.0.5.1
System: ubuntu-server 24.04.1
PHP: 8.3.11
NGinx: 1.27.0
Reverse Proxy NGinx: 1.26.2
DataBase: PostgreSQL 17.2
I upgraded nc 30.0.4 to 30.0.5.1 and also some installed apps so as client_push (notify_push)
occ app:update --all
The upgrade was successful as far as i have tested. But a reboot of the server brought down my notify_push service and i couldn't start it anymore.
Message was: "bundled binary not working on your system"
systemctl start notify_push failed, journalctl notify_push says
My service config is as follows:
[Unit]
Description = Push daemon for Nextcloud clients
Documentation=https://github.com/nextcloud/notify_push
After=nginx.service php8.3-fpm.service postgresql.service redis.service
[Service]
Environment = PORT=7867
Environment = NEXTCLOUD_URL=https://MY.FQDN.CLOUDNAME
ExecStart = /var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php
User=www-data
Type=notify
Restart=always
RestartSec=60
[Install]
WantedBy = multi-user.target
So i tried to downgrade and made following steps:
- occ app:remove notify_push
→ notify_push 1.0.0 disabled and removed - download the tar.gz file of the 0.7 version from the nextcloud apps store
unpack the file/folder to the …/nextcloud/apps dir - check user rights, if all (also recursive) files → especially the binary file is accessible by the webuser (e,g, www-data)
- command …occ app:enable notify_push
→ should report that notify_push app version 0.7.0 is enabled - restart the service
→ systemctl restart notify_push.service
→ systemctl status notify_push.service - and see this!!
The service starts with 0.7 version / binary very well with same config that made 1.0.0 crash.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the service configuration and the bundled binary at apps/notify_push/bin/x86_64/notify_push, then compare the startup output from notify_push 1.0.0 with the working 0.7.0 binary. Reproduce the failure using systemctl start notify_push and inspect the corresponding journalctl output. Done means identifying why 1.0.0 reports “bundled binary not working on your system” on the stated Ubuntu and Nextcloud setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, rust, ubuntu
- Domain
- backend, devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100