[ https://issues.apache.org/jira/browse/KUDU-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178494#comment-16178494 ]
Yee commented on KUDU-1867: --------------------------- # {code:java} + exec /opt/cloudera/parcels/KUDU-1.4.0-1.cdh5.12.1.p0.10/lib/kudu/sbin/kudu-tserver --tserver_master_addrs=elasticsearch159 --flagfile=/opt/cm-5.12.1/run/cloudera-scm-agent/process/164-kudu-KUDU_TSERVER/gflagfile F0924 23:26:20.927377 1101 tablet_server_main.cc:72] Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could not lock /home/kudu14/fs_data_dirs/data/block_manager_instance: Could not lock /home/kudu14/fs_data_dirs/data/block_manager_instance: lock /home/kudu14/fs_data_dirs/data/block_manager_instance: Resource temporarily unavailable (error 11) {code} > Improve the "Could not lock .../block_manager_instance" error message > --------------------------------------------------------------------- > > Key: KUDU-1867 > URL: https://issues.apache.org/jira/browse/KUDU-1867 > Project: Kudu > Issue Type: Bug > Components: fs > Affects Versions: 1.2.0 > Reporter: Jean-Daniel Cryans > Labels: newbie > > It's possible for users to encounter a rather cryptic error when trying to > run Kudu while it's already running or with a different user than what was > previously used: > {code} > Check failed: _s.ok() Bad status: IO error: Failed to load FS layout: Could > not lock /path/to/data/block_manager_instance: Could not lock > /path/to/data/block_manager_instance: lock > /path/to/data/block_manager_instance: Resource temporarily unavailable (error > 11) > {code} > This is the log line that we FATAL with, so unless you already know what it > means you're left to your own guessing and log digging. Instead, the error > message could be more prescriptive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)