httpd dead but pid file exists
-
Also, consider just moving to a maintained server. RHEL 6 is one thing today, a stretch, but one thing. RHEL 5 constitutes and abandoned server of no value. Why bother with trying to fix a workload deemed "not important enough to run?"
-
@scottalanmiller said in httpd dead but pid file exists:
Also, consider just moving to a maintained server. RHEL 6 is one thing today, a stretch, but one thing. RHEL 5 constitutes and abandoned server of no value. Why bother with trying to fix a workload deemed "not important enough to run?"
We've been told we are phasing it out but if history is any indicator that could mean years. They like to tell us what we want to hear and then not doing anything about it.
-
No one has asked yet (and I'm assuming this) but why haven't you restored to a known working condition?
-
@wirestyle22 said in httpd dead but pid file exists:
@scottalanmiller said in httpd dead but pid file exists:
Also, consider just moving to a maintained server. RHEL 6 is one thing today, a stretch, but one thing. RHEL 5 constitutes and abandoned server of no value. Why bother with trying to fix a workload deemed "not important enough to run?"
We've been told we are phasing it out but if history is any indicator that could mean years. They like to tell us what we want to hear and then not doing anything about it.
Well then, just tell them it phased itself out. Problem solved since they were planning to do this anyway. If they push back, tell them that they need to move to something supportable if phasing out wasn't the actual plan.
You need to tell them what you want to hear.
-
@DustinB3403 said in httpd dead but pid file exists:
No one has asked yet (and I'm assuming this) but why haven't you restored to a known working condition?
I need to understand why this happened in order to prevent it from happening in the future. Nothing has turned up any answers.
-
@wirestyle22 said in httpd dead but pid file exists:
@DustinB3403 said in httpd dead but pid file exists:
No one has asked yet (and I'm assuming this) but why haven't you restored to a known working condition?
I need to understand why this happened in order to prevent it from happening in the future. Nothing has turned up any answers.
Is this something that you can restore to separate hardware/hypervisor just so the system is operable while you work on this down system?
It seems like there is a need to have this system function, but not with any real priority. So the simple approach might be to just stand up a working version and compare them side by side.
-
@wirestyle22 said in httpd dead but pid file exists:
@DustinB3403 said in httpd dead but pid file exists:
No one has asked yet (and I'm assuming this) but why haven't you restored to a known working condition?
I need to understand why this happened in order to prevent it from happening in the future. Nothing has turned up any answers.
It's always nice to know root cause, but sometimes it is very difficult to replicate an issue like this.
-
@IRJ said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
@DustinB3403 said in httpd dead but pid file exists:
No one has asked yet (and I'm assuming this) but why haven't you restored to a known working condition?
I need to understand why this happened in order to prevent it from happening in the future. Nothing has turned up any answers.
It's always nice to know root cause, but sometimes it is very difficult to replicate an issue like this.
And not worth your time. On Wall St. we had things like this happen from time to time and the question was always... what's the value of getting the system back online vs. the cost of downtime and resources to try to track down something that might never be an issue again?
Almost never did root cause analysis make the cut when actual business value was applied. It sounds great, it sounds like something IT should be doing. But when we put on our real IT hats and do our proper cost analysis, it's rarely a good idea. And to do it on a RHEL 5 system slated for decommission? Essentially zero chance that any investigation could be justified.
-
is there a way I can ignore
/usr/lib/php/modules/oci8.sojust to verify apache will start if this file is not in play? I actually think a file level restore of this file will fix it but I want to test that before I offer it as a solution -
@wirestyle22 said in httpd dead but pid file exists:
is there a way I can ignore
/usr/lib/php/modules/oci8.sojust to verify apache will start if this file is not in play? I actually think a file level restore of this file will fix it but I want to test that before I offer it as a solutionYou'd "ignore" it by removing any PHP app that tries to use it.
-
@wirestyle22 said in httpd dead but pid file exists:
is there a way I can ignore
/usr/lib/php/modules/oci8.sojust to verify apache will start if this file is not in play? I actually think a file level restore of this file will fix it but I want to test that before I offer it as a solutionAre you unable to take a backup of this system?
Seems like an odd thing to try and do when solutions exist for this very case of "just in case"
-
@DustinB3403 said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
is there a way I can ignore
/usr/lib/php/modules/oci8.sojust to verify apache will start if this file is not in play? I actually think a file level restore of this file will fix it but I want to test that before I offer it as a solutionAre you unable to take a backup of this system?
Seems like an odd thing to try and do when solutions exist for this very case of "just in case"
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
-
@wirestyle22 said in httpd dead but pid file exists:
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
If they don't get back to you, just ask "do you still need this system, I was told it was in the process of being decommed, seems like that's been accomplished." And if they take weeks, not your problem.
Why are you even working on their system if they manage it?
-
@wirestyle22 said in httpd dead but pid file exists:
@DustinB3403 said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
is there a way I can ignore
/usr/lib/php/modules/oci8.sojust to verify apache will start if this file is not in play? I actually think a file level restore of this file will fix it but I want to test that before I offer it as a solutionAre you unable to take a backup of this system?
Seems like an odd thing to try and do when solutions exist for this very case of "just in case"
I don't manage the backups, they are managed in France.
The hell?
@wirestyle22 said in httpd dead but pid file exists:
So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
Okay. . . well then I guess the system really doesn't matter if your recovery team says it'll take a week to just respond to a request.
-
@DustinB3403 said in httpd dead but pid file exists:
Okay. . . well then I guess the system really doesn't matter if your recovery team says it'll take a week to just respond to a request.
For real, this seems like THE answer. Is there just no other work to be done? Tell the business "backup team can't restore for now" and leave it. If "no restores" is the system design, sounds like they already decommissioned it and didn't inform you.
-
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
If they don't get back to you, just ask "do you still need this system, I was told it was in the process of being decommed, seems like that's been accomplished." And if they take weeks, not your problem.
Why are you even working on their system if they manage it?
They manage the backups, not the application server.
-
@wirestyle22 said in httpd dead but pid file exists:
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
If they don't get back to you, just ask "do you still need this system, I was told it was in the process of being decommed, seems like that's been accomplished." And if they take weeks, not your problem.
Why are you even working on their system if they manage it?
They manage the backups, not the application server.
Ah, that makes slightly more sense. But sounds like they have placed a priority on this differently than you. If they are allowed to take that long to respond, I think that that is telling you a lot about what the expectation of you working on this is... zero.
-
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
If they don't get back to you, just ask "do you still need this system, I was told it was in the process of being decommed, seems like that's been accomplished." And if they take weeks, not your problem.
Why are you even working on their system if they manage it?
They manage the backups, not the application server.
Ah, that makes slightly more sense. But sounds like they have placed a priority on this differently than you. If they are allowed to take that long to respond, I think that that is telling you a lot about what the expectation of you working on this is... zero.
I'm going to be working on this every day until it's resolved, so it doesn't matter either way. I think this is likely due to a corrupt file, but I don't know how to ignore it to test apache in a realistic way.
-
@wirestyle22 said in httpd dead but pid file exists:
I'm going to be working on this every day until it's resolved,
So tell your recovery team to restore this system as at a separate instance and leave the dead one how it is so you can poke at it.
And just wait a week until they get back to you.
-
@wirestyle22 said in httpd dead but pid file exists:
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
@scottalanmiller said in httpd dead but pid file exists:
@wirestyle22 said in httpd dead but pid file exists:
I don't manage the backups, they are managed in France. So far they have gotten back to me within a week. I don't want to wait that long to have them just delay what I want to do anyway.
If they don't get back to you, just ask "do you still need this system, I was told it was in the process of being decommed, seems like that's been accomplished." And if they take weeks, not your problem.
Why are you even working on their system if they manage it?
They manage the backups, not the application server.
Ah, that makes slightly more sense. But sounds like they have placed a priority on this differently than you. If they are allowed to take that long to respond, I think that that is telling you a lot about what the expectation of you working on this is... zero.
I'm going to be working on this every day until it's resolved, so it doesn't matter either way. I think this is likely due to a corrupt file, but I don't know how to ignore it to test apache in a realistic way.
You can't just ignore corrupt files, you have to remove any functionality that needs that file.
