Cannot connect to LabRAD about scalabrad HOT 5 CLOSED

If this is a firewall problem it's going to take me a loooong time to figure it out. Help appreciated there.

from scalabrad.

@DanielSank, two recent issues I had that are potentially related are:

1. Error message "Expected STARTTLS" - #36
2. Error message "Exception: Connection lost." - labrad/pylabrad#186

Some questions which may be useful in the diagnosis:

1. Which pylabrad commit are you running (on all affected computers)?

2. When you run the scalabrad manager, what is the full command you are using? (Particularly any flags used)

3. Can you figure out which scalabrad version you are running? If running from the source, which commit? If from bintray, try looking in the following locations:

   a. Full directory where the manager is located (should be SCALABRAD/bin/labrad); look in the last folder of SCALABRAD.
   b. SCALABRAD/lib/scalabrad_2.11-xxx.jar. Please provide xxx (e.g., 0.5.1, 0.4.0, etc.)

from scalabrad.

Here's a copypasta from the ansible script which started the manager

[Unit]
Description=Labrad Manager

[Service]
ExecStartPre=mkdir -p /var/run/labrad
ExecStart={{ lrdir }}/scalabrad/bin/labrad --password {{ lrpass }} --registry file:///var/lib/labrad/registry.sqlite --tls-required false
Restart=always
RestartSec=5s
User=labrad
Environment=LABRADNODE={{ nodename }}
Environment=PYTHONPATH={{ lrdir }}/pylabrad:{{ lrdir }}
Environment=LABRADPASSWORD={{ lrpass }}

[Install]
WantedBy=multi-user.target

I'm guessing the --tls-required false is relevant, but not sure.

from scalabrad.

1. Which pylabrad commit are you running (on all affected computers)?

On the client machine: 88606135acf01e03e2df924ab2cd7a37a0762149. I'm not sure how the pylabrad version on the manager is relevant.

1. When you run the scalabrad manager, what is the full command you are using? (Particularly any flags used)

See previous post.

1. Can you figure out which scalabrad version you are running? If running from the source, which commit?

0.5.1

from scalabrad.

This was a firewall problem. The solution was to open tcp on 7682.

Thank you, @ejeffrey.

from scalabrad.