[jira] [Commented] (MESOS-8278) Mesos Containerizer cannot recover due to check failure.

2018-01-19 Thread Gilbert Song (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333109#comment-16333109
 ] 

Gilbert Song commented on MESOS-8278:
-

[~kaysoky] [~jieyu] , not impacted by standalone container changes. Please see 
https://issues.apache.org/jira/browse/MESOS-8416 for root cause.

> Mesos Containerizer cannot recover due to check failure.
> 
>
> Key: MESOS-8278
> URL: https://issues.apache.org/jira/browse/MESOS-8278
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: Gilbert Song
>Priority: Critical
>  Labels: containerizer, csi-post-mvp, standalone
>
> Mesos containerizer cannot recover due to a check failure on nested 
> container's sandbox directory.
> {noformat}
> I1129 22:00:42.556479  5812 containerizer.cpp:670] Recovering containerizer
> F1129 22:00:42.560739  5812 containerizer.cpp:912] CHECK_SOME(directory): is 
> NONE 
> *** Check failure stack trace: ***
> @ 0x7f7e6cf1294d  google::LogMessage::Fail()
> @ 0x7f7e6cf11d1e  google::LogMessage::SendToLog()
> @ 0x7f7e6cf1261d  google::LogMessage::Flush()
> @ 0x7f7e6cf15a98  google::LogMessageFatal::~LogMessageFatal()
> @ 0x55ca72a95197  _CheckFatal::~_CheckFatal()
> @ 0x7f7e6bb23770  
> mesos::internal::slave::MesosContainerizerProcess::recover()
> @ 0x7f7e6bbe643c  
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS4_5state10SlaveStateEESB_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_EOT2_ENKUlRS9_PNS_11ProcessBaseEE_clESP_SR_
> @ 0x7f7e6bbe6295  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi16__callIvJOSS_EJLm0ELm1SE_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
> @ 0x7f7e6bbe61f6  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi1clIJSS_EvEESH_DpOT_
> @ 0x7f7e6bbe5f02  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEESt5_BindIFZNS0_8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS9_5state10SlaveStateEESG_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSL_FSJ_T1_EOT2_EUlRSE_S2_E_SE_St12_PlaceholderILi1E9_M_invokeERKSt9_Any_dataOS2_
> @ 0x7f7e6ce37cf4  std::function<>::operator()()
> @ 0x7f7e6ce1ded4  process::ProcessBase::visit()
> @ 0x7f7e6cea38fe  process::DispatchEvent::visit()
> @ 0x7f7e6a9741b1  process::ProcessBase::serve()
> @ 0x7f7e6ce1a8eb  process::ProcessManager::resume()
> @ 0x7f7e6ce2b86e  
> process::ProcessManager::init_threads()::$_7::operator()()
> @ 0x7f7e6ce2b715  
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvE3$_7vEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> @ 0x7f7e6ce2b6e5  std::_Bind_simple<>::operator()()
> @ 0x7f7e6ce2b6bc  std::thread::_Impl<>::_M_run()
> @ 0x7f7e6617d030  (unknown)
> @ 0x7f7e65c966aa  start_thread
> @ 0x7f7e659cbe9d  (unknown)
> {noformat}
> Maybe related to the change of standalone container support.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MESOS-8278) Mesos Containerizer cannot recover due to check failure.

2017-12-15 Thread Jie Yu (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292986#comment-16292986
 ] 

Jie Yu commented on MESOS-8278:
---

[~kaysoky] I am not sure, probably unrelated.

