You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Marc Roos <M....@f1-outsourcing.eu> on 2020/08/22 18:56:33 UTC
mesosphere csilvm doesn't have socket after startup
I am not sure if the csi standard requires that CSI_ENDPOINT should be
set, in any case.
- csilvm does not work without specifically setting -unix-addr-env
CSI_ENDPOINT. So either document this or make it default.
- I could not test with csc on csilvm master branch only this update csi
1.2(?). So merge this pull request finally, so other people do not waste
time trying to get this master working.
E0822 19:00:42.980020 18830 provider.cpp:541] Failed to recover resource
provider with type 'org.apache.mesos.rp.local.storage' and name
'local_vg': Timed out waiting for endpoint
'unix:///tmp/mesos-csi-Q16CR1/endpoint.sock'
E0822 19:00:42.980559 18828 container_daemon.cpp:150] Failed to launch
container
'org-apache-mesos-rp-local-storage-local_vg--io-mesosphere-csi-lvm-csilv
m--CONTROLLER_SERVICE-NODE_SERVICE': Timed out waiting for endpoint
'unix:///tmp/mesos-csi-Q16CR1/endpoint.sock'
E0822 19:00:42.980654 18828 service_manager.cpp:751] Container daemon
for
'org-apache-mesos-rp-local-storage-local_vg--io-mesosphere-csi-lvm-csilv
m--CONTROLLER_SERVICE-NODE_SERVICE' failed: Timed out waiting for
endpoint 'unix:///tmp/mesos-csi-Q16CR1/endpoint.sock'