kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Lipcon <t...@cloudera.com>
Subject Re: Newbie questions for kudu 0.6.0 and impala-kudu
Date Sun, 10 Jan 2016 21:46:50 GMT
Looks like this was cross-posted to the old and new mailing list, so
copy-pasting my responses from the other thread here. Let's continue the
follow-up discussion on this new list.

On Sat, Jan 9, 2016 at 4:32 AM, yash datta <saucam@gmail.com> wrote:

> Hey,
>
> So I resolved #2 , since I was missing a softlink libanonymous.so
>
> ln -sf libanonymous.so.2 libanonymous.so
>


It's odd that you didn't have the symlink to begin with, though -- I never
would advise users to make manual changes inside /usr like that. Here's my
ls -l /usr/lib64/sasl2/ on a RHEL6 system:

[todd@d2106 ~]$ ls -l /usr/lib64/sasl2
total 84
lrwxrwxrwx. 1 root root    22 Jan  2  2014 libanonymous.so ->
libanonymous.so.2.0.23
lrwxrwxrwx. 1 root root    22 Jan  2  2014 libanonymous.so.2 ->
libanonymous.so.2.0.23
-rwxr-xr-x. 1 root root 18776 Nov 27  2012 libanonymous.so.2.0.23
lrwxrwxrwx. 1 root root    18 Jan  2  2014 liblogin.so -> liblogin.so.2.0.23
lrwxrwxrwx. 1 root root    18 Jan  2  2014 liblogin.so.2 ->
liblogin.so.2.0.23
-rwxr-xr-x. 1 root root 18808 Nov 27  2012 liblogin.so.2.0.23
lrwxrwxrwx. 1 root root    18 Jan  2  2014 libplain.so -> libplain.so.2.0.23
lrwxrwxrwx. 1 root root    18 Jan  2  2014 libplain.so.2 ->
libplain.so.2.0.23
-rwxr-xr-x. 2 root root 18808 Nov 27  2012 libplain.so.2.0.23
lrwxrwxrwx. 1 root root    19 Jan  2  2014 libsasldb.so ->
libsasldb.so.2.0.23
lrwxrwxrwx. 1 root root    19 Jan  2  2014 libsasldb.so.2 ->
libsasldb.so.2.0.23
-rwxr-xr-x. 2 root root 22784 Nov 27  2012 libsasldb.so.2.0.23


> But again, both master, tserver report a FAILED state when first started,
> though apparently now there are no errors (no error logs, both processes
> are up, UI reports both processes as normal running)
>
> Wondering If there are some other logs/indicators of any problem.
>

Once the server is running, what happens if you run:

kudu-ts-cli status

on that machine? You could also try temporarily editing
/etc/init.d/kudu-master to remove the stdout and stderr redirects on this
line:

$TS_CLI_PATH --server_address="$FLAGS_rpc_bind_addresses" status 1>/dev/null
2>&1
and see if you see some more useful logging when you run the script.



>
> Also wanted to know how to supply my own hive-site.xml to impala-kudu
>
>
I think the following docs should help:
http://www.cloudera.com/content/www/en-us/documentation/archive/impala/2-x/2-1-x/topics/impala_noncm_installation.html

Todd

