Notify Push Service does not start automatically

[hokaido]

Hi,

I have installed NC 23.0.0 on Ubuntu 20.0.4 LTS.
Was running fine as NC 21, Nc 22 etc.
By random I noticed that the Notify Push Service is not started automatically after a reboot.

Thats the error:

Jan 08 16:35:58 domain.com notify_push[701]:    0: Failed to connect to Nextcloud database
Jan 08 16:35:58 domain.com notify_push[701]:    1: error returned from database: 1130: Host '127.0.0.1' is not allowed to connect to this MariaDB server
Jan 08 16:35:58 domain.com notify_push[701]:    2: 1130: Host '127.0.0.1' is not allowed to connect to this MariaDB server
Jan 08 16:35:58 domain.com notify_push[701]: Location:
Jan 08 16:35:58 domain.com notify_push[701]:    /tmp/krankerl.UyibIgt7EFoA/notify_push/src/storage_mapping.rs:58
Jan 08 16:35:58 domain.com notify_push[701]: Backtrace omitted.
Jan 08 16:35:58 domain.com notify_push[701]: Run with RUST_BACKTRACE=1 environment variable to display it.
Jan 08 16:35:58 domain.com notify_push[701]: Run with RUST_BACKTRACE=full to include source snippets.
Jan 08 16:35:58 domain.com systemd[1]: notify_push.service: Main process exited, code=exited,

When I enter “service notify_push restart” it is up and running immediately.

How can this be solved?

Thanks

[MichaIng]

Probably it is not configured to start after the database. Can you show:

systemctl cat notify_push

In case of MariaDB adding After=mariadb.service to the [Unit] section may solve it.

[hokaido]

systemctl cat notify_push:

# /etc/systemd/system/notify_push.service
[Unit]
Description = Push daemon for Nextcloud clients
[Service]
Environment=PORT=7867
Environment=NEXTCLOUD_URL=https://domain.com
ExecStart=/var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php
User=www-data
[Install]
WantedBy = multi-user.target
root@xy:/home/xyz#

[crobarcro]

I have the same problem, there is also a github issue here:

[hokaido]

It worked for a long time, but now there is again an error (under NC 23.0.2)

notify_push.service - Push daemon for Nextcloud clients
     Loaded: loaded (/etc/systemd/system/notify_push.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-02-20 00:06:06 CET; 26s ago
    Process: 4625 ExecStart=/var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php (code=exited, status=203/EXEC)
   Main PID: 4625 (code=exited, status=203/EXEC)

Feb 20 00:06:06 domain.com systemd[1]: Started Push daemon for Nextcloud clients.
Feb 20 00:06:06 domain.com systemd[4625]: notify_push.service: Failed to execute command: Permission denied
Feb 20 00:06:06 domain.com systemd[4625]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push: Permission denied
Feb 20 00:06:06 domain.com systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Feb 20 00:06:06 domain.com systemd[1]: notify_push.service: Failed with result 'exit-code'.
root@domain.com:/home/user100#

Can anyone help?

[hokaido]

No one with the same problem?

[marketingnerd]

Push notifications are also not working for me.

[gopher333]

Apperently there seem to be some problems with notify_push:

1. The log from hokkaido shows that the permissions of the notify_push Binary are wrong. Change them to sudo chmod a+x notify_push
2. Even then, the tip of inserting After=mariadb.service into /etc/systemd/system/notify_push.service seems to be necessary
3. The binary seems to have problems with 64 Bit OS (here: Ubuntu 22.04 64 Bit
   Adding the packets
   sudo apt install binfmt-support qemu qemu-user-static
   show relief