[axxs-sysadmin] borg?

[Sonia Hamilton]

On Wed, 2008-02-06 at 17:43 +1100, musicman wrote:
> Hola All,
> 
> I just restarted Apache on borg because it seemed to be down.
> 
> I got two warnings:
> 
> Forcing reload of web server (apache2)...[Wed Feb 06 06:41:43 2008]
> [warn] VirtualHost 66.135.32.15:443 overlaps with VirtualHost
> 66.135.32.15:443, the first has precedence, perhaps you need a
> NameVirtualHost directive
> httpd (no pid file) not running
> [Wed Feb 06 06:41:44 2008] [warn] VirtualHost 66.135.32.15:443
> overlaps with VirtualHost 66.135.32.15:443, the first has precedence,
> perhaps you need a NameVirtualHost directive
> 

I started to look thru the Apache configs, but gave up as my connection
is so slow (coming from Mexico - holidaying here).

Do this to find all the files that refer to VirtualHosts, to resolve
problem:

cd /etc/httpd
find . -type f -exec grep -iH virtualhost '{}' ';' | less

> Also, dmesg has some funny responses at the bottom - stuff I've never
> seen before?
> TCP: Treason uncloaked! Peer 208.78.63.99:2439/80 shrinks window
> 2376802631:2376804091. Repaired.
> TCP: Treason uncloaked! Peer 208.78.63.99:2439/80 shrinks window
> 2376802631:2376804091. Repaired.
> TCP: Treason uncloaked! Peer 208.78.63.99:2833/80 shrinks window
> 2194267477:2194268207. Repaired.
> TCP: Treason uncloaked! Peer 201.62.18.180:27963/80 shrinks window
> 1533122533:1533122534. Repaired.
> TCP: Treason uncloaked! Peer 80.126.38.192:50458/80 shrinks window
> 3047759972:3047761597. Repaired.
> TCP: Treason uncloaked! Peer 80.126.38.192:50458/80 shrinks window
> 3047759972:3047761597. Repaired.
> TCP: Treason uncloaked! Peer 80.126.38.192:50458/80 shrinks window
> 3047759972:3047761597. Repaired.
> TCP: Treason uncloaked! Peer 122.129.8.64:2736/80 shrinks window
> 1041388277:1041388318. Repaired.
> TCP: Treason uncloaked! Peer 122.129.8.64:2752/80 shrinks window
> 1105649468:1105653681. Repaired.
> TCP: Treason uncloaked! Peer 202.174.143.174:47114/80 shrinks window
> 1732416064:1732416065. Repaired.

Don't know - google? 

I did an iptables -L - notice you're using a minimal firewall (rate
limiting only) - maybe configure iptables using shorewall?

-- 
Sonia Hamilton
blog: http://SoniaHamilton.wordpress.com