aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1938) Aurora failed without log detail
Date Mon, 26 Jun 2017 16:46:01 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063380#comment-16063380
] 

Stephan Erb commented on AURORA-1938:
-------------------------------------

The current snippet you posted does not tell us why Aurora thinks the storage is not ready.
Normally those messages point to problems with the replicated log, or maybe connectivity issues
between your Aurora schedulers. 

The log lines indicates that Aurora cannot even properly connect to the ZooKeeper ensemble.
This is a prerequisite for a working cluster as well.
{code}2017-06-20 17:38:58,527:1(0x7f13511fc700):ZOO_ERROR@handle_socket_error_msg@1697: Socket
[10.176.128.91:2181] zk retcode=-4, errno=111(Connection refused): server refused to accept
the client
{code} 

How many Aurora schedulers do you have? 3 or 5?  Would be great to have the full log of those
(if you feel comfortable sharing those). 


> Aurora failed without log detail
> --------------------------------
>
>                 Key: AURORA-1938
>                 URL: https://issues.apache.org/jira/browse/AURORA-1938
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>    Affects Versions: 0.13.0
>            Reporter: Luc Nguyen
>             Fix For: 0.13.0
>
>         Attachments: Error_1.txt, Error_2.txt
>
>
> Aurora failed without log detail
> We also had a backup for Aurora as well. However, the Aurora backup was also failed.
> It was bother us that there was no log which showing the failure in detail.
> Was there anyone running the same problem?



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

Mime
View raw message