Most mail delivery systems have a maximum size for attachments. In the past, if an elog attachment was larger than this size, the email server refused to accept this email and no notification is sent. Now one can specify the maximum allowed email attachment size with

Max email attachment size = <n>

where <n> is the number of bytes. If an email attachment is larger than <n>, the attachment is not sent with the email notification, but rather replaced by a link to the elog server for that attachment. By clicking on the link in the email notification, a browser will then open and download the large attachment. For each each elog installation, the admin has to figure out what the maximum attachment size of their SMTP server is, and then put this number into the elogd.cfg setting  above. For most installations, the default of 10 MB will just work fine.

Stefan

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.

The dump does not help me much. I need to reporduce the problem in a controlled environment.

Stefan

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 "&#268;" and "&#269;". 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.

Actually unicode characters are converted by your browser into HTML code (such as &#268) where 268 decimal = 10C hex. elog just writes to file what it gets from the browser. When an existing elog entry gets shown by the browser, the code is translated back to the character. Why do you care what is written to the log file? If you use scripts or so to parse your log files, you have to adapt them to correctly decode HTML encoded characters. This is necessary since log files are ASCII and thus encode one charecter in one byte. Your Slovenian characters require two bytes in unicode, so some kind of "special" encoding is necessary.

Stefan

Hello Stefan,

thank you for the reply. The explanation does not solve my problem though. 

1) Could you elaborate, why the body text field CORRECTLY writes the character while the attribute fields write and display the HTML code?

2) If I understand you correctly the problem also contradicts your statement: "When an existing elog entry gets shown by the browser, the code is translated back to the character." and is visible in this very post. The subject field writes and displays it incorrectly, while the body text writes and displays it perfectly OK. See: Č č ?

3) We do not use any scripts. If we were to use a script to replace the HTML code with the actual character, the attribute fields would still display È instead of Č. Also, I have no idea how to write such a script. :)

Thanks,

Matej

In the attribe filed, HTML code is not allowed for security reasons. If you want to bypass this (on your own risk), put

allow html = 1

into your config file.

Stefan

This tag does not change the behaviour, but I have noticed that I only have the problem in Chrome and Firefox but not in Internet explorer.

Matej

To conclude this topic, we sadly can't use the characters č and Č propperly in the application. I have marked the problems in the screenshots below:

red square - the user name is changed immediately after saving. It is also written into the log file in the attribute "Lovec" preset as $long_name. This cannot be displayed correctly even when using HTML and the text tag.

orange sqare - This appears in translated menus and in the attribute "Preža" where the options are listed. The character is written correctly in the translation and the log file, but is displayed incorrectly as È and è.

pink square - After using the script on this attribute "Opis" to insert the html text tag the field correctly displays the characters. The minor problem remains when exporting this to a csv file where the html text tag remains.

I have no idea what effort it would take to change the ANSI background of the application to UNICODE and I can't really expect you to do this. On the other hand most modern applications go through this step eventually, mostly because of the Chinese and the Russian markets.

Thanks again for the otherwise great product, I guess we'll have to start using letters c and C instead. Best reagards,
Matej

I had time to look at the problem in detail. I found that a &#xxx; sequence is not correctly identified as HTML code, and thus displayed in plain when used in an attribute. I fixed it in the current git revision and now it looks find in attribute (see attachment). Can you give it a try? Please note that you need "Allow HTML = 1" in your config file.

Great news Stefan! Please pardon my ignorance, but I was not able to "make" it. I have no idea how to run this on Windows where the current POC log resides.  

Easiest is to install the Cywgin environment (www.cygwin.com) and there select the C compiler package which installs also "make".

Phew, made it, sort of. Had to copy the contents of the mxml folder from an older version, the folder was empty in this git. I also had to change the SSL to 0 and then it compiled without errors plus I had to copy the cygwin1.dll to the folder to make the service run.

So yes, I can confirm that manually inputting the Č in the attribute field now works correctly. Excellent! This solves the pink problem then. Any similar solutions for the red and orange ones?

