Re: Logging entries from the command line, posted by kenzo Abrahams on Mon Oct 26 12:26:03 2015
|
Hi Stephan I got it to work for some reason elog was complaining that my encoding of the message wasnt allowed. I allowed the lognook to allow ELcode and it works perfectly.
Thank you for the help.
| kenzo Abrahams wrote: |
|
Yes I can it works perfectly from the browser.
| Stefan Ritt wrote: |
|
This indicates that the username/password is not correct. Can you log in to that logbook in your browser with the username "John" and password "Blue"?
| kenzo Abrahams wrote: |
|
Hi Stephan
The error message I get is "Error: Command Submit not allowed". I dont know if this might be an issue but it says Response Recieved: HTTP/1.1 404 Not Found in the first line of the servers response
| Stefan Ritt wrote: |
|
Run the elog command with an additional -v flag (verbose output), and you will see what the elogd server return. It's HTML, but you should be able to see some error message.
| kenzo Abrahams wrote: |
|
Good Afternoon
Im trying to automatically post an entry using information saved in a text file. I have followed the example in the users guide but i always seem to get a error message saying transmission failed. Lets say for instance I have a user named John and his password is Blue and he wants to log into a logbook called home from a textfile the command im using to log a message from the file is
elog -h localhost -p 8080 -u John Blue -l home -a Author=John -m textfile
I cant seem to figure out why i keep getting this error message. I even tried deleting the password file because i thought it might be an authentication issue.
Can anybody assist me please it would be much appreciated.
Regards
|
|
|
|
|
|
|
Re: Logfiles, posted by Stefan Ritt on Tue Mar 29 23:05:56 2005
|
> Is there an option that elog creates one logfile for one entry in the
> database? It seems that there elog is creating one logfile for one day.
No. One file per day was chosen in order to keep the number of files small.
For which purpose would you need such an option? |
|
Re: Logfiles, posted by Becher on Wed Mar 30 16:05:34 2005
|
I want exchange the logs as files and not with the mirroring function. My
collegue and me are already exchanging all our project files, so the logs from
ELOG could be included in this exchange. |
|
Re: Logfiles, posted by Stefan Ritt on Wed Mar 30 16:31:36 2005
|
> I want exchange the logs as files and not with the mirroring function. My
> collegue and me are already exchanging all our project files, so the logs from
> ELOG could be included in this exchange.
If you do not want to use the mirroring, then you can extract a single entry with
the "hidden" download command. Like for this entry:
http://midas.psi.ch/elogs/Forum/1039?cmd=Download
Tell your browser to save the result locally and you have a file with just this
message. Note however that if you ship these files around, and combine them with an
existing logbook by copying them to the logbook directory, you could have two
entries with the same ID, in which case elogd would produce unpredictable results. |
|
Re: Logfile not registering entry numbers?, posted by Andreas Luedeke on Fri Oct 19 13:08:30 2018
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
| Sergio Navarrete wrote: |
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
|
Re: Logfile not registering entry numbers?, posted by David Pilgram on Mon Oct 29 14:26:28 2018
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now.
A quick (relative term, that) search usually finds the entry which references the missing "Reply to" line, and editing that, all is well. I'm not sure how this can happen, but it does. NB, I'm still on elog 2.9.2 so I don't know how the draft facility works and possibly enhances the possibility of this issue.
Note that this is different to the case (rather more frequent) where the entry in the "In reply to" field is missing. This causes elog to go into a continuous loop and only the strongest measures ("kill -9 xxxx in linux) will break this out. This can happen more frequently as if you delete a thread with a large number (>40?) of entries, elog crashes, but more importantly, hasn't finished the job. Clicking on the remenents of the thread (which are usually the later entries) causes the endless loop.
| Andreas Luedeke wrote: |
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
| Sergio Navarrete wrote: |
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
|
|
Re: Logfile not registering entry numbers?, posted by Stefan Ritt on Wed Apr 1 15:57:27 2020
|
I finally found some time to fix that bug. Was just that the log file hat #0, the bug should not have had any ohter side effects. Now the logfile is fine.
| David Pilgram wrote: |
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now.
A quick (relative term, that) search usually finds the entry which references the missing "Reply to" line, and editing that, all is well. I'm not sure how this can happen, but it does. NB, I'm still on elog 2.9.2 so I don't know how the draft facility works and possibly enhances the possibility of this issue.
Note that this is different to the case (rather more frequent) where the entry in the "In reply to" field is missing. This causes elog to go into a continuous loop and only the strongest measures ("kill -9 xxxx in linux) will break this out. This can happen more frequently as if you delete a thread with a large number (>40?) of entries, elog crashes, but more importantly, hasn't finished the job. Clicking on the remenents of the thread (which are usually the later entries) causes the endless loop.
| Andreas Luedeke wrote: |
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
| Sergio Navarrete wrote: |
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
|
|
|
Re: Logfile not registering entry numbers?, posted by Sergio Navarrete on Thu Dec 16 08:23:22 2021
|
It seems that the latest Windows binary still predates this fix. Will there be a new installer soon? Thanks for your support.
| Stefan Ritt wrote: |
|
I finally found some time to fix that bug. Was just that the log file hat #0, the bug should not have had any ohter side effects. Now the logfile is fine.
| David Pilgram wrote: |
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now.
A quick (relative term, that) search usually finds the entry which references the missing "Reply to" line, and editing that, all is well. I'm not sure how this can happen, but it does. NB, I'm still on elog 2.9.2 so I don't know how the draft facility works and possibly enhances the possibility of this issue.
Note that this is different to the case (rather more frequent) where the entry in the "In reply to" field is missing. This causes elog to go into a continuous loop and only the strongest measures ("kill -9 xxxx in linux) will break this out. This can happen more frequently as if you delete a thread with a large number (>40?) of entries, elog crashes, but more importantly, hasn't finished the job. Clicking on the remenents of the thread (which are usually the later entries) causes the endless loop.
| Andreas Luedeke wrote: |
|
It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".
I've looked into the code: the message is written before the new entry is submitted, and only then the entry ID is defined.
For new entries one would need to make the logging print line later - but that would blow up the code.
The message IDs are correct for saving drafts and editing entries. I'll discuss with Stefan if that should be fixed.
Andreas
| Sergio Navarrete wrote: |
|
I have configured a logbook with the logfile on, but when a user replies to an entry the line logged goes
Date Time [User@IP] {Logbook} NEW entry #0
How can I make the #0 be the real entry number for the reply?
|
|
|
|
|
|