What would the Observium poller wrapper be coredumping into /etc/apache2?
Where did this error come from?
Adam.
Sent from BlueMail
On 26 Sep 2016, 13:27, at 13:27, Laurence Mayer laurence@istraresearch.com wrote:
I see the following in my logs, assuming it is somewhat related, but nos sure how.
Fatal Python error: PyEval_AcquireThread: NULL new thread state [Mon Sep 26 21:25:57.557593 2016] [core:notice] [pid 4727] AH00051: child pid 5330 exit signal Aborted (6), possible coredump in /etc/apache2 Fatal Python error: PyEval_AcquireThread: NULL new thread state [Mon Sep 26 21:26:12.574612 2016] [core:notice] [pid 4727] AH00051: child pid 4735 exit signal Aborted (6), possible coredump in /etc/apache2
On Mon, Sep 26, 2016 at 9:11 PM, Laurence Mayer laurence@istraresearch.com wrote:
Sorry for the back-and-forth, indeed it looks like it ran once and
then
stopped generating the graph.
Crontab is running as before, don't see the reason that RDD is not generating the graphs correctly.
Any ideas?
Thanks Laurence
[image: Inline image 1]
On Mon, Sep 26, 2016 at 8:55 PM, Laurence Mayer < laurence@istraresearch.com> wrote:
Please ignore, my bad.
Regards Laurence
On Mon, Sep 26, 2016 at 8:49 PM, Laurence Mayer < laurence@istraresearch.com> wrote:
Hi,
I upgraded this morning to the latest version and for some reason
the
graphs are now not being generated (rrd). I do see the files being updated (date and time looks as of now).
You can see here for example the CPUs are 100% (should be) however
the
graph shows nothing.
[image: Inline image 1]
Any ideas?
Thanks Laurence
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium