Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 278 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 277, 278, 279 ... 805, 806, 807   Next  
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  66447   Sat Jul 18 10:41:28 2009 Reply Adam BlandfordAdam.Blandford@dsto.defence.gov.auQuestionWindows2.7.5Re: Using conditional attributes

Sorry about the multiple entries!!! -> browser problems

  66448   Mon Jul 20 08:18:45 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.5Re: Using conditional attributes

Adam Blandford wrote:

Hi

I have a logbook including the attributes: Author, Topic Date, Phase, Reference, Subject, Start Time, End Time, Duration

The Phase attribute has a number of MOptions including: Design, Manufacture, Testing, Results, Transport

I only want the attributes Start Time, End Time, and Duration to be shown if the Transport Phase is selected. I have tried using the conditional attributes

MOptions Phase = Design{1}, Manufacture{1}, Testing{1}, Results{1}, Transport{2}

and

{1} Show Attributes Edit = Author, Topic Date, Phase, Subject, Start Time, End Time, Duration
{2} Show Attributes Edit = Author, Topic Date, Phase, Subject

This works to show the attributes when the relevant Phase is selected but the Edit page shows the Phase options including the {1}/{2}. Is there are way that these conditionals are not displayed?

Also, I would like the "Duration" Atrribute to be a calculated value showing the time difference between Start Time and End Time. Is this possible?

Thanks,

Adam

The conditional attributes work only with Options, but not with MOptions as written in the documentation. I tried your set-up with Options and it worked ok. If you attribute Phase is non-exclusive, meaning it could be Manufacture and Testing at the same time, then you have to play some tricks with an additional attribute like

Attributes = Author, Topic Date, ..., Duration, Transport

 

MOptions Phase = Design, Manufacture, Testing, Results, Transport

Options Transport = Yes{2}, No{1}

{1} Show Attributes Edit = ...

{2} Show Attributes Edit = ...

An automatic calculation of Duration is unfortunately not implemented.

  66450   Mon Jul 20 10:30:44 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.6Re: Elog Crashes

lance wrote:
Stefan,
 
Our log is crashing on a regular basis and I have been unable to identify the reason. Now the if the log crashes that is not a major problem however when you try to stop the daemon from the services it fails to stop. This means that the daemon cannot be restarted. The only way then is to start killing processes. This is not something I want none experienced guys to do.
 
Looking at the processes is look like the elogd.exe is still running and doesn’t die when you try to stop the daemon service.
 
I checked the times it was crashing with events in the elog logfiles but there was nothing actually happening at these times. It seems something is causing it to just hang.
 
I have attached the eventlog files for you if you have any ideas I would appreciate them.
 
I have not run the log in verbose mode as I have thus far been unable to redirect the output of the screen in order to see what is happening. If you have any tips on how to redirect the output I would save the file for off line analysis. Our log is used 24/7 therefore it is critical that it be kept running so if I was to run it with the –v option the guys would have to restart it and I would lose the data.
 
Any help is much appreciated
 
 
Regards,
 
Lance

Using the Windows event log won't help much. I guess in your case elogd is driven into some kind of endless loop (does the CPU go to 100%???). There are only two possibilities to tackle this:

1) You find a way to reliably reproduce this problem, tell me how to do this. When I can reproduce it here, I can fix it easily.

2) You do debugging yourself. Under Linux this is simple, since you have debuggers on most systems. Under Windows however, you first have to install the Visual C++ development environment. I believe there is a free version (Express?) which you can use. You then run elogd under the debugger, and when it hangs you investigate where. This needs some basic knowledge about C++ development and I'm not sure if you have this, but maybe you can find someone around you who does. 

  66451   Mon Jul 20 13:52:58 2009 Reply Richard Stamperr.stamper@rl.ac.ukQuestionWindows2.7.5Re: Using conditional attributes

Stefan Ritt wrote:

Adam Blandford wrote:

Hi

I have a logbook including the attributes: Author, Topic Date, Phase, Reference, Subject, Start Time, End Time, Duration

