Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 185 of 238  Not logged in ELOG logo
icon4.gif   "Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Thu Nov 24 20:08:00 2005 
Hi, it's me again!

I have found one possible bug. We have declared top groups for our logbooks; one for administration and one for the shift logbooks. In the [global]-section there is a "Logbook dir"-statement of the form
[global]
Top group Admin = <...>
Top group Shiftlogs = beamtime1,beamtime2,...

Logbook dir = /data/logbooks
Now, in the [global Shiftlogs] section there is another "Logbook dir"-statement to have all associated logbooks in one tree:
[global Shiftlogs]
Logbook dir = /data/logbooks/shift-logbooks

[beamtime1]
Subdir = beamtime1
The problem is, that the manually created subdirectories /data/logbooks/shift-logbooks/beamtimeN are ignored, and the elogd creates new "Subdir"-directories /data/logbooks/beamtimeN (as if the "Logbook dir" statement in the top group [global] section were ineffective). Is this a bug or configuration error from our side?

There are also one question/request (you see that we use the elog extensively now Wink):
When searching for a particular event in our shift log using the "Find" function, it would often be useful not to go to the single entry, but to the page where that entry resides. This way we can see the whole context of the event. When clicking onto an entry in the "Find" result page, this takes us of course to the single entry, but could you add a function to go to the page instead. Alternatively, is it possible to include a button "Go to page" in the single entry view (it need not even be exactly +/-N entries around, the usual page partition would do)?

Thanks in advance.

Yoshio
    icon2.gif   Re: "Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Fri Nov 25 14:05:08 2005 
OK, I found the note about "Logbook dir" in Stephen Wood's entry (http://midas.psi.ch/elogs/Forum/1101) Wink
    icon2.gif   Re: "Logkook dir" in top group [global] section ineffective, posted by Stefan Ritt on Thu Dec 22 20:50:57 2005 

Yoshio Imai wrote:
There are also one question/request (you see that we use the elog extensively now Wink):
When searching for a particular event in our shift log using the "Find" function, it would often be useful not to go to the single entry, but to the page where that entry resides. This way we can see the whole context of the event. When clicking onto an entry in the "Find" result page, this takes us of course to the single entry, but could you add a function to go to the page instead. Alternatively, is it possible to include a button "Go to page" in the single entry view (it need not even be exactly +/-N entries around, the usual page partition would do)?


I implemented that request. When you click on "list", it takes you to the listing page containing the current entry, which is even highlighted. Have a look at this forum if this is what you like.
       icon2.gif   Re: "Logkook dir" in top group [global] section ineffective, posted by Yoshio Imai on Wed Jan 4 15:27:31 2006 

Stefan Ritt wrote:
I implemented that request. When you click on "list", it takes you to the listing page containing the current entry, which is even highlighted. Have a look at this forum if this is what you like.


Thank you!
I just installed the latest revision; it is exactly what we need.
I found one problem, however: while linking the binaries for elogd, the linker complained about an undefined reference to forkpty implemented in libutil. I had to add the linker option
 -lutil 
to the Makefile target elogd:, then it compiled correctly.

