Apache2 -> Segmentation fault

Hello Nextcloud community,

I face this issue already twice, when the Nextcloud server is not reachable anymore. In the error.log of Apache, I see segmentation faults. After a restart of Apache, the Nextcloud instance is working again.

Would appreciate if someone can provide me some help on analyzing this problem.

Nextcloud version (18.0.3):
Operating system and version (Raspbian GNU/Linux 10 (buster)):
Apache or nginx version (Apache/2.4.38 (Raspbian)):
PHP version (7.3):

The issue you are facing:
Nextcloud is not reachable anymore. Host system works fine.

Is this the first time you’ve seen this error? (Y):

Steps to replicate it:

Happened twice but I was not able to reproduce it.

The output of your Nextcloud log in Admin > Logging:

Not relevant because no logs that belongs to the date this issue occured.

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => '',
  'passwordsalt' => '',
  'secret' => '',
  'trusted_domains' => 
  array (
    0 => '192.168.0.2',
  ),
  'datadirectory' => '/media/nc/nextcloud-data',
  'dbtype' => 'mysql',
  'version' => '19.0.4.2',
  'overwrite.cli.url' => 'http://192.168.0.2/nextcloud',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nc',
  'dbpassword' => '',
  'installed' => true,
  'simpleSignUpLink.shown' => false,
  'maintenance' => false,
  'theme' => '',
  'loglevel' => 2,
);

The output of access.log in /var/log/apache:
https://pastebin.ubuntu.com/p/5sZwkGjgxv/

The output of error.log in /var/log/apache:
https://pastebin.ubuntu.com/p/9YbNpkk2XK/

You were using the text editor on Nextcloud when this happened. Hard to say what is happening, Segmentation Faults ideally never happen, so mostly that is some memory corruption. if you can get core dumps (well difficult if you don’t know how to reproduce), that could tell you a bit more at which point it is happening.

Just in general, I’d look into the caching stuff in the documentation, this can reduce the overall load on the server and perhaps then this problems goes away as well. Even though it’s indicating that something is not configured correctly…