Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 546 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  513   Sat Mar 27 18:52:16 2004 Warning Charles DuncanCharles@YorkU.CAQuestionLinux2.5.1-1 Debian LinuxRe: Elog Utility
> > a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> > use the -p 8080 option with elog. I was able to get it to work when I 
> > moved my server to port 80.
> 
> That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
> newest version from release 2.5.2 issued today.
> 
> > b) I cannot get elog to work with and attributes or logbooks that contain 
> > spaces. Please refer the the following example:
> > 
> > elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> > Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> > Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> > a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> > Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> > Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> > Change Description"
> 
> There was also some bug which has been fixed, plus you need following syntax:
> 
> elog -h ... -p 8080 -a "Station Number=CC001" ...
> 
> note the "" are around the whole attribute=value string, not only the attribute.

Steve,

Thank you for the updates!!!

everything works great... -p 8080 and all my attribs get set. 

The only part that does not work is -l "Log Book" the -l variable has to stay as 
one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
word and fails.

-Charles-
  514   Sun Mar 28 12:45:45 2004 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.5.1-1 Debian LinuxRe: Elog Utility
> The only part that does not work is -l "Log Book" the -l variable has to stay as 
> one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
> word and fails.

I fixed that as well, please obtain the updated version at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elog.c?rev=1.20

Let me know if you cannot compile the C file and need an executable.
  68687   Fri Sep 15 15:16:42 2017 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux3.1.2Re: Elog System Requirements

Hi Alan,

we run our ELOG server (38 GB Logbook data in about 50 logbooks dating back up to 16 years) on a virtual Linux box.
The memory is important, since ELOG scans through all entries and creates an index at start-up. But we have only about 6% used out of 2GB: ELOG is not very demanding. If you have many and large pictures attached, then "convert" needs a bit of memory to work with.
Since "elogd" is a single task, you will not gain much from many CPUs. File IO is often a limiting factor: we've tried a while to run the logbook data on an AFS directory, and that did not turn out well. A local disk is best, an NFS disk works fine as well (in our case).

Cheers, Andreas

Alan Grant wrote:

In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome.

 

  738   Fri Oct 15 08:15:38 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.5.4.5Re: Elog Service Terminated
> I
  739   Fri Oct 15 09:38:51 2004 Reply Geo Geogorilla_geo@yahoo.comBug reportWindows2.5.4.5Re: Elog Service Terminated
> > 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.

Hi 
It says not enough memory ..
May i know what is the min config ? i am running on a server with 512mb of ram.

Below is the screen dump , last action , i am doing a move .
regards


GET /IFSOCC%20Archive/?Priority=_all_&cmd=Move+to&destm=IFSOCC+Current&s0=2&s1=1
&nsel=2 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%20Archive/?select=1
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; YComp 5.
0.0.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: SMSESSION=gwcUsAfDyITnesMpbzOdnbiETbAhZ1hysT2HnwE7WfO6jIHkENkdIQ+CAIgsw6
Q5mcqulHlb/0oMZFmquKY/2EEVRKqZ/lVAhiAfjYw7zN3ET1D4xULgAzNGwMp2bZjBAVrlnyWr65ffCc
9OpoiyMeOQVbGmp62TAxTRCoRBcp6r/h0QZzyVQiMt7BOU5mvq1t7WzJuEzlGoNoes7R0iKImJkIfPIu
l0IETa6Jy/n+BdZ+dYsk0lpkZD+snvc9I/kvDTOo9OOYjhs40+ZYkT++/c77ngivzjO5/0KyMnD7KbZF
ZbkyMaNmKYc8y4tnwLk652E1K++D64tVdV/5i+C6F1LktT6wPDDFrCxpVtzNawW7XAb+U38LBUsS6KbZ
XOYOLnYDrB3DUz40Xxzcz/w5k0AH55SlxqWu3r+3qx5X1qB+juyiEXiLcWfNRH2AWmGtAGYyrXbQa2V+
MgRDW8Gf/h4Gp1i8HtQt+5FYa9lWrTkwH/SDpkTVgvdqqoxjHHBAVuv4sqDHSrYlkbFuvR3hnZSZANaz
V1GOT6J5xhwmQvBDl2MeJgUOYVEr1qXmhXDw3Qkw0Q34JnaGUHp61mvZr8WyagqrZIldQTgUEKHcqlT1
GkRESynnF5GxUBKpOvxsR3EtNZUSQL1yeqSavAnphTgsuefSn2FMVGaPpDPbgzEFoLDbZlAhwT6DOGMO
guHDS2ooxyHLDKAS/Oywzdvrq+yml1ruPrxVcxe+i698tbLlkcUR2d170OYbxKr57W6harI0MnhmkTeC
Fby+2vsO+ysiCP/bDJ5LcjmUlGQ/eoaFOdwcY+utasbMwfa1BQlNmG1cnie9+Y2q9u+fX8L8Ucd6bxAf
A/bvw3X5FOAuIptdqpgrm+Ol4B6fjFyD9SSdZQF6ysnN1Loo71YnmA5aQPzlOkcdnG; urem=0; unm=
ifsocc; upwd=aWZzb2Nj


xrealloc: not enough memory
  740   Sat Oct 16 20:32:54 2004 Question Geo Geogorilla_geo@yahoo.comBug reportWindows2.5.4.5Re: Elog Service Terminated
> 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
  751   Mon Oct 18 13:47:20 2004 Reply Geo Geogorilla_geo@yahoo.comBug reportWindows2.5.4.5Re: Elog Service Terminated
> > 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
  68793   Fri May 4 16:05:32 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux2.9.2Re: Elog ID entry bug at >99999 entries

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

Joseph McKenna wrote:

We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000... 

68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...

Is this a know bug we can find a fix for? We are using:  elogd 2.9.2 built Jul 14 2015, 18:58:06 revision

 

Attachment 1: elog-test.png
elog-test.png
ELOG V3.1.5-3fb85fa6