Gene Heskett wrote: > Bob Proulx wrote: > > $ grep SSLCipherSuite /etc/apache2/mods-available/ssl.conf > > SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5 > > This is not valid for a 2.22 install
What is the error you are seeing? That looks to be okay to me.
rwp@havoc:~$ cat /etc/debian_version
7.8
rwp@havoc:~$ dpkg -l apache2
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii apache2 2.2.22-13+de i386 Apache HTTP Server metapackage
rwp@havoc:~$ grep SSLCipherSuite /etc/apache2/mods-available/ssl.conf
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5
# to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
Note however that I always override it in the site config file. But
the point is that I think you must have some other problem in your
configuration.
> However on the restart, I logged this in /var/log/apache2/error.log:
>
> [Sat Mar 21 18:08:02 2015] [info] removed PID file /var/run/apache2.pid
> (pid=2954)
> [Sat Mar 21 18:08:02 2015] [notice] caught SIGTERM, shutting down
> [Sat Mar 21 18:08:03 2015] [notice] Apache/2.2.22 (Debian) configured --
> resuming normal operations
> [Sat Mar 21 18:08:03 2015] [info] Server built: Dec 27 2014 21:24:43
> [Sat Mar 21 18:08:03 2015] [debug] worker.c(1757): AcceptMutex: sysvsem
> (default: sysvsem)
> [Sat Mar 21 18:08:03 2015] [error] (2)No such file or directory: Couldn't
> bind unix domain socket /var/log/httpd/${APACHE_RUN_DIR}/cgisock.4944
Using /var/log/httpd on a Debian system? The use of "httpd" is more
typical of a Red Hat system. Did you make an edit that followed a Red
Hat guide on your Debian system and cross the streams?
Are you running FastCGI with your Apache instead of the internal
Apache handler? (Which is fine.) Check the configuration for it.
Something might be snafu there setting the communication socket.
Also a cgi communication socket would normally go in /var/run not
/var/log. So something is snafu there. For example using
/var/run/fcgiwrap.socket is typical with fcgiwrap and spawn-fcgi.
When I restart my Debian apache2 I see this:
# service apache2 restart
[Sat Mar 21 17:10:16 2015] [notice] caught SIGTERM, shutting down
[Sat Mar 21 17:10:17 2015] [notice] Apache/2.2.22 (Debian) DAV/2 SVN/1.6.17
configured -- resuming normal operations
I hate to ask but it is also important to know if you are using
systemd or not since it affects everything.
> No clue how to fix this one, APACHE_RUN_DIR is not set in the environment.
> Broken init.d script perhaps??
It is in the /etc/apache2/envvars file.
$ grep APACHE_RUN_DIR /etc/apache2/envvars
export APACHE_RUN_DIR=/var/run/apache2$SUFFIX
> [Sat Mar 21 18:08:04 2015] [crit] cgid daemon failed to initialize
>
> But this seems to be a never mind as it doesn't seem to effect performance
> in any case. How important is it?
I have no idea.
Bob
signature.asc
Description: Digital signature
