elogd 2.6.0 crash on password Forgot?, posted by Mike on Tue Jan 3 17:20:16 2006 
|
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 |
"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? |
|
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. |
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. |
|
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 
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. |
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
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 |
|
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. |
|
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
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. |
|
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 |
|
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. |
|
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! |
|
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 |
|
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. |
|
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. |
|
duplicate & presets, posted by Willem Koster on Mon Dec 12 15:17:39 2005
|
I'm (mis)using elog as a database. I like the fact that I can have presets for fields, but I also like the fact
that I can make a duplicate of an entry. Now when I make a duplicate, all the fields get overwritten with the
preset-value. Is there a way to get the preset-values only on entering a NEW reord and NOT on a duplicate ?
I could take away the presets, most of them are "***" (literally) to be able to search for entries that do not
have a value, but I don't know how to search for empty fields.
PS: They wanted to do a CMDB in BMC-Magic (really expensive $$$-ware), but after about 1 afternoon (and about 6
prototypes) they went with elog since it was fast, cheap and already implemented (and filled with 200 entries
through a script using some old CSV list we had lying around) :-)
|
|
Re: duplicate & presets, posted by Stefan Ritt on Wed Dec 21 20:24:14 2005
|
> I'm (mis)using elog as a database. I like the fact that I can have presets for fields, but I also like the fact
> that I can make a duplicate of an entry. Now when I make a duplicate, all the fields get overwritten with the
> preset-value. Is there a way to get the preset-values only on entering a NEW reord and NOT on a duplicate ?
I fixed that in the SVN revision 1583. The fix will be contained in the upcoming version 2.6.1. |