Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 638 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  1427   Wed Oct 5 13:22:08 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | Windows2.6.0-b4Re: Post appearing twice

Dan Chitwood wrote:
We are having trouble on our logbook with posts appearing twice. Both posts contain the same ID number, time, etc. This most often occurs when the e-log entry is being written for an extended period of time (ie. more than 30 minutes), but I don't know if that is the root cause of the problem. It may also be related to posts that are edited after an initial posting. Could this be due to an improper setting in our config file?


Besides the trivial case that people hit the submit button twice I can only imagine one possible cause: If you edit an existing entry, there is a button Resubmit as new entry at the bottom. If that button is checked, the old entry gets deleted and a new one gets submitted. If the delete of the old entry fails for some reason, you could maybe get two entries.

May I suggest following: Use a very simple config file (like the demo one from the distribution) and see if you can reproduce the problem. If not, add you config options one by one to the config file, and see at which option the problem starts. This way you might find the cause of it.

Your problem has not been reported by anybody else so far, so chances are high that it's related to a config setting.
  1426   Wed Oct 5 13:07:51 2005 Reply Stefan Rittstefan.ritt@psi.chBug fixOtherV2.5.9-2Re: error when searching for POST

Guenter Nowak wrote:
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error


This bug has been fixed in the current CVS version.
  1425   Tue Oct 4 20:33:05 2005 Reply David Spindlerdsspindler@earthlink.netQuestionWindows2.5.7Re: Can't use the command-line client

David Spindler wrote:
I just noticed in the changelog that my apparent problem with MOptions may have been fixed. I will try a newer version and see if it works.


It did.

Keep up the good work.
  1424   Tue Oct 4 20:24:26 2005 Reply David Spindlerdsspindler@earthlink.netQuestionWindows2.5.7Re: Can't use the command-line client
I just noticed in the changelog that my apparent problem with MOptions may have been fixed. I will try a newer version and see if it works.
  1423   Tue Oct 4 19:40:27 2005 Question David Spindlerdsspindler@earthlink.netQuestionWindows2.5.7Re: Can't use the command-line client
I have a similar problem. I am using Windows version, and whenever I use the elog client to send entry, it will not take with MOptions set. I usually have 2 attributes required (both MOptions), and I get the message that it is missing a required attribute. When I use ROptions, or Options, it works fine. Is there a problem with MOptions, or am I perhaps using a badly formatted commandline?

Commandline as follows: C:\elog>elog -h IP_ADR -p 80 -l gbld -u username password -a Type=Other -a Operator=SCADA -a Category=Controls -a Subject=Alarm "Please ignore."

Type and Category are required and MOptions.

Below is the pertinent part of the config file:

;***** Attribute Section
Attributes = Log Date, Operator, Type, Category, Engine, Work Order #, EPN, Fuel Tank 1 (A&B), Fuel Tank 2 (C&D), Engine Hours Stop, Engine Hours Start, Email To, Subject

Comment EPN = (Equipment Piece Number)
Comment Fuel Tank 1 (A&B) = (West)
Comment Fuel Tank 2 (C&D) = (East)

MOptions Type = Alarm, Trouble, ESP, Haz. Wx.,Problem, PM, Routine, Load Test, Other
MOptions Category = Engine, Generator, Controls, Fuel, Oil, HV Switchgear, MLG&W, Other
Options Engine = All, 1A, 2A, 3A, 4A, 5A, 1B, 2B, 3B, 4B, 5B, 1C, 2C, 3C, 4C, 5C, 1D, 2D, 3D, 4D, 5D, A Bus, B Bus, C Bus, D Bus, A&B Busses, C&D Busses, West Gen (001), East Gen (002)

Required Attributes = Type, Category, Subject

If time permits, I would appreciate any help possible.

BTW, I like the additional elcode.
  1422   Mon Sep 26 11:03:52 2005 Entry Guenter NowakGuenter.Nowqak@t-systems.atBug fixOtherV2.5.9-2error when searching for POST
is this an elog bug?
calling
http://midas.psi.ch/elogs/Linux%20Demo/?cmd=Find
(ELOG V2.6.0-beta4)
and typing
POST
in uppercase-letters
I get the error

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /elogs/Linux Demo/.

Reason: Error reading from remote server



--------------------------------------------------------------------------------

Apache/2.0.46 (Red Hat) Server at midas.psi.ch Port 80


doing the same thing on my elog installation (ELOG V2.5.9-2) gives the error

Die Seite kann nicht angezeigt werden.
Die gewünschte Seite ist zurzeit nicht verfügbar. Möglicherweise sind technische Schwierigkeiten aufgetreten oder Sie sollten die Browsereinstellungen überprüfen.

--------------------------------------------------------------------------------

Versuchen Sie Folgendes:

... (some text skipped, guenter)

Fehler: Server oder DNS kann nicht gefunden werden
Internet Explorer

if if dont type all letters in uppercase no problem occurs

thanks
guneter
  1421   Fri Sep 23 19:23:26 2005 Angy Dan Chitwooddchitwoo@uiuc.eduBug reportLinux | Windows2.6.0-b4Post appearing twice
We are having trouble on our logbook with posts appearing twice. Both posts contain the same ID number, time, etc. This most often occurs when the e-log entry is being written for an extended period of time (ie. more than 30 minutes), but I don't know if that is the root cause of the problem. It may also be related to posts that are edited after an initial posting. Could this be due to an improper setting in our config file?
  1420   Fri Sep 23 17:27:40 2005 Question ScottKsnkgak@yahoo.com Linux2.6.0elog fails to connect with "cannot get host name: Success" message
I can't seem to connect using elog: elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt it run fine through the web interface on http://<myhost>:8080/Servers I have URL = http://<myhost>:8080 in my elogd.cfg Any clues what I'm doing wrong? Thanks for any help. ScottK
ELOG V3.1.5-3fb85fa6