upgrade problem, posted by Tim Schelfhout on Tue Mar 15 19:53:55 2016
|
Hello there,
After several years of great ELOG usage I decided to upgrade our ELOG server. I am using it to keep
a logbook of my students.
ELOG runs as a windows service but since I cannot access or change windows services (only have access to the
ELOG directory) I upgraded by installing the executable to my laptop then copying the new ELOG version over the server installation.
Tried this first on my laptop going from V2.9.2-2475 to the last version 3.1.1 and this worked without a problem.
When I tried to reproduce this on the server all the data is there but ELOG displays it as if no theme was installed. (using the default
by the way) No colors, no formatting
... at first I thougt this was because the copy was not complete but a second try reproduced the same result???
Tried going back to the old version but then ALL data was gone (structure and all logbooks still there, but data in logbooks gone) ....
Used -v switch to debug and the logging displayed an MD5 hash mismatch, so the logbooks could not be opened. A restore fixed this ....
I guess upgrading means changing the logbook structure?
Anyway does anyone have any idea why the upgrade loses formatting ?? Tips are welcome |
Re: upgrade problem, posted by Andreas Luedeke on Wed Mar 16 08:39:55 2016
|
Hi Tim,
starting with ELOG version 3 all entries are moved into sub-directories for each year.
If you move the files back from the sub-directories and restart elogd, then the entries should appear again in the logbook with ELOG 2.9.2.
I don't know how to solve your other problem. Maybe you should talk to someone locally who can administer your windows server?
Cheers, Andreas
| Tim Schelfhout wrote: |
|
Hello there,
After several years of great ELOG usage I decided to upgrade our ELOG server. I am using it to keep
a logbook of my students.
ELOG runs as a windows service but since I cannot access or change windows services (only have access to the
ELOG directory) I upgraded by installing the executable to my laptop then copying the new ELOG version over the server installation.
Tried this first on my laptop going from V2.9.2-2475 to the last version 3.1.1 and this worked without a problem.
When I tried to reproduce this on the server all the data is there but ELOG displays it as if no theme was installed. (using the default
by the way) No colors, no formatting
... at first I thougt this was because the copy was not complete but a second try reproduced the same result???
Tried going back to the old version but then ALL data was gone (structure and all logbooks still there, but data in logbooks gone) ....
Used -v switch to debug and the logging displayed an MD5 hash mismatch, so the logbooks could not be opened. A restore fixed this ....
I guess upgrading means changing the logbook structure?
Anyway does anyone have any idea why the upgrade loses formatting ?? Tips are welcome
|
|
Pre-populate filed based on selection, posted by Jimmy Bria on Mon Mar 14 16:00:02 2016 
|
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.
Thank you,
Jimmy
|
|
Re: Pre-populate filed based on selection, posted by Stefan Ritt on Tue Mar 15 03:48:58 2016
|
Use "conditional attributes" as described in the documentation: https://midas.psi.ch/elog/config.html#conditional
| Jimmy Bria wrote: |
|
Hi,
Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.
Thank you,
Jimmy
|
|
|
Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:19:02 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12
/lib64/libc.so.6
/usr/lib64/libssl.so.10
rpm -i elog-latest.i386.rpm
error: Failed dependencies:
libc.so.6 is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386
libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386
libssl.so.6 is needed by elog-3.1.1-1.i386 |
|
elogd -m Error sending local entry: Error transmitting message, posted by Dave on Thu Mar 10 00:26:03 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.
Can anyone tell me why I get this error?
==============================
Here is the command & output:
c:\Program Files (x86)\ELOG>elogd -m
Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical
Retrieving entries from "http://166.22.64.201/System Log"...
Error sending local entry: Error transmitting message |
elogd -m , posted by Dave on Thu Mar 10 00:16:33 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.
Can anyone tell me why I get this error?
==============================
Here is the command & output:
c:\Program Files (x86)\ELOG>elogd -m
Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical
Retrieving entries from "http://166.22.64.201/System Log"...
Error sending local entry: Error transmitting message |
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script will then automatically stage all changes and create an appropriate git commit message. For a "new" entry in the logbook the commit message is a bit more verbose. When editing or deleting a message only a short commit message like "Edit message 25" should be created. Therefore I really need to distinguish between "new", "edit", and "delete".
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected. 
What I did so far to understand what goes wrong is I looked into elogd.c and found invoid submit_elog(LOGBOOK * lbs) that bedit is sometimes true and sometimes false, when creating a new entry, although it should be false then (right?).
This is why elogd then sometimes retrieves the wrong shell command from getcfg(lbs->name, "Execute edit"...) instead of getcfg(lbs->name, "Execute new"...) around line 23610 (not exact due to some eprintf()s inserted here and there to look at bedit and so on).
When deleting an entry, everything works fine: the shell command defined via "Execute delete=" is run, but this happens somewhere else in the code so it's not a surprise.
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016
|
| Juergen Diefenbach wrote: | I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the one specified by "Execute edit=" is executed. Most of the time it doesn't work as expected.
[...]
Do you have an idea how to fix this or can you point me in some direction to further track it down? Thank you! |
I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
If that is the case then Stefan will know where to look 
Cheers
Andreas |
|
Re: Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Mon Mar 7 13:03:13 2016
|
| Andreas Luedeke wrote: | I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
If that is the case then Stefan will know where to look
Cheers
Andreas |
Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!
In principle I could live with this as I don't think I need to have drafts enabled.
Cheers,
Jürgen |
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016
|
| Juergen Diefenbach wrote: |
| Andreas Luedeke wrote: | I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
If that is the case then Stefan will know where to look
Cheers
Andreas |
Alright, I tried "Save drafts = 0" in the config file and now it seems to work all the time as expected!
Thank you, Andreas!
In principle I could live with this as I don't think I need to have drafts enabled.
Cheers,
Jürgen |
I would speculate that "Execute new" is not executed, when a draft is saved (as one would expect, since it's only a draft), but is neither executed when a draft is submitted (not as one would expect).
Good that you're fine for the moment.
If you could add a minimal configuration to reproduce the problem, then Stefan would have it easier to debug it. |
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:12:45 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
|
Re: Attribute Field Size Limited to 255 Characters, posted by Andreas Luedeke on Thu Mar 3 14:51:55 2016
|
No. At least there is no simple method.
You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have a hard time finding the right one to increase.
Cheers, Andreas
| Mike Bodine wrote: |
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?
|
|
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:02:26 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |