Forums » Software Installation »
start-leginon.py: K2 client does not import into Leginon Launcher
Added by Jason de la Cruz almost 11 years ago
Here is my situation:
1. Leginon clients were started successfully on K2 PC and microscope PC.
2. On Linux processing server, in the setup GUI (start-leginon.py), both microscope and K2 PC hostnames were added in the "Edit Clients" dialog; the Leginon main window started successfully.
3. When checking the clients, however, the K2 PC hostname does not show up in the Launcher list (from the Leginon main window), but the microscope hostname does, in addition to the hostname for the processing server.
I've checked the hosts file on all computers, and they all have each other's hostnames and IP addresses referenced. The hosts can ping each other via hostname. The test1.py and test2.py scripts were run successfully between the processing server and K2 PC. However, it seems as if the processing server does not see the K2 client.
I've repeated the steps above with only the K2 PC hostname added (only the K2 PC hostname specified as client) and noticed that the hostname for the processing server was added to Leginon instead of the K2 PC hostname. Please advise.
Replies (3)
RE: start-leginon.py: K2 client does not import into Leginon Launcher - Added by Anchi Cheng almost 11 years ago
Jason,
When you ran test1.py test2.py, did you try it both ways? Meaning test1.py starts at processing host and at K2 PC? The test only test TCP transport in one direction.
If K2 PC hostname does not appear in the available Launcher list in Leginon gui after you've added it in the Client list in the setup wizard, the two-way communication was not established.
RE: start-leginon.py: K2 client does not import into Leginon Launcher - Added by Jason de la Cruz almost 11 years ago
Hi Anchi,
Thanks for your suggestion. I had not tried the scripts in the other direction, i.e., test1.py on the processing server and test2.py on the K2 PC. Doing so succeeded with the message REMOTE CLIENT RESPONDED.
The solution was to enter the client hostname in all lowercase letters (where available) when specifying it on the processing server, even when the processing server is running on Windows. This is because python on the K2 PC reported the hostname in lowercase letters.
So, even if Windows shows its hostname as K2-PC, the python socket connection uses the lowercase: k2-pc.
The connection succeeded with the K2 hostname entered in lowercase letters, and I was able to use Leginon to acquire an image on the K2.
RE: start-leginon.py: K2 client does not import into Leginon Launcher - Added by Anchi Cheng almost 11 years ago
Jason,
Thanks for posting the solution. I've added a caution note in Start_Leginon_at_your_main_working_station_remotely with link to this issue.
Could you verify that test1.py on the K2 PC does give you all lower-case hostname? Thanks.