On 04/25/2016 07:47 PM, Brahmina Burgess wrote:
Did your upgrade move you from apache 2.2 to apache 2.4?
Unless you are running Debian Sid, or perhaps some Debian-derived distro
with which I am not familiar, a simple apt-get upgrade should never
change the version of your Apache beyond
On 04/25/2016 06:01 PM, tom wrote:
I figured the problem is in the included file, but I changed nothing
between working and non-working states...
The network that you are on changed, so you would have to change the IP
addresses that Apache can listen on as the IP address of the computer
will
thanks, sounds promising. I'll check tomorrow and let you know how it turns
out...
On Mon, Apr 25, 2016 at 6:47 PM, Brahmina Burgess <
brahmina.burg...@bc.libraries.coop> wrote:
> Hi Tom,
>
> Did your upgrade move you from apache 2.2 to apache 2.4? Apache 2.4
> requires some changes of
Hi Tom,
Did your upgrade move you from apache 2.2 to apache 2.4? Apache 2.4
requires some changes of authorization configs. I ran into quite a bit
of trouble with this upgrade as a result of an innocent 'apt-get
update/upgrade. See apache's docs on the matter here:
Hey Jason,
The move didn't involve much. At home, everything, including apache,
started fine and I could see the default page. I unplugged the computer,
moved it to the library, plugged it back in, and apache wouldn't start.
I figured the problem is in the included file, but I changed nothing
On 04/25/2016 12:30 PM, tom wrote:
I had evergreen running on this very computer. I moved it to a different
location, and now apache won't start.
Hi, Tom.
Your issue probably arises from changes in the environment caused by the
above mentioned move.
It would be useful if you could share
Hi guys,
Sounds like the conference was great!
I have a mystery. I had evergreen running on this very computer. I moved
it to a different location, and now apache won't start.
The cause is apparently a syntax error on line 220 in apache2.conf. The
line in question is the one that reads
