Datetime format with elog client, posted by Alan Grant on Wed Oct 26 16:39:38 2016
|
What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the
field's data parameter).
I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 |
Re: Datetime format with elog client, posted by Alan Grant on Wed Oct 26 21:41:42 2016
|
UPDATE:
As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when
I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including |
|
Re: Datetime format with elog client, posted by Alan Grant on Thu Oct 27 04:16:10 2016
|
I really appreciate your reply David.
There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating?
It sounds interesting. |
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Alan Grant on Thu Dec 15 15:42:06 2016
|
Hi Stefano.
This may or may not have anything to do with your specific problem but I notice you have the single word "date" as part of your
attribute name and Date is actually a reserved word in Elog. Although your attribute is not exclusively called "date" I have found that |
|
Elog crashes with null Username, posted by Alan Grant on Sun Dec 18 08:51:47 2016
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username
and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn
to these recurring lines in the log: |
|
Re: Elog crashes with null Username, posted by Alan Grant on Mon Dec 19 19:42:05 2016
|
Thanks for the speedy fix.
FYI, our other Elog instances which are running ealrier versions do not exhibit this problem, as I confirmed that entering null
ID/password returns "Invalid Username or password" as expected. This may be why it wasn't mentioned by anyone else before. Maybe something |
|
Duplicate entries, posted by Alan Grant on Thu Mar 16 15:15:34 2017
|
Periodically (rarely) on manually adding a record into Elog it generates a duplicate record with its own incremented ID and I don't know
why. I just delete the duplicate in the meantime but would like to know if anyone else has seen this and whether their is a answer/fix for it. Thanks. |
|
Re: Elog crashes with null Username, posted by Alan Grant on Fri Apr 21 05:27:35 2017
|
Are you using the current git revision Xuan?
Xuan Wu wrote:
We also meet this issue occasionally, |