# ask-community

Praveen Kumar Jha

09/19/2022, 6:42 AM
Hi All, With the latest release of dagster of 1.0.7 the run_status_sensor is failing which was previously running on version 0.15.8 Below is the error message showing: dagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server File "/usr/local/lib/python3.8/site-packages/dagster/_daemon/", line 451, in _process_tick_generator yield from _evaluate_sensor( File "/usr/local/lib/python3.8/site-packages/dagster/_daemon/", line 502, in _evaluate_sensor sensor_runtime_data = repo_location.get_external_sensor_execution_data( File "/usr/local/lib/python3.8/site-packages/dagster/_core/host_representation/", line 789, in get_external_sensor_execution_data return sync_get_external_sensor_execution_data_grpc( File "/usr/local/lib/python3.8/site-packages/dagster/_api/", line 54, in sync_get_external_sensor_execution_data_grpc api_client.external_sensor_execution( File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 299, in external_sensor_execution chunks = list( File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 124, in _streaming_query raise DagsterUserCodeUnreachableError("Could not reach user code server") from e The above exception was caused by the following exception: grpc._channel._MultiThreadedRendezvous: <_MultiThreadedRendezvous of RPC that terminated with: status = StatusCode.UNAVAILABLE details = "failed to connect to all addresses; last error: UNKNOWN: Cannot assign requested address" debug_error_string = "UNKNOWN:Failed to pick subchannel {created_time:"2022-09-19T051137.721533249+00:00", children[UNKNOWNfailed to connect to all addresses; last error: UNKNOWN: Cannot assign requested address {created_time:"2022-09-19T051137.721531548+00:00", grpc_status:14}]}"
File "/usr/local/lib/python3.8/site-packages/dagster/_grpc/", line 122, in _streaming_query yield from response_stream File "/usr/local/lib/python3.8/site-packages/grpc/", line 426, in next return self._next() File "/usr/local/lib/python3.8/site-packages/grpc/", line 826, in _next raise self Can someone suggest what is the issue and why is it failing.


09/19/2022, 3:14 PM
Hey Praveen - I haven't seen this particular error before. Can you share more about how you're running dagster (locally? In Docker/k8s?) Does the problem go away if you downgrade to 0.15.8?