After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.

Cannot open file /usr/local/elogdata/logbooks/djeks/password!

oops?

> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
> 
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81
> 
> This command runs on the server, but when I access https://172.16.24.108/ i 
> get a page cannot be displayed, ive also put the URL = 
> https://172.16.24.108 entry in the elogd.cfg file
> 
> HELP!!!!!!!

Can you access your server locally under http://172.16.24.108:81 ??? If not, 
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag 
when starting elogd. If you can access it, and cannot access it under 
https://, then something must be wrong with your stunnel configuration. Maybe 
you run already a secure server under port 443? User "netstat -a" to check 
that.

Ooops, I destroyed the original post, now how can we fix this :)

Im not running anything on port 443, one thing I did notice is that when 
stunnel is run and setup, I can run a netstat and nothing is bound to those 
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the 
command initially ?


CONFUSED ????

> > I was wondering if you can help me understand the concept and if i am 
doing 
> > something wrong with securing Elog via SSL
> > 
> > Basically im running elog on a redhat 8 box with stunnel already 
installed 
> > as part of OpenSSL, on the server i ran the command specified in the 
> > instructions
> > 
> > stunnel -d 443 -r 172.16.24.108:81
> > 
> > This command runs on the server, but when I access https://172.16.24.108/ 
i 
> > get a page cannot be displayed, ive also put the URL = 
> > https://172.16.24.108 entry in the elogd.cfg file
> > 
> > HELP!!!!!!!
> 
> Can you access your server locally under http://172.16.24.108:81 ??? If 
not, 
> then you maybe specified the wrong port, so check elogd.cfg and the "-p" 
flag 
> when starting elogd. If you can access it, and cannot access it under 
> https://, then something must be wrong with your stunnel configuration. 
Maybe 
> you run already a secure server under port 443? User "netstat -a" to check 
> that.

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

> 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.

This is a known problem and has been fixed in version 2.3.4, which has been 
released today. To prove that it's working, I attached the current 
elogd.cfg from this forum.

Is there a way to change the title entry for individual log books, and 
forms ive completely rebranded our system but ut stil says ELOG ENTRIES on 
the summary screen

> Is there a way to change the title entry for individual log books, and 
> forms ive completely rebranded our system but ut stil says ELOG ENTRIES on 
> the summary screen

I changed the default title recently to "ELOG - <logbook>" where <logbook> 
is the name of the current logbook. For the individual messages, the 
title "ELOG" can be changed with the elogd.cfg option "Page title". This 
title can even contain attributes from the logook entry like:

Page title = ELOG - $subject

where $subject gets replaced by the subject of the logbook entry.