The solution for a manual fix is in the link that I indicated you before
Donât do this, look at the manual fix above
Thatâs weird, that image was built for NC14. Yes, please try the new one, it should come with NC14
Thanx, had some issues copying the .user.ini with wget, so i just viewed the remote file, copied the content and created a new one with vi .user.ini and pasted the content there. All working now
please, report this on github
thank you very much!
Hi there all
I took the plunge and downloaded the beta update which appeared to work well⌠However this morning I had a notification of an auto update and now I get the following:
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
What have I done?
Del
Same issue here after a clean install of the docker image on a Raspi 3 B+
First, make sure you have read and tried this
Thatâs a classic symptom of a hardware issue.
Next, please share the output of sudo ncp-report
I will make a copy of the SD card etc as mentioned in the link. The SD card and power supply is the same set that has been used since NC12!
In the meantime here is my ncp-report, which I see that php is down.
NextCloudPi version v0.62.2
NextCloudPi image NextCloudPi_03-18-18
distribution Raspbian GNU/Linux 9 \n \l
automount yes
USB devices sda
datadir /media/myCloudDrive/ncdata
data in SD no
data filesystem btrfs
data disk usage 25G/932G
rootfs usage 2.1G/15G
swapfile /var/swap
dbdir /media/myCloudDrive/database
Nextcloud check ok
Nextcloud version 14.0.1.1
HTTPD service up
PHP service down
MariaDB service up
Redis service up
Postfix service up
internet check ok
port check 80 closed
port check 443 open
IP REMOVED SENSITIVE VALUE
gateway REMOVED SENSITIVE VALUE
interface eth0
certificates REMOVED SENSITIVE VALUE
NAT loopback no
uptime 4:43
</details>
<details>
<summary>Nextcloud configuration</summary>
{
âsystemâ: {
âpasswordsaltâ: âREMOVED SENSITIVE VALUEâ,
âsecretâ: âREMOVED SENSITIVE VALUEâ,
âtrusted_domainsâ: {
â0â: âdigitalcarnage.webhop.meâ,
â1â: â192.168.0.11â,
â5â: ânextcloudpi.localâ,
â4â: âdigitalcarnage.webhop.meâ,
â3â: âdigitalcarnage.webhop.meâ,
â7â: ânextcloudpiâ,
â8â: ânextcloudpi.lanâ
},
âdatadirectoryâ: âREMOVED SENSITIVE VALUEâ,
âoverwrite.cli.urlâ: âhttps://digitalcarnage.webhop.me/â,
âdbtypeâ: âmysqlâ,
âversionâ: â14.0.1.1â,
âdbnameâ: âREMOVED SENSITIVE VALUEâ,
âdbhostâ: âREMOVED SENSITIVE VALUEâ,
âdbportâ: ââ,
âdbtableprefixâ: âoc_â,
âmysql.utf8mb4â: true,
âdbuserâ: âREMOVED SENSITIVE VALUEâ,
âdbpasswordâ: âREMOVED SENSITIVE VALUEâ,
âinstalledâ: true,
âinstanceidâ: âREMOVED SENSITIVE VALUEâ,
âmemcache.localâ: â\OC\Memcache\Redisâ,
âmemcache.lockingâ: â\OC\Memcache\Redisâ,
âredisâ: {
âhostâ: âREMOVED SENSITIVE VALUEâ,
âportâ: 0,
âtimeoutâ: 0,
âpasswordâ: âREMOVED SENSITIVE VALUEâ
},
âmail_smtpmodeâ: âsendmailâ,
âmail_smtpauthtypeâ: âLOGINâ,
âmail_from_addressâ: âREMOVED SENSITIVE VALUEâ,
âmail_domainâ: âREMOVED SENSITIVE VALUEâ,
âoverwriteprotocolâ: âhttpsâ,
âmaintenanceâ: false,
âlogfileâ: â/media/myCloudDrive/ncdata/nextcloud.logâ,
âmail_smtpsecureâ: âtlsâ,
âmail_smtpauthâ: 1,
âmail_smtphostâ: âREMOVED SENSITIVE VALUEâ,
âmail_smtpportâ: â587â,
âmail_smtpnameâ: âREMOVED SENSITIVE VALUEâ,
âmail_smtppasswordâ: âREMOVED SENSITIVE VALUEâ,
âthemeâ: ââ,
âloglevelâ: â2â,
âlog_typeâ: âfileâ,
âupdater.release.channelâ: âstableâ
}
}
</details>
<details>
<summary>HTTPd logs</summary>
[Tue Oct 02 06:25:02.984140 2018] [ssl:warn] [pid 958:tid 1996324112] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Tue Oct 02 06:25:03.000654 2018] [mpm_event:notice] [pid 958:tid 1996324112] AH00489: Apache/2.4.25 (Raspbian) OpenSSL/1.0.2l configured â resuming normal operations
[Tue Oct 02 06:25:03.000708 2018] [core:notice] [pid 958:tid 1996324112] AH00094: Command line: â/usr/sbin/apache2â
[Tue Oct 02 08:22:53.722395 2018] [mpm_event:notice] [pid 958:tid 1996324112] AH00491: caught SIGTERM, shutting down
[Tue Oct 02 10:17:16.498536 2018] [ssl:warn] [pid 661:tid 1996397840] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Tue Oct 02 10:17:17.061452 2018] [ssl:warn] [pid 971:tid 1996397840] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Tue Oct 02 10:17:18.003398 2018] [mpm_event:notice] [pid 971:tid 1996397840] AH00489: Apache/2.4.25 (Raspbian) OpenSSL/1.0.2l configured â resuming normal operations
[Tue Oct 02 10:17:18.003504 2018] [core:notice] [pid 971:tid 1996397840] AH00094: Command line: â/usr/sbin/apache2â
</details>
<details>
<summary>Database logs</summary>
2018-10-02 10:17:37 1995722064 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-10-02 10:17:37 1995722064 [Note] InnoDB: Using Linux native AIO
2018-10-02 10:17:37 1995722064 [Note] InnoDB: Using generic crc32 instructions
2018-10-02 10:17:37 1995722064 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-02 10:17:37 1995722064 [Note] InnoDB: Completed initialization of buffer pool
2018-10-02 10:28:32 1995722064 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-02 10:28:32 1995722064 [Note] InnoDB: Read redo log up to LSN=1797815808
2018-10-02 10:28:32 1995722064 [Note] InnoDB: The log sequence numbers 1797302425 and 1797302425 in ibdata files do not match the log sequence number 1797750608 in the ib_logfiles!
2018-10-02 10:28:37 1995722064 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite bufferâŚ
2018-10-02 10:28:42 1995722064 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-02 10:28:42 1995722064 [Note] InnoDB: Waiting for purge to start
2018-10-02 10:28:42 1995722064 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1797750608
2018-10-02 10:28:42 1421865776 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-10-02 10:28:42 1995722064 [Note] Plugin âFEEDBACKâ is disabled.
2018-10-02 10:28:42 1995722064 [Note] Recovering after a crash using tc.log
2018-10-02 10:28:42 1995722064 [Note] Starting crash recoveryâŚ
2018-10-02 10:28:42 1995722064 [Note] Crash recovery finished.
2018-10-02 10:28:42 1995722064 [Note] Server socket created on IP: â127.0.0.1â.
2018-10-02 10:28:42 1995722064 [Note] /usr/sbin/mysqld: ready for connections.
Version: â10.1.23-MariaDB-9+deb9u1â socket: â/var/run/mysqld/mysqld.sockâ port: 3306 Raspbian 9.0
</details>
Have just copied SD image to laptop, reformatted the card and copied the img back. Still no service
Dj
output of systemctl status php7.0-fpm
and systemctl status php7.2-fpm
?
Hello and thank you for your response. Output from the followingâŚ
systemctl status php7.0-fpm
gives:
Unit php7.0-fpm.service could not be found.
systemctl status php7.2-fpm
gives:
php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor prese
Active: inactive (dead) since Tue 2018-10-02 15:44:27 UTC; 16h ago
Docs: man:php-fpm7.2(8)
Process: 640 ExecStart=/usr/sbin/php-fpm7.2 --nodaemonize --fpm-config /etc/ph
Main PID: 640 (code=exited, status=0/SUCCESS)
Status: "Processes active: 0, idle: 4, Requests: 8, slow: 0, Traffic: 0.1req/
Oct 02 15:17:15 nextcloudpi systemd[1]: Starting The PHP 7.2 FastCGI Process Man
Oct 02 15:17:19 nextcloudpi systemd[1]: Started The PHP 7.2 FastCGI Process Mana
Oct 02 15:44:27 nextcloudpi systemd[1]: Stopping The PHP 7.2 FastCGI Process Man
Oct 02 15:44:27 nextcloudpi systemd[1]: Stopped The PHP 7.2 FastCGI Process Mana
After a CTRL z, gives
[2]+ Stopped systemctl status php7.2-fpm
Hope this helps�
DJ
yes, try systemctl start php7.2-fpm
, and then again letâs see the status systemctl status php7.2-fpm
Iâm experiencing similar issues after upgrading from 60.x to the current version with the NCP-Updater.
Logs:
NcPI Updater: https://pastebin.com/HkcSkVws
sudo ncp-report: https://pastebin.com/sEzMzehL
Seems like the PHP7.2 was not properly installed. Using SSH i tried to manually install php7.2 with this message:
`root@nextcloudpi:~# apt-get install php7.2-fpm
Reading package lists⌠Done
Building dependency tree
Reading state information⌠Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
php7.2-fpm : Depends: php7.2-cli but it is not going to be installed
Depends: php7.2-opcache but it is not going to be installed
Depends: libc6 (>= 2.27) but 2.24-11+deb9u3 is to be installed
Depends: libsodium23 (>= 1.0.14) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.`
Hello
Here is the result of the status
Many thanks. Once again for your time.
NextCloudPi v0.62.2 is up to date
Last login: Wed Oct  3 14:37:52 2018 from 192.168.0.6
pi@nextcloudpi : ~ $  sudo systemctl status php7.2-fpm
â php7.2-fpm.service - The PHP 7.2 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.2-fpm.service; enabled; vendor prese
   Active: active (running) since Wed 2018-10-03 14:38:55 UTC; 2min 56s ago
     Docs: man:php-fpm7.2(8)
 Main PID: 10108 (php-fpm7.2)
   Status: "Processes active: 0, idle: 4, Requests: 30, slow: 0, Traffic: 0req/s
   CGroup: /system.slice/php7.2-fpm.service
           ââ10108 php-fpm: master process (/etc/php/7.2/fpm/php-fpm.conf)
           ââ10109 php-fpm: pool www
           ââ10110 php-fpm: pool www
           ââ10111 php-fpm: pool www
           ââ10112 php-fpm: pool www
Oct 03 14:38:54 nextcloudpi systemd[1]: Starting The PHP 7.2 FastCGI Process Man
Oct 03 14:38:55 nextcloudpi systemd[1]: Started The PHP 7.2 FastCGI Process Mana
lines 1-15/15 (END)
Dj
Hi Nachoparker
I have just checked my instance and it is working again. I guess after the start instruction. What Iâve not checked is that it will be OK after a restart otherwise everything is perfect again.
Thanks
Dj
Hi
My nextcloudpi debian install was working perfectly until now. When I try to access nextcloudpi via webpage, I get the attached output. Any ideas what needs to be fixed?
Thanks, that did the trick!