I am also experiencing the same exact problem as explained above. It only seems to happen when a part of the title has changed. I will include my config for an example. Make a few entries, then change the "Customer" paramater. Then try and edit an entry in the thread.

 Enable attachments = 1

Attributes = Employee, Customer, XXX-ID, XXXX Number, SCD, Type, Status, Folder Created, XXXX Received, Equipment Installed, XXX Carrier Up, Customer Carrier Up, QA Completed

Thread display = $Customer  -  $SLR-ID  -  $Type  -  $Status  -  SCD: $SCD  - XXXX: $XXXX Number

Propagate attributes = Status

Locked Attributes = Employee
Options Type = Activation, Termination, Change
Options Folder Created = Yes, No, N/A
Options XXXX Received = Yes, No, N/A
Options Equipment Installed = Yes, No, N/A
Options XXX Carrier Up = Yes, No, N/A
Options Customer Carrier Up = Yes, No, N/A
Options QA Completed = Yes, No

Entries per page = 100

Preset Text = $short_name @ $utcdate -
Append on reply = $short_name @ $utcdate -

Locked Attributes = Employee

Preset Employee = $long_name

Options Status = Open, Closed

Quick Filter = Status, Type

Type SCD = datetime

Summary lines = 0
Enable Attachments = 0
Suppress default = 2
Entries per page = 10

Suppress Email to users = 1

Display mode = threaded
Collapse to last = 1
Expand default = 0
Subst on reply Employee = $long_name 

Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x000646c7.

 Hi,

I have a MacOSX 10.6.7 laptop that periodically synchronizes my logbook with that on a Debian linux web server.  Both instances of ELOG are 2.9.0-2396.

When I create a new entry on the laptop, the indicated time stamp is correct.  When I click Synchronize on the laptop, the entry that gets mirrored to the Debian server has a time stamp exactly one hour earlier (in the past) on the Debian side.

Likewise, when I create a new entry on the Debian server, the indicated time stamp is correct.  When I click Synchronize on the laptop, the entry that gets mirrored from the Debian machine to the laptop has a time stamp that is exactly one hour in the future on the laptop.

This appears to be due to an incorrect handling of times with regard to "summer" (daylight savings) and "standard" time when mirroring between these two different machines.

Is there a straightforward workaround to immunize against this sensitivity?

Thanks!

Andreas

 1. It appears that some times find_thread_head is called with message references that do not exist. That is not good.

I put in a little check like this  before seeing if the message has an "in_reply_to" reference:

The line:

if (lbs->el_index[i].in_reply_to)

becomes:

if (i < *lbs->n_el_index && lbs->el_index[i].in_reply_to)
 

2. The trouble started when I deleted a message in the middle of a thread, which left the thread badly "connected" (references to a deleted message).

3. Also, when a thread is badly connected, it is a problem moving messages to a different logbook. ELOG complains that it cannot access the message (with the invalid reference). But ELOG should ignore it, since the message was deleted.

Soren

 Hi Maureen,

You write "Upgrading from 2.6.0" Is that version working on the same computer?
If so then its strange. Else try with one of the demo config files and see what happens, try different ports etc.

If the service is running it should work the rest too. I'm running it on a Win7 64 bit so 64 bit is not the problem....

Best

Per

I am in the process of upgrading from 2.6.0 to 2.9.0.  I am installing it on a windows 2008 r2 server which is 64 bit.  I am having a few issues and am just wondering if Windows 2008 R2 is support with version 2.9.0.  Is there anything I need to know about the installation other than just run the exe file?  So far I have run the exe file and installed the software, the service is running, however I cannot get into the application.  I do not have IIS installed, it does mention it in the installation documentation, is this a requirement?  Any hints or ideas at this point would be appreciated.  I am close I just need that last tweek.  Thanks

I am in the process of upgrading from 2.6.0 to 2.9.0.  I am installing it on a windows 2008 r2 server which is 64 bit.  I am having a few issues and am just wondering if Windows 2008 R2 is support with version 2.9.0.  Is there anything I need to know about the installation other than just run the exe file?  So far I have run the exe file and installed the software, the service is running, however I cannot get into the application.  I do not have IIS installed, it does mention it in the installation documentation, is this a requirement?  Any hints or ideas at this point would be appreciated.  I am close I just need that last tweek.  Thanks

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I get into the same problem in other circumstances such as when opening some threads (maybe because they contain "Reply-to" references to non-existing messages, but I have problems reproducing this on the test installation.

I should maybe also submit the incriminating thread.

Soren

Hello @all,

for a logbook I have also to set up a guest access. As I want to have a login page first opening the logbook,  I created a second logbook entry in the elog.cfg that points to the same subdir as the original logbook. The idea of this guest access is, that users who have no login rights can read selected items with selected attributes. Therefor I restricted the guest account with all available "Guest"-commands in the elog.cfg.

But this is not sufficient. Let's suppose I have an attribute called 'Accessibility' with options 'public' and 'private'. What I am searching for is a filter command for the list display, i.e. if an entry has the accessibility flag 'public', a guest sees this entry in the list and can access it. But if the entry has the accessibility flag private, the entry should not be displayed for guests but for users, that are logged in.

I read the administrator guide carefully, but I didn't found a command that provides for that. Does such a filtering command for the list exist? If not, is it possible to implement one?

Best regards,

Wolfgang Bayer