Thanks,
Matej

Pink problem: Yes the CSV export preserves the html tags, but what to do. CSV files are plain text with 8 bit characters. Unicode characgers have to be represented with more than one byte. So either HTML encoding or some special escape sequence encoding. If you like the second better than the first, I'm sure you find some conversion program on the internet.

Orange problem: No clue how C is converted to E. Maybe depends on the encoding of your browser? There is a elog option "charset = xxx" with which you can play.

Special characters in use names should now work in the current version.

That's great, Stefan, it works indeed. I tried fiddling around a bit with different charsets but haven't been succesful yet. I'll play around some more.

Hi,

I recently upgraded elog from 2.7 to 3.1 and have a hard time to insert images inline. The attachements work just fine. I am certain it is something silly, but I cannot figure it out.

1. In edit mode, I click the image icon
2. A pop-up "Image Propertied" shows with two tabs "Image Info" and "Upload" (selected)
3. Click on Browse button and select an image
4. Now
   • if I click OK, I get an error "Image source URL is missing".
   • if I go to "Image Info" tab - what URL am I supposed to enter, 68757/<1> ?

I found an old thread elog:68410 (from 2016) but could not find a solution that would work for me. Where does "Preview attachments" option should be inserted? In the global section?

Hopefully there's a simple explanation for this

Piotr

Before you click OK on your point 4, click on "Send to Server".

Stefan

I did just that. The image was properly send to the server (it appears in the attachement list). However clicking OK still produces "Image source URL is missing".

What is the URL that refers to an attachment? I've tried 68759/<1> and 68759/1 and even elog:1234/<1> (where 1234).

Got it to work.  Removed "Preview attachments = 1" from the global section.

Thanks for your help.

Piotr

Hi!

Tryed windows an linux version. On booth the "Register new User" dialog is not displaying a password line.
so what password is used for the new user? Further the user can't change his password, because he didn't know the old one.

And if an admin user trys to change the password of an other user, a error is displyed that the old password of the admin user is
wrong and nothing happens with the password of the non-admin user.

elog console (admin user awrzkrz changes the password of testuser1):

GET /demo/?cmd=Config&config=TestUser1&cfgpage=1&admin=1&cfg_user=TestUser1&active=1&new_user_name=TestUser1&new_full_name=TEST+User&new_user_email=test%40heaven.org&cmd=Change+password HTTP/1.1
Returned 1032 bytes
GET /demo/?config=TestUser1&newpwd=test1234&newpwd2=test1234 HTTP/1.1
Returned 20 bytes
GET /demo/?cmd=Change%20password&config=awrzkrz&fail=1 HTTP/1.1
Returned 1215 bytes
 

Thanks for help!

Have you configures user-level access via

password file = anyfile.pwd

Can your elogd server write to that file?

If yes, can you please post your config file?

Stefan

Hi Stefan,

thanks for the quick reply.

Yes, i've configured user-level access. Here is my cfg:

[global]
port = 9191
Usr = abc
Grp = abc
SMTP host = mail.xy.at
Protect Selection page =  1
Password file = elog_pw.xml
Logfile = elog_log.txt
Logging level = 2
Admin user = User1, Admin
Self register = 2
Restrict edit = 1
Allow password change = 1

[demo]
Theme = default
Authentication = Kerberos
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Oth                                                          er
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

And, yes, the password file is r7w accessible for the elogd:
[root@localhost logbooks]# cat elog_pw.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- created by MXML on Tue Feb 27 14:54:52 2018 -->
<list>
  <user>
    <name>Admin</name>
    <password encoding="SHA256">3c2QQ0KjIU1OLtB29cl8Fplc2WN7X89bnoEjaR7tWu.</password>
    <full_name>Admin</full_name>
    <last_logout>0</last_logout>
    <last_activity>0</last_activity>
    <email>admin@hell.org</email>
    <inactive>0</inactive>
    <email_notify/>
  </user>
  <user>
    <name>TestUser1</name>
    <password encoding="SHA256">3c2QQ0KjIU1OLtB29cl8Fplc2WN7X89bnoEjaR7tWu.</password>
    <full_name>User1</full_name>
    <last_logout>0</last_logout>
    <last_activity>0</last_activity>
    <email>test@heaven.org</email>
    <inactive>0</inactive>
    <email_notify/>
  </user>
