All dependencies satisfied
Enter custom installation directory or press enter
(C:\labscript_suite):
Adding to Python search path (C:\Users\QC-Eval\Anaconda3\envs\labscript\labscript_suite.pth)
Copying files
Traceback (most recent call last):
File "setup.py", line 527, in <module>
function(*args)
File "setup.py", line 419, in install
make_labconfig_file(install_folder)
File "setup.py", line 328, in make_labconfig_file
from labscript_utils.labconfig import LabConfig, default_config_path
File "C:\Users\QC-Eval\Labscript\installer\labscript_utils\__init__.py", line 49, in <module>
from labscript_utils.versions import get_version, VersionException, check_version
File "C:\Users\QC-Eval\Labscript\installer\labscript_utils\versions.py", line 196, in <module>
check_version('importlib_metadata', '0.17', '2.0')
File "C:\Users\QC-Eval\Labscript\installer\labscript_utils\versions.py", line 174, in check_version
version = get_version(module_name, project_name)
File "C:\Users\QC-Eval\Labscript\installer\labscript_utils\versions.py", line 142, in get_version
version = _get_metadata_version(project_name, import_path)
File "C:\Users\QC-Eval\Labscript\installer\labscript_utils\versions.py", line 85, in _get_metadata_version
dists = finder.find_distributions(name=project_name, path=[import_path])
TypeError: find_distributions() got an unexpected keyword argument 'name'
usage:
python setup.py install
python setup.py uninstall [<path>]
python setup.py build
python setup.py dist
python setup.py clean
python -m runviewer
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.8/runpy.py", line 192, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.8/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 24, in <module>
check_version('labscript_utils', '2.10.0', '3')
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/versions.py", line 206, in check_version
_initialise()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/versions.py", line 49, in _initialise
'importlib_metadata', '0.17', '2.0', version=importlib_metadata.__version__
AttributeError: module 'importlib.metadata' has no attribute '__version__'
--
You received this message because you are subscribed to the Google Groups "The labscript suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/d0d22695-44bf-46b6-a5bf-df9771b72bd4%40googlegroups.com.
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
python -m zprocess.lock
Hi Fred,This is because of some changes in Python 3.8. The importlib_metadata package was made part of the standard library, and dropped its __version__ attribute.The pull request to add Python 3.8 compatibility to check_version() is here:I haven't merged it yet. There may be other issues running with Python 3.8 as well. This one:Has been merged into BLACS, so you will want to update to get that too. Please report bugs if you hit any others!It might be the case that not all of our dependencies have Python 3.8 builds in the conda repositories yet for all platforms. h5py seems to only have win-64 and linux-64 builds for example. pyzmq is missing a win-32 build as well. If support is missing for anything on your platform, you can either stick to Python 3.7 for a bit longer, or resort to installing the packages from pip (which can be messy since conda is not as good at managing packages installed by pip).In the not too distant future, labscript suite components will be installable as conda packages. So it will be a bit more obvious whether we support a new Python version or not since we simply will not have built new packages for the new Python version until we've done some basic testing and merged the required changes.-Chris
To unsubscribe from this group and stop receiving emails from it, send an email to labscri...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/74d6f3aa-3faf-4140-9b1d-34c9212dca71%40googlegroups.com.
(lss3) fredjendrzejewski@MacBook-Air-5 labscript_suite % python -m runviewer
Traceback (most recent call last):
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 343, in ensure_connected_to_zlog
client.ping(timeout=0.05)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 58, in <module>
logger = setup_logging('runviewer')
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/setup_logging.py", line 37, in setup_logging
ensure_connected_to_zlog()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 353, in ensure_connected_to_zlog
client.ping(timeout=15)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
HI Fred,Which component is failing to connect (i.e. could I see more lines of the traceback)? It could be zlog (the logging server that starts automatically) instead of zlock. You might try opening process explorer (this one is great if you don't already use it - will show you the command line of the processes etc) and killing Python processes to ensure another copy of zlog or zlock is not running.The line to run to manually start zlock using settings configured from labconfig is:python -m labscript_utils.zlockThough python -m zprocess.zlock or python -m zprocess.locking (the latter is now an alias for the former) should both work fine if you are running zlock on the default port and not using encryption (labscript_utils.zlock is just a wrapper that sets these).One frustrating issue I've been seeing here at NIST is that some computers are only able to be looked up by hostname for IPV6, the local DNS is not giving IPv4 addresses. This causes some computers to fail to connect to each other when given hostnames (though "localhost" should be fine...). I enabled IPV6 in zprocess to fix the issue, but hit some other bugs and reverted it for the time being. So the workaround for that (if you're running zlock on a different computer to everything else which it sounds like you're not) is to specify the zlock host in labconfig as an IPV4 address instead of a hostname. I hope to get zprocess working properly with IPV6 soon.-Chris
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/74d6f3aa-3faf-4140-9b1d-34c9212dca71%40googlegroups.com.
Excellent. This shows that zlog is not running, so runviewer tries to start it, but then it is still not running. Could you try running:
python -m labscript_utils.zlog
And posting presumably what will be an error showing zlog failing to start?
I recently changed the way that zlog decides where to write its own log file (a bit meta - the logging server has a log file), so perhaps there is a bug with that.
-Chris
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/a826cd47-de24-488a-a1c6-cc9d234af685%40googlegroups.com.
Oh, I spoke to soon, I misread the code. I did indeed tell it to make the directory if it doesn’t exist:
if directory is not None:
logpath = os.path.join(directory, '%s.log' % name)
if not os.path.exists(directory):
os.mkdir(directory)
else:
logpath = None
So I’m out of ideas again - will hopefully get some clue what’s wrong from any error message zlog gives you.
-Chris
python -m labscript_utils.zlog
[2019-12-03 20:00:22,712] WARNING Can't open or do not have permission to write to log file /var/log/zlog.log. Only terminal logging will be output.
[2019-12-03 20:00:22,712] INFO This is zlog server, running on tcp://0.0.0.0:7340
Excellent. This shows that zlog is not running, so runviewer tries to start it, but then it is still not running. Could you try running:
python -m labscript_utils.zlog
And posting presumably what will be an error showing zlog failing to start?
I recently changed the way that zlog decides where to write its own log file (a bit meta - the logging server has a log file), so perhaps there is a bug with that.
-Chris
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/a826cd47-de24-488a-a1c6-cc9d234af685%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/6c9e4427-965d-486b-9f5b-8b5efa0f11e4%40googlegroups.com.
Hi Fred,
Something is fishy! Zprocess up to 2.18.0 tries to log to /var/log/zlog.log, but zprocess 2.18.1 doesn't try to make a log file unless requested to by labscript_utils.zlog (which doesn't ask it to - the change for that hasn't been merged yet). So based on that warning, it looks like you're running zprocess less than 2.18.1. Also, in zprocess 2.16 the bind address changed from 'tcp://0.0.0.0' to 'tcp://*' (which mean the same thing except the latter includes IPv6). So it seems based on that log line that you're running zprocess < 2.16. What do you get if you run in Python:import zprocessprint(zprocess.__version__)print(zprocess.__file__)
>>> import zprocess
>>> print(zprocess.__version__)
2.18.1
>>> print(zprocess.__file__)
/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/__init__.py
Also, since you are able to start zlog manually, is runviewer able to start whilst it is running? Do you see any output in the zlog terminal saying that it received requests from runviewer?
[2019-12-03 20:50:43,618] INFO This is zlog server, running on tcp://*:7340
[2019-12-03 20:50:48,391] INFO [127.0.0.1] said hello
[2019-12-03 20:50:48,393] INFO [127.0.0.1] Access confirmed for /Users/fredjendrzejewski/labscript_suite/runviewer/runviewer.log
[2019-12-03 20:51:04,428] INFO Opening /Users/fredjendrzejewski/labscript_suite/runviewer/runviewer.log
[2019-12-03 20:51:04,428] INFO New client (total: 1) for /Users/fredjendrzejewski/labscript_suite/runviewer/runviewer.log
[2019-12-03 20:51:04,439] INFO [127.0.0.1] Client done (remaining: 0) with /Users/fredjendrzejewski/labscript_suite/runviewer/runviewer.log
[2019-12-03 20:51:04,440] INFO No more clients, closing /Users/fredjendrzejewski/labscript_suite/runviewer/runviewer.log
2019-12-03 20:51:04,425 ERROR runviewer: Got an exception:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 302, in connect_to_zlock_server
client.ping(timeout=0.05)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 105, in ping
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 85, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 62, in <module>
import labscript_utils.h5_lock
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/h5_lock.py", line 104, in <module>
connect_to_zlock_server()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 312, in connect_to_zlock_server
client.ping(timeout=15)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 105, in ping
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 85, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
Traceback (most recent call last):
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 302, in connect_to_zlock_server
client.ping(timeout=0.05)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 105, in ping
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 85, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 62, in <module>
import labscript_utils.h5_lock
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/h5_lock.py", line 104, in <module>
connect_to_zlock_server()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 312, in connect_to_zlock_server
client.ping(timeout=15)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 105, in ping
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlock/__init__.py", line 85, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
You might have a broken zprocess install. If you run in a terminal:cd /Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/ls | grep zprocessWhat do you see? You should see the following:zprocess
zprocess-2.18.1-py3.8.egg-info
zprocess
zprocess-2.18.1.dist-info
If there is more than one zprocess folder there, you might try running rm -rf zprocess* in that directory (this will remove all traces of zprocess) and installing zprocess again. If it is a broken install, this is the kind of thing I'm trying to avoid by moving to conda packages :). If you do delete all traces of pip-installed zprocess, you might consider trying my experimental conda package for zprocess:conda install -c cbillington zprocess
There is one other possibility for a broken install, and this would be if you had run pip install --user zprocess. This would have installed zprocess to some subdirectory of your home directory, I don't know which. But print(zprocess.__file__) from above should reveal if this is the case.We'll get to the bottom of this!-Chris
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/6c9e4427-965d-486b-9f5b-8b5efa0f11e4%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/443920d6-e8ac-4397-9597-72c7fd4a0ebe%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "The labscript suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/2cf9b639-7f09-4cce-97c1-611775e16818%40googlegroups.com.
Good to hear!You're welcome, but if you have time I'd like to get to bottom of it so that I can resolve the issue for osx. So some questions if you don't mind! If you don't have time that's ok. Anyone else with a mac feel free to chime in, otherwise I might harass mac-owning friends later to investigate.1. What update are you referring to, before which you didn't need to start servers manually? osx, Python, zprocess, labscript_utils? Do you recall which version (even approximately, or as a duration of time since you last updated it) of the relevant component you were on previously?
2. Does the following code create a text file in your home directory?import osfrom subprocess import DEVNULL, Popen
import tempfile
def start_daemon(cmd):
if not os.fork():
os.setsid()
Popen(
cmd,
stdin=DEVNULL,
stdout=DEVNULL,
stderr=DEVNULL,
close_fds=True,
cwd=tempfile.gettempdir(),
)
HOME = os.getenv('HOME')
start_daemon(['python', '-c', f'open("{HOME}/yes_it_works.txt", "w")'])Don't forget to delete the file if so, then...
3. What about if you replace DEVNULL with open(os.devnull, 'w'), does it create the file then? (I realised we're passing devnull in 'write' mode as stdin to the processes, that might be not allowed!)
4. In labscript_utils.ls_zprocess you will see two functions connect_to_zlock_server() and ensure_connected_to_zlog(), which are the functions responsible for starting the two servers if they're not running. They both have lines likezprocess.start_daemon(
[sys.executable, '-m', 'labscript_utils.zlock', '--daemon'])What happens if you remove '--daemon' from both of the lists? Can you then start runviewer without having to manually start the servers?
Traceback (most recent call last):
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 343, in ensure_connected_to_zlog
client.ping(timeout=0.05)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 58, in <module>
logger = setup_logging('runviewer')
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/setup_logging.py", line 37, in setup_logging
ensure_connected_to_zlog()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 353, in ensure_connected_to_zlog
client.ping(timeout=15)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
5. What happens if you keep '--daemon', but replace zprocess.start_daemon with subprocess.Popen (you'll need to add import subprocess at the top of the file)?
/Users/fredjendrzejewski/miniconda3/envs/lss3/bin/python: Error while finding module specification for 'labscript_utils.zlog' (ModuleNotFoundError: No module named 'labscript_utils')
Traceback (most recent call last):
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 345, in ensure_connected_to_zlog
client.ping(timeout=0.05)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/Users/fredjendrzejewski/labscript_suite/runviewer/__main__.py", line 58, in <module>
logger = setup_logging('runviewer')
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/setup_logging.py", line 37, in setup_logging
ensure_connected_to_zlog()
File "/Users/fredjendrzejewski/labscript_suite/labscript_utils/ls_zprocess.py", line 355, in ensure_connected_to_zlog
client.ping(timeout=15)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 116, in ping
self._send(b'hello', timeout=timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 90, in _send
self._new_socket(timeout)
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/zlog/__init__.py", line 71, in _new_socket
'tcp://%s:%s' % (self.host, str(self.port)), timeout=timeout
File "/Users/fredjendrzejewski/miniconda3/envs/lss3/lib/python3.7/site-packages/zprocess/security.py", line 251, in connect
raise TimeoutError('Could not connect to server: timed out')
zprocess.utils.TimeoutError: Could not connect to server: timed out
The motivation for test 2 is to see if we can create daemon processes (processes that keep running after their parents exit) at all in your environment. Test 3 is one hypothesis about how we might be doing this wrong. Tests 4 and 5 are because I can see we're actually "daemonising" the processes twice - we're creating a daemon process that is creating another daemon process. The tests are to see what happens if we only do it once by removing each of the two steps one a time.-Chris
To unsubscribe from this group and stop receiving emails from it, send an email to labscri...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/38954e39-de42-4894-a9a7-f8d1bd2ea773%40googlegroups.com.
Thanks Fred.Unfortunately that gives me no leads, since no changes to labscript code made it work, and no isolated tests of similar functionality didn't work. I'll see if I can commandeer a friend's mac and reproduce the issue, and continue to home in on the place that must exist between the isolated examples and the non-working real code.Wouldn't be surprised if it is a new mac security feature to not allow spawning background processes in some cases, it seems to be the trend for apple to be locking things down a bit more. Might have to have labscript code talk with launchd to start a background service the official way.-Chris
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/38954e39-de42-4894-a9a7-f8d1bd2ea773%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/c903d155-16ab-47d9-8e3d-39f0c1ad72bd%40googlegroups.com.