ELOG Forum

To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.

Soren

Indeed it was the JavaScript line

if (document.form1.Number.value != '- garder les valeurs d'origine -') {

which caused the trouble. The "'" character closed the string '- garder les valeurs d', which caused an exception. I changed it to

if (document.form1.Number.value != "- garder les valeurs d'origine -") {

and now it should work fine.

Thanks a lot for changing that. Now French should work as well.

Soren

66758

Sat Mar 13 09:40:37 2010

Stefan Ritt wrote:

Mirza Ehsan wrote:

I am using eLog ELOG V2.6.1-1681 which has 7 log books under 8 categories. Out of 7 log books, 2 are daily used. It happened that two weeks back. I modified information on two log books which were not used for quite longtime. Hence using CONFIG, I updated these log books, changing text etc. After that eLog in general started giving error. Any time when we click SUBMIT button in any log book, eLog shows page not found. That submit crashes eLog and as a result elogd service stops. Restarting elogd service, eLog operation comes back and the log which I submitted was actualy saved. Difficulty is that this problem is happening with every single submit action.

I searched forum and learnt that upgrading eLog to newest version 2.7.8 will solve this problem. Upgrade created more problems, I was not able to open any log, authentication was not accepted. I restored that backup and went back to previous version. eLog started working but with submit error.

If any one can help me in fixing this problem

I propose that you get 2.7.8 working. If the authentication fails, try do do password recovery, or recreated the accounts.

Thanks for the reply. I found problem with existing version. I opened log book group without opening log book details in configuration, that is why at submitting or opening elog was not able to find log book for that group and was getting lost.

Regarding moving to 2.7.8, I want to know that in this new version file location for pwd and log books will remain same or are changed. If changed then I have to change location manually. Also how I can perform password recovery.

66757

Fri Mar 12 19:30:53 2010

Re: Fail to connect to SMTP server on WinXP but works on Win2K

Stefan Ritt wrote:

David Spindler wrote:

Fantastic. I forgot the icon and when I resent nothing was left.

Here goes again!

I have been running Elog for years on a Win2K machine with no email problems. I have been forced to move it to a WinXP machine and I always get this message under WinXP: "Error sending Email via "netsvr10.prod.company.com": Cannot connect to server"

I noticed this a long time ago but was not concerned until I wqas forced to use WinXP. We have years of data in the Elog and to lose the use of it would hinder our operation a lot.

Here is an entry from the elog.log file when it worked under Win2K:

28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} NEW entry #0
28-Oct-2009 18:28:38 [609144@199.82.127.9] {Generals} Email from <christophermeyer@fedex.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
28-Oct-2009 18:28:42 [609144@199.82.127.9] {Generals} 220 netsvr10.prod.company.com -- Server ESMTP (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit))

Here is an entry from today's elog.log under WinXP that does not work.

06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} NEW entry #0
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com
06-Mar-2010 11:48:23 [117361@127.0.0.1] {Gbld} READ entry #1612

We use an SMTP server without authentication.

I picked a bad example with an IP address of 127.0.0.1, but it is the same as a valid IP address such as the working entries above or the entry below.

06-Mar-2010 10:31:43 [117361@199.81.166.149] {Gbld} READ entry #1691
06-Mar-2010 10:39:10 [117361@199.81.166.149] {Gbld} NEW entry #0
06-Mar-2010 10:39:11 [117361@199.81.166.149] {Gbld} Email from <david.spindler@company.com> to david.spindler@company.com, SMTP host smtp.mail.company.com

The only idea I have is that your Windows firewall prevents outgoing network traffic on port 25 (SMTP). You should put an exception into the firewall rule. You can try that by opening a DOS box and entering

telnet smtp.mail.company.com 25

if you see a reply, the traffic is allowed. If it blocks, the firewall prevents this kind of traffic.

I have tried setting up a VM (VMWare) with W2K and testing it out on both a W2K and WXP host. In both cases the Elog successfully sends emails. I don't know if this helps, or not.

