Closed sf-migrator-bot closed 8 years ago
I'm assuming more should follow. The problem is that when running spock, everything stops after storing profile, right when spock should actually open.
Original comment by: juvanjan@SF (http://sf.net/u/juvanjan)
Hi,
For pure questions (not bugs/feature-requests) the sardana-users mailing list is a better place. Could you please send your question there?
https://lists.sourceforge.net/lists/listinfo/sardana-users
Original comment by: cpascual (http://sf.net/u/cpascual)
Original comment by: cpascual (http://sf.net/u/cpascual)
On a second though, I see that this can indeed be a bug report, so I write some reply here:
Please try the following:
+++++++++++++++++++++++++++++++ Open a new terminal and run:
~$ Pool demo1 --log-level=debug
(answer "Y" to question about create new instance. The last line should be something similar to: "MainThread INFO 2014-03-20 14:37:26,504 TaurusRootLogger: Ready to accept request in 0:00:00.998257")
Open another terminal and run: ~$ MacroServer demo1 --log-level=debug
(answer "Y" to question about create new instance) (copy the pool name printed above and press ENTER twice) (some log appears... the last line should be similar to: "MainThread INFO 2014-03-20 14:41:02,843 TaurusRootLogger: Ready to accept request in 0:00:08.827606")
Open another terminal and run: ~$ spock
(you should get a spock prompt) +++++++++++++++++++++++++++++++
If something does not work, pleasesend the full output from each terminal. Also send us the versions of python, tango, pytango, taurus and sardana that you are using and any info such as the way you installed them)
Note, I adapted the above instructions from: https://sourceforge.net/p/sardana/wiki/SardanaTraining-WorkshopBCN20130522/
Original comment by: cpascual (http://sf.net/u/cpascual)
Pool ends with "ready to accept request" MacroServer stops at "creating pool ..." (registering pool) this happens in code: http://www.sardana-controls.org/_modules/sardana/macroserver/macroserver.html
After adding some more logging print-outs, i've pinpointed the problem to the line: pool = Device(name)
Sardana - 1.3.1 Tango - 8.1.2 Python - 2.6.6 iPython - 0.10 Taurus - 3.2.0 pyTango - 8.1.1 pyQt - 4.6.2 pyQwt - Taurus reports 5.1.1, installed version is 5.2
(for the following ill-ordered spam I apologise)
yum install http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm yum install http://rpms.famillecollet.com/enterprise/remi-release-5.rpm yum install gcc-c++ boost kernel-devel kernel-headers omniORB-devel zlib-devel libtool doxygen mysql-devel mysql-server java-1.7.0-openjdk-devel
Tango: http://sourceforge.net/projects/tango-cs/files/tango-8.1.2c.tar.gz/download ./configure --with-mysql-ho=databaseHostname --with-mysql-admin=databaseUsername --with-mysql-admin-passwd=passwordForUser --with-mysqlclient-lib=/usr/lib64/mysql
PyTango: yum install boost-python boost-devel numpy python-devel ipython export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig easy_install -U PyTango
Additional: yum install flex bison qt-devel qt-mysql sip-devel PyQt4-devel PyQwt-devel libxslt-devel PyQt4-webkit PyXML SOAPpy h5py numpy-f2py spyder openpgm pyOpenSSL pyflakes python-argparse python-dateutil python-foolscap python-imaging python-matplotlib python-lxml python-ply scipy rpm -Uvh ftp://ftp.maxlab.lu.se/pub/maxlab/packages/el6/x86_64/maxlab-release-2-1.el6.maxlab.x86_64.rpm yum install PyMca python-guiqwt python-guidata
Original comment by: juvanjan@SF (http://sf.net/u/juvanjan)
Appending logs
Original comment by: juvanjan@SF (http://sf.net/u/juvanjan)
Is the pool still running on the other terminal? And, are you passing the correct pool name to the macroserver?
I notice that in your MS log, the last line says: Creating pool Pool_demo1_1 That means that you gave the door alias ('Pool_demo1_1') to the macroserver when prompted. It should be ok (in fact I tested in my case and worked ok), but I normally give the tango device name ('Pool/demo1/1') and I wonder if the problem may be there.
To check, try the following
Here is an example on how it goes on my computer. Try to reproduce it: (I will intercalate my own comments preceded by "#####")
###################################################
#### ON ONE TERMINAL:
#### Create a new Door: USE A NEW NAME!!! (e.g. demo2)
~$ Pool demo2 --log-level=debug
demo2 does not exist. Do you wish create a new one (Y/n) ?
#### Y<ENTER>
####(...) It should get to the "accepting requests" line
###################################################
#### ON A DIFERENT TERMINAL (without closing the previous one):
~$ MacroServer demo2 --log-level=debug
demo2 does not exist. Do you wish create a new one (Y/n) ?
#### Y<ENTER>
#### Now you should get a list of available Pools and their state:
#### Make sure that it says that Pool/demo2/1 is running
Pool_demo1_1 (a.k.a. Pool/demo1/1)
Pool_demo2_1 (a.k.a. Pool/demo2/1) (running)
#### And now you get a prompt for introducing the Pool name.
#### Make sure to copy the pool name exactly as I write it below
#### and then hitting <ENTER> twice
Please select pool to connect to (return to finish): Pool/demo2/1
Please select pool to connect to (return to finish):
#### (...) You may get a warning about "EventChannel": ignore it.
#### and then many INFO and DEBUG logs till we get to the following lines:
MainThread DEBUG 2014-03-21 08:42:56,824 MS_demo2_1: Creating pool Pool/demo2/1
MainThread DEBUG 2014-03-21 08:42:56,917 Door/demo2/1: -> init_device
MainThread DEBUG 2014-03-21 08:42:56,919 Door/demo2/1: <- init_device
MainThread INFO 2014-03-21 08:42:56,922 TaurusRootLogger: Ready to accept request in 0:00:24.211205
###################################################
#### Now, EVEN IF YOU STILL GOT STUCK on the Creating pool line,...
#### OPEN A THIRD TERMINAL (without closing the other two) and try:
~$ ipython
In [1]: import taurus
In [2]: pool = taurus.Device('Pool/demo2/1')
In [3]: pool.state()
Out[3]: PyTango._PyTango.DevState.ON
In [4]: ms = taurus.Device('MacroServer/demo2/1')
In [5]: ms.state()
Out[5]: PyTango._PyTango.DevState.ON
In [6]: door = taurus.Device('Door/demo2/1')
In [7]: door.state()
Out[7]: PyTango._PyTango.DevState.ON
Original comment by: cpascual (http://sf.net/u/cpascual)
I've followed your instructions and I get the same result as before.
Yesterday I've created a fresh copy of CentOS and am now appending exact installation process as well as interesting output from installing PyTango.
Appending both logs and Ipython output aswell.
Original comment by: juvanjan@SF (http://sf.net/u/juvanjan)
Taurus dependencies: Checking required dependencies of taurus.core... Checking for Python >=2.6.0... [OK] (Found 2.6.6) Checking for PyTango >=7.1.0... [OK] (Found 8.1.1) Checking required dependencies of taurus.qt... Checking for PyQt >=4.4.0... [OK] (Found 4.6.2) Checking for PyQwt >=5.2.0... [OK] (Found 5.2.1) Checking OPTIONAL dependencies of taurus.qt... Checking for Qub >=1.0.0... [WARNING] (Not found]) Checking for spyderlib >=2.0.0... [OK] (Found 2.1.10) Checking for qtcontrols >=1.0.0... [WARNING] (Not found])
After checking the code, everything stops at: pool = Device(name) ...in file: http://www.sardana-controls.org/_modules/sardana/macroserver/macroserver.html
Original comment by: juvanjan@SF (http://sf.net/u/juvanjan)
Hi. Sorry for the long silence...
From your install_process.txt I see that you install zmq from upstream. If you installed zmq>=4, you may have hit this issue (which I just recently discovered):
https://sourceforge.net/p/tango-cs/bugs/662/
If that is the case, you could apply the already existing patch to Tango (or you could install zmq 3.2.4)
Original comment by: cpascual (http://sf.net/u/cpascual)
Original comment by: cpascual (http://sf.net/u/cpascual)
Original comment by: cpascual (http://sf.net/u/cpascual)
Original comment by: reszelaz (http://sf.net/u/zreszela)
Hi Jan,
Long time has passed from your last message, so I believe you must have solved your problem. I will proceed to close this ticket. If actually you still need any help don't hesitate to reply here or drop a message to the users mailing list.
Cheers, Zibi
Original comment by: reszelaz (http://sf.net/u/zreszela)
Hej,
I actually encountered the same problem. On Linux Sardana starts without problems with the following version numbers installed:
But on Windows (10) Sardana stops when creating the pool. Starting the Pool and the Macroserver by hand and then running Spock is also fine, but I guess it would be nice to figure out, why Sardana is not starting up correctly. I installed the following versions on the Win machine:
Best
Daniel
Hello! As I found no other place where to seek help regarding Sardana I'll try here.
I've installed sardana on CentOS and am facing a problem. Running Pool from command line works, but if I run Sardana or MacroServer it stops at "creating pool ..." debug message.
Reported by: juvanjan@SF ( http://sf.net/u/juvanjan )
Original Ticket: sardana/tickets/145