Subst variables and Execute, posted by soren poulsen on Wed Jul 21 16:26:17 2010
|
Hi
I am trying to use this line from the documentation:
Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log
It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)
How can I make this line work ?
Soren
|
Re: Subst variables and Execute, posted by soren poulsen on Thu Jul 22 10:17:29 2010
|
Stefan Ritt wrote: |
soren poulsen wrote: |
Hi
I am trying to use this line from the documentation:
Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log
It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)
How can I make this line work ?
Soren
|
Have you started the server with the "-x" flag as written in the documentation?
|
Thanks a lot for replying despite the heat. Yes, I executed with the "-x" flag.
It is just a quoting problem, I guess. This line works:
Execute new = echo New message with ID $message id of type $type from $long_name on $remote_host >> /tmp/elog.log
It evaluates to:
SHELL "echo New message with ID 24706 of type elogtype from Soren Poulsen on 137.138.22.11 >> /tmp/elog.log"
So next step is to replace "new" with "edit" and "delete".
That works as well.
Soren
|
Re: Subst variables and Execute, posted by soren poulsen on Mon Jul 26 11:41:44 2010
|
soren poulsen wrote: |
Stefan Ritt wrote: |
soren poulsen wrote: |
Hi
I am trying to use this line from the documentation:
Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log
It does not seem to have the intended effect (of printing a line with the message id, etc in the file /tmp/elog.log
)
How can I make this line work ?
Soren
|
Have you started the server with the "-x" flag as written in the documentation?
|
Thanks a lot for replying despite the heat. Yes, I executed with the "-x" flag.
It is just a quoting problem, I guess. This line works:
Execute new = echo New message with ID $message id of type $type from $long_name on $remote_host >> /tmp/elog.log
It evaluates to:
SHELL "echo New message with ID 24706 of type elogtype from Soren Poulsen on 137.138.22.11 >> /tmp/elog.log"
So next step is to replace "new" with "edit" and "delete".
That works as well.
Soren
|
There is sometimes a problem with substitutions like "Execute delete = echo $message id".
It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.
In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.
Soren |
Re: Subst variables and Execute, posted by soren poulsen on Thu Jul 29 13:45:47 2010
|
Stefan Ritt wrote: |
soren poulsen wrote: |
There is sometimes a problem with substitutions like "Execute delete = echo $message id".
It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.
In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.
Soren
|
I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it.
|
It is of course my job to reproduce it (and explain how-to). Thanks for your consideration. |
Authentication error message, posted by soren poulsen on Tue Mar 15 17:37:19 2011
|
It is very good to have Kerberos authentication available. It is just the error message which is a bit cryptic.
If you enter your Kerberos password once, and later fail to authenticate with a wrong password, you get:
Kerberos error:
Decrypt integrity check failed.
Please check your Kerberos configuration
That is not really urgent!
Soren
|
Re: Authentication error message, posted by soren poulsen on Mon Apr 11 19:31:23 2011
|
Stefan Ritt wrote: |
soren poulsen wrote: |
It is very good to have Kerberos authentication available. It is just the error message which is a bit cryptic.
If you enter your Kerberos password once, and later fail to authenticate with a wrong password, you get:
Kerberos error:
Decrypt integrity check failed.
Please check your Kerberos configuration
That is not really urgent!
Soren
|
Can you tell me how to reproduce this? If I do it here, I just get back to the login page:

Maybe it has to do with your specific Kerberos implementation? What server are you using?
|
I am sorry but I cannot reproduce this any more. It happened several times when I was testing different kinds of wrong user input to the authentication dialog but now there is no issue any longer. However, there has been other issues lately in this domain and it may be that the Kerberos installation has been patched by our automatic update installation.
Case closed! Thanks anyway for responding.
Soren |
ELOG deamon stuck in find_thread_head(), posted by soren poulsen on Sat Apr 30 19:45:30 2011
|
ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.
If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.
I started in GDB and break with ctrl-C when the process gets stuck, to be told :
Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()
I then made a core dump.
I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).
I get into the same problem in other circumstances such as when opening some threads (maybe because they contain "Reply-to" references to non-existing messages, but I have problems reproducing this on the test installation.
I should maybe also submit the incriminating thread.
Soren
|
Re: calculate diff of 2 date(s), posted by sohail bhatti on Mon Feb 6 15:59:04 2017
|
Alex Kühnel wrote: |
thx!
Stefan Ritt wrote: |
There is the "subst on edit = ..." option you should use in addition.
Stefan
Alex Kühnel wrote: |
is ist possible that subst only works for the initial create of a logbook entry? when I
change/edit one of the parameter "Einsatzbegin" or "Einsatzende" the "Einsatzzeit" is not changed.
regards
/alex
Alex Kühnel wrote: |
I found the solution in the forum :-)
subst Einsatzzeit = $shell(/usr/local/elog/diff.sh \"$Einsatzbeginn\"
\"$Einsatzende\")
and diff.sh is
#!/bin/sh
#set -x
s1=$(date -d "$1" +%s)
s2=$(date -d "$2" +%s)
d=$(echo "($s2-$s1)/60"|bc -lq)
printf "%.0f Minuten" $d
Alex Kühnel wrote: |
hi
I have an elogsystem for documenting emergency services. I have a
starttime and an endtime. Is it possible to calculate the diff between the 2 timestamps and convert it to minutes?
Attributes = Bereitschafts Kalender Woche, Bereitschafts Woche,
Einsatzbeginn, Einsatzende, Einsatzzeit, Telefon Nummer, Station, Status, Problem
Options Status= Offen{1}, Erledigt{2}, Geschlossen{3}
......
Type Einsatzbeginn = datetime
Type Einsatzende = datetime
....
Subst Einsatzzeit = $shell(Einsatzende - Einsatzbeginn)
regards
/alex
|
|
|
|
|
|