Elogd crashes when submitting replies, posted by Cliff Shaw on Thu Dec 10 16:05:59 2009
|
Hi Stefan,
I recently installed the latest Elog 2.7.8 revision 2277 after running Elog 2.7.7 revision 2246 for several months without any problems. However once I submit an entry by using the Reply command Elog crashes and Windows XP reports an error message screen. This also stops the elogd service.
I have pinpointed it down to the command "subst on reply Subject = $Subject" by removing my whole configuration file and just added the line "subst on reply Subject = $Subject" to your demo configuration file.
Elog seems to also stops the elogd service with any "subst on reply" command.
Do you have any suggestions?
Thank you,
Regards
Cliff Shaw |
Re: Elogd crashes when submitting replies, posted by Stefan Ritt on Sat Dec 12 20:30:35 2009
|
Cliff Shaw wrote: |
Hi Stefan,
I recently installed the latest Elog 2.7.8 revision 2277 after running Elog 2.7.7 revision 2246 for several months without any problems. However once I submit an entry by using the Reply command Elog crashes and Windows XP reports an error message screen. This also stops the elogd service.
I have pinpointed it down to the command "subst on reply Subject = $Subject" by removing my whole configuration file and just added the line "subst on reply Subject = $Subject" to your demo configuration file.
Elog seems to also stops the elogd service with any "subst on reply" command.
Do you have any suggestions?
Thank you,
Regards
Cliff Shaw
|
Thanks for reporting that problem. I finally found the bug and fixed it. I made a new elog278-2 for you to download. |
401 Authorization problem, posted by Ian Stokes-Rees on Fri Dec 11 18:53:17 2009
|
Grrr. Forgetting to pick an icon means my message was blasted.
I have installed elog 2.7.8 and it is running. When I connect to it and get a login window, I am always denied. If I remove the passwords, then I can login with no password information. I have tried both command line for setting passwords and directly in the elogd.cfg file.
Suggestions on what I might be doing wrong would be appreciated.
Regards,
Ian
PS - are there RESTful interfaces to automate the generation of log entries via an HTTP POST or HTTP GET? |
Re: 401 Authorization problem, posted by Stefan Ritt on Sat Dec 12 20:18:46 2009
|
Ian Stokes-Rees wrote: |
Grrr. Forgetting to pick an icon means my message was blasted.
I have installed elog 2.7.8 and it is running. When I connect to it and get a login window, I am always denied. If I remove the passwords, then I can login with no password information. I have tried both command line for setting passwords and directly in the elogd.cfg file.
Suggestions on what I might be doing wrong would be appreciated.
Regards,
Ian
PS - are there RESTful interfaces to automate the generation of log entries via an HTTP POST or HTTP GET?
|
Which password scheme are you using? Is it Read passoword = ... or Password file = ...? If you use a password file (that's what most people do) you have to create yourself an account just as you did for this forum here. There is no other way to enter the encrypted password into the password file. Just follow "To start a new password file..." in the documentation. |
2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Nov 2 21:23:38 2009
|
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
Thanks,
David |
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Tue Nov 3 09:04:34 2009
|
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. |
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Wed Nov 11 19:45:19 2009
|
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Re: Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Heinzmann on Tue Nov 17 19:31:46 2009
|
David Spindler wrote: |
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Hi,
I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.
Regards,
Michael
|
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Fri Nov 20 19:32:22 2009
|
David Spindler wrote: |
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Sorry for the delay.
1: The offending log file.
|
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Mon Dec 7 21:25:23 2009
|
David Spindler wrote: |
David Spindler wrote: |
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Sorry for the delay.
1: The offending log file.
|
I know it looks like I am totally inept. I apologize. Obviously I was in a hurry the last couple of posts.
Ok, let's try this again.
The offending log file:
|
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by David Spindler on Thu Dec 10 18:12:19 2009
|
David Spindler wrote: |
David Spindler wrote: |
David Spindler wrote: |
Stefan Ritt wrote: |
David Spindler wrote: |
I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.
I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.
This is running under Win2K with SP4 as an automatic service on port 80.
I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.
If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.
|
I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash.
|
In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:
|
Sorry for the delay.
1: The offending log file.
|
I know it looks like I am totally inept. I apologize. Obviously I was in a hurry the last couple of posts.
Ok, let's try this again.
The offending log file:
|
Ok, I am now assuming the offending log file has been removed. Correct? |
Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5, posted by Stefan Ritt on Thu Dec 10 19:06:18 2009
|
David Spindler wrote: |
Ok, I am now assuming the offending log file has been removed. Correct?
|
No, you never submitted any file. It was missing in all your posts. In worst case send it by email to me. |
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 |
Re: Certificate Error, posted by John Lemko on Tue Dec 8 22:06:47 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
Thanks for your reply. I appreciate it alot.
When I created my certificate it came out as a .cer [there was no .key file] and looking at the code that was posted
below it looks like unless there is a server.crt and server.key file in the ssl folder the program will exit: So I
guess I need to figure out how to generate a certificate that elog will understand using a .key file and a .crt file.
So I might have to research certificates more.
To be honest I'm not an expert on SSL. I just use following code inside ELOG to initialize the SSL connection:
SSL_CTX *init_ssl(void)
{
char str[256];
SSL_METHOD *meth;
SSL_CTX *ctx;
SSL_library_init();
SSL_load_error_strings();
meth = SSLv23_method();
ctx = SSL_CTX_new(meth);
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/server.crt", sizeof(str));
if (!file_exist(str)) {
eprintf("Cerificate file \"%s\" not found, aborting\n", str);
return NULL;
}
if (SSL_CTX_use_certificate_file(ctx, str, SSL_FILETYPE_PEM) < 0)
return NULL;
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/server.key", sizeof(str));
if (!file_exist(str)) {
eprintf("Key file \"%s\" not found, aborting\n", str);
return NULL;
}
if (SSL_CTX_use_PrivateKey_file(ctx, str, SSL_FILETYPE_PEM) < 0)
return NULL;
if (SSL_CTX_check_private_key(ctx) < 0)
return NULL;
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/chain.crt", sizeof(str));
if (file_exist(str))
SSL_CTX_use_certificate_chain_file(ctx, str);
return ctx;
} |
Re: Certificate Error, posted by Stefan Ritt on Tue Dec 8 20:16:59 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.
How did you install the certificate? Maybe it ended up in the IIS directory and not in the elog directory? |
Re: Certificate Error, posted by John Lemko on Tue Dec 8 21:57:37 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.
>
> How did you install the certificate? Maybe it ended up in the IIS directory and not in the elog directory?
That is a good point. I just installed the cert by double clicking on it. Then selecting either trusted root CA or
personal to install the certificate. Is there a different way to install the certificate for elog?
Thanks alot for your help. |
elogd keeps crashing, any thoughts?, posted by Allen on Thu Dec 3 20:25:50 2009
|
We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see:
Dec 3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
Any thoughts? |
Re: elogd keeps crashing, any thoughts?, posted by Stefan Ritt on Fri Dec 4 23:45:56 2009
|
Allen wrote: |
We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see:
Dec 3 14:01:23 nissrv18a kernel: [419738.139675] elogd[32003]: segfault at 4 ip 00007f183b19b560 sp 00007fff79f5e278 error 4
in libc-2.10.1.so[7f183b119000+166000]
Any thoughts?
|
I need more information about that. Please have a look at Faq #19. |
default Status descending, posted by Terry Shuck on Tue Dec 1 14:20:04 2009
|
Is there a way to configure ELOG to default to the Status column in descending order rather than the Date in descending order?
Thanks |
Re: default Status descending, posted by Stefan Ritt on Tue Dec 1 14:22:28 2009
|
Terry Shuck wrote: |
Is there a way to configure ELOG to default to the Status column in descending order rather than the Date in descending order?
Thanks
|
Sort attributes = Status
... as written in the manual. |
Re: default Status descending, posted by Terry Shuck on Tue Dec 1 15:11:19 2009
|
Thanks for the quick response. This works. I noticed that the Dates aren't descending, is there a way to have the dates descending while sorting Status?
Thanks again!
Stefan Ritt wrote: |
Terry Shuck wrote: |
Is there a way to configure ELOG to default to the Status column in descending order rather than the Date in descending order?
Thanks
|
Sort attributes = Status
... as written in the manual.
|
|
Re: default Status descending, posted by Stefan Ritt on Wed Dec 2 11:57:09 2009
|
Terry Shuck wrote: |
Thanks for the quick response. This works. I noticed that the Dates aren't descending, is there a way to have the dates descending while sorting Status?
Thanks again!
Stefan Ritt wrote: |
Terry Shuck wrote: |
Is there a way to configure ELOG to default to the Status column in descending order rather than the Date in descending order?
Thanks
|
Sort attributes = Status
... as written in the manual.
|
|
For this you need
Sort attributes = Status, Date
which however only works from version 2.7.8 on. |
"Reply to" Author in this forum, posted by David Pilgram on Thu Nov 26 14:27:27 2009
|
Hi Stefan,
This has happened twice on this forum now, starting from Mon 23rd November.
Someone submits an entry (Me, 66625, Bertram Metz 66628)
I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
yourself. My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
Is this a bug, or some wierd affect of us forgetting to log out?
Regards,
David. |
Re: "Reply to" Author in this forum, posted by Stefan Ritt on Thu Nov 26 17:42:02 2009
|
> Hi Stefan,
>
> This has happened twice on this forum now, starting from Mon 23rd November.
>
> Someone submits an entry (Me, 66625, Bertram Metz 66628)
> I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> yourself. My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
>
> Is this a bug, or some wierd affect of us forgetting to log out?
>
> Regards,
>
> David.
Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
Re: Re: Re: ...
in the subject line. I changed this now completely so that we can have
Preset on reply Author = $full_name
Preset on first reply Subject = Re: $Subject
which fixes both things. The modification is in revision 2271. |
Re: "Reply to" Author in this forum, posted by David Pilgram on Thu Nov 26 20:37:02 2009
|
> > Hi Stefan,
> >
> > This has happened twice on this forum now, starting from Mon 23rd November.
> >
> > Someone submits an entry (Me, 66625, Bertram Metz 66628)
> > I assume you post a reply (66626, 66629), but it shows up as if I or Bertram are the author of the reply, not
> > yourself. My reply to you (66627) was really authored by me, and I expressed puzzlement then at this point.
> >
> > Is this a bug, or some wierd affect of us forgetting to log out?
> >
> > Regards,
> >
> > David.
>
> Thanks for pointing out this issue. This bug was introduced recently, when I tried to avoid the
>
> Re: Re: Re: ...
>
> in the subject line. I changed this now completely so that we can have
>
> Preset on reply Author = $full_name
> Preset on first reply Subject = Re: $Subject
>
> which fixes both things. The modification is in revision 2271.
Thanks Stefan! |
elogd.cfg for this forum, posted by Bertram Metz on Tue Nov 24 10:38:26 2009
|
Hi Stefan,
I'm interested in the current configuration file for this discussion forum. Could you please post it to the
'config examples' logbook?
Thanks,
Bertram |
Re: elogd.cfg for this forum, posted by Bertram Metz on Thu Nov 26 13:12:23 2009
|
> Hi Stefan,
>
> I'm interested in the current configuration file for this discussion forum. Could you please post it to the
> 'config examples' logbook?
>
> Thanks,
> Bertram
Sure, here it is! |