[jira] [Resolved] (IMPALA-5700) Improve error message when catalogd fails to start

["Tim Armstrong (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-5700.
-----------------------------------
    Resolution: Cannot Reproduce

> Improve error message when catalogd fails to start
> --------------------------------------------------
>
>                 Key: IMPALA-5700
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5700
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Infrastructure
>            Reporter: Jim Apple
>            Priority: Major
>
> When catalogd fails to start, the error message is
> {noformat}
> Starting Catalog Service logging to /home/ubuntu/Impala/logs/cluster/catalogd.INFO
> Error starting cluster: Unable to start catalogd. Check log or file permissions for more details.
> {noformat}
> But sometimes that log shows no useful information and the other message doesn't explain which file permissions to check. An example log without much information:
> {noformat}
> I0723 21:42:15.238229  5972 init.cc:218] Cpu Info:
>   Model: Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz
>   Cores: 8
>   Max Possible Cores: 8
>   L1 Cache: 32.00 KB (Line: 64.00 B)
>   L2 Cache: 256.00 KB (Line: 64.00 B)
>   L3 Cache: 45.00 MB (Line: 64.00 B)
>   Hardware Supports:
>     ssse3
>     sse4_1
>     sse4_2
>     popcnt
>     avx
>     avx2
>   Numa Nodes: 1
>   Numa Nodes of Cores: 0->0 | 1->0 | 2->0 | 3->0 | 4->0 | 5->0 | 6->0 | 7->0 |
> I0723 21:42:15.238239  5972 init.cc:219] Disk Info: 
>   Num disks 2: 
>     ram (rotational=true)
>     xvda (rotational=false)
> I0723 21:42:15.238245  5972 init.cc:220] Physical Memory: 59.97 GB
> I0723 21:42:15.238250  5972 init.cc:221] OS version: Linux version 4.4.0-1020-aws (buildd@lgw01-14) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #
> {noformat}
> Changing the ownership of all the files in the home directory of the user did not alleviate the problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)