Re: Need help with debugging Apache on Debian 10.2

2020-01-17 Thread Angela Korra'ti
The PHP issues were primarily involved with Wordpress plugins. I had to go 
through and find several that were not compatible with PHP 7. I _think_ I found 
and fixed all of those, but it’s certainly possible that the issue might be 
caused by a bad plugin.

But I don’t know for sure. I’ve tried digging through Apache’s error.log and 
have not found any more obvious error messages to point me at things that need 
fixing.

I’ve tried uninstalling and reinstalling PHP, on the theory that I may have 
confused it by making the jump not only through multiple versions of Debian, 
but also multiple versions of PHP. And yes, I have the PHP mod active in 
Apache. 

Re: getting a core dump… that’s the part I need help with. I did get the 
debugger installed but I am not experienced with how to use it in a way that’d 
let me actually get useful data. 

The big blocking problem would seem to be that I don’t actually know what’s 
causing the problem, so I can’t trigger it on purpose. So it would seem that 
I’d need to run Apache with the debugger somehow in the hope that I’d actually 
catch the problem when it happens? But I don’t know how to do that either.

> On Jan 17, 2020, at 9:12 PM,   wrote:
> 
> I'd look first into that PHP part (I'm assuming you're running
> mod_php, so it's in the Apache binary, and a crash in PHP would
> crash the server, too).
> 
> Which kind of problems did you have with PHP?
> 
> Any possibility of getting a core dump you can look into with
> the debugger?
> 
> (Sorry for not looking at your web site -- bad connectivity
> at the moment),
> 
> Cheers
> -- tomás



Re: Need help with debugging Apache on Debian 10.2

2020-01-17 Thread tomas
On Fri, Jan 17, 2020 at 08:38:18PM -0800, Angela Korra'ti wrote:
> Yes we did, we did the upgrade in two distinct stages.
> We did run into roadblocks as we went, but those were
> mostly around PHP incompatibilities that we had to
> address to bring our sites back up.

I'd look first into that PHP part (I'm assuming you're running
mod_php, so it's in the Apache binary, and a crash in PHP would
crash the server, too).

Which kind of problems did you have with PHP?

Any possibility of getting a core dump you can look into with
the debugger?

(Sorry for not looking at your web site -- bad connectivity
at the moment),

Cheers
-- tomás


signature.asc
Description: Digital signature


Re: Need help with debugging Apache on Debian 10.2

2020-01-17 Thread Angela Korra'ti
P.S. Confirmed that systemctl reload apache2.service throws no errors.

> On Jan 17, 2020, at 8:38 PM, Angela Korra'ti  
> wrote:
> 
> Yes we did, we did the upgrade in two distinct stages. We did run into 
> roadblocks as we went, but those were mostly around PHP incompatibilities 
> that we had to address to bring our sites back up.
> 
> I’m _pretty_ sure we don’t have any config incompatibilities in Apache… 
> because yeah, Apache does in fact run. But I’ll doublecheck if the reload 
> command you’re asking about throws any actual errors.
> 
> And perhaps a config inspection of our Apache install is called for. We’ve 
> got not only the main config file, but several supplementary ones for the 
> various domains we host as well.
> 
>> On Jan 17, 2020, at 4:43 PM, Dan Ritter  wrote:
>> 
>> Did you upgrade to 9 in between? 
>> 
>> 8 had apache 2.2, and a bunch of config things changed from 2.2
>> to 2.4.  That usually shows up in apache failing to start,
>> though.
>> 
>> Does 
>> 
>> systemctl reload apache2.service
>> 
>> cause an error?
>> 
>> Worst case: if things are massively unstable, you might copy all the
>> data off elsewhere, re-install Debian 10 from scratch, and then bring
>> the data back in.
>> 
>> -dsr-
>> 
>> 
>> -- 
>> https://randomstring.org/~dsr/eula.html is hereby incorporated by reference.
>>   there is no justice, there is just us.
> 



