Re: Problems with 2.3.2, posted by Stefan Ritt on Fri Mar 14 10:30:25 2003
|
> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> > port bindings, basically im running elog bound to port 81 and when i
> > install the new RPM it refuses to bind to this port, i tried port 8080
and
> > that worked fine
The bug has been fixed in V 2.3.3 which has been released today. |
|
Re: Elog 2.3.3, problems of 2.3.2 solved, posted by djek on Thu Mar 20 21:07:09 2003
|
> > 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!
>
> If you installed from the RPM, elogd runs under the user "elog". If you have
> installed a previous version under a different user, it might be that elogd
> does not have read or write access to it. A
>
> "chown -R elog.elog /usr/local/elogdata"
>
> might help.
>
It did, a lot, guess I missed that one in the changelog.
Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked
As a test I changed subdir to it's relative path
restarted
It kept working
mmmm, I wonder where that twighlight tune comes from ... |
|
Re: Elog 2.3.3, problems of 2.3.2 only partly solved, posted by Stefan Ritt on Thu Mar 20 21:07:09 2003
|
> 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!
If you installed from the RPM, elogd runs under the user "elog". If you have
installed a previous version under a different user, it might be that elogd
does not have read or write access to it. A
"chown -R elog.elog /usr/local/elogdata"
might help.
- Stefan |
|
Re: Elog and SSL, posted by Stefan Ritt on Fri Mar 21 16:24:05 2003
|
> 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. |
|
Re: Re: Elog and SSL, posted by Recai Oktas on Fri Mar 21 16:52:12 2003
|
Ooops, I destroyed the original post, now how can we fix this :) |
|
Re: Elog and SSL, posted by nick on Mon Mar 31 12:44:33 2003
|
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. |
|
Re: Disappearing attachments, posted by Stefan Ritt on Wed Apr 2 10:15:22 2003
|
> 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. |
|
Re: Logbook Title bar , posted by Stefan Ritt on Wed Apr 2 21:45:18 2003
|
> 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. |