Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?

I am using the latest version of Elog and i tried the 2.5.3 version too 
have this problem 

Thanks!

> Hi
> I have a problem here which the ELOG service get terminated unexpectedly
> on the Windows Server.
> Is there any way to debug this problem ?
> 
> I am using the latest version of Elog and i tried the 2.5.3 version too 
> have this problem 
> 
> Thanks!


I have found the reason when will it terminate ,
When a user is not found on the server will hang in version 2.5.3 and in 
version 2.5.4 it will terminate by itself as show below.

--------------logs
GET /?redir=&uname=ifcosad&upassword=jklasjd HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, 
application/vnd.ms-
powerpoint, application/vnd.ms-excel, application/msword, application/x-
shockwav
e-flash, */*
Referer: http://sinccbap2kp38.sq.com.sg:8877/
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; YComp 5.0.2.6)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0

D:\Program Files\ELOG>
-----------end of log 

here is the logs . And in version 2.5.4 , when i tried to  move some entries 
to another db and i get a xrelloc error 

GET /IFSOCC+Archive/?
Priority=_all_&cmd=Move+to&destm=IFSOCC+Current&s0=1&s1=2&s
2=3&s3=4&nsel=4 HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, 
application/vnd.ms-
powerpoint, application/vnd.ms-excel, application/msword, application/x-
shockwav
e-flash, */*
Referer: http://sinccbap2kp38.sq.com.sg:8877/IFSOCC+Archive/?select=1
Accept-Language: en-gb
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; YComp 5.0.2.6)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=aWZzb2Nj


xrealloc: not enough memory


Thanks !
Geo

Hello to all,
i'm running ELOG on FreeBSD 5.2.
We've noticed an issue where e-mail notification from ELOG seem to
have their arrival time in the future, looks like it's about 13 hours ahead.


E-mail gateway to which ELOG posts its e-mail shows this e-mail transaction:
--------------------------------------------
Received: from elogunixbox.somewhere.net ([x.x.x.x]) by  
mailunixbox.somewhere.net with SMTP id <143408>; Mon, 11 Oct 2004 12:22:43 
+1300
To: crypt0@somewhere.net
From: elogposter@somewhere.net
Subject: New ELOG entry
X-Mailer: Elog, Version 2.5.3
X-Elog-URL: http://elog.somewhere.net/somelogbook/47
X-Elog-submit-type: web|elog
Date:  Mon, 11 Oct 2004 12:26:28 -3736512
--------------------------------------------


The last line in that log seems to have some strange time zone offset
(-3736512)
Usually you'd see a GMT+13 (New Zealand time zone on summer time).


Here's ELOG's own logs of that same e-mail delivery:
--------------------------------------------
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Mailer: 
Elog, Version 2.5.3
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-URL: 
http://elog.somewhere.net/somelogbook/47
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} X-Elog-
submit-type: web|elog
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Date: Mon, 
11 Oct 2004 12:26:28 -3736512
11-Oct-2004 12:26:28 [crypt0@somepc.internal.lan] {somelogbook} Content-
Type: TEXT/PLAIN; charset=US-ASCII
--------------------------------------------

I noticed that there was a post talking about ELOG on MacOSx having some 
time issues, but nothing mentioning FreeBSD..

Any ideas?
Thanks to all in advance.
GL.

> Date:  Mon, 11 Oct 2004 12:26:28 -3736512

The timezone offset (-3736512) is obtained from the "timezone" variable, which
is initialized with the tzset() function inside elogd. See "man tzset" for
details. It looks like if the timezone on your FreeBSD box is not correctly
defined. 

Try to compile and execute following C program:

#include <stdio.h>
#include <time.h>

main()
{
   tzset();
   printf("timezone: %d\n", timezone);
}

This should print something like "timezone: -3600". If not, you might consider
defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
details about this.

Ok, i compiled the code below and ran it,
it prints out:

timezone: 134513644

but in BASH shell if i type DATE, then this is the output:
Mon Oct 18 09:44:00 NZDT 2004
so it does know about NZ time...

Anyone got ideas?

Thanks all.
G.