66756

Fri Mar 12 16:18:20 2010

Re: Last 3 days of log entries

> David send me his modification and I put it into the main source code, so it will be contained in the next Windows 
> version.

I made an interim 2.7.8-3 version which contains the fix and can be downloaded from the web site.

66755

Fri Mar 12 13:54:14 2010

Re: Elogd crashes when closing more than ten entries

Cliff Shaw wrote:

Hi Stefan,

I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.

As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed.

Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.

Unfortunately I cannot reproduce your error. In my test set-up it works fine, so it might be related to your configuration. Can you send me your config file, a zip with the needed logbook entries (xxxxxxa.log files), and a recipe what to click exactly in what order.

66754

Fri Mar 12 12:59:25 2010

Ulf Helmersson wrote:

This programing have stoped working, I guess after last update.

Elog is running on Solaris.

Ulf Helmersson

Options Type = Journal Article{1}, Proceeding Article{2}, Book chapter{3}, Book{4}, Patent{5}

{1} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Abbrivated journal name, Volume, First page, Year, Elsevier format, AIP/APS format, IOP format

{2} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Conference name, Place, Country, First page, Year, Month.Days, Volume, Elsevier format Proceeding

{3} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Book Title, Editors, Publisher, Place, First page, Year, Elsevier format Book chapter

{4} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Publisher, Place, First page, Year, Elsevier format Book, IOP format Book

{5} Show Attributes = Type, Logged by, Key words, File, File path, Authors, Title, Patent number, Year, First page, Elsevier format Patent

The option

Show Attributes =

has been changed to

Show Attributes Edit =

to distinguish between normal entry display an edit mask. So please adjust your configuration file and everything will be fine again.

66753

Fri Mar 12 12:49:39 2010

difficulty with slow connections (was Re: frequent crashes on SL4)

> Hi, Stefan.  When someone using a satellite connection tries to upload an attachment *or* edit a long entry, it fails and they are presented
> with an "Internal Server Error."  This is a huge improvement over the previous behavior of crashing elogd, but we were wondering if there is any
> hope of improving this further so that one can edit large entries or upload attachments over a slow (in this case, satellite) connection.  Do
> you have any ideas or plans on working on this further?  Apparently ELOG is the "only" service this user has trouble with from  home.

There was a timeout of 1 sec. in the elogd daemon, which probably is too short for a satellite connection. Unfortunately I have no satellite here 
around to test it, so I "blindly" increased it to 6 seconds in the current SVN version. Please give it a try. You can increase this yourself, its here 
in the code at (Rev. 2291) line 28270:

   FD_ZERO(&readfds);
   FD_SET(_sock, &readfds);
   timeout.tv_sec = 6;            <----
   timeout.tv_usec = 0;
   status = select(FD_SETSIZE, (void *) &readfds, NULL, NULL, (void *) &timeout);

so you can change the 6 to 10 or so. The disadvantage of a large value is the following: Suppose you submit an entry, and in the middle of the 
submission your browser dies (or the user closes it). If you have a timeout of n seconds, the elogd server will wait that time until it closes the 
connection. During this waiting time is cannot respond to other request, so it might look dead. That's why we should not make it too long.

- Stefan

66752

Fri Mar 12 12:28:36 2010

Re: could not get the threaded display working

FX FRERE wrote:

I have been trying to get the display mode into threaded by default, it does not work on any of my logbooks. I saw related threads in this forum but none gave me a solution (unless the 2.7.8-2282 is available for download).

The display mode is taken from the configuration option "Display mode = ..." only the very first time a users accesses a logbook. When the user switches to any other mode (summary, full) by clicking on the according menu option, the new mode is stored in a cookie in the browser and overrides the "Display mode = ..." setting. Maybe that is what you see.

Goto page Previous 1, 2, 3 ... 381, 382, 383 ... 805, 806, 807 Next

ELOG V3.1.5-3fb85fa6