On Sat, Jan 9, 2016 at 5:07 PM, yash datta <saucam@gmail.com> wrote:
>
>> Hi all,
>>
>> I recently installed kudu 0.6.0 binaries from :
>>
>>
>> http://archive.cloudera.com/beta/kudu/redhat/6/x86_64/kudu/0.6.0/RPMS/x86_64/
>>
>> I am encountering a couple of problems, any help will be highly
>> appreciated :
>>
>>
>> 1. First off when running the master , I get this :
>>
>> [admin@NNydatta yash]# service kudu-master start
>>
>> Failed to start Kudu Master Server. Return value: 1        [*FAILED*]
>>
>>
>> But I see the master process start successfully and on running this same
>> command again I get a SUCCESS
>>
>> I can connect to the UI as well
>>
>>
>> I dont see any particular errors , but the  WARNING logs are these :
>>
>>
>> Log file created at: 2016/01/09 04:14:33
>>
>> Running on machine: NNydatta
>>
>> Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
>>
>> W0109 04:14:33.987498 31678 log_util.cc:165] Could not read footer for
>> segment:
>> /data/kudu/master/wals/00000000000000000000000000000000.recovery/wal-000000001:
>> Not found: Footer not found. Footer magic doesn't match
>>
>> W0109 04:14:33.987738 31678 log_reader.cc:149] Log segment
>> /data/kudu/master/wals/00000000000000000000000000000000.recovery/wal-000000001
>> was likely left in-progress after a previous crash. Will try to rebuild
>> footer by scanning data.
>>
>> W0109 04:14:33.988415 31679 env_posix.cc:649] The filesystem does not
>> support fallocate().
>>
>> W0109 04:14:33.991582 31683 catalog_manager.cc:348] Catalog manager is
>> not initialized!
>>
>>
>> Are there any other logs which I need to inspect to see why master is
>> returning error status (even though the process does get started) ?
>>
>>
>> 2.  On starting tserver , I get a failed error but again the process
>> comes up
>>
>>
>> In the ERROR logs I get :
>>
>>
>> E0108 17:57:31.618916 27298 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:32.672613 27304 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:33.673751 27323 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:34.674798 27326 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:35.675832 27328 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:36.676900 27330 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:37.716624 27334 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:38.717875 27344 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>> E0108 17:57:39.719038 27355 sasl_helper.cc:130] Sasl Client: Unable to
>> find ANONYMOUS SASL plugin
>>
>>
>> my sasl libs are in the default path so I should not have got these error
>> I suppose ?
>>
>> (I have gone through this thread
>> https://groups.google.com/forum/#!topic/kudu-user/k0DuoElPXiY)
>>
>>
>> [admin@NNydatta yash]# ls -lrt /usr/lib64/sasl2/
>>
>> total 164
>>
>> -rwxr-xr-x 1 admin root 22784 Nov 27  2012 *libsasldb.so.2.0.23*
>>
>> -rwxr-xr-x 1 admin root 18808 Nov 27  2012 *libplain.so.2.0.23*
>>
>> -rwxr-xr-x 1 admin root 18808 Nov 27  2012 *liblogin.so.2.0.23*
>>
>> -rwxr-xr-x 1 admin root 52088 Nov 27  2012 *libdigestmd5.so.2.0.23*
>>
>> -rwxr-xr-x 1 admin root 22936 Nov 27  2012 *libcrammd5.so.2.0.23*
>>
>> -rwxr-xr-x 1 admin root 18776 Nov 27  2012 *libanonymous.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    19 Dec 21 06:28 *libsasldb.so.2* ->
>> *libsasldb.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    18 Dec 21 06:28 *libplain.so.2* ->
>> *libplain.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    18 Dec 21 06:28 *libplain.so* ->
>> *libplain.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    18 Dec 21 06:28 *liblogin.so.2* ->
>> *liblogin.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    18 Dec 21 06:28 *liblogin.so* ->
>> *liblogin.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    22 Dec 21 06:28 *libdigestmd5.so.2* ->
>> *libdigestmd5.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    22 Dec 21 06:28 *libdigestmd5.so* ->
>> *libdigestmd5.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    20 Dec 21 06:28 *libcrammd5.so.2* ->
>> *libcrammd5.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    20 Dec 21 06:28 *libcrammd5.so* ->
>> *libcrammd5.so.2.0.23*
>>
>> lrwxrwxrwx 1 admin root    22 Dec 21 06:28 *libanonymous.so.2* ->
>> *libanonymous.so.2.0.23*
>>
>>
>> What am I missing here?
>>
>>
>> 3. I also installed impala-kudu from :
>>
>>
>>
>> http://archive.cloudera.com/beta/impala-kudu/redhat/6/x86_64/impala-kudu/0.5.0/RPMS/x86_64/
>>
>>
>> From where does impala pick hive-site.xml to determine how to connect to
>> the hive metastore ?
>>
>>
>> Thanks and Best Regards
>>
>> Yash Datta
>>
>>
>> --
>> When events unfold with calm and ease
>> When the winds that blow are merely breeze
>> Learn from nature, from birds and bees
>> Live your life in love, and let joy not cease.
>>
>
>
>
> --
> When events unfold with calm and ease
> When the winds that blow are merely breeze
> Learn from nature, from birds and bees
> Live your life in love, and let joy not cease.
>



-- 
Todd Lipcon
Software Engineer, Cloudera

Mime
View raw message