nextcloud / nextcloud/notify_push

Found argument config.php which wasn't expected

Open
#134 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Using version 0.2.4 and nextcloud 22.2.0.

Debian 11 64bit with a 3900x and MySQL with redis.

[Unit]
Description = Push daemon for Nextcloud clients

[Service]
Environment=PORT=7867
Environment=NEXTCLOUD_URL=https://cloud.url.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@cloud:/var/www/nextcloud/config# systemctl status notify_push
● notify_push.service - Push daemon for Nextcloud clients
     Loaded: loaded (/etc/systemd/system/notify_push.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2021-10-16 06:05:50 PDT; 15s ago
   Main PID: 40867 (code=exited, status=1/FAILURE)
        CPU: 5ms

Oct 16 06:05:50 cloud systemd[1]: Started Push daemon for Nextcloud clients.
Oct 16 06:05:50 cloud notify_push[40867]: error: Found argument 'config.php' which wasn't expected, or isn't valid in this context
Oct 16 06:05:50 cloud notify_push[40867]: USAGE:
Oct 16 06:05:50 cloud notify_push[40867]:     notify_push [FLAGS] [OPTIONS] [--] [CONFIG_FILE]
Oct 16 06:05:50 cloud notify_push[40867]: For more information try --help
Oct 16 06:05:50 cloud systemd[1]: notify_push.service: Main process exited, code=exited, status=1/FAILURE
Oct 16 06:05:50 cloud systemd[1]: notify_push.service: Failed with result 'exit-code'.

There are no errors in the nextcloud.log.

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 shown systemd invocation and comparing it with the binary's --help output, using the provided notify_push command and config.php path. Trace how the CONFIG_FILE argument is parsed and verify the service starts successfully with the documented invocation on the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend, cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.