No access to Nextcloud by browser after update to 1.36.2 / httpd down / Cannot load Zend OPcache

Dear Community,

I am facing the following problem and hope, somebody can help.

Description of problem

  • about 3 days ago I wanted to log in the admin webui (:4443) to see status of my nextcloudpi (e.g. latest available update installed)
  • just before that everything worked normal
  • I also could not log in to my Nextcloud by browser (time out)
  • also no access by Android or Windows client at the moment
  • I am able to connect by SSH

After some searching I collected the following info to hopefully support the problem solving:

Extract of output of ncp-report
(sorry, I don´t know how to use pastebin)

	<--! Paste this in GitHub report -->

	<details>
	<summary>NextCloudPi diagnostics</summary>

	```

	Cannot load Zend OPcache - it was already loaded
	NextCloudPi version  v1.36.2
	NextCloudPi image    NextCloudPi_09-12-17
	distribution         Raspbian GNU/Linux 9 \n \l
	automount            yes
	USB devices          sda
	datadir              /media/USBdrive/ncdata
	data in SD           no
	data filesystem      ext2/ext3
	data disk usage      35G/343G
	rootfs usage         2.6G/30G
	swapfile             /var/swap
	dbdir                /var/lib/mysql
	Nextcloud check      ok
	Nextcloud version    20.0.8.1
	HTTPD service        down
	PHP service          up
	MariaDB service      up
	Redis service        up
	Postfix service      up
	internet check       ok
	port check 80        closed
	port check 443       closed
	IP                   ***REMOVED SENSITIVE VALUE***
	gateway              ***REMOVED SENSITIVE VALUE***
	interface            eth0
	certificates         ***REMOVED SENSITIVE VALUE***
	NAT loopback         no
	uptime               1day

	```
	</details>


	<details>
	<summary>HTTPd logs</summary>

	```


	```
	</details>

output of systemctl status apache2

	systemctl status apache2
	● apache2.service - The Apache HTTP Server
	   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
	   Active: failed (Result: exit-code) since Mon 2021-05-24 13:08:53 UTC; 1 day 19h ago
	  Process: 622 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)

	May 24 13:08:51 raspberrypi systemd[1]: Starting The Apache HTTP Server...
	May 24 13:08:53 raspberrypi apachectl[622]: AH00526: Syntax error on line 10 of /etc/apache2/conf-enabled/http2.conf:
	May 24 13:08:53 raspberrypi apachectl[622]: SSLProtocol: Illegal protocol 'TLSv1.3'
	May 24 13:08:53 raspberrypi apachectl[622]: Action 'start' failed.
	May 24 13:08:53 raspberrypi apachectl[622]: The Apache error log may have more information.
	May 24 13:08:53 raspberrypi systemd[1]: apache2.service: Control process exited, code=exited status=1
	May 24 13:08:53 raspberrypi systemd[1]: Failed to start The Apache HTTP Server.
	May 24 13:08:53 raspberrypi systemd[1]: apache2.service: Unit entered failed state.
	May 24 13:08:53 raspberrypi systemd[1]: apache2.service: Failed with result 'exit-code'.
	May 26 07:50:40 raspberrypi systemd[1]: apache2.service: Unit cannot be reloaded because it is inactive.

apache error.log.1 (error.log is empty and older)

[Fri May 14 06:25:02.656797 2021] [ssl:warn] [pid 921:tid 1995981168] AH01909: localhost:4443:0 server certificate does NOT include an ID which matches the server name
[Fri May 14 06:25:03.000556 2021] [mpm_event:notice] [pid 921:tid 1995981168] AH00489: Apache/2.4.25 (Raspbian) OpenSSL/1.0.2u configured -- resuming normal operations
[Fri May 14 06:25:03.000647 2021] [core:notice] [pid 921:tid 1995981168] AH00094: Command line: '/usr/sbin/apache2'
[Fri May 21 11:04:17.313814 2021] [core:warn] [pid 921:tid 1995981168] AH00045: child process 27511 still did not exit, sending a SIGTERM
[Fri May 21 11:05:07.848232 2021] [core:warn] [pid 921:tid 1995981168] AH00045: child process 19816 still did not exit, sending a SIGTERM
[Fri May 21 11:05:08.849751 2021] [mpm_event:notice] [pid 921:tid 1995981168] AH00491: caught SIGTERM, shutting down

