Thanks Fernando,<br><br>I thinks this arrangement looks fine. The only change I can think of is to handle the errors that end up in the logs in such a way that the user also gets informed of them. <br><br>In my example, if you hadn't pointed me to the logs I wouldn't have figured out what was going on. The ipcluster script should output a dignostic of the whole startup process, or at least spit out some meaningful error messages. What do you think about it?
<br><br>Flávio<br><br><div><span class="gmail_quote">On 11/21/06, <b class="gmail_sendername">Fernando Perez</b> <<a href="mailto:fperez.net@gmail.com">fperez.net@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 11/21/06, Brian Granger <<a href="mailto:ellisonbg.net@gmail.com">ellisonbg.net@gmail.com</a>> wrote:<br>> It looks like the engines are starting but are not finding the<br>> controller you have running. Things to check:
<br>><br>> 1. Do you have a firewall blocking ports on the controller's computer?<br>><br>> 2. Did you tell the engines where the controller is running:<br>><br>> ipengine --controller-ip=[ip of the machine running the controller]
<br>><br>> Another way of finding out what is going on is to start the<br>> ipcontroller and ipengine with the -l flags:<br>><br>> ipcontroller -l cont<br>> ipengine -l eng<br>><br>> These will cause the log files to be written to disk in the format:
<br>><br>> contpid.log<br>> engpig.log<br><br>Also, note that if you are using ipcluster to start things, it makes<br>all logs go to<br><br>~/.ipython/ipcluster-PID1-{con|eng}-HOST-PID2.log<br><br>where:<br><br> - PID1: PID of the starting process (the ipcluster script). This
<br>simply allows you to have a common lexicographical sorting tag for all<br>processes (controller and engines) coming from a given invocation of<br>iplucster.<br><br>- 'con' or 'eng': tag to mark whether that log file is for a
<br>controller or an engine<br><br>- HOST: host where that particular process is actually running.<br><br>- PID2: PID of that particular process (controller or engine).<br><br>This format seems to allow easy automatic organization, debugging and
<br>cleanup of logfiles, feel free to suggest improvements.<br><br>Cheers,<br><br>f<br></blockquote></div><br><br clear="all"><br>-- <br>Flávio Codeço Coelho<br>registered Linux user # 386432<br>---------------------------
<br>"Laws are like sausages. It's better not to see them being made."<br>Otto von Bismark