elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt

 Andreas, thank you very much. I was able to get the stand alone function working fine on my site, including a number of add'l attributes and options (SSL, etc).

> Is there any possibility to start elogd as a service under NT/2000/XP 
> having local service as its user? Yes, I've read the documentation. Maybe 
> things have changed.

What do you mean by "local service as its user"? If you install elogd as a 
service with FireDaemon or via SRVANY.EXE, you use the "Services" section 
under Computer Management ("Verwalten") to configure the elogd service. 
Although the documentation says that one should use the "This account" with 
the appropriate password, it is possible to use the "Local System account" 
as well. But I'm not 100% sure what implications this has for the ownership 
of the logbook database files, but it should be ok in most cases.

> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
> 
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81
> 
> This command runs on the server, but when I access https://172.16.24.108/ i 
> get a page cannot be displayed, ive also put the URL = 
> https://172.16.24.108 entry in the elogd.cfg file
> 
> HELP!!!!!!!

Can you access your server locally under http://172.16.24.108:81 ??? If not, 
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag 
when starting elogd. If you can access it, and cannot access it under 
https://, then something must be wrong with your stunnel configuration. Maybe 
you run already a secure server under port 443? User "netstat -a" to check 
that.

Im not running anything on port 443, one thing I did notice is that when 
stunnel is run and setup, I can run a netstat and nothing is bound to those 
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the 
command initially ?


CONFUSED ????

> > I was wondering if you can help me understand the concept and if i am 
doing 
> > something wrong with securing Elog via SSL
> > 
> > Basically im running elog on a redhat 8 box with stunnel already 
installed 
> > as part of OpenSSL, on the server i ran the command specified in the 
> > instructions
> > 
> > stunnel -d 443 -r 172.16.24.108:81
> > 
> > This command runs on the server, but when I access https://172.16.24.108/ 
i 
> > get a page cannot be displayed, ive also put the URL = 
> > https://172.16.24.108 entry in the elogd.cfg file
> > 
> > HELP!!!!!!!
> 
> Can you access your server locally under http://172.16.24.108:81 ??? If 
not, 
> then you maybe specified the wrong port, so check elogd.cfg and the "-p" 
flag 
> when starting elogd. If you can access it, and cannot access it under 
> https://, then something must be wrong with your stunnel configuration. 
Maybe 
> you run already a secure server under port 443? User "netstat -a" to check 
> that.

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.

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!

> 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-

> 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.