Created attachment 832204 [details] ocspd configuration Version-Release number of selected component (if applicable): ocspd-1.9.0-1.fc19.x86_64 ERROR: Internal memory allocation error!: TCP_CHECK from keepalived balancer daemon and others tcpcheck daemons. # systemctl status ocspd ocspd.service - OpenCA OCSP Responder Loaded: loaded (/usr/lib/systemd/system/ocspd.service; disabled) Active: inactive (dead) since Fri 2013-11-29 12:12:07 CET; 4s ago Process: 24932 ExecStart=/usr/sbin/ocspd -d -c /etc/ocspd/ocspd.conf $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 24933 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/ocspd.service Nov 29 12:11:52 buho2.bichos.org ocspd[24933]: ERROR: Internal memory allocation error! Nov 29 12:11:52 buho2.bichos.org ocspd[24933]: ERROR::Can not parse REQ Nov 29 12:11:57 buho2.bichos.org ocspd[24933]: ERROR: Internal memory allocation error! Nov 29 12:11:57 buho2.bichos.org ocspd[24933]: ERROR::Can not parse REQ Nov 29 12:12:02 buho2.bichos.org ocspd[24933]: ERROR: Internal memory allocation error! Nov 29 12:12:02 buho2.bichos.org ocspd[24933]: ERROR::Can not parse REQ Nov 29 12:12:07 buho2.bichos.org ocspd[24933]: ERROR: Internal memory allocation error! Nov 29 12:12:07 buho2.bichos.org ocspd[24933]: ERROR::Can not parse REQ You can simple testing it with,(equivalent keepalived tcpcheck): telnet IP PORT <<<EOF example: telnet 172.16.0.111 2560 <<<EOF
Created attachment 832207 [details] keepalived configuration
I tried to reproduce the "Internal memory allocation" error with your ocspd.conf file (only file names and of course file contents have been changed) without success. Do you have a recipe to reproduce? Does it always occur? What was the ocsp activity (i.e.: request count, frequency, time up) before the problem occurred? Thanks for more info.
Hi Patrick: You can get this error using 'tcping' command tool, similar to 'keepalived' TCP_CHECK: Start the service: # systemctl start ocspd Show status: # systemctl status ocspd ocspd.service - OpenCA OCSP Responder Loaded: loaded (/usr/lib/systemd/system/ocspd.service; enabled) Active: active (running) since Wed 2013-12-04 10:32:28 CET; 13s ago Process: 29248 ExecStart=/usr/sbin/ocspd -d -c /etc/ocspd/ocspd.conf $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 29249 (ocspd) CGroup: name=systemd:/system/ocspd.service \u2514\u250029249 /usr/sbin/ocspd -d -c /etc/ocspd/ocspd.conf Dec 04 10:32:27 buho1.bichos.org ocspd[29248]: OpenCA OCSPD v1.9.0 - starting. Dec 04 10:32:28 buho1.bichos.org ocspd[29248]: CRL loaded for first_ca Dec 04 10:32:28 buho1.bichos.org systemd[1]: Started OpenCA OCSP Responder. No errors for now, we check the service with 'tcping' three times: # tcping 172.16.0.111 2560 <<< this is a simple tcp check for open port. 172.16.0.111 port 2560 open. # tcping 172.16.0.111 2560 172.16.0.111 port 2560 open. # tcping 172.16.0.111 2560 172.16.0.111 port 2560 open. We see the ocspd status: # systemctl status ocspd ocspd.service - OpenCA OCSP Responder Loaded: loaded (/usr/lib/systemd/system/ocspd.service; enabled) Active: active (running) since Wed 2013-12-04 10:32:28 CET; 13s ago Process: 29248 ExecStart=/usr/sbin/ocspd -d -c /etc/ocspd/ocspd.conf $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 29249 (ocspd) CGroup: name=systemd:/system/ocspd.service \u2514\u250029249 /usr/sbin/ocspd -d -c /etc/ocspd/ocspd.conf Dec 04 10:32:27 buho1.bichos.org ocspd[29248]: OpenCA OCSPD v1.9.0 - starting. Dec 04 10:32:28 buho1.bichos.org ocspd[29248]: CRL loaded for first_ca Dec 04 10:32:28 buho1.bichos.org systemd[1]: Started OpenCA OCSP Responder. Dec 04 10:32:36 buho1.bichos.org ocspd[29249]: ERROR: Internal memory allocation error! Dec 04 10:32:36 buho1.bichos.org ocspd[29249]: ERROR::Can not parse REQ Dec 04 10:32:36 buho1.bichos.org ocspd[29249]: ERROR: Internal memory allocation error! Dec 04 10:32:36 buho1.bichos.org ocspd[29249]: ERROR::Can not parse REQ Dec 04 10:32:37 buho1.bichos.org ocspd[29249]: ERROR: Internal memory allocation error! Dec 04 10:32:37 buho1.bichos.org ocspd[29249]: ERROR::Can not parse REQ It shows three errors due three tcping executions, this is the same effect with keepalived tcp_check. Thanks. Jose Luis
@jose luis: thanks a lot: tcping did the trick, but telnet didn't. This is related to client closing the connection before timeout and without sending the whole request. The "memory allocation error" is not real and thus can be safely ignored. I've just produced a patched version for tests: can you try http://kojipkgs.fedoraproject.org//work/tasks/6153/6256153/ocspd-1.9.0-2.fc19.x86_64.rpm please ?
Hi Patrick: We've tested the patched version you sent and it works perfectly. Many thanks. Jose Luis & Xose
Thanks a lot for testing, guys. Official update will be available soon.
ocspd-1.9.0-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ocspd-1.9.0-2.fc19
ocspd-1.9.0-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ocspd-1.9.0-2.fc18
ocspd-1.9.0-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ocspd-1.9.0-2.fc20
Package ocspd-1.9.0-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ocspd-1.9.0-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22828/ocspd-1.9.0-2.fc20 then log in and leave karma (feedback).
ocspd-1.9.0-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
ocspd-1.9.0-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
ocspd-1.9.0-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.