Here my version information:
Observium CE
19.8.10000 (22nd August 2019)
OS
Linux 4.4.0-176-generic [amd64] (Ubuntu 16.04)
Apache
2.4.18 (Ubuntu)
PHP
7.0.33-0ubuntu0.16.04.12 (OPcache: ENABLED)
Python
2.7.12
MySQL
5.7.29-0ubuntu0.16.04.1 (extension: mysqli 5.0.12-dev)
SNMP
NET-SNMP 5.7.3
RRDtool
1.5.5
Fping
3.13 (IPv4 and IPv6)
Von: observium observium-bounces@observium.org Im Auftrag von Adam Armstrong via observium Gesendet: Donnerstag, 9. April 2020 17:36 An: 'Observium' observium@observium.org Cc: Adam Armstrong adama@observium.org Betreff: Re: [Observium] Apache dies with Segmentation Fault
Sounds like some apache/php/opcode cache interaction. I'd usually guess rrdtool, but since this is effecting the ui and not specifically graph generation, it's more likely to be a php issue.
Never seen this issue specifically before though, what is it running on?
Adam.
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Beulen, Klaus via observium Sent: 09 April 2020 10:09 To: observium@observium.orgmailto:observium@observium.org Cc: Beulen, Klaus <Klaus.Beulen@thyssenkrupp.commailto:Klaus.Beulen@thyssenkrupp.com> Subject: [Observium] Apache dies with Segmentation Fault
Hi,
we are currently using Observium CE 19.8.10000 as a test installation to monitor part of our switch/router infrastructure (currently about 290 devices, mostly Cisco). From time to time we have problems accessing the UI, the web browser just answers "Page does not work - observium did not send an answer - ERR_EMPTY_RESPONSE". When I check the error.log in /var/logs/apache, I find lots of lines like
... [Wed Apr 08 14:44:44.362412 2020] [core:notice] [pid 1367] AH00051: child pid 27005 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Apr 08 14:44:44.362479 2020] [core:notice] [pid 1367] AH00051: child pid 1696 exit signal Segmentation fault (11), possible coredump in /etc/apache2 [Wed Apr 08 14:44:53.366005 2020] [core:notice] [pid 1367] AH00051: child pid 7903 exit signal Segmentation fault (11), possible coredump in /etc/apache2 ...
Is this a known bug/error in this version, or did I eventually configure something wrong? All packages are up to date ("apt update; apt upgrade").
Regards, Klaus.