Are there any known common causes of “Cannot kill process: Success!” in error.log? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Come Celebrate our 10 Year Anniversary!Are there any issues migrating from RHEL to CentOS?Cannot kill httpd process even with -9Apache shuts down unintentionallyHttp request blocked on port 80Apache2.4 Service Will Not Start on Windows Server 2008Apache2 + Varnish 5 + phpmyadmin causes Segmentation fault (11) - ERR_EMPTY_RESPONSEI can't start Apache with module mod_jkYum cannot update - there are conflictsApache Wont Start with SSL (Mis?)Configured
Determine whether an integer is a palindrome
2018 MacBook Pro won't let me install macOS High Sierra 10.13 from USB installer
Is this Half dragon Quaggoth Balanced
latest version of QGIS fails to edit attribute table of GeoJSON file
Understanding piped command in Gnu/Linux
(Brexit) Why is there so little support for joining EFTA in the British parliament?
Google .dev domain strangely redirects to https
3D Masyu - A Die
Random body shuffle every night—can we still function?
Problem with display of presentation
Why can't fire hurt Daenerys but it did to Jon Snow in season 1?
malloc in main() or malloc in another function: allocating memory for a struct and its members
The Nth Gryphon Number
Is the time—manner—place ordering of adverbials an oversimplification?
Short story about astronauts fertilizing soil with their own bodies
Does the universe have a fixed centre of mass?
Weaponising the Grasp-at-a-Distance spell
Did John Wesley plagiarize Matthew Henry...?
Centre cell vertically in tabularx
Can gravitational waves pass through a black hole?
Can haste grant me and my beast master companion extra attacks?
Was the pager message from Nick Fury to Captain Marvel unnecessary?
Where and when has Thucydides been studied?
Centre cell contents vertically
Are there any known common causes of “Cannot kill process: Success!” in error.log?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Come Celebrate our 10 Year Anniversary!Are there any issues migrating from RHEL to CentOS?Cannot kill httpd process even with -9Apache shuts down unintentionallyHttp request blocked on port 80Apache2.4 Service Will Not Start on Windows Server 2008Apache2 + Varnish 5 + phpmyadmin causes Segmentation fault (11) - ERR_EMPTY_RESPONSEI can't start Apache with module mod_jkYum cannot update - there are conflictsApache Wont Start with SSL (Mis?)Configured
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
Operating system: CentOS Linux release 7.6.1810 (Core)
Error log: /var/log/httpd/error.log
Apache version: Apache/2.4.6
In attempting to debug a PHP cron task, I am seeing some segfaults in error.log around the times it is attempting to execute. Each segfault recording is preceded on the line above with the a "cannot kill process" error for a different process ID (for example):
Sun Apr 14 18:18:27 2019 (1893): Error Cannot kill process 1169: Success!
[Sun Apr 14 18:18:27.170950 2019] [core:notice] [pid 6755] AH00052: child pid 1893 exit signal Segmentation fault (11)
The process ID (and obviously, the time stamp) on the top line are different for each instance. It is never the same as the pid or child pid in the second line.
I haven't found any information on this error message. It is not an easy one to search for.
The basic process is that I have some PHP (7.1.27) cron tasks running in Drupal 8.6.12, and crontab uses wget on the Drupal site's cron URL to make it check if any are behind schedule, and runs any that are. There is a weekly task (which runs some very slow MySQL queries) that seems as if it's failing because httpd is stopping entirely partway through the task (I'm not sure if this is actually the case or not, but the evidence I have points to this), meaning Drupal therefore cannot record a success or a failure, and on the next crontab run it tries to run it again, believing it to not have run yet. I believe this is what these segfaults are telling me, but I can't make heads or tails of the "Success!" error message. I'm not sure what this error is even reporting to be able to debug further.
Edit: Additional info from httpd -l:
Compiled in modules:
core.c
mod_so.c
http_core.c
Info from httpd -V:
Server MPM: prefork
threaded: no
forked: yes (variable process count)
centos apache-2.4 centos7
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Operating system: CentOS Linux release 7.6.1810 (Core)
Error log: /var/log/httpd/error.log
Apache version: Apache/2.4.6
In attempting to debug a PHP cron task, I am seeing some segfaults in error.log around the times it is attempting to execute. Each segfault recording is preceded on the line above with the a "cannot kill process" error for a different process ID (for example):
Sun Apr 14 18:18:27 2019 (1893): Error Cannot kill process 1169: Success!
[Sun Apr 14 18:18:27.170950 2019] [core:notice] [pid 6755] AH00052: child pid 1893 exit signal Segmentation fault (11)
The process ID (and obviously, the time stamp) on the top line are different for each instance. It is never the same as the pid or child pid in the second line.
I haven't found any information on this error message. It is not an easy one to search for.
The basic process is that I have some PHP (7.1.27) cron tasks running in Drupal 8.6.12, and crontab uses wget on the Drupal site's cron URL to make it check if any are behind schedule, and runs any that are. There is a weekly task (which runs some very slow MySQL queries) that seems as if it's failing because httpd is stopping entirely partway through the task (I'm not sure if this is actually the case or not, but the evidence I have points to this), meaning Drupal therefore cannot record a success or a failure, and on the next crontab run it tries to run it again, believing it to not have run yet. I believe this is what these segfaults are telling me, but I can't make heads or tails of the "Success!" error message. I'm not sure what this error is even reporting to be able to debug further.
Edit: Additional info from httpd -l:
Compiled in modules:
core.c
mod_so.c
http_core.c
Info from httpd -V:
Server MPM: prefork
threaded: no
forked: yes (variable process count)
centos apache-2.4 centos7
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
1
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19
add a comment |
Operating system: CentOS Linux release 7.6.1810 (Core)
Error log: /var/log/httpd/error.log
Apache version: Apache/2.4.6
In attempting to debug a PHP cron task, I am seeing some segfaults in error.log around the times it is attempting to execute. Each segfault recording is preceded on the line above with the a "cannot kill process" error for a different process ID (for example):
Sun Apr 14 18:18:27 2019 (1893): Error Cannot kill process 1169: Success!
[Sun Apr 14 18:18:27.170950 2019] [core:notice] [pid 6755] AH00052: child pid 1893 exit signal Segmentation fault (11)
The process ID (and obviously, the time stamp) on the top line are different for each instance. It is never the same as the pid or child pid in the second line.
I haven't found any information on this error message. It is not an easy one to search for.
The basic process is that I have some PHP (7.1.27) cron tasks running in Drupal 8.6.12, and crontab uses wget on the Drupal site's cron URL to make it check if any are behind schedule, and runs any that are. There is a weekly task (which runs some very slow MySQL queries) that seems as if it's failing because httpd is stopping entirely partway through the task (I'm not sure if this is actually the case or not, but the evidence I have points to this), meaning Drupal therefore cannot record a success or a failure, and on the next crontab run it tries to run it again, believing it to not have run yet. I believe this is what these segfaults are telling me, but I can't make heads or tails of the "Success!" error message. I'm not sure what this error is even reporting to be able to debug further.
Edit: Additional info from httpd -l:
Compiled in modules:
core.c
mod_so.c
http_core.c
Info from httpd -V:
Server MPM: prefork
threaded: no
forked: yes (variable process count)
centos apache-2.4 centos7
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Operating system: CentOS Linux release 7.6.1810 (Core)
Error log: /var/log/httpd/error.log
Apache version: Apache/2.4.6
In attempting to debug a PHP cron task, I am seeing some segfaults in error.log around the times it is attempting to execute. Each segfault recording is preceded on the line above with the a "cannot kill process" error for a different process ID (for example):
Sun Apr 14 18:18:27 2019 (1893): Error Cannot kill process 1169: Success!
[Sun Apr 14 18:18:27.170950 2019] [core:notice] [pid 6755] AH00052: child pid 1893 exit signal Segmentation fault (11)
The process ID (and obviously, the time stamp) on the top line are different for each instance. It is never the same as the pid or child pid in the second line.
I haven't found any information on this error message. It is not an easy one to search for.
The basic process is that I have some PHP (7.1.27) cron tasks running in Drupal 8.6.12, and crontab uses wget on the Drupal site's cron URL to make it check if any are behind schedule, and runs any that are. There is a weekly task (which runs some very slow MySQL queries) that seems as if it's failing because httpd is stopping entirely partway through the task (I'm not sure if this is actually the case or not, but the evidence I have points to this), meaning Drupal therefore cannot record a success or a failure, and on the next crontab run it tries to run it again, believing it to not have run yet. I believe this is what these segfaults are telling me, but I can't make heads or tails of the "Success!" error message. I'm not sure what this error is even reporting to be able to debug further.
Edit: Additional info from httpd -l:
Compiled in modules:
core.c
mod_so.c
http_core.c
Info from httpd -V:
Server MPM: prefork
threaded: no
forked: yes (variable process count)
centos apache-2.4 centos7
centos apache-2.4 centos7
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Apr 16 at 13:07
s11111
asked Apr 15 at 18:03
s11111s11111
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 15 at 18:03
s11111s11111
1163
asked Apr 15 at 18:03
s11111s11111
1163
1163
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
s11111 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
1
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19
add a comment |
1
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
1
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19
1
1
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
1
1
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
s11111 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963166%2fare-there-any-known-common-causes-of-cannot-kill-process-success-in-error-lo%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
s11111 is a new contributor. Be nice, and check out our Code of Conduct.
s11111 is a new contributor. Be nice, and check out our Code of Conduct.
s11111 is a new contributor. Be nice, and check out our Code of Conduct.
s11111 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963166%2fare-there-any-known-common-causes-of-cannot-kill-process-success-in-error-lo%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Hmm. You might be running into this PHP bug, or a related bug. You can workaround it by using php-fpm and the event MPM. Of course you should be doing that anyway for the significantly improved performance.
– Michael Hampton♦
Apr 16 at 14:56
@MichaelHampton Thank you very much - I'll admit this is a little outside of my expertise. Are there any other implications I should be aware of or address in making these changes? I'm primarily a PHP developer with limited sysadmin experience.
– s11111
Apr 16 at 15:10
1
Nothing major. It's just reconfiguring Apache and PHP and there are plenty of tutorials on how to do that.
– Michael Hampton♦
Apr 16 at 15:11
Thank you! I will attempt it.
– s11111
Apr 16 at 15:19