ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67055
|
Sat Apr 23 14:32:38 2011 |
 | Pelle | Sorry, found it | Info | Linux | 2,3.8 | Re: elog2sql - a script to convert elog logbooks to a MySQL database | > > I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread. > > Thanks, > > Pelle
Sorry, found it in the contribution list https://midas.psi.ch/elogs/Contributions/5 |
|
67054
|
Sat Apr 23 08:56:26 2011 |
| Pelle | pelle@sm4xiu.eu | Info | Linux | 2,3.8 | Re: elog2sql - a script to convert elog logbooks to a MySQL database |
I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread.
Thanks,
Pelle |
|
67053
|
Fri Apr 22 00:56:43 2011 |
| Pelle | pelle@sm4xiu.eu | Question | Windows | V2.7.4-212 | Re: Automatic Copy to |
| Grant Jeffcote wrote: |
| Stefan Ritt wrote: |
| Grant Jeffcote wrote: | Stefan,
Is there any way I might be able to initiate the 'copy to' function by selecting a 'tick box' (boolean) or conditional attribute choice in an entry page when submitting that page? We have a requirement where we run a main 'Operations' log and have another log with some entries needing to be in both (for additional actions etc). I understand the Operator can always manually use the 'Copy To' function after submitting the original entry but was wondering if there was some way a shell script (execute function?) or similar may be activated by a boolean or even a 'conditional' choice?
Thx |
I put your request on the whishlist. |
Thanks Stefan. |
Hi Stefan,
Any progress on this whish?
We are evaluating Elog to use it as disaster management log so we need to be able to have several logs that merges into one big log where analytic people can see the whole picture/timeline of whats going on in one single logg.
It can very well be as easy as a elog command-line option that initiates the whole thing with the help of Cron/Sheduler but the best would of course be to copy the whole idea from the mirroring function also for the copy/move task.
....or if there is a possibility to write directly to other logs than the current one in the moment of saving the entry....
Best,
Pelle |
|
67052
|
Thu Apr 21 21:06:20 2011 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Bug report | Linux | 2.9.0 | Re: elog 2.8.0 as daemon crashes when editing selected threaded list |
| Mark Bergman wrote: |
|
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem where elog consistently crashes when attempting to edit multiple entries. This is a very common use case, as we use a "status" field, set to "open" or "closed" to track problems. When a problem is resolved, we will go to the "list" display, set it to "threaded", "select" the thread, and then edit it, to change the status field for all posts in the thread to "closed".
Now, as soon as the "edit" button is clicked, elog crashes. This happens on every thread and logbook that I've tried. The elog logfile itself doesn't show anything useful.
However, if eLog is run with "-v" in place of "-D", it does not crash.
Environment:
CentOS 5.4
eLog 2.8.0 built Aug 5 2010, 12:24:11
|
I'm now running eLog 2.9.0 and seeing the same crashes. However, I've got some more information that may be helpful.
The crash seems to be directly related to the order of replies in the thread. For example, in this thread I am replying to the original entry. The original entry has 2 children (the entries are siblings) and no grandchildren.
In our installation, eLog crashes consistently under the following conditions:
go to the "list" display
set it to "threaded"
"select" a thread that has siblings at any generation of replies
choose "edit"
If the selected thread only has one entry at any generation, eLog does not crash.
Here's a horrible attempt at a display of two message threads. Note that in the first example, there are 2 replies at the same generation (siblings)--both the person who responded and the original submitter replied to the initial submission. After that, all replies were to successive generations.
-------------- Causes eLog to Crash ------------------
! Full Name (submitter) module failure
=> Full Name (submitter) Re: module failure
=> Full Name (replier) Re: module failure
=> Full Name (submitter) Re: Re: module failure
=> Full Name (submitter) Re: Re: Re: module failue
------------------------------------------------------
-------------- No eLog Problem ------------------
! Full Name (submitter) Labwide failure of mcc
=> Full Name (replier) Re: Labwide failure of mcc
=> Full Name (submitter) Re: Re: Labwide failure of mcc
=> Full Name (replier) Re: Re: Re: Labwide failure of mcc
------------------------------------------------------
|
|
67051
|
Fri Apr 15 12:02:50 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.9.0 | Re: Self Register = 3 doesn't work any longer |
| Olivier Callot wrote: |
|
I tried again and confirm the version number. I never got this pannel saying that my request will be processed by an adminstrator. Maybe the installation was incomplete? Is this pannel outside the standard src files? I receive the mail as administrator, but the accout is already valid BEFORE I validate it.
This was working in previous versions, i.e. the entry was not created at all. And login wasn't possible.
We went back to 2.8.0 as the server is regularly crashing with 2.9.0 and we have to keep it alive for our running experiment. We are trying to isolate and reproduce the problem...
|
Try to use the simple config file, and see what happens there. Maybe it's a config option you use differently in the experiment. If you identify the config option which triggers the problem, I can probably reproduce it and fix it. Concerning crashes of 2.9.0: We have it running stably for our experiments, that's why I released it. But there are major changes since 2.8.0, mainly the Kerberos authentification (actually people from CERN asked for that). So it could be that in your case there are problems I don't see. In that case you have to test with which options in the config file the problems start. If elogd crashes, a stack dump would maybe also be helpful for me. |
|
67050
|
Fri Apr 15 11:49:43 2011 |
| Olivier Callot | Olivier.Callot@cern.ch | Bug report | All | 2.9.0 | Re: Self Register = 3 doesn't work any longer |
| Stefan Ritt wrote: |
|
| Olivier Callot wrote: |
|
With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks
|
Are you sure about that (maybe used an older revision of elogd where this indeed was a problem?). The current V2.9.0-2412 gives me this:
If I then log in as the admin user, I see the configuration of the new user, but the account is not activated:
So the user cannot log in. The config file is:
[global]
port = 8080
password file = passwd
smtp host = mail.psi.ch
Self register = 3
Admin user = stefan
[demo1]
Attributes = Project, Category
Can you double check?
|
HI Stefan,
I tried again and confirm the version number. I never got this pannel saying that my request will be processed by an adminstrator. Maybe the installation was incomplete? Is this pannel outside the standard src files? I receive the mail as administrator, but the accout is already valid BEFORE I validate it.
This was working in previous versions, i.e. the entry was not created at all. And login wasn't possible.
We went back to 2.8.0 as the server is regularly crashing with 2.9.0 and we have to keep it alive for our running experiment. We are trying to isolate and reproduce the problem... |
|
67049
|
Fri Apr 15 08:49:26 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.9.0 | Re: Elog 2.9.0 buffer overflow crash bug ubuntu linux | > When running openvas (a nessus fork) against elog 2.9.0 I provoked the following crash:
>
> Apr 9 17:32:06 unixland elogd[1300]: POST / HTTP/1.0#015#012Host: unixland.home
> #015#012Content-Length: -800#015#012#015#012XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
> Apr 9 17:32:06 unixland kernel: [664894.491242] elogd[1300]: segfault at b7713d
> 2e ip 080b6956 sp bf8d5ea0 error 4 in elogd[8048000+96000]
>
> openvas reports that it was testing for CVE-2002-1212 when the crash occurred.
>
> Startup info:
>
> Apr 9 19:35:54 unixland elogd[21584]: elogd 2.9.0 built Apr 9 2011, 17:49:08
> Apr 9 19:35:54 unixland elogd[21584]: revision 2411
>
> -- rouilj
I haven't tried openvas, but added a check for the negative content-length you have in the request
above in SVN revision 2413. Can you try if it still crashes?
- Stefan |
|
67048
|
Fri Apr 15 08:37:21 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.9.0 | Re: Self Register = 3 doesn't work any longer |
| Olivier Callot wrote: |
|
With the recent Elog 2.9.0 rev 2412 the Self Register = 3 option doesn't work as expected: The user is immediately allowed to login. This is not what this option was doing, which is to wait for an approval by the administrator. Can this behaviour be restored, or should I change the value of the Self Register flag? Thanks
|
Are you sure about that (maybe used an older revision of elogd where this indeed was a problem?). The current V2.9.0-2412 gives me this:
If I then log in as the admin user, I see the configuration of the new user, but the account is not activated:
So the user cannot log in. The config file is:
[global]
port = 8080
password file = passwd
smtp host = mail.psi.ch
Self register = 3
Admin user = stefan
[demo1]
Attributes = Project, Category
Can you double check?
|
|