ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66652
|
Thu Dec 10 18:12:19 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
David Spindler wrote: |
David Spindler wrote: |
David Spindler wrote: |
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Sorry for the delay.
1: The offending log file.
|
I know it looks like I am totally inept. I apologize. Obviously I was in a hurry the last couple of posts.
Ok, let's try this again.
The offending log file:
|
Ok, I am now assuming the offending log file has been removed. Correct? |
66653
|
Thu Dec 10 19:06:18 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
David Spindler wrote: |
Ok, I am now assuming the offending log file has been removed. Correct?
|
No, you never submitted any file. It was missing in all your posts. In worst case send it by email to me. |
66655
|
Sat Dec 12 20:18:46 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.8 | Re: 401 Authorization problem |
Ian Stokes-Rees wrote: |
Grrr. Forgetting to pick an icon means my message was blasted.
I have installed elog 2.7.8 and it is running. When I connect to it and get a login window, I am always denied. If I remove the passwords, then I can login with no password information. I have tried both command line for setting passwords and directly in the elogd.cfg file.
Suggestions on what I might be doing wrong would be appreciated.
Regards,
Ian
PS - are there RESTful interfaces to automate the generation of log entries via an HTTP POST or HTTP GET?
|
Which password scheme are you using? Is it Read passoword = ... or Password file = ...? If you use a password file (that's what most people do) you have to create yourself an account just as you did for this forum here. There is no other way to enter the encrypted password into the password file. Just follow "To start a new password file..." in the documentation. |
66656
|
Sat Dec 12 20:30:35 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.8 | Re: Elogd crashes when submitting replies |
Cliff Shaw wrote: |
Hi Stefan,
I recently installed the latest Elog 2.7.8 revision 2277 after running Elog 2.7.7 revision 2246 for several months without any problems. However once I submit an entry by using the Reply command Elog crashes and Windows XP reports an error message screen. This also stops the elogd service.
I have pinpointed it down to the command "subst on reply Subject = $Subject" by removing my whole configuration file and just added the line "subst on reply Subject = $Subject" to your demo configuration file.
Elog seems to also stops the elogd service with any "subst on reply" command.
Do you have any suggestions?
Thank you,
Regards
Cliff Shaw
|
Thanks for reporting that problem. I finally found the bug and fixed it. I made a new elog278-2 for you to download. |
66657
|
Sat Dec 12 20:31:44 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Extend fields in ELOG |
Michael Dannmeyer wrote: |
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
Michael Dannmeyer wrote: |
Stefan Ritt wrote: |
Michael Dannmeyer wrote: |
I want to extend the usage of ELOG and have 2 Questions:
1. Is it possible to have Fields which only appears if another selection is done? e.g. I create a new entry. This new entry has a type field. If I chose the Type "ABC" another field appears where the departemnt could be choosen. If I select Type "DEF" the Department field does not appear.
2. I have a field Status. This is a predefined field with 3 entries (New, under progress, closed). If i change the status field time, date old and new status should be logged or written in the text field. I can log this with the answer field with a new ID. But is there any other way to log it in the text field or log it with no new ID?
Can i implement the wishes above? If yes how does it work?
Thanks for your help
Michael
|
1. is simple, just use conditional attributes like:
Attributes = Author, Type, Status, Revisions, Department
Options Type = ABD{1}, DEF{2}
Show Attributes Edit = Author, Type, Status, Revisions
{1}Show Attributes Edit = Author, Type, Status, Revisions, Department
{2}Show Attributes Edit = Author, Type, Status, Revisions
2. is more complicated. Have a look at FAQ # 11. Try something like:
Options Status = New, Under progress, Closed
Subst Revisions = $date status $status
Subst on Edit Revisions = $Revisions<br>$date status $status
But when testing this, I realized that there is a bug in elog and the subsitution is done before the submission, not after. I fixed that in SVN revision 2263, so it will be contained in the next Windows release.
|
Hello,
i tried
Options Status = New, Under progress, Closed
Subst Revisions = $date status $status
Subst on Edit Revisions = $Revisions<br>$date status $status
but it won't work. When I change the status i saw an information in the status bar of Internet Explorer like "Entry has changed" (Eintrag wurde verändert) but it is not written in the notes field. Or is it written to another field?
Do I have to update first to the latest Windows Version? You wrote something about SVN revision 2263. When do you expect the windows version where this problem is fixed is available to download?
Best Reagrds
Michael
|
Hello,
it now works with the revisions. When do you expect that the new Windos version, which corrects the error you described, is available for download?
Best reagrds
Michael
|
You can download version 2.7.8 already since a while from https://midas.psi.ch/elog/download/windows/
|
I installed the latest windows Version but have massive Problems with it. I can create a new entry and the revisions filed is updated. If I want to change the status field from "new" to e.g. "under progress" the elogd service at the server crashes every time i want to save the changes so i switched back to 2.7.5-2130 and it works without any service crashes.
|
Can you try elog278-2. It should fix that problem. |
66661
|
Thu Jan 7 21:22:09 2010 |
| Aaron Couture | acouture@lanl.gov | Bug report | Linux | rev2280 | Re: Problem with CRYPT+SSL and elog command line entries |
I Aaron Couture wrote: |
I have attached a possible patch--basically pirated from elogd.c Because strlcpy needed for the crypt cares about size, do_crypt needed the size, which had not been a concern for base64_encode in elog.c As a result, base64_encode changed slightly as well. I think the implementation places a limit of 32 characters on passwords, which seemed to already be the limit in elogd.c The elog.c limit appeared to be 80 characters. I tested both SSL and SSL+CRYPT for commandline elog entries with both a logbook specific write password as well as username/password combo in a password file.
AJC
I am in the process of setting up a new ELOG logbook. I checked out rev2280 from svn.savannah.psi.ch. I knew I wanted to encrypt passwords, so when I compiled, I used flags
USE_SSL=1
and
USE_CRYPT=1
I am running Red Hat enterprise linux 3, glibc-devel-2.3.2-95.50, openssl-devel-0.9.7a-33.25
Everything seemed to be working fine--I was able to set up logbooks using both a password file as well as write passwords and make entries to the logs. Then I tried to use the command line 'elog' to make an entry which failed to both logbooks.
/opt/elog/pro/elogd -c /opt/elog/pro/dansce_fancy.cfg -l Demo1 -w <mypassword>
Would change the password in dansce_fancy.cfg and I could make entries through the web interface, but
elog -h acouture -s -p 8081 -w <mypassword> -l Demo1 -a Author="Aaron Couture" -a Type=Routine -m Sampleinfo.txt -x -n 1
failed with
Error: Invalid user name or password
I got the same behaviour when I used a logbook with a user/password pair defined in a password file.
When I looked at the output from running elogd with the -v flag, I could see that everything was being received on the server side, but that the password did not agree with the write password in dansce_fancy.cfg
I then recompiled elog with
USE_SSL=1
USE_CRYPT=
And then the elog command line entries worked, both with write passwords and a password file (after recreating the password file and the write password). Looking at the elog.c source code, it appears that it does not know to use crypt rather then base64_encode when USE_CRYPT is true. elogd.c defined different behaviour if USE_CRYPT is defined.
Thanks,
Aaron Couture
|
|
66663
|
Fri Jan 8 18:26:56 2010 |
| Aaron Couture | acouture@lanl.gov | Bug report | Linux | rev2280 | Re: Problem with CRYPT+SSL and elog command line entries |
Aaron Couture wrote: |
I Aaron Couture wrote: |
There was some sloppiness in the original patch--__USE_XOPEN wasn't defined, but worked when elog wasn't compiled alone. Now the appropriate ifndef/define statements are in elog.c
I have attached a possible patch--basically pirated from elogd.c Because strlcpy needed for the crypt cares about size, do_crypt needed the size, which had not been a concern for base64_encode in elog.c As a result, base64_encode changed slightly as well. I think the implementation places a limit of 32 characters on passwords, which seemed to already be the limit in elogd.c The elog.c limit appeared to be 80 characters. I tested both SSL and SSL+CRYPT for commandline elog entries with both a logbook specific write password as well as username/password combo in a password file.
AJC
I am in the process of setting up a new ELOG logbook. I checked out rev2280 from svn.savannah.psi.ch. I knew I wanted to encrypt passwords, so when I compiled, I used flags
USE_SSL=1
and
USE_CRYPT=1
I am running Red Hat enterprise linux 3, glibc-devel-2.3.2-95.50, openssl-devel-0.9.7a-33.25
Everything seemed to be working fine--I was able to set up logbooks using both a password file as well as write passwords and make entries to the logs. Then I tried to use the command line 'elog' to make an entry which failed to both logbooks.
/opt/elog/pro/elogd -c /opt/elog/pro/dansce_fancy.cfg -l Demo1 -w <mypassword>
Would change the password in dansce_fancy.cfg and I could make entries through the web interface, but
elog -h acouture -s -p 8081 -w <mypassword> -l Demo1 -a Author="Aaron Couture" -a Type=Routine -m Sampleinfo.txt -x -n 1
failed with
Error: Invalid user name or password
I got the same behaviour when I used a logbook with a user/password pair defined in a password file.
When I looked at the output from running elogd with the -v flag, I could see that everything was being received on the server side, but that the password did not agree with the write password in dansce_fancy.cfg
I then recompiled elog with
USE_SSL=1
USE_CRYPT=
And then the elog command line entries worked, both with write passwords and a password file (after recreating the password file and the write password). Looking at the elog.c source code, it appears that it does not know to use crypt rather then base64_encode when USE_CRYPT is true. elogd.c defined different behaviour if USE_CRYPT is defined.
Thanks,
Aaron Couture
|
|
|
66665
|
Mon Jan 11 10:00:14 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.7-2246 | Re: Each day new logbookfile |
Ben Weyn wrote: |
I have installed Elog in a Windows-environment. It's working fine, but i get a new logbookfile each day. Is it possible to have all entries in 1 logbookfile?
|
No. The standard database engine inside ELOG works this way. It allows you to backup then every month or year easily just on the file system by copying all 10????a.log files for example. If you would have just one file (which could become very large), there is no easy way to do that. |
|