Opening a new thread here as my previous posts have been tagged onto existing (and solved) threads (some in wrong section).
Environ: RasPi 3 B+ With NCP docker-compose install (stable for some months)
NC Config
| datadirectory | /data/nextcloud/data |
|---|---|
| dbtype | mysql |
| version | 15.0.8.1 |
| overwrite.cli.url | https://*redacted/ |
| dbname | nextcloud |
| dbhost | localhost |
| dbport | |
| dbtableprefix | oc_ |
| mysql.utf8mb4 | 1 |
| dbuser | ncadmin |
| dbpassword | ****redacted |
| installed | 1 |
| instanceid | ocypc7j5jmvr |
| memcache.local | \OC\Memcache\Redis |
| memcache.locking | \OC\Memcache\Redis |
| redis | |
| host | /var/run/redis/redis.sock |
| port | 0 |
| timeout | 0 |
| password | ****redacted |
NCP Info
| NextCloudPi version | v1.12.7 |
|---|---|
| NextCloudPi image | NextCloudPi_docker_11-30-18 |
| distribution | Debian GNU/Linux 9 \n \l |
| automount | no |
| USB devices | none |
| datadir | /data/nextcloud/data |
| data in SD | yes |
| data filesystem | ext2/ext3 |
| data disk usage | 15G/59G |
| rootfs usage | 15G/59G |
| swapfile | /var/swap |
| dbdir | /data/database |
| Nextcloud check | ok |
| Nextcloud version | 15.0.8.1 |
| HTTPD service | up |
| PHP service | up |
| MariaDB service | up |
| Redis service | up |
| Postfix service | up |
| internet check | ok |
| port check 80 | closed |
| port check 443 | closed |
| IP | 172.18.0.2 |
| gateway | 172.18.0.1 |
| interface | eth0 |
| certificates | redacted |
| NAT loopback | no |
| uptime | 21min |
Issue: After some erroneous database changes (yeah OK I know…!) (see this post for bg) I keepo finding that NC cannot start due to database access permission problem for the ncadmin user
SQLSTATE[HY000] [1045] Access denied for user 'ncadmin'@'localhost' (using password: YES)
, sure enough checking the configs I see that the NCP side the ncadmin password has changed after restart/reboot.
Manually changing this in the NC config (/data/nextcloud/config/config.php) resolves the issue (as does manually changing the pass in the database, but I keep getting back to the issue of ncadmin password mismatch.
Checking the NCP-provisioning script I can more or less see what is happening and to where, but it’s not clear to me whether this script is run regularly or just at initial first start up after install.
What ideally needs to be done is to reset the ncadmin user permissions back to default but IDK how this is best done tbh. Had a go with ncp-config from the cli but don’t recall seeing any password reset options for the DB user ncadmin…
Currently NC is running but cannot upgrade NCP to 1.13.0 from 1.12.7 log output here:
ncp-log
# ncp-update
Downloading updates
Performing updates
Cannot load Zend OPcache - it was already loaded
Config value squareSizes for app previewgenerator set to 32
Cannot load Zend OPcache - it was already loaded
Config value widthSizes for app previewgenerator set to 128 256 512
Cannot load Zend OPcache - it was already loaded
Config value heightSizes for app previewgenerator set to 128 256
Cannot load Zend OPcache - it was already loaded
System config value jpeg_quality set to string 60
Running unattended-upgrades
Unattended upgrades active: yes (autoreboot true)
--2019-06-03 09:41:18-- https://packages.sury.org/php/apt.gpg
Resolving packages.sury.org (packages.sury.org)... 104.31.94.169, 104.31.95.169, 2606:4700:30::681f:5ea9, ...
Connecting to packages.sury.org (packages.sury.org)|104.31.94.169|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1769 (1.7K) [application/octet-stream]
Saving to: '/etc/apt/trusted.gpg.d/php.gpg'
/etc/apt/trusted.gpg.d/php.gp 100%[=================================================>] 1.73K --.-KB/s in 0s
2019-06-03 09:41:19 (6.04 MB/s) - '/etc/apt/trusted.gpg.d/php.gpg' saved [1769/1769]
Running nc-notify-updates
Restarting periodic command scheduler: cronStopping periodic command scheduler: cron.
Starting periodic command scheduler: cron.
update web notifications enabled
Installing nc-backup
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Hit:5 https://packages.sury.org/php stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
pigz is already the newest version (2.3.4-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installing nc-restore
Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://deb.debian.org/debian stretch InRelease
Hit:3 http://deb.debian.org/debian stretch-updates InRelease
Hit:4 http://deb.debian.org/debian stretch Release
Hit:5 https://packages.sury.org/php stretch InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
file is already the newest version (1:5.30-1+deb9u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
./update.sh: line 235: /etc/fail2ban/filter.d/ufwban.conf: No such file or directory
The Zend opcache errors appeared related to this https://github.com/nextcloud/nextcloudpi/issues/416
but deleting the offending line in /etc/php/7.2/… does not resolve the matter…
Also some concerning DB log error messages after each restart:
mysql.log
2019-06-03 9:21:42 1995397936 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer…
2019-06-03 9:21:43 1995397936 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-03 9:21:43 1995397936 [Note] InnoDB: Waiting for purge to start
2019-06-03 9:21:43 1995397936 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 845850815
2019-06-03 9:21:43 1111487296 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-06-03 9:21:43 1995397936 [Note] Plugin ‘FEEDBACK’ is disabled.
2019-06-03 9:21:43 1995397936 [Note] Recovering after a crash using tc.log
2019-06-03 9:21:43 1995397936 [Note] Starting crash recovery…
2019-06-03 9:21:43 1995397936 [Note] Crash recovery finished.
2019-06-03 9:21:43 1995397936 [Note] Server socket created on IP: ‘127.0.0.1’.
2019-06-03 9:21:43 1995397936 [ERROR] mysqld: Table ‘./mysql/user’ is marked as crashed and should be repaired
2019-06-03 9:21:43 1995397936 [Warning] Checking table: ‘./mysql/user’
2019-06-03 9:21:43 1995397936 [ERROR] mysql.user: 1 client is using or hasn’t closed the table properly
2019-06-03 9:21:43 1995397936 [ERROR] mysqld: Table ‘./mysql/db’ is marked as crashed and should be repaired
2019-06-03 9:21:43 1995397936 [Warning] Checking table: ‘./mysql/db’
2019-06-03 9:21:43 1995397936 [ERROR] mysql.db: 1 client is using or hasn’t closed the table properly
2019-06-03 9:21:43 1995397936 [Note] mysqld: ready for connections.
Version: ‘10.1.38-MariaDB-0+deb9u1’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 Debian 9.8
Any ideas?
):