Hi

I am having a little problem with e-log that I can easily reproduce.

I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.

So this only happens when I am not observing the input formats or the mandatory fields.

This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.

Soren

Hi Stefan,

I've been slowly moving threads, and twice now so far (and reproducably) had elog crash.

In each case, it is trying to move a thread with more than 24 entries; it copies the first 24 entries, then
crashes with "Segmentation Fault".  It does not erase the lock file /var/run/elog.pid

I have got around this by manually copying the entries beyond no 24, then deleting the thread entry by entry.

I am aware that I have an old and limited machine (586, 256MB RAM, running Slack 10), and at first I was
"content" to write it off as that; but when it crashed for the second time at exactly the same entry (the
twenty-forth) even though the size of the entries would have been significantly different, I wondered if there
was some factor within  elog that could affect this.

I've not tried it with Copy to:, but imagine it will also be affected as the only difference with this and Move
to: is the deletion of the thread after all the entries had been copied.

Hi Stefan,

I have a thread of 70 entries.  I added another entry, which was saved, but elog crashed.
It would restart, but crash every time I then tried to access that 71 entry thread.

By editing the yymmdda.log files to remove the latest entry, all was well again.
Add a test new entry (much smaller) also crashed elog as before.

If it is any help, this is the error message I caught on a console:

src/elogd.c:703: xrealloc: Assertion `*((unsigned int *) (temp + old_size)) == 0xdeadc0de' failed.
./log: line 1:  3123 Aborted    

Now I have got around this, by ending that thread with reference to a new one to continue, but is this to be
expected?  

If this is something (like memory allocation) that would have been in hiding from the start, I cannot imagine
that it is likely to be hit often enough to actually "bug fix" - it might, in any case, cause problems elsewhere.

In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.

Hi all !!!

i have just updated and 2.9.2-1 elog instance, and i have problems with the kerberos configuration.

I was surprised to see on the logs, that the 3.0 daemon was refusing to start because the system

config has kerberos listed as an authentication method. I saw on the logs that the current daemon

didnt have kerberos support compiled in.

Ive seen that there is ldap support, but couldnt find anything about configuring this auth sytem, does

amnyone have any example i could check ?

Did i have to use a patched version ? or compile it on my own ?

Regards

Hi, 
my elogd crashes sometimes when I click on the "Change config" button. What info should I collect more than below/attached?

In windows EventViewer I see this printouts:

###
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:25:30.000000000Z" /> 
  <EventRecordID>28059</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WER9155.tmp.WERInternalMetadata.xml</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_08bd38b0</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>0</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>
###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:47.000000000Z" /> 
  <EventRecordID>28058</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>1568</Data> 
  <Data>01d2e9c028b88983</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>7232f1e4-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Windows Error Reporting" /> 
  <EventID Qualifiers="0">1001</EventID> 
  <Level>4</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:24:07.000000000Z" /> 
  <EventRecordID>28057</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>108889037262</Data> 
  <Data>1</Data> 
  <Data>APPCRASH</Data> 
  <Data>Not available</Data> 
  <Data>0</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data /> 
  <Data /> 
  <Data>C:\Users\hognik\AppData\Local\Temp\WERBE94.tmp.WERInternalMetadata.xml
C:\Users\hognik\AppData\Local\Temp\WERCA4D.tmp.appcompat.txt triagedump.dmp
C:\Users\hognik\AppData\Local\Temp\WERCB77.tmp.WERDataCollectionFailure.txt</Data> 
 
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_elogd.exe_9ef84f861b91d5afaf68864978184ca611e7a22a_d4f2c951_0a4ff4e6</Data>

  <Data /> 
  <Data>0</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data>4104</Data> 
  <Data>94c2d6a18797708666faf33a7273855a</Data> 
  </EventData>
  </Event>

###

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2017-06-20T12:23:53.000000000Z" /> 
  <EventRecordID>28056</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>NIKLAS</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>elogd.exe</Data> 
  <Data>0.0.0.0</Data> 
  <Data>58f9c864</Data> 
  <Data>c0000005</Data> 
  <Data>00064eea</Data> 
  <Data>2338</Data> 
  <Data>01d2e9baf6174f0f</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>C:\Program Files (x86)\ELOG\elogd.exe</Data> 
  <Data>5206c994-55b3-11e7-826a-e4b3181bd6c1</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>
###

> Ooops, I just realized that the Windows 2.2.3 distribution contained the old 
> (2.2.2) executable for elogd.exe. I apologize for that. I have updated the 

that's ok. i just it was driving me nuts there for a while...everything is fine now...

i've tried other web based msg boards, but i keep coming back to elog...

Stefan - Just to say that this is an excellent piece of work well done.

I have just started an internal company Elog server, couple of 
clarifications :

1) is there a way around seeing the password in text when self regestering, 
if I turn this option off when the user changes his password will this 
password still be seen?

2) I have changed all the files to be owned on my RedHat Server by the 
user:group as elog:elog and set and moved the logbooks to another directory 
other than in /usr/local/elog namely /home/elog/logbooks, my concern is is 
I was to upgrade to a newer version would it be a simple install over the 
top? any caveats?

thanks again an absolute dream program.

kind regards Aamir