The dcos-rexray from mitel

Error getting authority

Thank you so much for this! I'm a noobie to this stuff so forgive me if this is a dumb question.

I got all the way down to where we need to restart the mesos slave service. I keep getting this error:

core@ip-10-0-0-30 ~ $ sudo systemctl stop dcos-mesos-slave.service
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to stop dcos-mesos-slave.service: Connection timed out
Failed to get load state of dcos-mesos-slave.service: Connection timed out

Any ideas? Thanks!

coredump when starting libmesos_dvdi_isolator-0.28.1.so

Hi,

I follow your procedure but dcos-mesos-slave never restart.
As I get a core dump I try to compile libmesos_dvdi_isolator-0.28.1.so by myself with latest version but I get the same error.
Do you have any idea of what is going wrong?

Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.161881  4956 state.cpp:89] Slave host rebooted
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.174623  4954 status_update_manager.cpp:200] Recovering status update manager
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.175006  4954 docker.cpp:773] Recovering Docker containers
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.175273  4951 containerizer.cpp:407] Recovering containerizer
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.176826  4951 docker_volume_driver_isolator.cpp:152] DockerVolumeDriverIsolator recover() was called
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.179658  4951 docker_volume_driver_isolator.cpp:177] dvdicheckpoint::recover() called
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: I0605 06:33:23.179944  4951 state.cpp:58] Recovering state from '/tmp/mesos'
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: ABORT: (/pkg/src/mesos/3rdparty/libprocess/3rdparty/stout/include/stout/result.hpp:114): Result::get() but state == NONE
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: *** Aborted at 1465108403 (unix time) try "date -d @1465108403" if you are using GNU date ***
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: PC: @     0x7f4e6996669b (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: *** SIGABRT (@0x134e) received by PID 4942 (TID 0x7f4e65e17700) from PID 4942; stack trace: ***
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e69cee0f0 (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6996669b (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e69967c61 (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @           0x40b8dc _Abort()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @           0x40b91c _Abort()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6b5e05eb Result<>::get()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e66e3224f mesos::slave::DockerVolumeDriverIsolator::recover()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6b703245 mesos::internal::slave::MesosContainerizerProcess::recoverIsolators()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6b70d929 mesos::internal::slave::MesosContainerizerProcess::_recover()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6b72a8f7 _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEEZNS0_8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERKSt4listINS6_5slave14ContainerStateESaISC_EERK7hashsetINS6_11ContainerIDESt4hashISI_ESt8equal_toISI_EESE_SN_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSU_FSS_T1_T2_ET3_T4_EUlS2_E_E9_M_invokeERKSt9_Any_dataS2_
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6bbd4881 process::ProcessManager::resume()
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6bbd4b87 _ZNSt6thread5_ImplISt12_Bind_simpleIFSt5_BindIFZN7process14ProcessManager12init_threadsEvEUlRKSt11atomic_boolE_St17reference_wrapperIS6_EEEvEEE6_M_runEv
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e6a1e3d73 (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e69ce452c (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 mesos-slave[4942]: @     0x7f4e69a2680d (unknown)
Jun 05 06:33:23 dcostest-gra1-slavepub01 systemd[1]: dcos-mesos-slave-public.service: Main process exited, code=dumped, status=6/ABRT
Jun 05 06:33:23 dcostest-gra1-slavepub01 systemd[1]: dcos-mesos-slave-public.service: Unit entered failed state.
Jun 05 06:33:23 dcostest-gra1-slavepub01 systemd[1]: dcos-mesos-slave-public.service: Failed with result 'core-dump'.

Thanks for your great job you by writing this procedure.

Bertrand

Package from installation link doesn't work with ec2 driver

Hi! Big thanks for the documentaion, but I faced the issue with version of rexray when install it via link that you provided.
curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s stable

When I was installed via it, I got exeption
invalid driver name

Link that works with AWS(ec2 driver) is
curl -sSL https://dl.bintray.com/emccode/rexray/install | sh -s -- stable 0.3.3

mitel / dcos-rexray Goto Github PK

dcos-rexray's People

Contributors

Stargazers

Watchers

dcos-rexray's Issues

Error getting authority

coredump when starting libmesos_dvdi_isolator-0.28.1.so

Package from installation link doesn't work with ec2 driver

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent