Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

After installation of Ambari (2.7.1) and HDP (3.0.1), services don't start

Highlighted

After installation of Ambari (2.7.1) and HDP (3.0.1), services don't start

New Contributor

94486-01.png

94487-03.png

I am trying to install HDP in a single node for development (Ambari agent and host on the same node, also all the components). I am using the default guides and documentation from Hortonworks but I am stuck after installing the components.

After installation of Apache Ambari (2.7.1.0) and HDP stack (HDP-3.0.1.0 [3.0.1.0-187]), services can't start. even after installation or after a reboot and manual request.
Ranger fails to start, then the next procedures stop due to a timeout in the Ambari operation. I suppose the same situation will apply for the other services (except for those already running)

Where I can diagnose the applications or the OS to unlock this issue? I am sure it is not an Ambari bug but it must be something from my OS. I have tried other suggestions from similar issues but with success.

Firewall is disabled by default. Also, I am using PostgreSQL as DB support.

Here are the command outputs:

Step 9 of Cluster wizard:

stderr: 
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/RANGER/package/scripts/ranger_tagsync.py", line 133, in 
  RangerTagsync().execute()
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 354, in execute
  self.execute_prefix_function(self.command_name, 'post', env)
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 378, in execute_prefix_function
  method(env)
  File "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py", line 420, in post_start
  raise Fail("Pid file {0} doesn't exist after starting of the component.".format(pid_file))
resource_management.core.exceptions.Fail: Pid file /var/run/ranger/tagsync.pid doesn't exist after starting of the component.



Manually trying to start all the components:

stderr: 

Command aborted. Reason: 'Server considered task failed and automatically aborted it'
 stdout:
2018-12-06
 11:05:29,218 - Stack Feature Version Info: Cluster Stack=3.0, Command 
Stack=None, Command Version=3.0.1.0-187 -> 3.0.1.0-187
Command aborted. Reason: 'Server considered task failed and automatically aborted it'

Command failed after 1 tries




Configuration from server:

ulimit -c
unlimited

ulimit -u
unlimited

getenforce:
Disabled

umask:
0022

hostname:
myinstallationhost (I am shadowing this information just for privacy)

hostname -f:
myinstallationhost.mydomain.com

uname -a
Linux myinstallationhost 4.4.120-92.70-default #1 SMP Wed Mar 14 15:59:43 UTC 2018 (52a83de) x86_64 x86_64 x86_64 GNU/Linux

/etc/os-release:
NAME="SLES"
VERSION="12-SP2"
VERSION_ID="12.2"
PRETTY_NAME="SUSE Linux Enterprise Server 12 SP2"
ID="sles"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:12:sp2"

free -h
  total  used  free  shared  buffers  cached
Mem:  251G  19G  232G  202M  596M  8.1G
-/+ buffers/cache:  10G  241G
Swap:  8.0G  0B  8.0G

df -h
Filesystem  Size  Used Avail Use% Mounted on
devtmpfs  126G  8.0K  126G  1% /dev
tmpfs  126G  4.0K  126G  1% /dev/shm
tmpfs  126G  174M  126G  1% /run
tmpfs  126G  0  126G  0% /sys/fs/cgroup
/dev/sda3  98G  16G  82G  16% /
/dev/sda1  1.1G  4.6M 1021M  1% /boot/efi
/dev/sda4  4.8G  1.2G  3.5G  25% /tmp
/dev/sda5  9.8G  2.2G  7.1G  24% /var
/dev/sdb3  4.6G  17M  4.3G  1% /home
/dev/sda10  9.8G  23M  9.2G  1% /logs
/dev/sdb1  3.3T  373G  2.9T  12% /hadoop
/dev/sda9  64G  165M  63G  1% /datos
/dev/sda6  4.8G  601M  4.0G  13% /var/log
/dev/sda8  64G  54M  63G  1% /backup
/dev/sda11  11G  26M  9.6G  1% /scripts
/dev/sda7  980M  2.6M  910M  1% /var/log/audit
tmpfs  26G  0  26G  0% /run/user/2106
tmpfs  26G  0  26G  0% /run/user/2150
tmpfs  26G  0  26G  0% /run/user/0
tmpfs  26G  0  26G  0% /run/user/2155
tmpfs  26G  0  26G  0% /run/user/2143
tmpfs  26G  0  26G  0% /run/user/2144
tmpfs  26G  0  26G  0% /run/user/2152
tmpfs  26G  0  26G  0% /run/user/2130
tmpfs  26G  0  26G  0% /run/user/2153
/etc/hosts
#
# hosts  This file describes a number of hostname-to-address
#  mappings for the TCP/IP subsystem.  It is mostly
#  used at boot time, when no name servers are running.
#  On small systems, this file can be used instead of a
#  "named" name server.
# Syntax:
#   
# IP-Address  Full-Qualified-Hostname  Short-Hostname
#

127.0.0.1  localhost 

# special IPv6 addresses
::1  localhost ipv6-localhost ipv6-loopback

fe00::0  ipv6-localnet 

ff00::0  ipv6-mcastprefix 
ff02::1  ipv6-allnodes 
ff02::2  ipv6-allrouters 
ff02::3  ipv6-allhosts 
10.1.11.91  myinstallationhost.mydomain.com myinstallationhost

=====
/etc/hostname 
myinstallationhost.mydomain.com


Also, I am attaching Screenshots from Ambari Dashboard.

94490-03.png

94489-01.png

94488-00.png

94485-00.png

3 REPLIES 3

Re: After installation of Ambari (2.7.1) and HDP (3.0.1), services don't start

Rising Star

@Israel Zúñiga de la Mora

Can you check tagsync.pid exists under /var/run/ranger/ on Ranger tagsync host with appropriate permission

Re: After installation of Ambari (2.7.1) and HDP (3.0.1), services don't start

New Contributor

tagsync.pid does not exist on the location. There is the usersync.pid with permissions for ranger user, but there isn't a clue a bout the other file.


Also, I verified during the effort of starting all services (from Ambari Dashboard). But it didn't change anything.

ls -alsh


total 4.0K
   0 drwxr-xr-x  2 ranger hadoop   60 Dec  5 12:02 .
   0 drwxr-xr-x 50 root   root   1.3K Dec  7 12:54 ..
4.0K -rw-rw----  1 ranger hadoop    5 Dec  5 12:02 usersync.pid

Re: After installation of Ambari (2.7.1) and HDP (3.0.1), services don't start

New Contributor

Similar issue. Got such error after HA and SSL for Ranger had been configured.