Here goes mine, Eric
I've been able to reproduce the log failure signature with a change to the collectd.conf file
The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands
ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so
A simplex configuration... controller-0:~$ ls -lrt /usr/lib64/collectd/python.so -rwxr-xr-x. 1 root root 76008 Apr 14 2017 /usr/lib64/collectd/python.so controller-0:~$ ldd /usr/lib64/collectd/python.so linux-vdso.so.1 => (0x00007ffee5b9d000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f53e9b8a000) libutil.so.1 => /lib64/libutil.so.1 (0x00007f53e9987000) libm.so.6 => /lib64/libm.so.6 (0x00007f53e9685000) libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f53e926b000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f53e9067000) libc.so.6 => /lib64/libc.so.6 (0x00007f53e8c9a000) /lib64/ld-linux-x86-64.so.2 (0x00007f53e9fb8000) controller-0:~$ controller-0:~$ uname -a Linux controller-0 3.10.0-862.6.3.el7.35.tis.x86_64 #1 SMP PREEMPT Fri Jul 20 15:55:20 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux controller-0:~$