Re: running more then one shell command when new entries is submitted, posted by kenzo Abrahams on Wed Oct 28 11:11:27 2015
|
Hi Andreas
This worked perfectly thank you.
| Andreas Luedeke wrote: |
|
As far as I know ELOG is recognising a configuration line as a comment only when it starts with a ';'.
I can assure you that ELOG does not treat the rest of the line as a comment when you use a ';' within a $shell() command: I do it a lot and it works fine. Here's a simple, generic example using the bash:
Preset Author = $shell(if [ $short_name = "Anonym" ] ;then echo $Author;else echo \"$long_name, $Author\";fi)
It adds $long_name to the Author field for non-anonymous entries.
Cheers Andreas
| kenzo Abrahams wrote: |
|
If i put the ';' into Execute the rest of the command becomes a comment thats why i was trying to use '&&' instead. If I encapulate the whole command in "" or '' then both commands are executed but the files im trying to write to gets created but no data is piped into it. When I use Execute with one command and pipe its output to a file everything works fine though.
| Stefan Ritt wrote: |
|
The command is passed to your shell, and some shells except more than one command. Most Linux shells accept commands separated by ';', which you can try yourself by entering for example: ls *.c; ls*.h
| kenzo Abrahams wrote: |
|
Hi
Im just curious is it possible to run more then one command using Execute new = <command> or will i have to run a script to run muliple commands.
I tried using '&&' to seperate more then one command but it seems that the first one only gets executed and the rest are just ignored.
Regards
Kenzo
|
|
|
|
|
propogating messages through logbooks, posted by kenzo Abrahams on Thu Oct 29 12:30:43 2015
|
Hi there
Okay so let me explain what im trying to do. I have a table in a logbook (lets call it home) that the user fills
out. This information in the table is related to other logbooks (8 of them to be exact).
I want to propogate information from the table in the home logbook into the other logbooks. To do this I used
Execute new which runs my scripts. One of the scripts makes a call to the elog
client to submit the message. The problem is that this call to elog client never finishes because its hanging
waiting for the initial submit (one which triggered Execute new) to finish. The documentation
explained that only one submit can be processed at a time so i expected whats happening at the moment.
My question is are there any other ways to do what im trying to do?? In a nutshell how to propogate information
from one logbook to another autonomously.
Regards
Kenzo |
|
Re: propogating messages through logbooks, posted by Andreas Luedeke on Fri Oct 30 15:52:33 2015
|
> Hi there
>
> Okay so let me explain what im trying to do. I have a table in a logbook (lets call it home) that the user fills
> out. This information in the table is related to other logbooks (8 of them to be exact).
> I want to propogate information from the table in the home logbook into the other logbooks. To do this I used
> Execute new which runs my scripts. One of the scripts makes a call to the elog
> client to submit the message. The problem is that this call to elog client never finishes because its hanging
> waiting for the initial submit (one which triggered Execute new) to finish. The documentation
> explained that only one submit can be processed at a time so i expected whats happening at the moment.
>
> My question is are there any other ways to do what im trying to do?? In a nutshell how to propogate information
> from one logbook to another autonomously.
>
> Regards
> Kenzo
Hi Kenzo,
I think it would help me to understand your problem, if you would provide a minimal configuration file with two
logbooks.
There is no ELOG internal feature to propagate data from one logbook to another;
using a shell script is the only method I know.
But you could easily put your script into the background:
ELOG can handle multiple parallel request, by handling one request after the other.
Kind Regards, Andreas |
restrict edit time and autosave, posted by Kester Habermann on Fri Oct 30 18:20:22 2015
|
Hello,
When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after the autosave. If the time is up, it is no longer possible to submit the report.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103
Regards
Kester
|
Re: propogating messages through logbooks, posted by kenzo Abrahams on Mon Nov 2 07:39:07 2015 
|
> Hi Kenzo,
> I think it would help me to understand your problem, if you would provide a minimal configuration file with two
> logbooks.
>
> There is no ELOG internal feature to propagate data from one logbook to another;
> using a shell script is the only method I know.
> But you could easily put your script into the background:
> ELOG can handle multiple parallel request, by handling one request after the other.
>
> Kind Regards, Andreas
Hi Andreas
Im using python to do the scripting. Everything works fine until it comes to submitting the entry to my logbook.
The extractTable.py file is the one running the command to submit to elog.
I see now that im starting a subprocess in my python script (subprocess.call) and thats why its not finishing.
Could you perhaps suggest how I would go about doing this by putting my scripts in the
background? I might have to look at multiprocessing in python as well. The reason im using python is because im
doing alot of file processing as well. I do have to add that this method works perfectly when i just run the python
on its own. As soon as i run it by submiting an elog entrie from the browser it hangs on the subprocess.call method.
Regards, Kenzo |
|
Re: propogating messages through logbooks, posted by kenzo Abrahams on Mon Nov 2 08:37:06 2015
|
>
> > Hi Kenzo,
> > I think it would help me to understand your problem, if you would provide a minimal configuration file with two
> > logbooks.
> >
> > There is no ELOG internal feature to propagate data from one logbook to another;
> > using a shell script is the only method I know.
> > But you could easily put your script into the background:
> > ELOG can handle multiple parallel request, by handling one request after the other.
> >
> > Kind Regards, Andreas
>
> Hi Andreas
>
> Im using python to do the scripting. Everything works fine until it comes to submitting the entry to my logbook.
> The extractTable.py file is the one running the command to submit to elog.
> I see now that im starting a subprocess in my python script (subprocess.call) and thats why its not finishing.
> Could you perhaps suggest how I would go about doing this by putting my scripts in the
> background? I might have to look at multiprocessing in python as well. The reason im using python is because im
> doing alot of file processing as well. I do have to add that this method works perfectly when i just run the python
> on its own. As soon as i run it by submiting an elog entrie from the browser it hangs on the subprocess.call method.
>
> Regards, Kenzo
Hi Andreas
I sorted my problem out, I had to use threading in python such that I can time the submissions to the elog server.
Everything works fine now. Thank you for the assistance.
Regards
Kenzo |
|
Re: restrict edit time and autosave, posted by Andreas Luedeke on Mon Nov 2 08:41:20 2015
|
Hi Kester,
yes, I did run into the same problem, that I could not even delete old drafts due to our restrict edit time.
We allow anonymous submissions in our operation logbooks. After a while drafts of unsubmitted messages just pile up; and I need to remove them as administrator.
While I can do that easily for anonymous drafts, I cannot do that for drafts of other users: I don't easily see those drafts.
It would be really nice, if drafts would be handled different then other entries regarding "Restrict edit time" as you've suggested.
Cheers, Andreas
| Kester Habermann wrote: |
|
Hello,
When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after the autosave. If the time is up, it is no longer possible to submit the report.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103
Regards
Kester
|
|
|
email notification authentication failed, posted by Xuan Wu on Fri Nov 13 11:26:12 2015
|
Hi All,
I got into trouble setting up the automated email notification.
elog.cfg:
;Send automatic email notifications
SMTP host = mail.ihep.ac.cn
;SMTP host = 127.0.0.1
;Some SMTP server require username/passowrd authentication
;elogd -t <your password> for creating SMTP password
SMTP username = wux@ihep.ac.cn
SMTP Password = .JYEytMGvsHANeCIfQJXmscIt4NOtzJ8GbAnh3XH280
;SMTP Password = V3gxMzYxODAxMjAxNA==
;No Email notification
Suppress Email to users = 1
elogd -v:
GET /LEBT/?cmd=Forgot&login_name=wux HTTP/1.1
timezone: -28800, offset: 28800
Email from <wux@ihep.ac.cn> to wux@ihep.ac.cn, SMTP host mail.ihep.ac.cn:
220 ihep.ac.cn Anti-spam GT for Coremail System (ihep[20151015])
EHLO 10.1.44.220
250-mail
250-PIPELINING
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-coremail 1Uxr2xKj7kG0xkI17xGrUDI0s8FY2U3Uj8Cz28x1UUUUU7Ic2I0Y2Url11UVUCa0xDrUUUUj
250-STARTTLS
250 8BITMIME
AUTH LOGIN
username:
wux@ihep.ac.cnPassword:
.JYEytMGvsHANeCIfQJXmscIt4NOtzJ8GbAnh3XH280
535 Error: authentication failed
test with telnet:
[wux@logbook ~/elog]$ telnet mail.ihep.ac.cn 25
Trying 202.38.128.6...
Connected to mail.ihep.ac.cn.
Escape character is '^]'.
220 ihep.ac.cn Anti-spam GT for Coremail System (ihep[20151015])
EHLO 10.1.44.220
250-mail
250-PIPELINING
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-coremail 1Uxr2xKj7kG0xkI17xGrUDI0s8FY2U3Uj8Cz28x1UUUUU7Ic2I0Y2Ur3T0__UCa0xDrUUUUj
250-STARTTLS
250 8BITMIME
AUTH LOGIN
334 dXNlcm5hbWU6
AUTH PLAIN
535 Error: authentication failed
Connection closed by foreign host.
Any advice and suggestions will be appreciate.
|