Nextcloud-snap: Unable to troubleshoot snap issue on Ubuntu server 16.04

[mattiaR]

Hi, I am sorry if this sounds more of a request for documentation than an issue, but I am having the following problem and I am new to "snaps".
I have a nextcloud snap installed on a Ubuntu server 16.04, working like a charm till a couple of days back.
I then restarted the Ubuntu box, and after that I am haven't been able to access the web interface anymore.
I ran the following commands to try to restart the snap (I don't seem to find any documentation on how to do it):

sudo systemctl start snap.nextcloud.mysql
sudo systemctl start snap.nextcloud.apache

and the following to check the status

sudo systemctl status snap.nextcloud.apache

Output:

● 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 Wed 2018-01-24 16:11:53 CET; 12min ago
 Main PID: 21810 (run-httpd)
    Tasks: 3
   Memory: 332.0K
      CPU: 1.299s
   CGroup: /system.slice/snap.nextcloud.apache.service
           ├─21810 /bin/sh /snap/nextcloud/4371/bin/run-httpd -k start -DFOREGROUND
           ├─21825 /bin/sh /snap/nextcloud/4371/bin/setup_nextcloud
           └─23340 sleep 1

Jan 24 16:11:53 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 24 16:11:53 server-001 nextcloud.apache[21810]: Making sure nextcloud is setup...

sudo systemctl status snap.nextcloud.mysql

Output:

● 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 Wed 2018-01-24 16:10:46 CET; 24min ago
 Main PID: 21501 (start_mysql)
    Tasks: 31
   Memory: 222.8M
      CPU: 6.094s
   CGroup: /system.slice/snap.nextcloud.mysql.service
           ├─21501 /bin/sh /snap/nextcloud/4371/bin/start_mysql
           ├─21530 /bin/sh /snap/nextcloud/4371/bin/mysqld_safe --datadir=/var/snap/nextcloud/4371/mysql --pid-file=/tmp/pids/mysql.pid --lc-messa
           ├─21697 /snap/nextcloud/4371/bin/mysqld --basedir=/snap/nextcloud/4371 --datadir=/var/snap/nextcloud/4371/mysql --plugin-dir=/snap/next
           └─24732 sleep 1

Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.478828Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.482878Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.506531Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Ple
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674865Z 0 [ERROR] --initialize specified but the data directory has files in
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674932Z 0 [ERROR] Aborting
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: Starting MySQL
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: . *
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: Checking/upgrading mysql tables if necessary...
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: Checking if update is needed.
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: This installation of MySQL is already upgraded to 5.7.18, use --force if you still need to run m

(the output is cut as shown)

Both the processes seems up and running even though I see that strange "Making sure nextcloud is setup..." at the end of the apache process status.

It all seems fine.

I checked the nexcloud log in
/var/snap/nextcloud/common/nextcloud/data/nextcloud.log
It hasn't been updated in 5 days.

I cannot telnet port 443 or 80 of the box even from the box itself (connection refused), so I'd rule out a network issue.

Apache logs in /var/snap/nextcloud/current/apache also not update in 5+ days.

Is there anything else I can check?

Thanks

[kyrofa]

@mattiaR I don't care if you simply have a question, logging an issue is a perfectly fine way to request assistance :smiley: .

First of all, let's see some more complete logs. Can you please attach the output from this script?

[mattiaR]

Thanks @kyrofa, please see the output below, it actually seems a few services are failing, a recurring error seems to be "cannot change profile for the next exec call: No such file or directory"

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 Wed 2018-01-24 16:11:53 CET; 1h 14min ago
 Main PID: 21810 (run-httpd)
    Tasks: 3
   Memory: 336.0K
      CPU: 7.488s
   CGroup: /system.slice/snap.nextcloud.apache.service
           ├─21810 /bin/sh /snap/nextcloud/4371/bin/run-httpd -k start -DFOREGROUND
           ├─21825 /bin/sh /snap/nextcloud/4371/bin/setup_nextcloud
           └─31134 sleep 1

Jan 24 16:11:53 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 24 16:11:53 server-001 nextcloud.apache[21810]: Making sure nextcloud is setup...

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 22 11:04:12 server-001 nextcloud.apache[1234]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 nextcloud.apache[1432]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Control process exited, code=exited status=1
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.apache.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 22 11:04:12 server-001 nextcloud.apache[1478]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 nextcloud.apache[1513]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Control process exited, code=exited status=1
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.apache.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.apache.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 22 11:04:13 server-001 nextcloud.apache[1557]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.apache[1607]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Control process exited, code=exited status=1
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.apache.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 22 11:04:13 server-001 nextcloud.apache[1679]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.apache[1730]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Control process exited, code=exited status=1
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.apache.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.apache.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 22 11:04:14 server-001 nextcloud.apache[1796]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Control process exited, code=exited status=1
Jan 22 11:04:14 server-001 nextcloud.apache[1829]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Unit entered failed state.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Failed with result 'exit-code'.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:14 server-001 systemd[1]: Stopped Service for snap application nextcloud.apache.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.apache.service: Start request repeated too quickly.
Jan 22 11:04:14 server-001 systemd[1]: Failed to start Service for snap application nextcloud.apache.
Jan 24 16:11:53 server-001 systemd[1]: Started Service for snap application nextcloud.apache.
Jan 24 16:11:53 server-001 nextcloud.apache[21810]: Making sure nextcloud is setup...

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: inactive (dead) (Result: exit-code) since Mon 2018-01-22 11:04:13 CET; 2 days ago
 Main PID: 1711 (code=exited, status=1/FAILURE)

Jan 22 11:04:13 server-001 nextcloud.php-fpm[1711]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.php-fpm.

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.php-fpm.
Jan 22 11:04:12 server-001 nextcloud.php-fpm[1244]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.php-fpm.
Jan 22 11:04:12 server-001 nextcloud.php-fpm[1465]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 nextcloud.php-fpm[1541]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 nextcloud.php-fpm[1631]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 nextcloud.php-fpm[1711]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.php-fpm.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.php-fpm.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start 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 Wed 2018-01-24 16:10:46 CET; 1h 15min ago
 Main PID: 21501 (start_mysql)
    Tasks: 31
   Memory: 222.8M
      CPU: 13.386s
   CGroup: /system.slice/snap.nextcloud.mysql.service
           ├─21501 /bin/sh /snap/nextcloud/4371/bin/start_mysql
           ├─21530 /bin/sh /snap/nextcloud/4371/bin/mysqld_safe --datadir=/var/snap/nextcloud/4371/mysql --pid-file=/tmp/pids/mysql.pid --lc-messages-dir=/snap/nextcloud/4371/share --socket=/tmp/sockets/mysql.sock
           ├─21697 /snap/nextcloud/4371/bin/mysqld --basedir=/snap/nextcloud/4371 --datadir=/var/snap/nextcloud/4371/mysql --plugin-dir=/snap/nextcloud/4371/lib/plugin --lc-messages-dir=/snap/nextcloud/4371/share --log-error=/var/snap/nextcloud/4371/mysql/server-001.err --pid-file=/tmp/pids/mysql.pid --socket=/tmp/sockets/mysql.sock
           └─31135 sleep 1

Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.478828Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.482878Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.506531Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674865Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674932Z 0 [ERROR] Aborting
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: Starting MySQL
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: . *
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: Checking/upgrading mysql tables if necessary...
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: Checking if update is needed.
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: This installation of MySQL is already upgraded to 5.7.18, use --force if you still need to run mysql_upgrade

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 22 11:04:12 server-001 nextcloud.mysql[1189]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 nextcloud.mysql[1422]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Control process exited, code=exited status=1
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.mysql.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mysql.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 nextcloud.mysql[1522]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 nextcloud.mysql[1581]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Control process exited, code=exited status=1
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mysql.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 22 11:04:13 server-001 nextcloud.mysql[1647]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.mysql[1702]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Control process exited, code=exited status=1
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mysql.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 22 11:04:13 server-001 nextcloud.mysql[1771]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mysql.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:14 server-001 nextcloud.mysql[1791]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Control process exited, code=exited status=1
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Unit entered failed state.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:14 server-001 systemd[1]: Stopped Service for snap application nextcloud.mysql.
Jan 22 11:04:14 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 22 11:04:14 server-001 nextcloud.mysql[1865]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:14 server-001 nextcloud.mysql[1875]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Control process exited, code=exited status=1
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Unit entered failed state.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Failed with result 'exit-code'.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:14 server-001 systemd[1]: Stopped Service for snap application nextcloud.mysql.
Jan 22 11:04:14 server-001 systemd[1]: snap.nextcloud.mysql.service: Start request repeated too quickly.
Jan 22 11:04:14 server-001 systemd[1]: Failed to start Service for snap application nextcloud.mysql.
Jan 24 16:10:46 server-001 systemd[1]: Started Service for snap application nextcloud.mysql.
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.478828Z 0 [Warning] Changed limits: max_open_files: 1024 (requested 5000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.482878Z 0 [Warning] Changed limits: table_open_cache: 431 (requested 2000)
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.506531Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674865Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: 2018-01-24T15:10:48.674932Z 0 [ERROR] Aborting
Jan 24 16:10:48 server-001 nextcloud.mysql[21501]: Starting MySQL
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: . *
Jan 24 16:10:49 server-001 nextcloud.mysql[21501]: Checking/upgrading mysql tables if necessary...
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: Checking if update is needed.
Jan 24 16:10:50 server-001 nextcloud.mysql[21501]: This installation of MySQL is already upgraded to 5.7.18, use --force if you still need to run mysql_upgrade

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 Mon 2018-01-22 11:04:13 CET; 2 days ago
 Main PID: 1738 (code=exited, status=1/FAILURE)

Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.redis-server.

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.redis-server.
Jan 22 11:04:12 server-001 nextcloud.redis-server[1207]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.redis-server.
Jan 22 11:04:12 server-001 nextcloud.redis-server[1464]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 nextcloud.redis-server[1566]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 nextcloud.redis-server[1656]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 nextcloud.redis-server[1738]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.redis-server.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.redis-server.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 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: inactive (dead) (Result: exit-code) since Mon 2018-01-22 11:04:13 CET; 2 days ago
 Main PID: 1715 (code=exited, status=1/FAILURE)

Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.mdns-publisher.

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:12 server-001 nextcloud.mdns-publisher[1231]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 nextcloud.mdns-publisher[1449]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 nextcloud.mdns-publisher[1536]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.mdns-publisher[1628]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 nextcloud.mdns-publisher[1715]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.mdns-publisher.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.mdns-publisher.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start 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: inactive (dead) (Result: exit-code) since Mon 2018-01-22 11:04:13 CET; 2 days ago
 Main PID: 1732 (code=exited, status=1/FAILURE)

Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.renew-certs.

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.renew-certs.
Jan 22 11:04:12 server-001 nextcloud.renew-certs[1228]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.renew-certs.
Jan 22 11:04:12 server-001 nextcloud.renew-certs[1457]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.renew-certs[1552]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.renew-certs[1655]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 nextcloud.renew-certs[1732]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.renew-certs.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.renew-certs.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start 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: inactive (dead) (Result: exit-code) since Mon 2018-01-22 11:04:13 CET; 2 days ago
 Main PID: 1712 (code=exited, status=1/FAILURE)

Jan 22 11:04:13 server-001 nextcloud.nextcloud-cron[1712]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.nextcloud-cron.

Journal

-- Logs begin at Mon 2018-01-22 11:04:07 CET, end at Wed 2018-01-24 17:26:27 CET. --
Jan 22 11:04:11 server-001 systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:12 server-001 nextcloud.nextcloud-cron[1240]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:12 server-001 nextcloud.nextcloud-cron[1459]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:12 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:12 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:12 server-001 systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 nextcloud.nextcloud-cron[1534]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 nextcloud.nextcloud-cron[1627]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 systemd[1]: Started Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 nextcloud.nextcloud-cron[1712]: cannot change profile for the next exec call: No such file or directory
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Unit entered failed state.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Failed with result 'exit-code'.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Service hold-off time over, scheduling restart.
Jan 22 11:04:13 server-001 systemd[1]: Stopped Service for snap application nextcloud.nextcloud-cron.
Jan 22 11:04:13 server-001 systemd[1]: snap.nextcloud.nextcloud-cron.service: Start request repeated too quickly.
Jan 22 11:04:13 server-001 systemd[1]: Failed to start Service for snap application nextcloud.nextcloud-cron.

[kyrofa]

Okay this is weird. Even Apache seems to have that error, but then it came up successfully. I'm not sure what's happening here, but it looks like snapd's confinement is barfing on something (talk of "profiles" are messages coming from snap-confine, I believe). Try this.

First of all, run sudo snap refresh to make sure all your snaps are up-to-date. Then disable/re-enable the snap:

$ sudo snap disable nextcloud
$ sudo snap enable nextcloud

The idea there is to just make the snap restart. A reboot would do the same thing. What's the status after doing this?

[kyrofa]

Another quick question: can you give me details on this server? Are you hosting it yourself, using the real Ubuntu 16.04 server image? Or is it a cloud server somewhere? If so, which provider?

[mattiaR]

Hi Kyle, well it looks like disabling and re-enabling the snap worked, I am able to access the web interface and use the app now! The server is hosted by aruba.it.
Thank you very much, let me know if there is any other info I can provide you with if you want to understand what went wrong. Btw, is there any document in which all these commands are listed?
Thanks

[mattiaR]

Just an additional piece of info for posterity, I have to disable and enable the snapshot every time I reboot the box (not just enable, since it says it is already enabled).

[kyrofa]

Btw, is there any document in which all these commands are listed?

Yes indeed, right here.

Something isn't right here, let me ask the snapd devs.

[zyga]

Hello, snapd developer here.

Is the host (by any chance) a container? What is the output of systemd-detect-virt?
EDIT: Also, please share the output of snap version.

[kyrofa]

Can we also see the output of snap list and snap version, please?

[mattiaR]

Thanks for the link, here you go:

tia@server-001:~$ systemd-detect-virt
vmware
tia@server-001:~$ snap list
Name Version Rev Developer Notes
core 16-2.30 3887 canonical core
nextcloud 12.0.4snap1 4371 nextcloud -
tia@server-001:~$ snap version
snap 2.30
snapd 2.30
series 16
ubuntu 16.04
kernel 4.4.0-112-generic

[zyga]

So this looks very interesting. I will investigate it this and next week but it's not a priority task for me. I will try to reproduce the bug tomorrow inside vmware workstation. If you could share some details about how to do that (referring me to external sites, etc) I will have an easier time.

[mattiaR]

@zyga not sure if this was for me but I am just paying the hosting service (aruba.it) and I have root access to the unix box, I didn't set up the vmware environment nor I have visibility underneath the OS.

[weeTC]

Hey, this sounds very similar. Unfortunately, my system did not start working after disabling and re-enabling. I posted the issue on the nextcloud community support pages (https://help.nextcloud.com/t/snap-server-stops-working-after-system-reboot-cant-see-page/26586), but haven't made any more progress.

EDIT:
For reference, I am using a 16.0.4 instance on an openstack system.

[weeTC]

Just a follow-up - I was actually able to reproduce this problem on a fresh install and (potentially) solve it.

What I did

• After removing and purging nextcloud and snapd from my system, I did the usual check for updates and then reinstalled.
• On completion, the web interface could still not be reached.
• Running sudo netstat -plten however, I noticed that a process (nginx) was running on port 80.
• After Killing this, I restarted nextcloud using sudo snap restart nextcloud.
• The admin page was then available to me.
• Restarting the system however, the page was again unavailable.
• Following similar logic, killing the process running on the port again leads to nextcloud restarting (without help this time).

Conclusion
The key seems to be that after a restart, nginx (and presumably other programs) can steal the port connection before the nextcloud snap. I'm not sure if this is just a particular problem on my system, but I thought I'd post my thinking here just in case.

[kolmberger]

@weeTC: thanks a lot for your investigations, right now, I think my issue is similar if not has same root cause https://github.com/nextcloud/nextcloud-snap/issues/434
I was thinking it has to do with fail2ban in my case, but after reading your topic, my suspection goes more into package update, which I had not considered yet due to fiddling with fail2ban.
I also fiddled around with stopping and restarting services and had exactly same behaviour, that interface was reachable, but after reboot again not. My troubleshooting capabilities are quite poor, so it was not obvious though.
So ist it possible, that package updates do changes with resulting in stealed ports?

[mbreskovec]

Guys, I am tried install Collabora Office via Docker, which probably killed NextCloud, or it was one from reasons why my NextCloud crashed. I am removed Apache and Docker completely, reinstalled NextCloud, and now I can see that Apache and MySQL services are active again in Snap, but if I will check listening ports via Netstat, I don't see nothing listening on ports 80 and 443, and I can't connect to NextCloud of course. Any idea, how to solve it?

[kyrofa]

@corwin78 please log a new issue, and make sure you paste in the output from this script so we can debug. Thanks!

[mbreskovec]

@kyrofa new Issue #437 has been created. Thx.

[kyrofa]

There has been no activity here, but it's pretty clear this issue isn't related specifically to the Nextcloud snap. If it's still an issue and you'd like to continue poking the snapd devs, please log a bug against snapd.