</list>
 

br, Rainer

password file = anyfile.pwd

I'm afraid that there is something wrong because each user will be written with the same (hashed) password to the local password file,
irrespective of the given password within the "new User dialog".

So for instance, every user in my password file lokks like this:

    <name>TestUser1</name>
    <password encoding="SHA256">3c2QQ0KjIU1OLtB29cl8Fplc2WN7X89bnoEjaR7tWu.</password>
    <full_name>TEST User</full_name>
    <last_logout>0</last_logout>
    <last_activity>0</last_activity>
    <email>test@heaven.org</email>
    <inactive>0</inactive>
    <email_notify/>
  </user>
 

"password encoding" has got the same value for each user after creating them with their own passwords....

That's the main issue i have, because i don't know this password and can't set a known one....

frustrating....

any help would be appreciated

password file = anyfile.pwd

What happens when you don't use Kerberos authentication?

password file = anyfile.pwd

Yeah!!

That did it! I remove the line "Kerberos authentication" and now it works!

Thanks!

password file = anyfile.pwd

I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.

1. create new message
2. submit it
3. Edit this message again
4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
5. message disappeared from the list!
6. by clicking NEW message I found my lost one in the drafts, but all text was corrupted.

I've made small GIF presentation on this issue (attached, open in new window), may be this helps.

The message is not lost, but becomes a "draft". This works similar in most email systems. When you edit an email and son't send it, it stays in your "draft" email folder and does not show up in your "sent" folder. Same here. You are suppost to "submit" you entry, the "save" is just a temporary safety backup. If you do not submit (if you press BACK or your browser crashes), the entry is not submitted to the system, but stays around as a draft. If you create a new message, the system asks you to edit and finish your draft, so that it does not get lost. So always hit "submit" if you are finished editing a message, not just "save". 

If you want to see the draft message, they are rendered in red in the normal message list if you have

List drafts = 1

in your config file. No ide where your cluttering comes from. 

Stefan

Dear Stefan,

Thanks for quick reply.
I checked List drafts = 1 in config file - it does not show drafts in the list in my case.
Can it be blocked by any other option?
I have these options enabled:

Use Lock = 1
Save drafts = 1
List drafts = 1
 

Peter.

You might have to update to the current elog version. This feature was implemented in Dec. 2016. 

Stefan

We installed our elog from .apk in November 2017.

Version V3.1.2-bd75964

I suppose it already contains List drafts feature.

The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with 7 digit number at the end.

yes, that is exactly where I got this V3.1.2-bd75964 version!

Do you recommend to download it again from your site and compile?

Tell me your current seven digit number and I can check if your version is too old.

https://bitbucket.org/ritt/elog/commits/all?search=bd75964

Dear Stefan and Andreas,

We have updated our elog to V3.1.3-7933898, now I see the drafts in the list!

Thanks a lot for your help!

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

Dear elog community,

We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes

Locked by:
Draft:

But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.

How can I fix this?

Thanks,
Peter.

Drafts are message which somebody started to edit, but did not complete, like leaving the page without saving. If you don't like this, you can set "save drafts = 0".

The locking has a similar background. If you have locking on (vis "Use lock = 1"), then one person can "lock" a message, and other then cannot edit the same message. If you don't want that, switch locking off.

Best,
Stefan

Thanks for fast response!

I LIKE locking and saving drafts.
The only problem is that the locked message disappeared from the list.
This does not happen every time one left the editor, but sometimes.
I can send you the problematic message as it was disappeared, before I deleted Locked by and Draft attributes.
I can't imagine why it is not shown in the list.

I also experienced various sproradic issues with locking, so I usually keep it off.

Stefan