I forgot to mention, I also have Password file line in elogd.cfg file. Because without password file line, I wouldn't get login screen. I know my test account is not in the main.pwd file. I believe elogd does go to kerberos server to compare password. I just don't get why I get invalid username and password when I entered correct password, while kerberos error (expected) when I enter wrong password.  

Authentication = Kerberos

Kerberos Realm = xxx

Password file = main.pwd

 It's resolved.  I read the documentation again, and found out my mistake. I didnt have username defined on password file. 

 I haven't found anything in the forums about this. Apologies if its a duplicate.

I am fairly familiar with ELog, use it for multiple purposes on 5 different Virtual Servers at work. 

Currently looking to do some updates to one of the instances with the Date Type setting.

We have 17,000 entries all which have had manual entries for a Date Attribute for the last year and 8 months.

Due to regular entry errors on part of our contractors using it, (Eg: using "Aug" instead of "08", or using "-" instead of "/"), I want to change over to using the date type attribute (Type <attribute> = Date).

However the problem i found, the moment i save this in the config, and go to the list of entries, the date has changed on all of the entries to 12/31/1969. Which is BAD for our operation. So after removing the Type Date Setting the dates go back to normal.

Is there anyway to retain those dates so they display as they are and then only new entries would fall under the new date type setting?

Syntax manual didn't help much for this issue.

 Hi Garret,

Why cannot you just use $entry time ?  It uses the date that the entry was made which appears as the first line of every elog entry -

[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]

MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
 

You can use 'Time format = ' to get the date to display in the format you like.  You will see I have posted an issue about 'Date format = '.  I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread.  I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.

Of course I may have mis-understood your requirements.

 Tried using the Time format setting, however I only want the time to be selected, so when i enter the datetime type it shows the date and time.

If there was a way to just have the time to be drop down menus vs the date and time all together, I would find that helpful.

As for the "$entry time" suggestion, it only serves to log the exact time the entry was made into elog. Where as I want it to be manually set.

In this example we've created an sql script to pull information from an oracle database, which then creates an elog entry.

We have multiple fields which are populated and locked so only admin can edit them.

Our contractor then edits the entry with a date / time / location, and a few other things.

the Date and Time are separate attributes. We'd prefer to keep it like that just because of the other scripts that run on the elog entries, (pulls day by day reports and formats and calculates summaries in excel automatically).

Any other suggestions would be helpful.

Thanks for your reply.

 Hi,

I am experiencing repeated crashing of the elog daemon.

If I go into select mode while in threaded view, I can select an entire thread by selecting the top entry.

When I do so then press the Edit button, the server crashes.

I have to manually restart it. Syslog shows no error.

This does not happen under Summary or Full view.

Running Ubuntu 12.04, ELOG 2.9.2-2455

I can provide my elog.cfg if necessary.

Cheers!

Louis

P.S. i just crashed the forums ELOG following those same steps!! Sorry!! At least it was restarted in no time.

Hi All,

I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full view with attachments visible. If I shorten the name all is fine.

The crash report screenshot is attached. It looks like a too small buffer (?).