Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 649 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 648, 649, 650 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66572   Tue Nov 3 09:04:34 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.7 2246Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

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. 

  66596   Wed Nov 11 19:45:19 2009 Reply David Spindlerdsspindler@gmail.comBug reportWindows2.7.7 2246Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

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:

  66624   Fri Nov 20 19:32:22 2009 Reply David Spindlerdsspindler@gmail.comBug reportWindows2.7.7 2246Re: 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.

 

 

  66640   Mon Dec 7 21:25:23 2009 Reply David Spindlerdsspindler@gmail.comBug reportWindows2.7.7 2246Re: 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:

  66652   Thu Dec 10 18:12:19 2009 Reply David Spindlerdsspindler@gmail.comBug reportWindows2.7.7 2246Re: 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 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.7 2246Re: 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. 

  1558   Wed Dec 21 20:39:52 2005 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: 2.6.0-bata5

Carl Shirey wrote:
Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help.


There is a 2.6.0 out by now.
  65945   Fri Aug 8 14:20:27 2008 Reply Yoshio ImaiQuestionAll2.7.4xRe: 2 questions :: different colors in list view based on "type" + change verbage of "type"

dale cooper wrote:
I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should add
Style Shift Day = background-color:green
Style Shift Swing = background-color:blue
(and so on) to the config file.



Quote:
really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a line
Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>
and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ...
Goto page Previous  1, 2, 3 ... 648, 649, 650 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6