RRDTOOL Segmentation fault

Just getting started. Have 4 pollers running and trying to collect data from 3640 devices. Lots of them have no charts even though we have been running for over 3 weeks. First one I looked at has the following:

RRDTool Command

rrdtool graph /tmp/zq9FyGRCpXWZvirG -g --alt-autoscale-max --rigid -E --start 1525885200 --end 1525971600 --width 1728 --height 316.33333333333 -c BACK#EEEEEE00 -c SHADEA#EEEEEE00 -c SHADEB#EEEEEE00 -c FONT#000000 -c CANVAS#FFFFFF00 -c GRID#a5a5a5 -c MGRID#FF9999 -c FRAME#5e5e5e -c ARROW#5e5e5e -R normal --font LEGEND:8:DejaVuSansMono --font AXIS:7:DejaVuSansMono --font-render-mode normal COMMENT:’ Now Avg Max’ COMMENT:‘\n’ CDEF:inB= CDEF:outB= CDEF:octets=inB,outB,+ CDEF:doutB=outB,-1,* CDEF:inbits=inB,8,* CDEF:outbits=outB,8,* CDEF:bits=inbits,outbits,+ CDEF:doutbits=doutB,8,* VDEF:percentile_in=inbits,95,PERCENT VDEF:percentile_out=outbits,95,PERCENT CDEF:dpercentile_outn=doutbits,-1,* VDEF:dpercentile_outnp=dpercentile_outn,95,PERCENT CDEF:dpercentile_outnpn=doutbits,doutbits,-,dpercentile_outnp,-1,*,+ VDEF:dpercentile_out=dpercentile_outnpn,FIRST VDEF:totin=inB,TOTAL VDEF:avein=inbits,AVERAGE VDEF:totout=outB,TOTAL VDEF:aveout=outbits,AVERAGE VDEF:tot=octets,TOTAL COMMENT:’ \n’ HRULE:999999999999999#FFFFFF:‘Total In ’ GPRINT:inbits:LAST:%6.2lf%s GPRINT:inbits:AVERAGE:%6.2lf%s GPRINT:inbits:MAX:%6.2lf%s GPRINT:totin:%6.2lf%sB COMMENT:’\n’ HRULE:999999999999990#FFFFFF:’ Out’ GPRINT:outbits:LAST:%6.2lf%s GPRINT:outbits:AVERAGE:%6.2lf%s GPRINT:outbits:MAX:%6.2lf%s GPRINT:totout:%6.2lf%sB COMMENT:‘\n’ HRULE:999999999999990#FFFFFF:’ Agg’ GPRINT:bits:LAST:%6.2lf%s GPRINT:bits:AVERAGE:%6.2lf%s GPRINT:bits:MAX:%6.2lf%s GPRINT:tot:%6.2lf%sB COMMENT:‘\n’ HRULE:0#999999
RRDTool Output

Segmentation fault (core dumped)

Where do I start troubleshooting?

First would have been to provide the info asked for when opening an issue.

Sure, as soon as I find what is asked for. Certainly wan’t anything obvious on the start a new topic page, at least not to me.
It would have been helpful to point out where the requested info list is.

====================================

Component Version
LibreNMS 1.39-27-ge898075
DB Schema 249
PHP 7.0.28-0ubuntu0.16.04.1
MySQL 5.7.19-17-log
RRDTool 1.5.5
SNMP NET-SNMP 5.7.3

====================================

[OK] Composer Version: 1.6.5
[OK] Dependencies up-to-date.
[OK] Database connection successful
[FAIL] You have not set sql_mode=’’ in your mysql config.
[FIX] Set sql-mode=’’ in your mysql config file in the [mysqld] section.
[OK] Database schema correct
[FAIL] The poller (NMS1) has not completed within the last 5 minutes, check the cron job.
[FAIL] The poller (nmspoller4) has not completed within the last 5 minutes, check the cron job.
[WARN] Some devices have not been polled in the last 5 minutes. You may have performance issues.
[FIX] Check your poll log and see: http://docs.librenms.org/Support/Performance/
Devices:
172.19.116.107
172.19.121.86
172.19.125.216
172.19.87.75
172.19.75.138
172.19.75.140
172.19.108.79
172.19.121.101
172.19.121.87
172.19.116.225
172.19.121.125
172.19.87.94
172.19.139.250
172.19.108.53
172.19.96.204
and 143 more…
[FAIL] Discovery has not completed in the last 24 hours.
[FIX] Check the cron job to make sure it is running and using discovery-wrapper.py
[WARN] Your install is over 24 hours out of date, last update: Wed, 09 May 2018 01:37:06 +0000
[FIX] Make sure your daily.sh cron is running and run ./daily.sh by hand to see if there are any errors.

This is on the Web Server because that is where I saw the error I out in the original post. We are working on the pollers not completing in 5 minutes. If that may lead to the segmentation fault, please point that out and we will wait until we get the poller issue resolved and see if that corrects that problem.

I’d be looking at those - could easily be the the default lack of SQL mode causing RRDtool to segfault.

Thanks. We’ll get that done.

Possibly but honestly, you had to delete that text to post so it couldn’t get more obvious in the first place.

Fix all of what’s reported by validate. No point chasing a fix for something else when you have multiple other issues.