Member since
12-29-2015
12
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
6479 | 01-21-2016 08:44 PM | |
6088 | 01-01-2016 02:31 PM |
01-21-2016
08:44 PM
3 Kudos
Today I spoke with Robert Molina from Hortonworks and possibly found what is creating all those alerts! The sandbox is intended to be run on a desktop with a NAT networked interface. I set it up on a dedicaded headless server with a bridge adaptor. Looks like sandbox have a problem with that and that cause some of the services configs to not function properly! As a result some services works but reports network connections alerts! After some config change. The related alerts weren't there anymore. So always use a vm for and how it was intended to be used. Thanks to the hortonworks team and Robert who wanted to go to the bottom of this. Conclusion: If you want, like me, to test drive hortonworks on a headless server. Start from scratch and build it! What every sysadmin should do anyways... That's what I'll do this week end... P
... View more
01-13-2016
04:11 PM
18 hours later I'm down to 6 alerts: Here is the ambari screen shot: That is after I started the Ambari Metrics. It looks like It's some connection errore. For example, here is one ranger alert: Connection failed: [Errno 111] Connection refused to sandbox.hortonworks.com:5151 But if I connect to sandbox.hortonworks.com:5151 with a browser. It works!!! Looks like a dns resolution or a firewall connectivity problem... Is there a way to just reset the alerts?
... View more
01-12-2016
09:17 PM
2 Kudos
This is reproducible! I have the same BUG on HDP_2.3.2_virtualbox.ova
... View more
01-12-2016
09:11 PM
Mine doesn't look at all like that!!! Just to be on the safe side! I just re-import the HDP_2.3.2_virtualbox.ova with wirtualbox 4.3.26 I put 4 cpu and 16 gig of ram. I still have problems... Here is the ambari after start: I mean is it me or there shouldn't be any alerts??? That mean when horton saved the VM the alert were there! So I did a yum update on the vm but it's worst ! Here is the ambari after restart: The thing is all these alert make me questioned the accuracy and solidity of the distro. I mean I'm not even shure it's working out of the box! What if I installed something on it and it doesn't work! Is it what I've installed or the Hortonworks environement? I mean this is not right! Am I the only one with these problems? ... P
... View more
01-03-2016
08:38 PM
Hi all! I just download the latest sandbox.hortonworks.com HDP 2.3.2 but when started and running for an hour I still have some alerts on the ambari dashboard! Anybody has the same problem? Here are what I can copy from the ambari dashboard: HiveServer2 Process Connection failed on host sandbox.hortonworks.com:10000 (Execution of 'ambari-sudo.sh su ambari-qa -l -s /bin/bash -c 'export PATH='"'"'/usr/sbin:/sbi Hive Metastore Process Metastore on sandbox.hortonworks.com failed (Execution of 'ambari-sudo.sh su ambari-qa -l -s /bin/bash -c 'export PATH='"'"'/usr/sbin:/sbin:/usr/lib/a Ambari There are 21 stale
alerts from 1 host(s): History Server RPC Latency, HiveServer2 Process,
Ranger Usersync Process, WebHCat Server Status, Ambari Agent Disk Usage,
History Server Web UI, App Timeline Web UI, Hive Metastore Process,
Atlas Metadata Server Process, History Server CPU Utilization, History
Server Process, ResourceManager Web UI, NodeManager Health Summary,
ZooKeeper Server Process, ResourceManager CPU Utilization, NodeManager
Health, Flume Agent Status, Ranger Admin Process, NodeManager Web UI,
ResourceManager RPC Latency, Metadata Server Web UI
CRIT for about an hour There are 21 stale alerts from 1 host(s): History Server RPC Latency, I don't understand why the vm has multiples alerts out of the box! Is there a way to fix this or is there a vm without any errors?
... View more
Labels:
01-01-2016
02:31 PM
After some research I was able to have the VM work for more than 12 hours now. Looks like virtualbox 5 has some new features regarding clock. Here is my fix:
<code>I added grub arguments on the kernel clock=pit nosmp noapic nolapic
in order to have
clocksource=kvm-clock
Look to check clocksouce: Check what clocksource that you are using: <code>$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
Check which ones that are available: <code>$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
If you got a "kvm-clock" entry in "available_clocksource" try to use it by
setting kernel parameter: <code>clocksource=kvm-clock
From http://serverfault.com/questions/132197/best-pract... Peter
... View more
12-31-2015
05:51 PM
I don't think it's related to cpu assignment, The vm has 4 cpu @ 100% cap. And doing nothing. The load is below 0.3 most of the time. As for the kernel! The host has latest current kernel Linux host 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux And the known issue is related for kernel in lucid-updates not LTS 14.04 Thanks for the suggestions.
... View more
12-31-2015
04:19 PM
I downloaded the sandbox VM for virtualbox and started it on ubuntu host with virtualbox 5 and after a couple of hours it crash. On the screen I get : Message from syslog@sandbox at dec .... kernel:Bug: soft lockup - CPU2 stuck for 67s! [java:30253] and this message repeat itself on and on. The vm is stuck and non responsive. I need to poweroff and restart it! Here are the log vboxlog relevant lignes: 00:01:05.829053 VMMDev: Guest Log: 00:00:00.011489 main 4.3.22 r98236 started. Verbose level = 0
00:08:50.366623 TM: Giving up catch-up attempt at a 60 002 234 869 ns lag; new total: 60 002 234 869 ns
14:11:48.845736 PIIX3 ATA: Ctl#0: RESET, DevSel=0 AIOIf=0 CmdIf0=0xca (30357026 usec ago) CmdIf1=0x00 (-1 usec ago)
14:12:05.363192 PIIX3 ATA: execution time for ATA command 0xca was 46 seconds
14:12:05.366460 PIIX3 ATA: Ctl#0: finished processing RESET The host is a dell server with 2 quad xeon 32 gig ecc ram. I have two other VM running on the host. A debian 64 and a ubuntu lts 14.04 that run just fine. Anybody had a luck with virtualbox 5? Peter
... View more