Hi Luca,
Thanks for the details.
1. our server's ulimit values are:
]$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63714
ma
> Given where I AM what would you suggest would be the best course of action to
> get back to a working system please?
As was already suggested, run:
sudo netstat -tpln
to see what program occupies port 80. Also try:
ps -AFH
to see if other instances of Apache are already running. Compare the
Hi Eric
The info I'm getting from Phusion is that Standalone Passenger only uses
port 3000 by default or whatever else you stipulate at start time.
However they are helping me decipher why nginx 'appears' to be grabbing
port 80. Once I have an understanding of 'that bit' maybe I'll have a
b
On Tue, Apr 18, 2017 at 12:01 PM, Purvez wrote:
> Given where I AM what would you suggest would be the best course of action
> to get back to a working system please?
Decide which http server will listen on port 80? Whoever gets port 80
may have to proxy to the other server on an alt port.
--
Hi Marat
Many thanks for your input. Yes 14.04 was an upgrade from 13.10 ...BUT
I had tested it and it DID WORK!! I must admit that I didn't look at
the apache versions between 13.10 and 14.04 on ubuntu. (I really had no
'need' to...as everything worked)
Given where I AM what would you sug
Versions of Apache used by 14.04 and 16.04 are in fact very close: 2.4.7
and 2.4.18, I doubt their configurations are so much different (unless
14.04 was also an upgrade, since 13.10 used 2.2.x AFAIR). Breakage in
the way Apache is started (upstart vs systemd) is much more probable.
Reinstallat
Having spent considerable time chasing this problem around over the last
few weeks (and a sincere thank you to Daniel for his assistance) here is
some information that might save some time for somebody!
Environment:
Apache 2.4.25 compiled from source
PHP 7.1.3 compiled from source
mod_fcgid down
Trust me. it’s the safest way to know you are starting off clean and have
no remnants that didn’t upgrade properly, there were a number of
deprecations from old to new Apache and they do not upgrade nicely.
And it really does not take that long, it should take you (depending on how
many sites) tha
Hi Mitchell
Many thanks for your response. I'm coming to the same conclusion as
you. Best to cut my losses and rebuild Apache and PHPbut I HATE not
knowing what went wrong. So...I'm going to spend some time getting to
the bottom of the problem...whilst being pragmatic and building my
p
On Tue, Apr 18, 2017 at 10:35 AM, Rose, John B wrote:
> What are some troubleshooting methods that utilize this config to “helps to
> determine when the issue is php and when the issue is Apache.”
A high memory, high cpu, or crashed process can be determined to be
one or the other trivially if it
What are some troubleshooting methods that utilize this config to “helps to
determine when the issue is php and when the issue is Apache.”
Thanks
From: Daniel
Reply-To: "users@httpd.apache.org"
Date: Friday, April 7, 2017 at 9:18 AM
To: ""
Subject: Re: [users@httpd] What is preferred PHP inte
Hi Luca
Many thanks for your quick response. I think you have identified the
problem. I am running an ROR website with Phusion Passenger Standalone
to serve it via reverse proxy. Under 14.04 as far as I can tell
Passenger Standalone did not use any outside 'help'. However their
latest vers
My experience with upgrading from 14.04 to 16.04 is apache does not upgrade
well at all, had it happen on several servers already in the past.
I would suggest backup your entire etc/apache2 folder or rename it
/etc/apache_backup/
Then uninstall apache and purge it, uninstall PHP and purge it and
Hi!
2017-04-18 13:35 GMT+02:00 Purvez :
> Hi
>
> Newbie to the forum here so I hope I'm doing this right. If not please
> would someone guide me. Thx in advance.
>
> As the subject line says Apache2 is not working at all / satisfactorily
> since the Ubuntu upgrade. The details follow:
>
>
Hi
Newbie to the forum here so I hope I'm doing this right. If not please
would someone guide me. Thx in advance.
As the subject line says Apache2 is not working at all / satisfactorily
since the Ubuntu upgrade. The details follow:
===
Here is my full post on ask
Hi Luca,
Is it possible to pinpoint what is the wrong in my setting. I am still
unable to display the custom error message.
*The actual message from weblogic 12c in browser*
Error 500--Internal Server Error
>From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
T
Hi,
Some suggestions:
1) check your RHEL ulimits applied to httpd, the error message "Resource
temporarily unavailable: setuid: unable to change to uid" could be related
to maximum number of processes (allowed by the OS) reached. This should
allow you to spawn more httpd processes.
2) Have you c
17 matches
Mail list logo
