| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66624
|
Fri Nov 20 19:32:22 2009 |
 | David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| 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.
|
|
66630
|
Thu Nov 26 14:27:27 2009 |
 | David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7- | "Reply to" Author in this forum |
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. |
|
66631
|
Thu Nov 26 17:42:02 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7- | Re: "Reply to" Author in this forum |
> 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. |
|
66632
|
Thu Nov 26 20:37:02 2009 |
 | David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | 2.7.7- | Re: "Reply to" Author in this forum |
> > 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! |
|
66640
|
Mon Dec 7 21:25:23 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| 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:
|
|
66651
|
Thu Dec 10 16:05:59 2009 |
| Cliff Shaw | cliff.shaw@stratosglobal.com | Bug report | Windows | 2.7.8 | Elogd crashes when submitting replies |
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 |
|
66652
|
Thu Dec 10 18:12:19 2009 |
| David Spindler | dsspindler@gmail.com | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| 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? |
|
66653
|
Thu Dec 10 19:06:18 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.7 2246 | Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5 |
| 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. |