The Phase attribute has a number of MOptions including: Design, Manufacture, Testing, Results, Transport

I only want the attributes Start Time, End Time, and Duration to be shown if the Transport Phase is selected. I have tried using the conditional attributes

MOptions Phase = Design{1}, Manufacture{1}, Testing{1}, Results{1}, Transport{2}

and

{1} Show Attributes Edit = Author, Topic Date, Phase, Subject, Start Time, End Time, Duration
{2} Show Attributes Edit = Author, Topic Date, Phase, Subject

This works to show the attributes when the relevant Phase is selected but the Edit page shows the Phase options including the {1}/{2}. Is there are way that these conditionals are not displayed?

Also, I would like the "Duration" Atrribute to be a calculated value showing the time difference between Start Time and End Time. Is this possible?

Thanks,

Adam

The conditional attributes work only with Options, but not with MOptions as written in the documentation. I tried your set-up with Options and it worked ok. If you attribute Phase is non-exclusive, meaning it could be Manufacture and Testing at the same time, then you have to play some tricks with an additional attribute like

Attributes = Author, Topic Date, ..., Duration, Transport

 

MOptions Phase = Design, Manufacture, Testing, Results, Transport

Options Transport = Yes{2}, No{1}

{1} Show Attributes Edit = ...

{2} Show Attributes Edit = ...

An automatic calculation of Duration is unfortunately not implemented.

On the matter of automatic calculation of fields, it is possible using included javascript but you have to do the work yourself.  For example, we have a log which computes responsivity as the ratio of a photocurrent and optical power.  With log attributes called "Photocurrent", "Optical Power" and "Responsivity" there is a file in the logbooks directory called photomixer_javascript.html containing something like:

<script>

if (document.form1.Photocurrent) {
  document.form1.Photocurrent.onchange = new Function(
    "mod();"+
    "var power = parseFloat(document.form1.Optical_Power.value);"+
    "var current = parseFloat(document.form1.Photocurrent.value);"+
    "if (!isNan(power) && !isNan(current) && power != 0.0) {"+
    "  document.form1.Responsivity.value = Math.round(current/power*100)/100.0"+
    "}"
    );
  document.form1.Optical_Power.onchange = document.form1.Photocurrent.onchange;
}

</script>

and the elogd.cfg file includes

Bottom text = photomixer_javascript.html

for the relevant log.

The assignments to the onchange handlers are guarded because this javascript is included on all pages for that log, including the list pages where there is no such field as Photocurrent, (or Optical_Power) and the event handler function is defined dynamically for the same reason.

  66453   Wed Jul 22 08:03:28 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6-2230Re: Reply not working correct

kyle carpenter wrote:

Hi,

I love this software. I am not a programmer but have learned alot about the program.

I have 2 questions.   #### This is my modification ####

1. when i do a reply it will bring the original qutes with it but i have the option to change what had been entered. once i do the reply and reply to the reply i can not change the first reply but can change the second reply. This just started last week and i am not sure what has changed. i even uninstalled and reinstalled. If I try to just the HTML i tcomes up with code? If I do elcode seems to do ok just not able to stop the editing of the the last reply. Plain seems to do the same as ELcode.

2. I have also had trouble with E-Log not starting on my XP machines. Any ideas?

 

Thanks for sharing such a powerful program it is sweet.

Kyle

Sorry but I don't get your point. See I modified your original entry above. Now I will submit this entry, and do another reply.

  66454   Wed Jul 22 08:05:12 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.6-2230Re: Reply not working correct

Stefan Ritt wrote:

kyle carpenter wrote:

Hi,

I love this software. I am not a programmer but have learned alot about the program.

I have 2 questions.   #### This is my modification #### **** This is my second modification ****

1. when i do a reply it will bring the original qutes with it but i have the option to change what had been entered. once i do the reply and reply to the reply i can not change the first reply but can change the second reply. This just started last week and i am not sure what has changed. i even uninstalled and reinstalled. If I try to just the HTML i tcomes up with code? If I do elcode seems to do ok just not able to stop the editing of the the last reply. Plain seems to do the same as ELcode.

