The following error occured during the addition of new user, first time this occured:

"Cannot send email notification to "xxx@xxx.com" Sender address rejected: Domain not found

Please use your browser's back button to go back

We are using version 2.7.1-2002. Could this be a version issue? When we loaded the new version, the browser GUI was scrambled and illegible using Microsoft Edge/Explorer and Firefox.

This error comes from your email SMTP server, not from elog. It complains about the email address xxx@xxx.com which refers to a nonexisting domain. Just read the message.

Stefan

I have just upgraded elog from 2.9.2 -> 3.1.3.

3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.

Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.

When running 2.9.2 on the same machine, all runs wel (attachment 2)

cfd file: (I only left in one logbook - they are all configured the same)

[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y

[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type

Any ideas on how to solve this?

Hi Andreas,

Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories (version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking and removing all the logbook files in the main directory version 3 now works.

Cheers,

  Yves

Hello!

First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.

However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?

Thank you and best regards,

Matej

I see the same problem exists on this board as well. Actuall it appears only the attribute fields are affected. The č character was incorrectly written to the log file from the subject field above, but correctly from the body text below.

Hi,

I have been using elog for a few years and it is a wonderfull software and has been one that I can't go without. So thank you very much for making it. 

After about a year, I upgraded to the latest version. I noticed that it causes the system to crash. It doesn't seem to happen that often. 

I have installed this on 2 machines, one Windows 10 and one on Windows 7. Over the last week I got one BSOD on each OS. 

The elogs have different configs and logbooks. One is a simple elog that doesn't have any attachments or anything funky. Just straight text.

Please see attached a screenshot of the Memory.DMP which has happned seconds after an schedule restarted the elog service on my PC. 

I will keep monitoring and see if will happen again. But I thought I log it here anyway.

Thanks.

Cheers.

Ales.