【笔记】cdh报错记录

- kudu无法启动

报错日志：

+ exec /opt/cloudera/parcels/KUDU-1.4.0-1.cdh5.12.0.p0.25/lib/kudu/sbin/kudu-tserver --tserver_master_addrs=cdh-001,cdh-002 --flagfile=/opt/cm-5.12.0/run/cloudera-scm-agent/process/378-kudu-KUDU_TSERVER/gflagfile
F1011 11:37:04.014032 22141 tablet_server_main.cc:72] Check failed: _s.ok() Bad status: IO error: Could not create new FS layout: Unable to create block manager: Error during hole punch test. The log block manager requires a filesystem with hole punching support such as ext4 or xfs. On el6, kernel version 2.6.32-358 or newer is required. To run without hole punching (at the cost of some efficiency and scalability), reconfigure Kudu with --block_manager=file. Refer to the Kudu documentation for more details. Raw error message follows: Unexpected pre-punch file size for /data/kudu/tserverdata/data/hole_punch_test_file: expected 16384 but got 0
*** Check failure stack trace: ***
Wrote minidump to /var/log/kudu/minidumps/kudu-tserver/57890a8b-3497-2250-55b0281c-5441526e.dmp
*** Aborted at 1507693024 (unix time) try "date -d @1507693024" if you are using GNU date ***
PC: @     0x7efd10a9a5e5 __GI_raise
*** SIGABRT (@0x1de0000567d) received by PID 22141 (TID 0x7efd12d5a8c0) from PID 22141; stack trace: ***
    @     0x7efd11bcd7e0 (unknown)
    @     0x7efd10a9a5e5 __GI_raise
    @     0x7efd10a9bdc5 __GI_abort
    @          0x1b53f59 (unknown)
    @           0x8b9f6d google::LogMessage::Fail()
    @           0x8bbe2d google::LogMessage::SendToLog()
    @           0x8b9aa9 google::LogMessage::Flush()
    @           0x8bc8cf google::LogMessageFatal::~LogMessageFatal()
    @           0x85e046 (unknown)
    @     0x7efd10a86d1d __libc_start_main
    @           0x85d961 (unknown)

错误原因：
kudu支持的文件系统为ext4或xfs,当前的为ext3

- kudu无法启动
错误日志：
F1219 14:40:26.818169 28290 tablet_server_main.cc:72] Check failed: _s.ok() Bad status: Service unavailable: Cannot initialize clock: Error reading clock. Clock considered unsynchronized

错误原因：
时间未同步，需要先通过ntpd同步好时间