> > Date:  Mon, 11 Oct 2004 12:26:28 -3736512
> 
> The timezone offset (-3736512) is obtained from the "timezone" variable, which
> is initialized with the tzset() function inside elogd. See "man tzset" for
> details. It looks like if the timezone on your FreeBSD box is not correctly
> defined. 
> 
> Try to compile and execute following C program:
> 
> #include <stdio.h>
> #include <time.h>
> 
> main()
> {
>    tzset();
>    printf("timezone: %d\n", timezone);
> }
> 
> This should print something like "timezone: -3600". If not, you might consider
> defining the "TZ" environment variable. Maybe some FreeBSD expert knows some
> details about this.

Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?

I am using the latest version of Elog and i tried the 2.5.3 version too 
have this problem 

Thanks!

> I

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program. 

I fixed that in revision 1.496 (see CVS).

I have the following in a local logbook config: 
 
  append on edit = "\n\n[$date: $short_name]\n" 
 
When I upload an attachment to an entry, it appears like the page is 
getting refreshed in the browser and the 'append on edit' action is called 
again. This results in two appended strings in the text entry, one for the 
initial edit and one for the upload. 
 
Is this by design or an inadvertent result of uploading an attachment? 
 
My preferred handling of this - and perhaps a more intuitive behavior - 
would be to have the append/prepend actions happen once and only once for 
each edit or reply. 
 
BTW Stephan, many thanks for the great program. 

I fixed that in revision 1.496 (see CVS).

It would be nice if elogd would recognise the whole of this as a link
http://support.microsoft.com/default.aspx?scid=kb;en-us;138354 rather than 
just the first bit.

Has been fixed in revision 1.492.

> Has been fixed in revision 1.492.

Thanks, Stefan.

When creating new logbooks, I will create a single entry to test the  
configuration. After revising the configuration I want to delete that  
single entry and create a new one based on the revised config.  
  
elogd will crash every time upon deleting that single entry with an  
xrealloc error. Here are the syslog entries leading up to the crash:  
  
Oct  9 08:09:41 obstin8 elogd[20614]:  
GET /Support/1?cmd=Delete&nextmsg=0&confirm=Yes HTTP/1.1^M Connection:  
Keep-Alive^M User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux)  
(KHTML, like Gecko)^M Referer: http://localhost:8080/Support/1?cmd=Delete^M  
Accept: text/html, image/jpeg, image/png, text/*, image/*, */*^M  
Accept-Encoding: x-gzip, x-deflate, gzip, deflate^M Accept-Charset:  
iso-8859-1, utf-8;q=0.5, *;q=0.5^M Accept-Language: en^M Host:  
localhost:8080^M Cookie: urem=0; upwd=dDRubjNyBDI=; unm=mstolove  
Oct  9 08:09:41 obstin8 elogd[20614]: xrealloc: not enough memory  
  
This is on a Slackware 10 box using kernel 2.6.7. Elogd is accessed  
directly, not through an Apache proxy.  

This problem has been fixed in revision 1.491 and will be published in version
2.5.4-6.

We are trying to use ELog on Windows XP with Protection on individual log 
book and we unable to login after creating users even if we give correct 
user name and password login screen reappears. We are able to log in to the 
Elog when we use windows 98 Client we are running Elog on Windows XP and 
without password protection on logbook it is working fine with windows 98.

For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server

> W

> >

> > > We are trying to use ELog on Windows XP with Protection on individual log 
> > > book and we unable to login after creating users even if we give correct 
> > > user name and password login screen reappears. We are able to log in to the 
> > > Elog when we use windows 98 Client we are running Elog on Windows XP and 
> > > without password protection on logbook it is working fine with windows 98.
> > > 
> > > For win xp clients we are using winxp sp 1, ie 6.1 using a proxy server
> > 
> > First, upgrade to 2.5.4-5 (if you haven't done so). If the problem persists,
> > please start elogd on the server with the "-v" flag, capture the screen output
> > and send it to me by email so that I can have a look. Please send also your
> > elogd.cfg file.
> > 
> > - Stefan
> 
> Mr. Stefan
> 
> Following is elogd.cfg file text:
> 
> [global]
> port = 8080
> Main Tab = Home
> Protect Selection page = 1
> 
> [Daily Log]
> Password file = pwdfile
> Self register = 0
> Login expiration = 0
> Admin user = user
> Logout to main = 1
> Theme = bubbles
> Comment = Daily Call tracking and Issue Solving
> Attributes = Author, Type, Category, Subject
> IOptions Author = icon6.gif, icon7.gif
> Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
> 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

Mr. Stefan

We tried installing elog on another pc with almost the same configuration and are 
able to run it without any problems now.