Nextcloud-snap: snap.nextcloud.redis-server.service not active

Created on 15 Mar 2018  ·  10Comments  ·  Source: nextcloud/nextcloud-snap

Hi @all,

no idea what's happening. Server is runnung for a while with version 12.05 and now i have tried to bring up and upgradet to 13. I have tried something to bring back online.

grafik

why is nextcloud.redis-server not running?

grafik

redis server is inactive, how to enable this services?

Any idea what can i do ?

thx

picture unicorn667

Most helpful comment

Alright, forget that, then. Redis is mostly in-memory anyway, you don't really need flushed backup. Try simply moving it out of the way:

$ sudo mv /var/snap/nextcloud/current/redis/dump.rdb /var/snap/nextcloud/current/redis/dump.rdb.backup

Then try to fire Redis back up, which should work as it's no longer trying to recover a busted backup:

$ sudo systemctl start snap.nextcloud.redis-server.service
picture kyrofa on 19 Mar 2018
❤3 👍1

All 10 comments

Please paste in the output from this script, let's take a look.

kyrofa picture kyrofa on 15 Mar 2018

i have attached the logfile, is see mysql is also not running :-(


Apache

Status

● snap.nextcloud.apache.service - Service for snap application nextcloud.apache
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.apache.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:12 CET; 20min ago
 Main PID: 2463 (run-httpd)
    Tasks: 3
   Memory: 1.4M
      CPU: 2.507s
   CGroup: /system.slice/snap.nextcloud.apache.service
           ├─ 2463 /bin/sh /snap/nextcloud/5119/bin/run-httpd -k start -DFOREGROUND
           ├─ 2605 /bin/sh /snap/nextcloud/5119/bin/setup_nextcloud
           └─23943 sleep 1

Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.apache.
Mar 15 16:21:13 share nextcloud.apache[2463]: Making sure nextcloud is setup...
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.apache.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.apache.
Mar 15 16:21:13 share nextcloud.apache[2463]: Making sure nextcloud is setup...
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.apache.



PHP

Status

● snap.nextcloud.php-fpm.service - Service for snap application nextcloud.php-fpm
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.php-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:12 CET; 20min ago
 Main PID: 2482 (start-php-fpm)
    Tasks: 2
   Memory: 1.3M
      CPU: 2.568s
   CGroup: /system.slice/snap.nextcloud.php-fpm.service
           ├─ 2482 /bin/sh /snap/nextcloud/5119/bin/start-php-fpm
           └─23942 sleep 1

Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.php-fpm.
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.php-fpm.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.php-fpm.
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.php-fpm.



MySQL

Status

● snap.nextcloud.mysql.service - Service for snap application nextcloud.mysql
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.mysql.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:12 CET; 20min ago
 Main PID: 2467 (start_mysql)
    Tasks: 2
   Memory: 53.5M
      CPU: 4.880s
   CGroup: /system.slice/snap.nextcloud.mysql.service
           ├─ 2467 /bin/sh /snap/nextcloud/5119/bin/start_mysql
           └─23944 sleep 1

Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.mysql.
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.865751Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.866058Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.969539Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:16.434507Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:16.434615Z 0 [ERROR] Aborting
Mar 15 16:21:17 share nextcloud.mysql[2467]: Starting MySQL
Mar 15 16:21:21 share nextcloud.mysql[2467]: .... * The server quit without updating PID file (/tmp/pids/mysql.pid).
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.mysql.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.mysql.
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.865751Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.866058Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:15.969539Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:16.434507Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
Mar 15 16:21:16 share nextcloud.mysql[2467]: 2018-03-15T15:21:16.434615Z 0 [ERROR] Aborting
Mar 15 16:21:17 share nextcloud.mysql[2467]: Starting MySQL
Mar 15 16:21:21 share nextcloud.mysql[2467]: .... * The server quit without updating PID file (/tmp/pids/mysql.pid).
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.mysql.



Redis

Status

● snap.nextcloud.redis-server.service - Service for snap application nextcloud.redis-server
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.redis-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Thu 2018-03-15 16:28:23 CET; 12min ago
  Process: 10683 ExecStart=/usr/bin/snap run nextcloud.redis-server (code=exited, status=1/FAILURE)
 Main PID: 10683 (code=exited, status=1/FAILURE)

Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:23 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Mar 15 16:28:23 share systemd[1]: Failed to start Service for snap application nextcloud.redis-server.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:16 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:21:16 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:21:16 share systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Mar 15 16:21:16 share systemd[1]: Failed to start Service for snap application nextcloud.redis-server.
Mar 15 16:24:56 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:24:56 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:24:56 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:24:56 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:24:57 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:24:57 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:24:57 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:24:57 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:24:57 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:24:58 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:24:58 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:24:58 share systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Mar 15 16:24:58 share systemd[1]: Failed to start Service for snap application nextcloud.redis-server.
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:25:11 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:25:11 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:25:11 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:25:11 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:25:12 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:25:12 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:25:12 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:25:12 share systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Mar 15 16:25:12 share systemd[1]: Failed to start Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:22 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:22 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:22 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:23 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:23 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: Started Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Mar 15 16:28:23 share systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Mar 15 16:28:23 share systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Mar 15 16:28:23 share systemd[1]: Failed to start Service for snap application nextcloud.redis-server.



mDNS Publisher

Status

● snap.nextcloud.mdns-publisher.service - Service for snap application nextcloud.mdns-publisher
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.mdns-publisher.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:12 CET; 20min ago
 Main PID: 2465 (delay-on-failur)
    Tasks: 6
   Memory: 7.5M
      CPU: 448ms
   CGroup: /system.slice/snap.nextcloud.mdns-publisher.service
           ├─2465 /bin/sh /snap/nextcloud/5119/bin/delay-on-failure mdns-publisher nextcloud
           └─2570 mdns-publisher nextcloud

Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Mar 15 16:21:14 share nextcloud.mdns-publisher[2465]: 2018/03/15 16:21:14 Publishing share.local -> [193.196.153.180 fe80::f8fe:9bff:fea6:bf3b] with 60-second TTL
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.mdns-publisher.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Mar 15 16:21:14 share nextcloud.mdns-publisher[2465]: 2018/03/15 16:21:14 Publishing share.local -> [193.196.153.180 fe80::f8fe:9bff:fea6:bf3b] with 60-second TTL
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.mdns-publisher.



Certificate Renewer

Status

● snap.nextcloud.renew-certs.service - Service for snap application nextcloud.renew-certs
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.renew-certs.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:11 CET; 20min ago
 Main PID: 2455 (renew-certs)
    Tasks: 2
   Memory: 32.0M
      CPU: 5.827s
   CGroup: /system.slice/snap.nextcloud.renew-certs.service
           ├─2455 /bin/sh /snap/nextcloud/5119/bin/renew-certs
           └─3173 sleep 1d

Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    http://exmaple.com/.well-known/acme-challenge/56DWwgOJ8tUWoho7ZxWqwbJn9xhYRQo-Aqyv0y0O5aU:
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    Connection refused
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    To fix these errors, please make sure that your domain name was
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    entered correctly and the DNS A record(s) for that domain
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    contain(s) the right IP address. Additionally, please check that
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    your computer has a publicly routable IP address and that no
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    firewalls are preventing the server from communicating with the
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    client. If you're using the webroot plugin, you should also verify
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    that you are serving files from the webroot path you provided.
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.renew-certs.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:11 share systemd[1]: Started Service for snap application nextcloud.renew-certs.
Mar 15 16:21:22 share nextcloud.renew-certs[2455]: Saving debug log to /var/snap/nextcloud/current/certs/certbot/logs/letsencrypt.log
Mar 15 16:21:22 share nextcloud.renew-certs[2455]: Cert is due for renewal, auto-renewing...
Mar 15 16:21:23 share nextcloud.renew-certs[2455]: Renewing an existing certificate
Mar 15 16:21:23 share nextcloud.renew-certs[2455]: Performing the following challenges:
Mar 15 16:21:23 share nextcloud.renew-certs[2455]: http-01 challenge for example
Mar 15 16:21:23 share nextcloud.renew-certs[2455]: Using the webroot path /var/snap/nextcloud/current/certs/certbot for all domains.
Mar 15 16:21:23 share nextcloud.renew-certs[2455]: Waiting for verification...
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: Cleaning up challenges
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: Attempting to renew cert from /var/snap/nextcloud/current/certs/certbot/config/renewal/example.conf produced an unexpected error: Failed authorization procedure. example (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://example/.well-known/acme-challenge/56DWwgOJ8tUWoho7ZxWqwbJn9xhYRQo-Aqyv0y0O5aU: Connection refused. Skipping.
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: Running post-hook command: restart-apache
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: -------------------------------------------------------------------------------
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: Processing
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: /var/snap/nextcloud/current/certs/certbot/config/renewal/example.conf
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: -------------------------------------------------------------------------------
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: All renewal attempts failed. The following certs could not be renewed:
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:   /var/snap/nextcloud/current/certs/certbot/config/live/example/fullchain.pem (failure)
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: 1 renew failure(s), 0 parse failure(s)
Mar 15 16:21:27 share nextcloud.renew-certs[2455]: IMPORTANT NOTES:
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:  - The following errors were reported by the server:
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    Domain: example
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    Type:   connection
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    Detail: Fetching
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    http://example/.well-known/acme-challenge/56DWwgOJ8tUWoho7ZxWqwbJn9xhYRQo-Aqyv0y0O5aU:
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    Connection refused
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    To fix these errors, please make sure that your domain name was
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    entered correctly and the DNS A record(s) for that domain
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    contain(s) the right IP address. Additionally, please check that
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    your computer has a publicly routable IP address and that no
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    firewalls are preventing the server from communicating with the
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    client. If you're using the webroot plugin, you should also verify
Mar 15 16:21:27 share nextcloud.renew-certs[2455]:    that you are serving files from the webroot path you provided.
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.renew-certs.



Nextcloud Cron

Status

● snap.nextcloud.nextcloud-cron.service - Service for snap application nextcloud.nextcloud-cron
   Loaded: loaded (/etc/systemd/system/snap.nextcloud.nextcloud-cron.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2018-03-15 16:21:12 CET; 20min ago
 Main PID: 2472 (nextcloud-cron)
    Tasks: 2
   Memory: 32.8M
      CPU: 2.882s
   CGroup: /system.slice/snap.nextcloud.nextcloud-cron.service
           ├─ 2472 /bin/sh /snap/nextcloud/5119/bin/nextcloud-cron
           └─18832 sleep 15m

Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Mar 15 16:21:13 share nextcloud.nextcloud-cron[2472]: Waiting for Nextcloud config dir... done
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.

Journal

-- Logs begin at Thu 2018-03-15 16:19:47 CET, end at Thu 2018-03-15 16:41:02 CET. --
Mar 15 16:21:12 share systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Mar 15 16:21:13 share nextcloud.nextcloud-cron[2472]: Waiting for Nextcloud config dir... done
Mar 15 16:25:10 share systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.


unicorn667 picture unicorn667 on 15 Mar 2018
😕1

Don't worry, MySQL looks fine. However, the Redis journal is useless. Let's try the real Redis log: please attach /var/snap/nextcloud/current/redis/redis.log, should be something more helpful in there.

kyrofa picture kyrofa on 15 Mar 2018

Hi,

i have attached the redis log. i fixed following

You requested maxclients of 10000 requiring at least 10032 max file descriptors.
https://www.cyberciti.biz/faq/linux-increase-the-maximum-number-of-open-files/

and max client error
The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
https://easyengine.io/tutorials/redis/#maxclients

redis.log

https://underyx.me/2015/05/18/raising-the-maximum-number-of-file-descriptors

open file limit raised from 1024 to 64000

https://underyx.me/2015/05/18/raising-the-maximum-number-of-file-descriptors

thanks for reading

unicorn667 picture unicorn667 on 16 Mar 2018

It seems your redis database dump has been corrupted in some way, either by a bad disk or by a hard shutdown that didn't recover correctly. This is a good read, from which I get this suggestion:

First, step Redis completely:

$ sudo systemctl stop snap.nextcloud.redis-server.service

Now you're going to shell into the Nextcloud snap itself:

$ sudo snap run --shell nextcloud.occ

Run these commands (I'm assuming you're on amd64, if not please adjust accordingly):

$ export PATH="$SNAP/usr/sbin:$SNAP/usr/bin:$SNAP/sbin:$SNAP/bin:$PATH"
$ export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$SNAP/lib:$SNAP/usr/lib:$SNAP/lib/x86_64-linux-gnu:$SNAP/usr/lib/x86_64-linux-gnu"
$ export LD_LIBRARY_PATH="$SNAP/lib/x86_64-linux-gnu:$SNAP/usr/lib:$SNAP/usr/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH"
$ export LD_LIBRARY_PATH=$SNAP_LIBRARY_PATH:$LD_LIBRARY_PATH

Go to where the database is stored on disk:

$ cd $SNAP_DATA/redis
$ ls
dump.rdb  redis.log

That dump.rdb is the problem file. Redis includes a DB repair tool, so let's make a backup of our corrupted database and try to fix it:

$ cp dump.rdb dump.rdb.backup
$ redis-check-aof --fix dump.rdb

If that returns successfully, you should be able to remove the backup, exit the shell, and fire Redis back up:

$ sudo systemctl start snap.nextcloud.redis-server.service
kyrofa picture kyrofa on 16 Mar 2018

Hi,

i get now following error in my redis log file.
Any idea?

22026:M 19 Mar 08:41:56.960 # Short read or OOM loading DB. Unrecoverable error, aborting now.
22026:M 19 Mar 08:41:56.960 # Internal error in RDB reading function at rdb.c:1642 -> Unexpected EOF reading RDB file
22051:C 19 Mar 08:41:57.218 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
22051:C 19 Mar 08:41:57.218 # Redis version=4.0.2, bits=64, commit=1d03693c, modified=0, pid=22051, just started
22051:C 19 Mar 08:41:57.218 # Configuration loaded
22051:M 19 Mar 08:41:57.221 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
22051:M 19 Mar 08:41:57.221 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
22051:M 19 Mar 08:41:57.221 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
22051:M 19 Mar 08:41:57.223 * Running mode=standalone, port=0.
22051:M 19 Mar 08:41:57.223 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
22051:M 19 Mar 08:41:57.223 # Server initialized
22051:M 19 Mar 08:41:57.224 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
22051:M 19 Mar 08:41:57.224 # Short read or OOM loading DB. Unrecoverable error, aborting now.
unicorn667 picture unicorn667 on 19 Mar 2018

Alright, forget that, then. Redis is mostly in-memory anyway, you don't really need flushed backup. Try simply moving it out of the way:

$ sudo mv /var/snap/nextcloud/current/redis/dump.rdb /var/snap/nextcloud/current/redis/dump.rdb.backup

Then try to fire Redis back up, which should work as it's no longer trying to recover a busted backup:

$ sudo systemctl start snap.nextcloud.redis-server.service
kyrofa picture kyrofa on 19 Mar 2018
❤3 👍1

thx for your excellent support in this issue, nextcloud is running

unicorn667 picture unicorn667 on 19 Mar 2018
👍1

@kyrofa , thank you for the solution. I had exactly same issue. Your solution has resolved it :+1:

SkyWheel picture SkyWheel on 4 Nov 2020

@SkyWheel moving the rdb, you mean?

kyrofa picture kyrofa on 4 Nov 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

edrohler picture edrohler  ·  3Comments
RadZaeem picture RadZaeem  ·  8Comments
WereCatf picture WereCatf  ·  3Comments
mo-seph picture mo-seph  ·  6Comments
JWise1203 picture JWise1203  ·  5Comments