Hi all,

On BlueOnyx we have the problem that the "Web Server Alias" settings
sometimes get lost from the Apache VirtualHost containers. The aliases
are still present in CODB, but Apache will no longer have them applied.

Of course this creates all kinds of problems and we want to get to the
bottom of what causes it, so that we can fix it for good.

So far the bug hunt has not uncovered the source of the problem. But to
help both you and us to get rid of this for good I published an updated
base-vsite for 5207R, 5208R and 5209R to the YUM repositories.

What does it do?

It extends "Active Monitor" with a component called "Web Server Aliases"
and this component is active by default.

Every time "Active Monitor" ("swatch") runs, this new component walks
through all Vsites and compares if the "Web Server Aliases" defined in
CODB are still present in the /etc/httpd/conf/vhosts/siteX config file
of the respective Vsite.

If it finds that the aliases are gone, it will re-apply them
automatically. Additionally this component will send a separate "Active
Monitor" email titled:

"<severname>  Active Monitor: Webserver Alias changes"

This email will contain a text like this:

---------------------------------------------------------------------
Active Monitor has detected a Webserver Alias problem related to the
following Vsites:

   * www.domain.com - Webserver Aliases: domain.com mail.domain.com
   * www.domain.net - Webserver Aliases: domain.net blog.domain.net
---------------------------------------------------------------------

It will list all Vsites that had missing Aliases that have been
re-applied automatically.

Furthermore the email will contain the contends of /var/log/messages
from the last 30 minutes as a text-attachment.

The very first time around that you get this email from a server might
not be that useful for you or for us. Because the CCE-transaction that
caused the issue happened too long ago to show up here. Like when you
just installed this update and the first Swatch-Run after the update
fixed an already pre-existing problem.

However: The next time you get this email out of the blue, please be so
kind and forward it to mstau...@blueonyx.it so that I can check your
attached logfile for suspicious transactions that might have caused the
loss of the "Web Server Aliases" in first place.


-- 
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx

Reply via email to