klemens-u / nextcloud-inotify

When a file is created/changed/deleted in the filesystem (e.g. over Samba) run Nextcloud file scanning for the parent directory efficently. Otherwise the updates would not be recognized by Nextcloud
1 stars 0 forks source link

[question] pidfile /tmp/watcher.pid already exists. Daemon already running? #1

Closed janusn closed 8 months ago

janusn commented 8 months ago

I have installed nextcloud in a docker container. I converted the setup a bit. However, the following message keep coming up in the log of the container:

$ docker logs -f nextcloud
[custom-init] Service files found in /custom-services.d
[custom-init] start_watcher: service detected, copying...
[custom-init] start_watcher: copied
[mod-init] Running Docker Modification Logic
[mod-init] Adding linuxserver/mods:universal-cron to container
[mod-init] Downloading linuxserver/mods:universal-cron from lscr.io
[mod-init] Installing linuxserver/mods:universal-cron
[mod-init] linuxserver/mods:universal-cron applied to container
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1016
User GID:    1016
───────────────────────────────────────

using keys found in /config/keys
chmod: changing permissions of '/etc/logrotate.d/watcher': Read-only file system
Initializing nextcloud 28.0.1.1 (this can take a while) ...
Setting permissions
Initializing finished
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│  old date  │  new date  │ path                                                                   │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2022-08-16 │ 2023-04-13 │ /config/nginx/nginx.conf                                               │
│ 2022-08-20 │ 2023-08-13 │ /config/nginx/ssl.conf                                                 │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] Files found, executing
[custom-init] install-nextcloud-inotify: executing...
fetch http://dl-cdn.alpinelinux.org/alpine/v3.18/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.18/community/x86_64/APKINDEX.tar.gz
v3.18.6-7-g0094b6ccd2e [http://dl-cdn.alpinelinux.org/alpine/v3.18/main]
v3.18.6-6-gc08ed1eac8b [http://dl-cdn.alpinelinux.org/alpine/v3.18/community]
OK: 20076 distinct packages available
(1/7) Installing mpdecimal (2.5.1-r2)
(2/7) Installing python3 (3.11.6-r0)
(3/7) Installing python3-pycache-pyc0 (3.11.6-r0)
(4/7) Installing pyc (0.1-r0)
(5/7) Installing py3-inotify-pyc (0.9.6-r12)
(6/7) Installing python3-pyc (3.11.6-r0)
(7/7) Installing py3-inotify (0.9.6-r12)
Executing busybox-1.36.1-r5.trigger
OK: 347 MiB in 265 packages
Connecting to raw.githubusercontent.com (185.199.111.133:443)
saving to '/usr/local/bin/watcher.py'
watcher.py           100% |********************************| 13805  0:00:00 ETA
'/usr/local/bin/watcher.py' saved
Connecting to raw.githubusercontent.com (185.199.111.133:443)
saving to '/usr/local/bin/watcher_nextcloud.sh'
watcher_nextcloud.sh 100% |********************************|  1336  0:00:00 ETA
'/usr/local/bin/watcher_nextcloud.sh' saved
[custom-init] install-nextcloud-inotify: exited 0
[ls.io-init] done.
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?
pidfile /tmp/watcher.pid already exists. Daemon already running?

environment: host: Ubuntu Linux 23.10 docker image: https://docs.linuxserver.io/images/docker-nextcloud/

janusn commented 8 months ago

It seems to be my fault. I have fixed it by rewriting the init script.