2. I have also had trouble with E-Log not starting on my XP machines. Any ideas?

 

Thanks for sharing such a powerful program it is sweet.

Kyle

Sorry but I don't get your point. See I modified your original entry above. Now I will submit this entry, and do another reply. **** And I can modify this ****

So this is my second reply. I can edit both your original entry and my first reply. 

Your point 2) is too unspecific. I need more information there. You could run the elogd daemon interactively and check if there is any error output in the console window.

  66456   Wed Jul 22 12:15:56 2009 Reply T. Ribbrockemgaron+elog@ribbrock.orgBug reportLinux2.7.6r2233Re: Crashes when editing entries

T. Ribbrock wrote:

For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running 2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group with three logbooks. In the "active" group, there are two logbooks that share the same index (using Subdir=...) and it looks like the crashes occur most of the time in these, though that's just a hunch so far. Also, most of the crashes seem to happen when submitting an entry that has been edited. Actually, submitting a modified entry has always been strange in our logbooks: When we hit submit, we get a pop-up window asking "Submit modified entry?". When choosing "OK", the entry that has been edited is duplicated. When choosing "Cancel", it is submitted correctly.

I've been running elogd like this (to get more info)

elogd -v > elog-2233-2.log 2>&1

The last entry I get in the log when elogd crashes is:

  Same index as logbook Machine Log
elogd: src/elogd.c:727: xfree: Assertion `*((unsigned int *) (temp - 4)) == 0xdeadc0de' failed.
Received unknown cookie "wikidb_mw__session"
Received unknown cookie "wikidb_mw__session"

I did actually make a few changes to the configuration before we noticed the crashes: I added one extra attribute and a few more conditionals.

 

Any additional information you need: Just let me know.

Regards,

Thomas

 Forgot to mention: I've also seen error messages like this upon a crash:

*** glibc detected *** corrupted double-linked list: 0x0911bbc0 ***

Regards,

Thomas

  66457   Wed Jul 22 12:46:36 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.6r2233Re: Crashes when editing entries

T. Ribbrock wrote:

For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been working fine so far, but more or less out of the blue it became rather unreliable. The current configuration is installed on two servers, one running 2.7.5.-r2174 on ClarkConnect 4 and one running 2.7.6-r2233 on Debian 4.0 - both show the same problem. Each of them has an "active" group with four logbooks and an "archive" group with three logbooks. In the "active" group, there are two logbooks that share the same index (using Subdir=...) and it looks like the crashes occur most of the time in these, though that's just a hunch so far. Also, most of the crashes seem to happen when submitting an entry that has been edited. Actually, submitting a modified entry has always been strange in our logbooks: When we hit submit, we get a pop-up window asking "Submit modified entry?". When choosing "OK", the entry that has been edited is duplicated. When choosing "Cancel", it is submitted correctly.

I've been running elogd like this (to get more info)

elogd -v > elog-2233-2.log 2>&1

The last entry I get in the log when elogd crashes is:

  Same index as logbook Machine Log
elogd: src/elogd.c:727: xfree: Assertion `*((unsigned int *) (temp - 4)) == 0xdeadc0de' failed.
Received unknown cookie "wikidb_mw__session"
Received unknown cookie "wikidb_mw__session"

I did actually make a few changes to the configuration before we noticed the crashes: I added one extra attribute and a few more conditionals.

 

Any additional information you need: Just let me know.

well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal writing beyond array boundaries, but I have no clue which part of the code makes this. It might be related to the fact that you use the same index (via Subdir=...) for two logbooks. In this scenario, you are only allowed to modify/add entries to one logbook, not the other. The other one may only be used for reading. And even then it's not guaranteed that new entries show up in the second logbook immediately, you might have to restart the server in order to re-index the logbooks. Internally, the daemon does not know that two logbooks are "the same" and one instance will not realize if the other instance modifies the data "below its feet". Can you try to give up the double logbooks and see if the problem goes away?

Goto page Previous  1, 2, 3 ... 277, 278, 279 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6