Confirmed: I installed Ubuntu 14 on that server and it works as expected, so it's got something to do with U16. From: Clayton Dukes <cdukes@logzilla.net> Date: Sunday, January 1, 2017 at 4:04 PM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: v3.9: Core dump on python module No idea if this helps - I'm not a programmer ;) - but here's a gdb output. Happy to provide the core file also if you want (it's only 5MB) Reading symbols from /usr/sbin/syslog-ng...(no debugging symbols found)...done. [New LWP 13186] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `syslog-ng -Fdve'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fd99f82a54b in PyModule_GetDict () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 (gdb) bt full #0 0x00007fd99f82a54b in PyModule_GetDict () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 No symbol table info available. #1 0x00007fd99fc223b8 in _py_get_main_module () from /usr/lib/syslog-ng/3.8/libmod-python.so No symbol table info available. #2 0x00007fd99fc22473 in _py_evaluate_global_code () from /usr/lib/syslog-ng/3.8/libmod-python.so No symbol table info available. #3 0x00007fd99fc22551 in python_evaluate_global_code () from /usr/lib/syslog-ng/3.8/libmod-python.so No symbol table info available. #4 0x00007fd99fc2342f in python_parse () from /usr/lib/syslog-ng/3.8/libmod-python.so No symbol table info available. #5 0x00007fd9a44b068f in plugin_parse_config () from /usr/lib/syslog-ng/libsyslog-ng-3.8.so.0 No symbol table info available. #6 0x00007fd9a44bd869 in main_parse () from /usr/lib/syslog-ng/libsyslog-ng-3.8.so.0 No symbol table info available. #7 0x00007fd9a4497690 in cfg_run_parser () from /usr/lib/syslog-ng/libsyslog-ng-3.8.so.0 No symbol table info available. #8 0x00007fd9a4497887 in cfg_read_config () from /usr/lib/syslog-ng/libsyslog-ng-3.8.so.0 No symbol table info available. #9 0x00007fd9a44acae7 in main_loop_read_and_init_config () from /usr/lib/syslog-ng/libsyslog-ng-3.8.so.0 No symbol table info available. #10 0x00000000004016f5 in main () No symbol table info available. From: Clayton Dukes <cdukes@logzilla.net> Date: Sunday, January 1, 2017 at 3:18 PM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: Re: v3.9: Core dump on python module Looks like this is happening with 3.8.1-3 as well :( Only difference I can see if Ubuntu 14 vs 16? Any ideas of what I can try? From: Clayton Dukes <cdukes@logzilla.net> Date: Sunday, January 1, 2017 at 2:56 PM To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu> Subject: v3.9: Core dump on python module Hey guys, just want you to know Ubuntu16 is dumping core on loading the python module. Ubuntu14 does not do this. [2017-01-01T19:54:52.576749] Module loaded and initialized successfully; module='mod-python' Segmentation fault (core dumped) -Clayton Dukes