Php core dump on large Captive portal system

[laragio]

Hi,
we have implemented a large Captive portal system with 40+ users connected at same time.
For the authentication we have set up a different machine that call the function on pfsense box to connect and disconnect user. We have a third lighttpd for this purpose with the same configuration of the lighttpd for the webGUI.

Today this system stopped to work, the user were authenticated but the rules wasn't added to ipfw and on system log there was many of this messages:

Jan 21 12:47:25 kernel: pid 1848 (php), uid 0: exited on signal 11 (core dumped)
Jan 21 12:45:38 kernel: pid 1517 (php), uid 0: exited on signal 11 (core dumped)
Jan 21 12:42:00 kernel: pid 1406 (php), uid 0: exited on signal 11 (core dumped)
Jan 21 12:41:40 kernel: pid 526 (php), uid 0: exited on signal 11 (core dumped)

and also the webGUI became very slow.

I have read a post to speed up the webGUI that tell to add
"PHP_FCGI_CHILDREN" => "16",
"PHP_FCGI_MAX_REQUESTS" => "{$max_requests}"
on lightttpd configuration

Is there any of you that can explain the meaning of the log?  Change the lighttpd configuration could solve the problem?
Any suggestion about that?

Thanks

[kloon]

Hi,

i am facing the same problem. We had setup a RADIUS server for authentication.

Jul 13 10:58:51 kernel: pid 27357 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:56:13 kernel: pid 55547 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:55:19 kernel: pid 17161 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:54:58 kernel: pid 53154 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:47:34 kernel: pid 52717 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:46:23 kernel: pid 52466 (php), uid 0: exited on signal 11 (core dumped)
Jul 13 10:45:15 kernel: pid 50592 (php), uid 0: exited on signal 11 (core dumped)

by any chance to solve this issue?

Thank you.

[jimp]

Usually signal 11 is indicative of a hardware problem. You may want to run some tests on your firewall (such as memtest86+) to rule that out.

Could also be a flaky PSU, overheating, etc.

[kloon]

alright, i found the root cause. it's due to our radius server does not respond to it.