> 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

> > I have a problem here which the ELOG service get terminated unexpectedly
> > on the Windows Server.
> > Is there any way to debug this problem ?
> 
> One can start the elogd server manually. So stop the service, and start 
> 
> c:\program files\elogd\elogd.exe -v
> 
> The "-v" flag shows all network traffic between the server and the browser. So
> maybe the last conversation before the crash can tell us something. Make a
> screendump of it and send it to me.

Here is the screen dump after we perform a deletion .
Another my the other thread , i show another dump when a move is perform

regards

GET /IFSOCC+Current/1?cmd=Delete&nextmsg=0&confirm=Yes 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+Current/1?cmd=Delete
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=dHBmc3Bk; SMSESSION=uvdhD3MUFAkDID0huNAnYhdoJxb
R74QgLwDYms+cAciPxtHlh0AIjpAqlgu6zcCeRzGLP3h7N/quulR8Z3KTWG0GQ7TQ9hdggdHTre8aoUW
YbAdTKbkWCJS/mDrfZbspmu/SiA0l4z1UEF7VAq79h78/ErlnUZPmQdbSacqYhD2Np3zqfy1GyMUtqGu
W2IW+iy5M4e7d6cIt9wkr5VmezTkmfzf8lE3RiYhE/bkjL7xBkDefFY/6tBcS28zoqBW1LhqZVnkq9FS
l5MS0vKiTDmiWusHkaD9iRaq1Gmk0lhzzvoQQ8n9ZD3ICzWAqEifRvMoqEWs1AkRA7ghEI6ONg27ffI+
F32gqXZqY7Je3I7tZOl2e4br2biwqRaQo8Rc2wztY4XxOaxdQVcbbzy1pcz9yRU6c+UTPaTNVj91o/mD
Cv+lojTVB6i6AVEqa7rgSObxGmcvYsmEIzFUqVwhgTkAYlCLMLp7Fy1HzWVj5u14bYhq53kGJaqa+SKE
FejtwlUWj7cgTkNLubCAStWUyAYwNeqDyVaYFz6HapDiXrpRNtn0cydS2zcJ1kfynloBWBp1f1vbW3U6
bCZEp6GQOUXSyWuGyP/k/umB9JrfBkstCoiou3pIWNG1Sf7Ni0+vLyaZFIt5YEDdkb3TXIZlIUjAFOsk
t3KVnfdtomNoE6cvsFIG9kJxCr6b7TIJAS+RxGQUYmHCK6R1oIUx9ZL8qXnjvDY2dGjyZg5aCYUx8smh
3DOO7WykAqEiPcNt7I1K4kwX1E+Eu5d/Y5X+qEZ553H4wNnlA/nXod374ksQ2AFqK9HVomVIi9AJg9sO
6ygrsRDArVPMjnzKatCb8yNTnor4dphH18XoANpvbvkmIUSRh+gwHNznLGE1blbfiOrxhXNVBVmfl1iU
Yts2NTkEQu4xwnooDA7YZ


xrealloc: not enough memory

I am not sure I understand your bug report.

I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?

Cheers, Andreas

Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.

You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX  The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message

Well, in my example the ID link worked just fine.

There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem.

Cheers, Andreas

As Andreas said we have to reproduce the problem. What is special in your case is the elog:SequencerEvents/XXXXX. This is non-standard and must be created through your configuration of elog or by an external script. I just guess that you have something like

Preset ID = elog:SequencerEvents/#####

which causes elog to preset the ID with the above string. Can it be that you just put five hashmarks in the preset?

Stefan

ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX format and it indeed had a silly hard coded length of that string.

Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog

Thank you all for your kind responses. Please consider this thread resolved: no bug in elog