Re: mysql in execute, posted by Stefan Ritt on Fri Dec 12 09:16:19 2008
|
Stefan Kanitz wrote: |
This doesn't work:
Execute new = mysql -h localhost -u root -D test1 -e "insert into `test2` (Autor, Adressat, Teil1, Teil2, Teil3,
Teil4, Teil5, Teil6, Teil7, Teil8 ) values ('$Autor', '$Adressat' , '$Teil1', '$Teil2', '$Teil3', '$Teil4', '$Teil5',
'$Teil6', '$Teil7', '$Teil8' )"
|
In the elogd.cfg file, you cannot have multi-line options. Either you put everything on a single line (I guess there is also some limit at a few hundred characters) or you call a batch file which then calls the mysql command. |
Re: mysql in execute, posted by Stefan Kanitz on Sat Dec 13 14:31:53 2008
|
Stefan Ritt wrote: |
Stefan Kanitz wrote: |
This doesn't work:
Execute new = mysql -h localhost -u root -D test1 -e "insert into `test2` (Autor, Adressat, Teil1, Teil2, Teil3,
Teil4, Teil5, Teil6, Teil7, Teil8 ) values ('$Autor', '$Adressat' , '$Teil1', '$Teil2', '$Teil3', '$Teil4', '$Teil5',
'$Teil6', '$Teil7', '$Teil8' )"
|
In the elogd.cfg file, you cannot have multi-line options. Either you put everything on a single line (I guess there is also some limit at a few hundred characters) or you call a batch file which then calls the mysql command.
|
Thanks!
|
elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 14:42:34 2009
|
Hi,
after setting
Date format = %Y-%m-%e
in elogd.cfg,
elogd hangs and must be restarted manually. Can anybody help me?
Thanks,
Steve |
Re: elogd hangs when Date format in elogd.cfg, posted by Stefan Kanitz on Thu Jan 8 15:36:28 2009
|
Stefan Kanitz wrote: |
Hi,
after setting
Date format = %Y-%m-%e
in elogd.cfg,
elogd hangs and must be restarted manually. Can anybody help me?
Thanks,
Steve
|
I found my mistake:It must be
Date format = %Y-%m-%d
Steve
|
Certificate Error, posted by John Lemko on Tue Dec 8 18:57:31 2009
|
Is there any documentation I can go through that explains how to remove the Certificate Error I am getting as shown in the attachment. I have tried creating my own certificate and putting it in the elog ssl folder but that just prevented the elog service from starting. Any help would be greatly appreciated. Thanks. |
Re: Certificate Error, posted by Gerhard Schneider on Tue Dec 8 19:22:06 2009
|
How did you create the certificate?
Are you running eLog on a server with more than one host name (CNAME entries) and are you pointing to your eLog
via one of that aliases?
Certificates that work with an Apache 1 Web server do work with eLog, too.
GS |
Re: Certificate Error, posted by John Lemko on Tue Dec 8 19:34:11 2009
|
>
> How did you create the certificate?
> Are you running eLog on a server with more than one host name (CNAME entries) and are you pointing to your eLog
> via one of that aliases?
>
> Certificates that work with an Apache 1 Web server do work with eLog, too.
>
> GS
The certificate that is on there right now is the one that gets created when you install elogs. I have tried
creating one with a windows server 2008 box with the CA role installed. The certificate is created without issue
and I can install it on the server but when I try to restart the elog service it wont start until I put the
original server.crt and server.key file back into the ssl directory.
I have DNS on the machine but only have one CNAME pointing to the elog server.
I don't know a lot about certificates so sorry if this doesn't help out much. |
Re: Certificate Error, posted by Gerhard Schneider on Tue Dec 8 19:47:56 2009
|
>
> The certificate that is on there right now is the one that gets created when you install elogs. I have tried
> creating one with a windows server 2008 box with the CA role installed. The certificate is created without issue
> and I can install it on the server but when I try to restart the elog service it wont start until I put the
> original server.crt and server.key file back into the ssl directory.
>
I don't know anything about Windows server CA, but eLog is very strict in the syntax of the CERTs.
I had to learn it the hard way when installing a chain CERT.
For server.crt and server.key it MUST NOT be a chain cert. Therefor you have to use chain.crt
Are the generated CERTs ASCII (with only one -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- in
server.crt
and -----BEGIN RSA PRIVATE KEY----- and -----END RSA PRIVATE KEY----- in server.key)?
So the eLog generated keys should look like..
GS |
|