Hello all,

I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.

Does anybody have any suggestions?

Regards,

Philip

I guess the underlying problem is the long time these requests take and block other users.

I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.

Thanks for the quick response!

It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.

The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.

Is there no good way of differentiating search operations from others by URL?

Look for "&subtext=" in the URL

This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter

For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.

Would there be a simple way to redirect all URLs BUT the ones which trigger searches?

No, no and again: no.

Noted. Thank you for your time

Hi all,

first off all let me say, that I realy like this great tool. That is a lot of help for keeping our server documentation up-to-date. Thanks to all contributors for that.

I right here, because I actually have an issue with saving entries working with IE11 (but also in IE9). When ever I enter an entry, and click the save button, the page open a page with the text: "OK 1"   or the second attemp: "OK 2"   3rd  "OK 3" and so on (see screenshot). To get back to my Item list, I have to click the back button in the internet explorer. I also opens a lot of draft entries in my databases.  When I submit my entry, I don't have an issue, and the entry is saved correctly.

This issue doesn't happen when using Google Chrome.

Had anyone an simlar issue using elog with IE?  It would be great to have some help with that issue.

Thanks

Torsten

This issue should have been fixed in the new version 3.1.1. If the problem still persists, try to clear your browser's cache, since it might still have cached the old JavaScript files having this bug.

Hello Stefan,

thanks for you reply. I tried an ujpdate today to my old installation, but also after cleaning the IE cache, the problem consists. The same result is, when doing a clean new installation, with the default elog.cfg and and cleaned cache as well an IE that was reseted to defaults.  

I am running version v3.1.1 3f311c5 now.      Do you maybe have another idea, to fix that issue.

Thanks

Torsten

Do you have the problem on this Forum as well?

If not, then something is wrong with your installation. Like old JavaScipt files etc. Start with a fresh installation and you should be fine.

If you have the same problem in this Forum, let me know and I will further investigate it.

Greetings all.  A few ELOG users have posted issues with ELOG 3.0 and newer not working with a variety of MS Windows operating systems,.
I have also encountered a similar problem in my environment.

For the following operating systems:        
1) Windows XP SP3 (32-bit)           
2) Windows Server 2003 SP 2 (32-bit)
when either elog.exe or elogd.exe are run from command line or file manager, the operating system reports the program is not a Win32 application.

I have other test computers that succesfully ran ELOG 3.0, 3.1 and 3.1.1
1) Windows Vista Enterprise (32-bit)
2) Windows 7 Professional (64-bit) 

Has ELOG 3.x and newer changed in regards to support for MS Windows but is not documented on the
official ELOG documentation?

Any help would be most appreciated.

NOTE: The current production ELOG I use on Windows Server 2003 is 2.92-2475 but I would like to use the
features available on the 3,.x versions.  Unfortunately, I am not able to change my production operating system.
 

I recompiled the executables according to

https://msdn.microsoft.com/en-us/library/jj851139.aspx

and replaces the elog311-1.exe distribution. Can you try if it works? Unfortunately I don't have a XP machine here.

/Stefan

Thank you for recompiling ELOG.  Unfortunately, there is no change in all the test machines
I ran the newly compiled ELOG 3.1.1-1 on.  I will use the 2.x version until our systems move
to a new operating system or I can find someone in my IT department who knows how to compile programs
from the source code. 

If anyone else has suggestions or could compile the source for us to try, please speak up.  There are
many installations of obsolete operating systems in production :
 

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

Apostrophes are encoded as "&#39;" inside the CKEditor used by elog, which sents the raw HTML text as email notification. You can test this by pressing the "Source" button at the top left menu in the CKEditor, then you see it. In my mail program (both Apple Mail and Thunderbird) this HTML enocding is correctly shown as the original apostroph, so I suspect that your mail program has an issue interpreting HTML encodings.

Hi,

The default email subject line for a new entry is: "New ELOG entry", and the default email subject line for an edited entry is: "Updated ELOG entry". However when we set "Use Email Subject", both new entries and the updated entries use the same email subject. Is there an equivalent of "Use Email Heading Edit" for the subject line? I tried "Use Email Subject Edit", to no avail.

Thanks in advance,

e.

Since there were no responses, I decided to make good use of the fact that the software is thankfully open-sourced. I modified elogd.c and added just a couple of lines to get what I wanted.

22245,22250d22244
<    if (old_mail && getcfg(lbs->name, "Use Email Subject Edit", subject, sizeof(subject))) {
<       i = build_subst_list(lbs, slist, svalue, attrib, TRUE);
<       sprintf(str, "%d", message_id);
<       add_subst_list(slist, svalue, "message id", str, &i);
<       strsubst_list(subject, sizeof(subject), slist, svalue, i);
<    } else

These lines just follow the comment line: /* compose subject from attributes */

Thanks, I added your code to the distribution and updated the documentation.

hello, in my spare time, I try to fix some bugs, typo, and update for Indonesian translation

Thanks, I included your changes in the distribution.

URL causes elogd to crash when a global password file name doesn't match any group's password file name. 

The offending URL is copied from the address field of the browser after sorting a logbook by on of the fileds.

After login out and using the copied URL, elogd shows the authentication dialog and then crashes after the credentials are submited.

Some debugging point me to a NULL pointer on the following instruction in line   25502  of elogd.c :

  if (lbs->pwd_xml_tree) {

The work around was to name the global password file as the password file of one of the groups.

I could not reproduce your problem. I can only fix it if I can reproduce it, so let's agree on a common test base. May I ask you to do the following:

• Download the most recent elog version from bitbucket and compile it
• Create two new logbooks "demo1" and "demo2" with minimal configuration, but using yor global password file which differs from the group ones
• Send me step-by-step instructions how to trigger the problem, including your elogd.cfg file and your password files (of course with fake accounts)

If I can reproduce the crash, I can fix it.

Hi,I'm new here :) and want to install elog on linux suse. could you please tell me, how can I find this following lib dependency.

linuxsuse#rpm -i elogi386.rpm
                 error: Failed dependencies:
                  libssl.so.6 is needed by elog-3.1.0-2.i386

Thanks in Advance

If you Google for "libssl.so.6 is needed", you will find for example this site: http://ubuntuforums.org/showthread.php?t=2096126 , which tells you to install the libssl-dev package.

Can you provide simliar guidance for Scientific Linux release 6.6 (Carbon, 64 bit version) as I get the "failed dependencies" after installing

openssl-devel package and I tried linking /usr/lib64/libssl.so.1.0.1e as libssl.so.6 in both /lib and /usr/lib ? -jph