Hello all,

I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...

Below is my configuration (at least the part that gives me headaches..)

[Onderhoud Diversen]
Theme = default

Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2

The goal of this part of the configuration is a way to notify and log maintenance on not specified equipment.
I expect a message-tag with: DIVOH: 280109-0001, where 280109 stands for 28th of January, 2009, the 0001 is the message number of that day.
Now when I enter something in it, submit the message it will display DIV-OH: 280109-0001 as I expect, but...
When I start with a new entry I would expect DIVOH: 280109-0002 as it is the second message.. Well, simply put.. I don't get DIVOH: 280109-0002 but instead I get DIVOH: 280109-0001 again.Below the part that does work correctly:

The following part of my configuration does work..

[Onderhoud Windows]
Theme = default

Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Categorie = Algemeen, Hardware, Software, Netwerk, Telefonie, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Opgelost
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= WSOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime

When I copy this one, adjust it to be the same as the first one, but then without the extra things it doesn't work, and with them, well.. it still won't.. :(
I am at a loss here where the mistake is, can someone shed some light on this? I would appreciate that very much.

Best regards,

Guido

 

Like many educational institutions we get "educational certificates" that are chain certificates..

With apache the full certificate chain is working as expected..

For elog I copied the appropriate files to server.crt and server.key

Netscape 3 is happy with that setup, Internet Explorer and Opera are mentioning the open certificate chain.

When I tried to copy the file known as SSLCACertificateFile in Apache to chain.crt elogd does not longer work and 

openssl s_client -showcerts -connect <myserver>:<elogd_port>

only shows: 

CONNECTED(00000003)
25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:

What do I do wrong?

Gerhard Schneider

> Like many educational institutions we get "educational certificates" that are chain certificates..
>  
> only shows: 
> 
> CONNECTED(00000003)
> 25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:
> 
> What do I do wrong?
> 

After reading the OpenSSL Documentation:

The certificates must be in PEM format and must be sorted starting with the subject's certificate (actual client or
server certificate), followed by intermediate CA certificates if applicable, and ending at the highest level (root) CA.

The chain.crt has to be of the following format:

HOST CERTIFICATE
INTERMEDIATE CERTIFICATE
ROOT CERTIFICATE

Then it is working w/o problems

GS

How did you create the certificate?
Are you running eLog on a server with more than one host name (CNAME entries) and are you pointing to your eLog
via one of that aliases?

Certificates that work with an Apache 1 Web server do work with eLog, too.

GS

> 
> The certificate that is on there right now is the one that gets created when you install elogs.  I have tried 
> creating one with a windows server 2008 box with the CA role installed.  The certificate is created without issue 
> and I can install it on the server but when I try to restart the elog service it wont start until I put the 
> original server.crt and server.key file back into the ssl directory.  
> 

I don't know anything about Windows server CA, but eLog is very strict in the syntax of the CERTs.
I had to learn it the hard way when installing a chain CERT.

For server.crt and server.key it MUST NOT be a chain cert. Therefor you have to use chain.crt

Are the generated CERTs ASCII (with only one -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- in
server.crt 
and -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- in server.key)?

So the eLog generated keys should look like..

GS

Let me start by saying that I really like ELOG-- it's a nice tool.

I'm trying out version 2.3.3. The problem that I'm having is with
attachments disappearing when I do the following:

1. create a new entry that contains one or more attachments.
2. verify that the new entry from step 1 saved correctly.
3. reply to the entry from step 1.
4. return to the entry from step 1 only to find the attachments gone.

The attachement files are still in the logbook directory, it's just that
they are no longer attached to the entry.

FWIW, I've attached the elog.config that I'm using...

Thanks,

Greg

I'm interested using elog for a lab notebook.  Once entries have been
entered they cannot be changed/edited.
Is it possible for elog to be setup to support something like this?  A write
only mode?

Does this truly disable the edit command or just hide it?

> > I'm interested using elog for a lab notebook.  Once entries have been
> > entered they cannot be changed/edited.
> > Is it possible for elog to be setup to support something like this?  A write
> > only mode?
> 
> What you need is an entry in the elogd.cfg file:
> 
> Manu commands = Back, New, Reply, Find, Config, Logout, Help
> 
> As you see, the "Edit" and "Delete" commands are missing here and therefore 
> do not get displayed. So you can enter a message with "New", but you cannot 
> change it afterwards.