> Mesos Containerizer cannot recover due to check failure.
> 
>
> Key: MESOS-8278
> URL: https://issues.apache.org/jira/browse/MESOS-8278
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: Gilbert Song
>Priority: Critical
>  Labels: containerizer, csi-post-mvp, standalone
>
> Mesos containerizer cannot recover due to a check failure on nested 
> container's sandbox directory.
> {noformat}
> I1129 22:00:42.556479  5812 containerizer.cpp:670] Recovering containerizer
> F1129 22:00:42.560739  5812 containerizer.cpp:912] CHECK_SOME(directory): is 
> NONE 
> *** Check failure stack trace: ***
> @ 0x7f7e6cf1294d  google::LogMessage::Fail()
> @ 0x7f7e6cf11d1e  google::LogMessage::SendToLog()
> @ 0x7f7e6cf1261d  google::LogMessage::Flush()
> @ 0x7f7e6cf15a98  google::LogMessageFatal::~LogMessageFatal()
> @ 0x55ca72a95197  _CheckFatal::~_CheckFatal()
> @ 0x7f7e6bb23770  
> mesos::internal::slave::MesosContainerizerProcess::recover()
> @ 0x7f7e6bbe643c  
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS4_5state10SlaveStateEESB_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_EOT2_ENKUlRS9_PNS_11ProcessBaseEE_clESP_SR_
> @ 0x7f7e6bbe6295  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi16__callIvJOSS_EJLm0ELm1SE_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
> @ 0x7f7e6bbe61f6  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi1clIJSS_EvEESH_DpOT_
> @ 0x7f7e6bbe5f02  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEESt5_BindIFZNS0_8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS9_5state10SlaveStateEESG_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSL_FSJ_T1_EOT2_EUlRSE_S2_E_SE_St12_PlaceholderILi1E9_M_invokeERKSt9_Any_dataOS2_
> @ 0x7f7e6ce37cf4  std::function<>::operator()()
> @ 0x7f7e6ce1ded4  process::ProcessBase::visit()
> @ 0x7f7e6cea38fe  process::DispatchEvent::visit()
> @ 0x7f7e6a9741b1  process::ProcessBase::serve()
> @ 0x7f7e6ce1a8eb  process::ProcessManager::resume()
> @ 0x7f7e6ce2b86e  
> process::ProcessManager::init_threads()::$_7::operator()()
> @ 0x7f7e6ce2b715  
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvE3$_7vEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> @ 0x7f7e6ce2b6e5  std::_Bind_simple<>::operator()()
> @ 0x7f7e6ce2b6bc  std::thread::_Impl<>::_M_run()
> @ 0x7f7e6617d030  (unknown)
> @ 0x7f7e65c966aa  start_thread
> @ 0x7f7e659cbe9d  (unknown)
> {noformat}
> Maybe related to the change of standalone container support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-8278) Mesos Containerizer cannot recover due to check failure.

2017-12-15 Thread Joseph Wu (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292980#comment-16292980
 ] 

Joseph Wu commented on MESOS-8278:
--

[~jieyu] Is this fixed by https://reviews.apache.org/r/64623/ ?

> Mesos Containerizer cannot recover due to check failure.
> 
>
> Key: MESOS-8278
> URL: https://issues.apache.org/jira/browse/MESOS-8278
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: Gilbert Song
>Priority: Critical
>  Labels: containerizer, csi-post-mvp, standalone
>
> Mesos containerizer cannot recover due to a check failure on nested 
> container's sandbox directory.
> {noformat}
> I1129 22:00:42.556479  5812 containerizer.cpp:670] Recovering containerizer
> F1129 22:00:42.560739  5812 containerizer.cpp:912] CHECK_SOME(directory): is 
> NONE 
> *** Check failure stack trace: ***
> @ 0x7f7e6cf1294d  google::LogMessage::Fail()
> @ 0x7f7e6cf11d1e  google::LogMessage::SendToLog()
> @ 0x7f7e6cf1261d  google::LogMessage::Flush()
> @ 0x7f7e6cf15a98  google::LogMessageFatal::~LogMessageFatal()
> @ 0x55ca72a95197  _CheckFatal::~_CheckFatal()
> @ 0x7f7e6bb23770  
> mesos::internal::slave::MesosContainerizerProcess::recover()
> @ 0x7f7e6bbe643c  
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS4_5state10SlaveStateEESB_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_EOT2_ENKUlRS9_PNS_11ProcessBaseEE_clESP_SR_
> @ 0x7f7e6bbe6295  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi16__callIvJOSS_EJLm0ELm1SE_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
> @ 0x7f7e6bbe61f6  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi1clIJSS_EvEESH_DpOT_
> @ 0x7f7e6bbe5f02  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEESt5_BindIFZNS0_8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS9_5state10SlaveStateEESG_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSL_FSJ_T1_EOT2_EUlRSE_S2_E_SE_St12_PlaceholderILi1E9_M_invokeERKSt9_Any_dataOS2_
> @ 0x7f7e6ce37cf4  std::function<>::operator()()
> @ 0x7f7e6ce1ded4  process::ProcessBase::visit()
> @ 0x7f7e6cea38fe  process::DispatchEvent::visit()
> @ 0x7f7e6a9741b1  process::ProcessBase::serve()
> @ 0x7f7e6ce1a8eb  process::ProcessManager::resume()
> @ 0x7f7e6ce2b86e  
> process::ProcessManager::init_threads()::$_7::operator()()
> @ 0x7f7e6ce2b715  
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvE3$_7vEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> @ 0x7f7e6ce2b6e5  std::_Bind_simple<>::operator()()
> @ 0x7f7e6ce2b6bc  std::thread::_Impl<>::_M_run()
> @ 0x7f7e6617d030  (unknown)
> @ 0x7f7e65c966aa  start_thread
> @ 0x7f7e659cbe9d  (unknown)
> {noformat}
> Maybe related to the change of standalone container support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MESOS-8278) Mesos Containerizer cannot recover due to check failure.