output of nc-update (initiated by ncp-config):

  sudo ncp-config
  Running nc-update
  Downloading updates
  Performing updates
  Running unattended-upgrades
  Unattended upgrades active: yes (autoreboot true)
  Running nc-autoupdate-nc
  automatic Nextcloud updates enabled
  Update to buster available. Type 'sudo ncp-dist-upgrade' to upgrade
  Cannot load Zend OPcache - it was already loaded

  Broadcast message from pi@raspberrypi (somewhere) (Wed May 26 07:50:43 2021):

  Update to buster available. Type 'sudo ncp-dist-upgrade' to upgrade

  cannot get tty name: Inappropriate ioctl for device
  ls: cannot access '/etc/php/7.3/fpm/conf.d/*-opcache.ini': No such file or directory
  ls: cannot access '/etc/php/7.3/cli/conf.d/*-opcache.ini': No such file or directory
  NextCloudPi updated to version v1.36.2
  Done. Press any key...

  Cannot load Zend OPcache - it was already loaded

With my very limited knowledge there I read from the following potentially important info from the logs:

HTTPD service        down

May 24 13:08:51 raspberrypi systemd[1]: Starting The Apache HTTP Server...
May 24 13:08:53 raspberrypi apachectl[622]: AH00526: Syntax error on line 10 of /etc/apache2/conf-enabled/http2.conf:
May 24 13:08:53 raspberrypi apachectl[622]: SSLProtocol: Illegal protocol 'TLSv1.3'

Is this somehow linked to the update lamp: allow only TLSv12 and TLSv13 (and that I am on Debian 9)?

I am grateful for any hint to solve this. Thanks a lot in advance

Sorry I have the same problem as above
Device: raspberry pi4
OS: raspberry lite
OVM
NCP (docker) fresh install
Currently I can’t access localhost:4443

Initializing empty volume..

Cannot load Zend OPcache - it was already loaded

Making /usr/local/etc/ncp-config.d persistent ...

Making /etc/services-enabled.d persistent ...

Making /etc/letsencrypt persistent ...

Making /etc/shadow persistent ...

Making /etc/cron.d persistent ...

Making /etc/cron.daily persistent ...

Making /etc/cron.hourly persistent ...

Making /etc/cron.weekly persistent ...

Making /usr/local/bin persistent ...

Cannot load Zend OPcache - it was already loaded

Making /etc/apache2 persistent ...

Starting PHP-fpm

Cannot load Zend OPcache - it was already loaded

Starting Apache

Starting mariaDB

2021-12-04 16:49:40 0 [Note] mysqld (mysqld 10.3.27-MariaDB-0+deb10u1) starting as process 115 ...

Cannot load Zend OPcache - it was already loaded

Starting Redis

Starting Cron

Starting Postfix

postsuper: Renamed to match inode number: 1 message

postsuper: warning: QUEUE FILE NAMES WERE CHANGED TO MATCH INODE NUMBERS
      
Provisioning

Cannot load Zend OPcache - it was already loaded

Provisioning Redis password

Updating NextCloud config with Redis password

Provisioning MariaDB password

Updating NextCloud config with MariaDB password

Cannot load Zend OPcache - it was already loaded

Running nc-limits

Cannot load Zend OPcache - it was already loaded

Using 5872339968B for PHP

Using 6 PHP threads

Using 1907115008 memory for the database

Stopping MariaDB database server: mysqld.

Starting MariaDB database server: mysqld . . . . . ..

Stopping redis-server: redis-server.

Starting redis-server: redis-server.

Starting notify_push daemon

Configuring Domain

Cannot load Zend OPcache - it was already loaded

Cannot load Zend OPcache - it was already loaded

System config value trusted_domains => 11 set to string 123.20.84.83

Cannot load Zend OPcache - it was already loaded

System config value trusted_domains => 1 set to string 172.17.0.11

Cannot load Zend OPcache - it was already loaded

Cannot load Zend OPcache - it was already loaded

Cannot load Zend OPcache - it was already loaded

Cannot load Zend OPcache - it was already loaded

Cannot load Zend OPcache - it was already loaded

Nextcloud version 21.0.4.1. NextCloudPi version v1.40.4
      

e

I thought this post looked a little lonely here so I figured I give it a try and give you guys a reply :slight_smile:

I am not sure at all if that is the case but it is very likely, the OPCache errors are occuring because there is a duplicate entry somewhere to the opcache .ini files which should be overall harmless and other than that the SSL error is the only one that is critical for you (from what I can tell)

I gathered some links below with some relevant information about the OPCache for others that are looking at this post

There are some instructions in the GitHub issue and PHP Freaks of possible locations to look for duplicate entries. As NCP is progressing from Buster to Bullseye this is going to happen again, hopefully someone that has some time over can make a PR with a fix for it pre-emptively this time :slight_smile:

About the access to localhost, is your local ip, hostname or ‘localhost’ added as trusted proxies?