The original error reappeared:
[New LWP 4655]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `php-fpm: pool smf
'.
Program terminated with
Unfortunately I didn't keep that particular core dump, but I have more
recent dumps. I've attached one of them. The error has changed:
[New LWP 3553]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by
Public bug reported:
I'm using php7.2-fpm to run the Simple Machines Community Forum. I have
an fpm pool dedicated to the forum. Every so often I see an error like
this in my fpm log:
[01-Mar-2020 01:18:15] WARNING: [pool smf] child 23384 exited on signal
7 (SIGBUS - core dumped) after 0.708817
I've attached a patch based on code found here:
https://github.com/SpamExperts/pyzor
** Patch added: "pyzor.patch"
https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/1852433/+attachment/5305455/+files/pyzor.patch
--
You received this bug notification because you are a member of Ubuntu
Traceback:
Traceback (most recent call last):
File "/usr/bin/pyzor", line 408, in
main()
File "/usr/bin/pyzor", line 152, in main
if not dispatch(client, servers, config):
File "/usr/bin/pyzor", line 237, in check
for digested in get_input_handler(style):
File
Public bug reported:
>From spamd.log:
Wed Nov 13 07:02:40 2019 [4966] info: pyzor: [10238] error: TERMINATED,
signal 15 (000f)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pyzor 1:1.0.0-3
Uname: Linux 5.1.17-x86_64-linode128 x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Public bug reported:
After upgrading a server from 12.04 to 14.04 I found that the nginx web
server wasn't starting automatically. I could start the server without
error from the command line. Running sudo /etc/init.d/nginx start
would produce no visible error, but the service would not be
Public bug reported:
After upgrading a server from 12.04 to 14.04 I found that the nginx web
server wasn't starting automatically. I could start the server without
error from the command line. Running sudo /etc/init.d/nginx start
would produce no visible error, but the service would not be