2017-12-06 Thread Adam B (JIRA) 

[ 
https://issues.apache.org/jira/browse/MESOS-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281410#comment-16281410
 ] 

Adam B commented on MESOS-8278:
---

cc: [~kaysoky]

> Mesos Containerizer cannot recover due to check failure.
> 
>
> Key: MESOS-8278
> URL: https://issues.apache.org/jira/browse/MESOS-8278
> Project: Mesos
>  Issue Type: Bug
>  Components: containerization
>Reporter: Gilbert Song
>Priority: Critical
>  Labels: containerizer, standalone
>
> Mesos containerizer cannot recover due to a check failure on nested 
> container's sandbox directory.
> {noformat}
> I1129 22:00:42.556479  5812 containerizer.cpp:670] Recovering containerizer
> F1129 22:00:42.560739  5812 containerizer.cpp:912] CHECK_SOME(directory): is 
> NONE 
> *** Check failure stack trace: ***
> @ 0x7f7e6cf1294d  google::LogMessage::Fail()
> @ 0x7f7e6cf11d1e  google::LogMessage::SendToLog()
> @ 0x7f7e6cf1261d  google::LogMessage::Flush()
> @ 0x7f7e6cf15a98  google::LogMessageFatal::~LogMessageFatal()
> @ 0x55ca72a95197  _CheckFatal::~_CheckFatal()
> @ 0x7f7e6bb23770  
> mesos::internal::slave::MesosContainerizerProcess::recover()
> @ 0x7f7e6bbe643c  
> _ZZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS4_5state10SlaveStateEESB_EENS_6FutureIT_EERKNS_3PIDIT0_EEMSG_FSE_T1_EOT2_ENKUlRS9_PNS_11ProcessBaseEE_clESP_SR_
> @ 0x7f7e6bbe6295  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi16__callIvJOSS_EJLm0ELm1SE_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE
> @ 0x7f7e6bbe61f6  
> _ZNSt5_BindIFZN7process8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS5_5state10SlaveStateEESC_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSH_FSF_T1_EOT2_EUlRSA_PNS0_11ProcessBaseEE_SA_St12_PlaceholderILi1clIJSS_EvEESH_DpOT_
> @ 0x7f7e6bbe5f02  
> _ZNSt17_Function_handlerIFvPN7process11ProcessBaseEESt5_BindIFZNS0_8dispatchI7NothingN5mesos8internal5slave25MesosContainerizerProcessERK6OptionINS9_5state10SlaveStateEESG_EENS0_6FutureIT_EERKNS0_3PIDIT0_EEMSL_FSJ_T1_EOT2_EUlRSE_S2_E_SE_St12_PlaceholderILi1E9_M_invokeERKSt9_Any_dataOS2_
> @ 0x7f7e6ce37cf4  std::function<>::operator()()
> @ 0x7f7e6ce1ded4  process::ProcessBase::visit()
> @ 0x7f7e6cea38fe  process::DispatchEvent::visit()
> @ 0x7f7e6a9741b1  process::ProcessBase::serve()
> @ 0x7f7e6ce1a8eb  process::ProcessManager::resume()
> @ 0x7f7e6ce2b86e  
> process::ProcessManager::init_threads()::$_7::operator()()
> @ 0x7f7e6ce2b715  
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvE3$_7vEE9_M_invokeIJEEEvSt12_Index_tupleIJXspT_EEE
> @ 0x7f7e6ce2b6e5  std::_Bind_simple<>::operator()()
> @ 0x7f7e6ce2b6bc  std::thread::_Impl<>::_M_run()
> @ 0x7f7e6617d030  (unknown)
> @ 0x7f7e65c966aa  start_thread
> @ 0x7f7e659cbe9d  (unknown)
> {noformat}
> Maybe related to the change of standalone container support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)