Nextcloudpi 503 Internal Server Error after Fresh Berryboot Install

ncp

#1

Here is my problem:

My first time playing with Nextcloudpi. Used Berryboot to install Nextcloudpi on a USB attached SSD (250gb). I am using the RaspberryPi B as my device with a powered USB hub for the SSD. There are no other OS installs on this SSD. I have attempted this install twice with the same result.

  • After install, Nextcloudpi does boot up. Ran ncp-update first thing.

    • the only initial FAILED comments on boot up were:
      • FAILED to start LSB: Resize the root filesystem to fill partition
        See systemctl status Resize2fs_once.service for details
      • FAILED to start The PHP 7.2 FastCGI Process Manager
        See systemctl status php7.2-fpm.service for details
    • subsequent reboots only give the first FAILED message (along with PostFix startup)
  • I am able to set up SSH and interact that way on my internal network

  • When I try to login through the WUI I receive the 503 Internal Server Error message.

Thus, I have never seen the WUI or been able to go through the wizard to set things up.

Here is the nap-report:

<–! Paste this in GitHub report -->

NextCloudPi diagnostics

NextCloudPi version  v1.5.1
NextCloudPi image    NextCloudPi_01-14-19
distribution         Raspbian GNU/Linux 9 \n \l
automount            no
USB devices          sda 
datadir              /var/www/nextcloud/data
data in SD           yes
data filesystem      aufs
data disk usage      1000M/219G
rootfs usage         1000M/219G
swapfile             none
dbdir                /var/lib/mysql
Nextcloud check      error
HTTPD service        up
PHP service          down
MariaDB service      up
Redis service        up
Postfix service      down
internet check       ok
port check 80        closed
port check 443       closed
IP                   ***REMOVED SENSITIVE VALUE***
gateway              ***REMOVED SENSITIVE VALUE***
interface            wlan0
certificates         ***REMOVED SENSITIVE VALUE***
NAT loopback         no
uptime               2:27

Nextcloud configuration

/usr/local/bin/ncp-report: line 48: 12598 Illegal instruction     sudo -u www-data php /var/www/nextcloud/occ config:list system

HTTPd logs

[Sun Feb 03 14:12:57.953222 2019] [ssl:error] [pid 493:tid 3069845056] AH02604: Unable to configure certificate localhost:443:0 for stapling
[Sun Feb 03 14:12:58.660085 2019] [ssl:warn] [pid 601:tid 3069845056] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Sun Feb 03 14:12:58.672188 2019] [ssl:error] [pid 601:tid 3069845056] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=archlinux / issuer: CN=archlinux / serial: 8DC01C299534EC96 / notbefore: Jan 13 23:56:49 2019 GMT / notafter: Jan 10 23:56:49 2029 GMT]
[Sun Feb 03 14:12:58.672550 2019] [ssl:error] [pid 601:tid 3069845056] AH02604: Unable to configure certificate localhost:4443:0 for stapling
[Sun Feb 03 14:12:58.677799 2019] [ssl:warn] [pid 601:tid 3069845056] AH01909: localhost:443:0 server certificate does NOT include an ID which matches the server name
[Sun Feb 03 14:12:58.680249 2019] [ssl:error] [pid 601:tid 3069845056] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=archlinux / issuer: CN=archlinux / serial: 8DC01C299534EC96 / notbefore: Jan 13 23:56:49 2019 GMT / notafter: Jan 10 23:56:49 2029 GMT]
[Sun Feb 03 14:12:58.680508 2019] [ssl:error] [pid 601:tid 3069845056] AH02604: Unable to configure certificate localhost:443:0 for stapling
[Sun Feb 03 14:12:59.036027 2019] [mpm_event:notice] [pid 601:tid 3069845056] AH00489: Apache/2.4.25 (Raspbian) OpenSSL/1.0.2l configured -- resuming normal operations
[Sun Feb 03 14:12:59.036836 2019] [core:notice] [pid 601:tid 3069845056] AH00094: Command line: '/usr/sbin/apache2'
[Sun Feb 03 16:12:25.044749 2019] [authz_host:error] [pid 635:tid 2756564016] [client 192.168.40.233:52547] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:12:45.243391 2019] [authz_host:error] [pid 635:tid 2756564016] [client 192.168.40.233:52548] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:12:45.243899 2019] [authnz_external:error] [pid 635:tid 2756564016] [client 192.168.40.233:52548] Invalid AuthExternal keyword (pwauth)
[Sun Feb 03 16:12:45.635628 2019] [authz_host:error] [pid 636:tid 2764960816] [client 192.168.40.233:52549] AH01753: access check of 'localhost' to /favicon.ico failed, reason: unable to get the remote host name, referer: https://192.168.40.87/
[Sun Feb 03 16:13:05.976473 2019] [authz_host:error] [pid 635:tid 2756564016] [client 192.168.40.233:52573] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:13:06.070892 2019] [authz_host:error] [pid 636:tid 2764960816] [client 192.168.40.233:52574] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:13:06.071383 2019] [authnz_external:error] [pid 636:tid 2764960816] [client 192.168.40.233:52574] Invalid AuthExternal keyword (pwauth)
[Sun Feb 03 16:13:23.301264 2019] [authz_host:error] [pid 635:tid 2756564016] [client 192.168.40.233:52591] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:13:43.843357 2019] [authz_host:error] [pid 636:tid 2764960816] [client 192.168.40.233:52641] AH01753: access check of 'localhost' to / failed, reason: unable to get the remote host name
[Sun Feb 03 16:13:43.843809 2019] [authnz_external:error] [pid 636:tid 2764960816] [client 192.168.40.233:52641] Invalid AuthExternal keyword (pwauth)
[Sun Feb 03 16:13:44.071932 2019] [authz_host:error] [pid 635:tid 2756564016] [client 192.168.40.233:52642] AH01753: access check of 'localhost' to /favicon.ico failed, reason: unable to get the remote host name, referer: https://192.168.40.87/

