Re: Elog and Certs, posted by Chuck Brost on Mon Aug 11 22:21:43 2014
|
| Andreas Luedeke wrote: |
|
| Chuck Brost wrote: |
|
Elog V2.9.1-2435 if it matters.
It is time again to install the certs for SSL in Elog, and the standard openssl command line does not seem to produce the files that I need in order to get it working on my system.
I copied the file to my trusty linux server and ran the command "openssl pkcs12 -in cert.p12 -clcerts -out cert.pem " as I did last time, last time I got a nice little .crt and .key file.. this time.. no such luck.. I can get by with the guys just hitting the continue and go past the expired cert notice for a bit.. but if I cannot fix it reasonably soon.. well, it won't be pretty for me.. <grin>
Any ideas that anyone can give will be appreciated.. this is a bit outside my usual duties around here..
|
I'm not an expert in this field, but I think openssl is not meant to create a certificate for you, it is meant to create a certificate request form (CSR) and then you buy the certificate with that form from a vendor. Once you have the certificate then you just need to copy it to the right place for ELOG (or Apache) to use it, you don't need openssl for that.
⇄
English (auto-detected) » English
You can have a look at: http://www.rackspace.com/knowledge_center/article/generate-a-csr-with-openssl
Good luck!
PS: This is of course an openssl question: another forum could may be more helpful?
|
for what it is worth, if anyone else is doing this.. try
openssl pkcs12 -in file.pkx -nodes -out file.pem
I have what I need and all is well! |
Re: Elog Utility, posted by Charles Duncan on Thu Mar 25 18:20:15 2004
|
> I am trying to use the Elog Utility to import a few thousand entries. So
> far I have run into a few problems.
>
> 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.
>
> 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"
>
> This line executes fine. Except only Hostname, Manufacturer, Memory and
> text are populated in the record. All the rest of the fields are blank.
>
> c) the only way I was able to get the transaction to work was by reducing
> the size of the log book to a single word (ie WSC2).
>
> Do I have to reduce all my attributes to single words? Or am I missing
> something simple to use as a delimiter for entry??
>
> Thanks in advance
>
> -Charles-
As a followup, this occurs not only in the Linux environment, but also under
Windows XP. I get the same results...
-Charles- |
|
Re: Elog Utility, posted by Stefan Ritt on Fri Mar 26 09:37:08 2004
|
> 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. |
|
Re: Elog Utility, posted by Charles Duncan on Sat Mar 27 18:52:16 2004
|
> > 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- |
|
Re: Elog Utility, posted by Stefan Ritt on Sun Mar 28 12:45:45 2004
|
> 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. |
|
Re: Elog System Requirements, posted by Andreas Luedeke on Fri Sep 15 15:16:42 2017
|
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.
|
|
|
Re: Elog Service Terminated, posted by Stefan Ritt on Fri Oct 15 08:15:38 2004
|
> I |
|
Re: Elog Service Terminated, posted by Geo Geo on Fri Oct 15 09:38:51 2004
|
> > 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 |
|