Attributes = Author, Category, Notification list
Email all = $Notification list

Theme = default
Comment = Logs des modification de scripts des 3 domaines
Attributes = Acteur, Action, Type, Nom du Scripts, Language, Domaine, Categorie, Commentaires,Notification
Options Action = Ajout, Modification, Suppression, Réseau, Autre, Hotfix
Options Type = Ouverture de session,Autre, deploiement
Options Language = VBS, AU3, Kix, Batch, Ksh, Perl
Options Domaine = VaubanHumanis, Humanis, Vauban
Extendable Options = Catégorie, Type, Action
Required Attributes = Acteur, Type, Lieu
Page Title = Modification Scripts - $subject
Reverse sort = 1
Quick filter = Date, Type
Suppress Email to users = 1
# Email all = someadminsuser@maildomain.com
Email all = $Notification
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}

Hi,

I am an apache ignoramus who has been trying to follow these instructions on a Debian 3.1 box.  I got hung up for
the following reason.  I had to explicitly enable some apache features, which was a simple matter of making the
following symlinks in /etc/apache2/mods-enabled: 

	proxy.conf -> ../mods-available/proxy.conf
	proxy.load -> ../mods-available/proxy.load
	rewrite.load -> ../mods-available/rewrite.load
	headers.load -> ../mods-available/headers.load
	ssl.conf -> ../mods-available/ssl.conf
	ssl.load -> ../mods-available/ssl.load

Easy enough.  The default proxy.conf has sensible-looking warnings about not running your server as an open proxy.
 However, I wasn't able to tweak it to encrypted port forwarding from :443 to :8079.

What I've done that works is to add a local proxy section to the /etc/apache2/conf.d/elogredirect.conf by Damon
Nettles:

	<VirtualHost *:443>
		### ... everything else

		<Proxy *>
			Allow from all
		</Proxy>
	</VirtualHost>

I think, since this is in a subsection, that it only affects that virtual host.  But it'd be nice if someone who
actually understands this language would reassure me that I'm not setting myself up for some security hole.  At
any rate it took me long enough to figure this out that I thought I'd post a note in public, and this seems like
the forum to do so.

Thanks.

Rob

• A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
  
• A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
  
• Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.