Re: Need help with debugging Apache on Debian 10.2

2020-01-17 Thread Angela Korra'ti
Yes we did, we did the upgrade in two distinct stages. We did run into 
roadblocks as we went, but those were mostly around PHP incompatibilities that 
we had to address to bring our sites back up.

I’m _pretty_ sure we don’t have any config incompatibilities in Apache… because 
yeah, Apache does in fact run. But I’ll doublecheck if the reload command 
you’re asking about throws any actual errors.

And perhaps a config inspection of our Apache install is called for. We’ve got 
not only the main config file, but several supplementary ones for the various 
domains we host as well.

> On Jan 17, 2020, at 4:43 PM, Dan Ritter  wrote:
> 
> Did you upgrade to 9 in between? 
> 
> 8 had apache 2.2, and a bunch of config things changed from 2.2
> to 2.4.  That usually shows up in apache failing to start,
> though.
> 
> Does 
> 
> systemctl reload apache2.service
> 
> cause an error?
> 
> Worst case: if things are massively unstable, you might copy all the
> data off elsewhere, re-install Debian 10 from scratch, and then bring
> the data back in.
> 
> -dsr-
> 
> 
> -- 
> https://randomstring.org/~dsr/eula.html is hereby incorporated by reference.
>there is no justice, there is just us.



Re: Need help with debugging Apache on Debian 10.2

2020-01-17 Thread Dan Ritter
Angela Korra???ti wrote: 
> However, as of when we updated to Debian 10.2, we started having recurring 
> issues with Apache throwing segmentation faults that resulted in all 
> PHP-based sites (notably, the Wordpress ones) throwing 503 errors from 
> varnish.
> 
> https://angelahighland.info/2020/01/12/need-help-with-debian-web-server-debugging/
> 
> To what I wrote in that post, I can add that we???ve also kept the server up 
> to date with security and other updates, and it???s been rebooted a couple of 
> times since the big upgrade to Debian 10. (We were previously on version 8.)

Did you upgrade to 9 in between? 

8 had apache 2.2, and a bunch of config things changed from 2.2
to 2.4.  That usually shows up in apache failing to start,
though.

Does 

systemctl reload apache2.service

cause an error?

Worst case: if things are massively unstable, you might copy all the
data off elsewhere, re-install Debian 10 from scratch, and then bring
the data back in.

-dsr-


-- 
https://randomstring.org/~dsr/eula.html is hereby incorporated by reference.
there is no justice, there is just us.



Need help with debugging Apache on Debian 10.2

2020-01-17 Thread Angela Korra’ti
Hi Debian users list,

My name is Angela and I run Debian 10.2 on my home web server. On that server, 
my wife and I are hosting several Wordpress sites as well as a small number of 
non-Wordpress ones.

However, as of when we updated to Debian 10.2, we started having recurring 
issues with Apache throwing segmentation faults that resulted in all PHP-based 
sites (notably, the Wordpress ones) throwing 503 errors from varnish.

And I am at my wit’s end as to how to fix this problem, because I do not have 
enough debugging experience with a Linux environment to know how to proceed.

I have written up the problem in detail here:

https://angelahighland.info/2020/01/12/need-help-with-debian-web-server-debugging/

That post (which is external to my home web server, since my home web server is 
unstable) includes:

* Behavior observed when the seg fault occurs
* What I’ve done to try to fix the problem so far
* Details on what we have installed on the system at this time

To what I wrote in that post, I can add that we’ve also kept the server up to 
date with security and other updates, and it’s been rebooted a couple of times 
since the big upgrade to Debian 10. (We were previously on version 8.)

Can anyone advise on best steps to get enough information to diagnose the 
problem? As I said in my post, I do have gdb and the Apache debug symbols 
package installed, but I don’t have experience with them so I don’t know how to 
effectively _use_ them.

Many thanks in advance to anyone who can assist!

Angela

Sent from my iPad