[
https://issues.apache.org/jira/browse/MESOS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631399#comment-16631399
]
Jorge Machado commented on MESOS-3484:
--------------------------------------
[~neilc] I have a very similar issue when starting apache aurora and it tries
to connect to master:
E0928 07:44:05.240464 6967 process.cpp:2455] Failed to shutdown socket with fd
393, address 53.54.203.253:56038: Transport endpoint is not connected
My command to start:
export JAVA_HOME=/usr/lib64/jvm/java
export GLOG_v=1
export LIBPROCESS_PORT=8083
export LIBPROCESS_SSL_KEY_FILE=/etc/ssl/private/server_2048.key
export SHLVL=1
export LIBPROCESS_SSL_ENABLED=true
export LIBPROCESS_SSL_CERT_FILE=/etc/ssl/server.crt
export LIBPROCESS_SSL_SUPPORT_DOWNGRADE=false
sudo ./bin/aurora-scheduler -http_port=8081 -cluster_name aurora_staging
-mesos_master_address
zk:/someHostname:[5181/mesos|zk://SMTCFZ2036.rd.corpintra.net:5181,SMTCFZ2037.rd.corpintra.net:5181,SMTCFZ2038.rd.corpintra.net:5181]
-backup_dir /home/machjor/aurora-scheduler-0.21.0/temp -serverset_path
/aurora -zk_endpoints
someZookeeper[:5181|http://smtcfz2036.rd.corpintra.net:5181/]
-native_log_file_path /home/machjor/aurora_log -native_log_zk_group_path
/aurora/replicated-log -thermos_executor_path
/home/machjor/aurora-scheduler-0.21.0
any idea ?
> Master failed to shutdown: failed on fd: Transport endpoint is not connected.
> -----------------------------------------------------------------------------
>
> Key: MESOS-3484
> URL: https://issues.apache.org/jira/browse/MESOS-3484
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.24.0
> Reporter: Chi Zhang
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