Database logs

2019-02-03 14:14:12 3062816032 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2019-02-03 14:14:12 3062816032 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-02-03 14:14:12 3062816032 [Note] InnoDB: The InnoDB memory heap is disabled
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-02-03 14:14:12 3062816032 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Using Linux native AIO
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Using generic crc32 instructions
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-02-03 14:14:12 3062816032 [Note] InnoDB: Completed initialization of buffer pool
2019-02-03 14:14:13 3062816032 [Note] InnoDB: Highest supported file format is Barracuda.
2019-02-03 14:14:14 3062816032 [Note] InnoDB: 128 rollback segment(s) are active.
2019-02-03 14:14:14 3062816032 [Note] InnoDB: Waiting for purge to start
2019-02-03 14:14:14 3062816032 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.41-84.1 started; log sequence number 4082558
2019-02-03 14:14:14 3062816032 [Note] Plugin 'FEEDBACK' is disabled.
2019-02-03 14:14:14 2516579136 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-02-03 14:14:14 3062816032 [Note] Server socket created on IP: '127.0.0.1'.
2019-02-03 14:14:14 3062816032 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.37-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Raspbian 9.0

Nextcloud logs


Thanks for your help.


#2

What is terminal output of

uname -a

Just want to make sure your rpi is supported (armv7)

Also, and not 100% sure, I never use aufs, but think NCP requires ext4 or btrfs


#3

Hi,
I think you might have the same problem I encountered (only I think I posted to the wrong category -installation):

Php7.2 doesn’t seem to work with the Rpi 1 architecture, hence php7.0 is needed instead. It’s a bit frustrating, as the NCP berryboot image is called ‘all pi’.

I have not yet managed to get php7.0 correctly associated with apache (without creating a huge mess).

Best solution would be if someone could share an older NCP image (2018 - NC14 with php7) - there was one floating around, but the torrent is down…

Any help would be highly appreciated…


#4

Rpi1 and Zero are no longer supported by NCP (since moving from php7.0 to php7.2)
(Minimal is armv7)
Fyi read article on rpi by creator and maintainer of NCP.


#5

Thanks, OliverV and thewer.

Yes, I checked and definitely have Armv6. Am going to order a new pi today.

Thanks for that article, OliverV


#6

I don’t recommend it

https://ownyourbits.com/2019/02/02/whats-wrong-with-the-raspberry-pi/


#7

Thanks, nachoparker. I am reading and trying to learn more. very helpful.