Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 204 of 796  Not logged in ELOG logo
ID Date Icon Authordown Author Email Category OS ELOG Version Subject
  1497   Fri Oct 28 23:45:33 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0beta2Re: Conditional hiding of attributes in list view

Yoshio Imai wrote:
I have also found one possible problem, maybe it's already solved in the
newest version: We have set up the elog under an stunnel, but the elog
server also responds to the original port (i.e. 80), displaying the logbook
selection page and from there even the login screen. Only after logging in
the elog server redirects the client browser to the https-page defined with
the URL-statement of the config file. The whole thing seems like an unwanted
behaviour, but could you change it so that it either doesn't respond on the
wrong URL at all, or at least redirects to the secured URL before presenting
the login window, so that we transfer the passwords encrypted?


I implemented that in revision 1540. On the logbook selection page, the links to the individual logbooks honor the "URL = ..." statement from the config file, and thus you get redirected via "https://...". More is unfortunately not possible. If elogd gets contacted the first time, it is impossible to figure out by elogd under which URL it got contacted, and therefore it cannot distinguish between secure and insecure connections. The only way is to switch off port 80 by a firewall and only allow "https://..." connections from outside.
  1502   Mon Nov 7 09:16:47 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Problems with ELOG and Internet Explorer

Elaine Cristina Franchini dos Anjos wrote:
We are facing a problem when using the Internet Explorer browser to edit
logbooks entries. The error occurs when we use the preview option.

After this, the connection becomes slow to display the preview and returns
"Server Not Found - Page cannot be displayed" or "Internal Server error" as result.
If we try to turn back to the edit page the browser retuns
"This page has been expired".

It happens at any time even we edit simple entries in Internet Explorer,
but never occurs in other browsers.

Software versions that are running :

Elog version 2.6.0-beta
Fedora Core release 1 (Yarrow)
Apache/2.0.54 (Unix) mod_ssl/2.0.54 OpenSSL/0.9.7g
(Elog is running under apache proxy)

Is there any bug report about this or there is something else
that I need to configure ?


I tried on this forum with Internet Explorer 6.0 and could not reproduce the problem, and I never heared anybody else mentioning this problem. Can you reproduce the problem on the forum?
  1503   Mon Nov 7 09:25:59 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.0beta5Re: ELOG v2.6.0-beta5 (Windows) crashes while using " Forgot password?"

Edmundo T Rodriguez wrote:
The following ELOG behavior seems to be like a bug ...

-> Anybody click on "Forgot password?" in the login screen, to have the system
send him the forgotten password, and after a little while trying, (possibly doing
resolution) the ELOG application crashes.

The ELOG service have to registered again.

The SMPT host may not be right, but ELOG should not crash just for that.

It should says something like "Can not find SMTP server", etc.


I have fixed that in SVN revision 1541.
  1505   Tue Nov 8 08:17:22 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0Re: Problems with ELOG and Internet Explorer

Elaine Cristina Franchini dos Anjos wrote:
I edited and used preview many times and the ELOG worked fine without errors in IE. So, I think my problem is something configured in the proxy or https that Internet Explorer doesn't work very well in this circumstance.


Have a look at your URL = ... statement in elogd.cfg
It should probably read
URL = https://antares.ccuec.unicamp.br:9696

ELOG uses redirection internally. To determine it's own address, it uses the URL statement. If you use Apache as an proxy together with https, you have to specify the URL under which you usually access ELOG from outside. If this is wrong, ELOG might try to redirect to http:// or something which might not be possible.

A good way to debug this is to run ELOG with the -v flag and carefully watch the HTTP traffic. You will see Location: ... statements which redirect the browser, then the browser will access the redirected URL (if it's correct), or you will see nothing (in case the browser tries to access a non-existing URL).
  1507   Tue Nov 15 08:40:31 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0-4Re: page2?cmd=List does not show next page

Oleg Solovyanov wrote:
Maybe I'm doing something wrong, but the following does not work on a Elog with multiple pages:

1. View message
2. Click List
3. Click Next or page number
4. Only the last page is shown

It looks like the URL pageN?cmd=List does not work, while pageN works.

Any hints?

Same behaviour can be seen also with Discussion forum on Elog site.


I don't understand. I tried on the Discussion forum:

1. View message, for example http://midas.psi.ch/elogs/Forum/1506

2. Click List, which takes me to http://midas.psi.ch/elogs/Forum/

3. Click Next, which takes me to http://midas.psi.ch/elogs/Forum/page2

Then I really see page2, not the last page. So what do you do differently?
  1509   Tue Nov 15 12:50:37 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.0beta5Re: Getting back from "Find" mode

Yoshio Imai wrote:
There is one question regarding the "Find" function of the elog. Clicking onto "Search" takes the user to the list view on only those entries that match the search conditions. Since we use the list view in "Full" mode by default, this usually is enough to give us an overview of the event we looked for.
Is there a more direct way to get back to the unfiltered list view than selecting an entry and go to "List" or using "Find" again and clicking on "Back"?


I can easily add another button for that, will put it on the wish list.
  1511   Wed Nov 16 15:27:40 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.0-4Re: page2?cmd=List does not show next page

Oleg Solovyanov wrote:
Somehow in my logbooks List command would add cmd=List to the URL
And this does not work...


You use an old version of elog. Please upgrade to the 2.6.0-beta5 which you can obtain from

http://savannah.psi.ch/viewcvs/trunk/src/elogd.c?root=elog&rev=1541
  1517   Fri Nov 18 21:03:03 2005 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.0beta5Re: Automatic creation of new entry in another logbook

Carlos Mateo wrote:
I am trying to create an entry in logbook2 when I submit a new entry in logbook1. The automatically created entry in logbook2 will have a reference to the entry that created it.
Please tell me for what purpose you need two identical logbooks. Maybe what you want can be achieved in a simpler way.
Carlos Mateo wrote:
1.- Using the "Execute new" I call elog to create the second entry. As the server is single-process, it locks: elog is waiting for elogd to be ready and elogd is waiting for elog to finish to accept new requests. As my server is on a Windows machine I canīt execute elog on background.
Have you tried to start your elog with the start command under Widnows, like start elog .... This is the equivalent of starting a process in the background under linux.
Carlos Mateo wrote:
2.- I tried to run 2 servers on different ports using the same elogd.cfd file, calling the second server from elog. This "almost" works: the logbook files are updated, but the original server must be restarted to "see" the changes.
This is because you use the same data directory for both servers. If one server writes a new entry to a file, the other server does not realize this. Only when you restart it, it rescans the whole data directory and gets aware of the new entry. Try using separate data directories for the two servers.
Carlos Mateo wrote:
3.- Using the "Menu text" option, I create a link to create the new entry. The problem is that attributes are not parsed: a link like this <a href="/logbook2/?cmd=New&pAttr=Value $ID">Test</a> wonīt substitute $ID
Parsing attributes is not implemented and therefore will not work.
ELOG V3.1.5-2eba886