One strange thing (maybe it isn't strange at all) is the following behaviour: when the list view is set to "summary", then the line containing the entry where we clicked "list" is highlighted, however when the list view is set to "full", it isn't. Is this "a bug, or a feature"? Wink

Thanks for the work from all, and happy new year.

Yoshio
          icon2.gif   Re: "Logkook dir" in top group [global] section ineffective, posted by Stefan Ritt on Mon Jan 9 20:09:16 2006 

Yoshio Imai wrote:
One strange thing (maybe it isn't strange at all) is the following behaviour: when the list view is set to "summary", then the line containing the entry where we clicked "list" is highlighted, however when the list view is set to "full", it isn't. Is this "a bug, or a feature"? Wink


Was a bug. I have fixed that in revision 1591.
icon1.gif   elogd 2.6.0 crash on password Forgot?, posted by Mike on Tue Jan 3 17:20:16 2006 elog-pw-crash.jpg
I have been having a repeatable crash on V2.6.0 everytime someone tries to recover a password using the option from the login screen. See attachment for a jpg of the message.

This is occuring on windows 2003. But I have also tested it on windows XP and it occurs there as well. In addition on XP I did a generic installtion and added the password option to the DEMO application and it fails there as well.

Mike
icon2.gif   "Syntax of elogd.cfg" - Document, posted by Edmundo T Rodriguez on Thu Dec 22 21:15:19 2005 
The document "ELOG - Syntax of elogd.cfg" is outdated!

Are we going to have an updated documented?

How much difference exists between the one posted as a reference
and new one covering all new options in ELOG?
    icon2.gif   Re: "Syntax of elogd.cfg" - Document, posted by Stefan Ritt on Fri Dec 23 09:07:14 2005 

Edmundo T Rodriguez wrote:
The document "ELOG - Syntax of elogd.cfg" is outdated!


I forgot to update the web server, but the document distributed in the 2.6.0 package was up to date.


Edmundo T Rodriguez wrote:
Are we going to have an updated documented?


I copied the actual version to the web server.


Edmundo T Rodriguez wrote:
How much difference exists between the one posted as a reference
and new one covering all new options in ELOG?


For the changes from one version to the other, have a look at the changelog.
icon5.gif   Maximum number of LogBooks? Bug?, posted by Mike on Thu Dec 22 14:32:00 2005 
Is there a Maximum number logbooks?

I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.

Error: Too many parameters (> 120). Cannot perform operation.

I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.

Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.

Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it.
    icon2.gif   Re: Maximum number of LogBooks? Bug?, posted by Stefan Ritt on Thu Dec 22 15:14:39 2005 

Mike wrote:
Is there a Maximum number logbooks?

I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.

Error: Too many parameters (> 120). Cannot perform operation.

I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.

Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.

Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it.


You're really pushing to the limit Wink

The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like

Attributes = ..., Server, ...
Options Server = Server1, Server2, ...

Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers.
       icon7.gif   Re: Maximum number of LogBooks? Bug?, posted by Mike on Thu Dec 22 15:39:23 2005 

Stefan Ritt wrote:


You're really pushing to the limit Wink

The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like

Attributes = ..., Server, ...
Options Server = Server1, Server2, ...

Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers.


Thanks for the quick reply and suggestion. I will give that a try.

You might want to consider adding a check that there aren't over 120 logbooks. I manually created the elog.cfg with 294 logbooks. Everything works, except for running into this problem.

Thanks again
icon5.gif   New docs?, posted by PJ Meyer on Thu Dec 22 01:17:12 2005 
Just looked at change log for 2.6
was wondering where the documentation for the new additions/changes is/are.
    icon2.gif   Re: New docs?, posted by Stefan Ritt on Thu Dec 22 08:58:25 2005 

PJ Meyer wrote:
Just looked at change log for 2.6
was wondering where the documentation for the new additions/changes is/are.


I usually keep http://midas.psi.ch/elog/config.html up-to-date, but I agree that it's a bit hard to find the additions there, that's why there is the change log Wink

The ELCode is described on a separate page, which can also be accessed by clicking on the ELCode link below the text box of the logbook entry page.
icon5.gif   Compile on Windows?, posted by Mike on Wed Dec 21 23:52:27 2005 
What version of Visual Studio do you use for compile Elog on windows.

I have downloaded the Tar from svn and am having some errors, but then I've go VS.Net 2003. I wondering if this was done with 6.0?

thanks
    icon2.gif   Re: Compile on Windows?, posted by Stefan Ritt on Thu Dec 22 08:53:43 2005 

Mike wrote:
What version of Visual Studio do you use for compile Elog on windows.

I have downloaded the Tar from svn and am having some errors, but then I've go VS.Net 2003. I wondering if this was done with 6.0?


Right now I'm using VS.Net 2003, but you should be able to compile it with 6.0, except that you have to redo the project file, which might not be backwards compatible. An alternative is to use gcc under cygwin, which is a free alternative for windows.
icon1.gif   Proxy question, posted by Jesse Wodin on Wed Dec 7 02:37:40 2005 
I'm trying to run elog 2.6.0-beta4 under Apache 2.0.  I follow the directions, and everything works fine, so my
elog runs as

http://grattalab3.stanford.edu/elog/

running under port 8082, with the following lines in my httpd.conf file

 Redirect permanent /elog http://grattalab3.stanford.edu/elog
 ProxyPass /elog/ http://grattalab3.stanford.edu:8082/

This machine has an alias, which is http://exo-elog.stanford.edu.  My question is, how can I run elog so that
when someone types in this name, it brings up my elog? I know that I can make a VirtualHost entry and put a
redirect at the document root of that virtual host, but that seems clumsy.  Can I just modify ProxyPass or add a
Redirect statement somehow?

Thanks!
    icon2.gif   Re: Proxy question, posted by Stefan Ritt on Wed Dec 21 20:59:26 2005 
> I'm trying to run elog 2.6.0-beta4 under Apache 2.0.  I follow the directions, and everything works fine, so my
> elog runs as
> 
> http://grattalab3.stanford.edu/elog/
> 
> running under port 8082, with the following lines in my httpd.conf file
> 
>  Redirect permanent /elog http://grattalab3.stanford.edu/elog
>  ProxyPass /elog/ http://grattalab3.stanford.edu:8082/
> 
> This machine has an alias, which is http://exo-elog.stanford.edu.  My question is, how can I run elog so that
> when someone types in this name, it brings up my elog? I know that I can make a VirtualHost entry and put a
> redirect at the document root of that virtual host, but that seems clumsy.  Can I just modify ProxyPass or add a
> Redirect statement somehow?

To my knowledge you need a VirtualHost entry, plus a "URL = http://exo-elog.stanford.edu" entry in elogd.cfg
icon5.gif   2.6.0-bata5, posted by Carl Shirey on Sat Dec 10 02:01:33 2005 
Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help.
    icon2.gif   Re: 2.6.0-bata5, posted by Stefan Ritt on Wed Dec 21 20:39:52 2005 

Carl Shirey wrote:
Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help.


There is a 2.6.0 out by now.
ELOG V3.1.5-3fb85fa6