Quantcast
Channel: Hortonworks » All Replies
Viewing all articles
Browse latest Browse all 3435

SLES 11.1 Ambari Registration Fails

$
0
0

Hi there – I am unable to run the Ambari “registration” step for a single-node HDP cluster on SLES 11.1.
The ssh keys setup is ok; ambari server and agent are installed and running; start|stop|status return ok.
I included the registration log outout, the ambari-server log the ambari-agent log and the bootstrap log below; as I think all of these seem to be relevant.

The “ambari-updates” zypper repository refresh doesnt work (not found) – but the other repositoriees work ok. Since Ambari-server and ambari-agent downloaded ok, I presume that failure of this repository connection is not an issue:

cd /etc/zypp/repos.d
rm ambari*
wget http://public-repo-1.hortonworks.com/ambari/suse11/1.x/GA/ambari.repo
–2015-08-02 16:06:45– http://public-repo- 1.hortonworks.com/ambari/suse11/1.x/GA/ambari.repo
Resolving proxy…
Connecting to proxy… connected.
Proxy request sent, awaiting response… 200 OK
Length: 745 [application/octet-stream]
Saving to: `ambari.repo’
2015-08-02 16:06:45 (46.3 MB/s) – `ambari.repo’ saved [745/745]

# zypper clean
All repositories have been cleaned up.
# zypper refresh
Repository ‘Hortonworks Data Platform Utils Version – HDP-UTILS-1.1.0.16′ is up to date.
Repository ‘REP6′ is up to date.
Repository ‘ambari-1.x – Updates’ is invalid.
[Updates-ambari-1.x|http://public-repo- 1.hortonworks.com/ambari/suse11/1.x/updates] Repository type can’t be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘ambari-1.x – Updates’ because of the above error.
Repository ‘Ambari 1.x’ is up to date.
Some of the repositories have not been refreshed because of an error.

The Registration log for the session (chrome or firefox) is: =================================

Error building the cache:
[|] Repository type can’t be determined.
Verifying Python version compatibility…
Using python /usr/bin/python2.6
Checking for previously running Ambari Agent…
ERROR: ambari-agent already running
Check /var/run/ambari-agent/ambari-agent.pid for PID.
(‘hostname: ok apjhana01.XXX.XXX.corp
ip: ok XX.XX.XXX.XX (…masked)
cpu: ok Intel(R) Xeon(R) CPU X7560 @ 2.27GHz
(…etc etc)
memory: ok 252.279 GB
disks: ok
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 1.1T 642G 375G 64% /
devtmpfs 127G 120K 127G 1% /dev
tmpfs 127G 248K 127G 1% /dev/shm
os: ok Welcome to SUSE Linux Enterprise Server 11 SP1 (x86_64) – Kernel %r (%t).
iptables: ok
Chain INPUT (policy ACCEPT 235M packets, 110G bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 234M packets, 110G bytes)
pkts bytes target prot opt in out source destination
selinux: UNAVAILABLE
yum: UNAVAILABLE
rpm: ok rpm-4.4.2.3-37.16.37
openssl: ok openssl-0.9.8h-30.27.11
curl: ok curl-7.19.0-11.24.25
wget: ok wget-1.11.4-1.15.1
net-snmp: UNAVAILABLE
net-snmp-utils: UNAVAILABLE
ntpd: UNAVAILABLE
ruby: ok ruby-1.8.7.p72-5.24.2
puppet: ok puppet-0.24.8-1.3.5
nagios: UNAVAILABLE
ganglia: UNAVAILABLE
passenger: UNAVAILABLE
hadoop: UNAVAILABLE
yum_repos: UNAVAILABLE
zypper_repos: ok
2 | HDP-UTILS-1.1.0.16 | Hortonworks Data Platform Utils Version – HDP-UTILS-1.1.0.16 | Yes | No
‘, None)
(‘INFO 2015-08-02 14:36:37,342 NetUtil.py:44 – DEBUG:: Connecting to the following url https://apjhana01.XXX.XXX.corp:4080/cert/ca
INFO 2015-08-02 14:36:37,343 NetUtil.py:58 – Failed to connect to https://apjhana01.XXX.XXX.corp:4080/cert/ca due to [Errno 111] Connection refused
INFO 2015-08-02 14:36:37,343 NetUtil.py:77 – Server at https://apjhana01.XXX.XXX.corp:4080 is not reachable, sleeping for 10 seconds…
INFO 2015-08-02 14:36:45,203 main.py:51 – signal received, exiting.
INFO 2015-08-02 14:36:53,390 shell.py:50 – Killing stale processes
INFO 2015-08-02 14:36:53,391 shell.py:58 – Killed stale processes
INFO 2015-08-02 14:36:53,391 main.py:141 – Connecting to the server at: https://apjhana01.XXX.XXX.corp:8440
INFO 2015-08-02 14:36:53,391 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://apjhana01.sin.XXX.corp:8440
INFO 2015-08-02 14:36:53,392 NetUtil.py:44 – DEBUG:: Connecting to the following url https://apjhana01.sin.XXX.corp:8440/cert/ca
INFO 2015-08-02 14:41:27,032 NetUtil.py:58 – Failed to connect to https://apjhana01.XXX.XXX.corp:8440/cert/ca due to [Errno 104] Connection reset by peer
INFO 2015-08-02 14:41:27,032 NetUtil.py:77 – Server at https://apjhana01.sin.XXX.corp:8440 is not reachable, sleeping for 10 seconds…
INFO 2015-08-02 14:41:37,043 NetUtil.py:44 – DEBUG:: Connecting to the following url https://apjhana01.sin.XXX.corp:8440/cert/ca
INFO 2015-08-02 14:41:37,044 NetUtil.py:58 – Failed to connect to https://apjhana01.sin.XXX.corp:8440/cert/ca due to [Errno 111] Connection refused
INFO 2015-08-02 14:41:37,044 NetUtil.py:77 – Server at https://apjhana01.sin.XXX.corp:8440 is not reachable, sleeping for 10 seconds…
INFO 2015-08-02 14:41:43,917 main.py:51 – signal received, exiting.
INFO 2015-08-02 14:42:46,560 shell.py:50 – Killing stale processes
INFO 2015-08-02 14:42:46,566 shell.py:58 – Killed stale processes
INFO 2015-08-02 14:42:46,566 main.py:141 – Connecting to the server at: https://apjhana01.sin.XXX.corp:8440
INFO 2015-08-02 14:42:46,566 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://apjhana01.sin.XXX.corp:8440
INFO 2015-08-02 14:42:46,567 NetUtil.py:44 – DEBUG:: Connecting to the following url https://apjhana01.sin.XXX.corp:8440/cert/ca
‘, None)

STDERR
Connection to apjhana01.sin.XXX.corp closed.
Registering with the server…
Registration with the server failed.
OK
Licensed under the Apache License, Version 2.0.
See third-party tools/resources that Ambari uses and their respective authors

ambari-server.log =======================================

19:59:45,262 INFO Configuration:288 – Web App DIR test /usr/lib/ambari-server/web
19:59:45,270 INFO CertificateManager:65 – Initialization of root certificate
19:59:45,270 INFO CertificateManager:69 – Certificate exists:true
19:59:45,364 INFO AmbariServer:290 – ********* Initializing Meta Info **********
19:59:45,885 INFO AmbariServer:300 – ********* Initializing Clusters **********
19:59:45,886 INFO AmbariServer:304 – ********* Current Clusters State *********
19:59:45,886 INFO AmbariServer:305 – Clusters=[ ]
19:59:45,886 INFO AmbariServer:307 – ********* Initializing ActionManager **********
19:59:45,886 INFO AmbariServer:309 – ********* Initializing Controller **********
19:59:45,890 INFO AmbariManagementControllerImpl:124 – Initializing the AmbariManagementControllerImpl
19:59:45,895 INFO Server:266 – jetty-7.6.7.v20120910
19:59:45,970 INFO ContextHandler:744 – started o.e.j.s.ServletContextHandler{/,file:/usr/lib/ambari-server/web/}
19:59:48,613 INFO AbstractConnector:338 – Started SelectChannelConnector@0.0.0.0:8080
19:59:48,614 INFO Server:266 – jetty-7.6.7.v20120910
19:59:48,616 INFO ContextHandler:744 – started o.e.j.s.ServletContextHandler{/,null}
19:59:49,673 INFO SslContextFactory:300 – Enabled Protocols [SSLv2Hello, SSLv3, TLSv1] of [SSLv2Hello, SSLv3, TLSv1]
19:59:49,681 INFO AbstractConnector:338 – Started SslSelectChannelConnector@0.0.0.0:8440
19:59:49,751 INFO SslContextFactory:300 – Enabled Protocols [SSLv2Hello, SSLv3, TLSv1] of [SSLv2Hello, SSLv3, TLSv1]
19:59:49,757 WARN AbstractConnector:335 – insufficient threads configured for SslSelectChannelConnector@0.0.0.0:8441
19:59:49,758 INFO AbstractConnector:338 – Started SslSelectChannelConnector@0.0.0.0:8441
19:59:49,758 INFO AmbariServer:324 – ********* Started Server **********
19:59:49,759 INFO ActionManager:61 – Starting scheduler thread
19:59:49,759 INFO AmbariServer:327 – ********* Started ActionManager **********
20:00:25,613 INFO AmbariLocalUserDetailsService:62 – Loading user by name: admin
20:00:26,633 INFO ClusterControllerImpl:92 – Using resource provider org.apache.ambari.server.controller.internal.UserResourceProvider for request type User
20:00:26,984 INFO PersistKeyValueService:82 – Looking for keyName CLUSTER_CURRENT_STATUS
20:03:33,584 INFO BootStrapImpl:97 – BootStrapping hosts apjhana01.sin.XXX.corp:
20:03:33,591 INFO BSRunner:166 – Host= apjhana01.sin.XXX.corp bs=/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py requestDir=/var/run/ambari-server/bootstrap/1 keyfile=/var/run/ambari-server/bootstrap/1/sshKey server=apjhana01.sin.XXX.corp
20:03:33,607 INFO BSRunner:196 – Kicking off the scheduler for polling on logs in /var/run/ambari-server/bootstrap/1
20:03:33,608 INFO BSRunner:200 – Bootstrap output, log=/var/run/ambari-server/bootstrap/1/bootstrap.err /var/run/ambari-server/bootstrap/1/bootstrap.out
20:03:33,610 INFO BSHostStatusCollector:55 – Request directory /var/run/ambari-server/bootstrap/1
20:03:33,610 INFO BSHostStatusCollector:62 – HostList for polling on [apjhana01.sin.XXX.corp]
20:03:33,786 INFO BSRunner:212 – Script log Mesg

Ambari-agent.log ==============================

INFO 2015-08-02 14:36:53,391 main.py:141 – Connecting to the server at: https://apjhana01.sin.XXX.corp:8440
INFO 2015-08-02 14:36:53,391 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://apjhana01.sin.XXX.corp:8440
INFO 2015-08-02 14:36:53,392 NetUtil.py:44 – DEBUG:: Connecting to the following url https://apjhana01.sin.XXX.corp:8440/cert/ca
INFO 2015-08-02 14:41:27,032 NetUtil.py:58 – Failed to connect to https://apjhana01.sin.XXX.corp:8440/cert/ca due to [Errno 104] Connection reset by peer
INFO 2015-08-02 14:41:27,032 NetUtil.py:77 – Server at https://apjhana01.sin.XXX.corp:8440 is not reachable, sleeping for 10 seconds…

/var/run/ambari-server/bootstrap/apjhana01.sin.XXX.corp.log ==================

Verifying Python version compatibility…
Using python /usr/bin/python2.6
Checking for previously running Ambari Agent…
tput: No value for $TERM and no -T specified
ERROR: ambari-agent already running
tput: No value for $TERM and no -T specified
Check /var/run/ambari-agent/ambari-agent.pid for PID.
(‘hostname: ok apjhana01.sin.XXX.corp\nip: ok 10.32.241.20\ncpu: ok Intel(R) Xeon(R) CPU X7560 @ 2.27GHz\nIntel(R) Xeon(R) CPU X7560 @ 2.27GHz\nIntel(R) Xeon(R) CPU X7560 @ 2.27GHz\nIntel(R) Xeon(R) CPU (..etc etc) \nmemory: ok 252.279 GB\ndisks: ok\n Filesystem Size Used Avail Use% Mounted on\n/dev/sda2 1.1T 642G 375G 64% /\ndevtmpfs 127G 120K 127G 1% /dev\ntmpfs 127G 248K 127G 1% /dev/shm\nos: ok Welcome to SUSE Linux Enterprise Server 11 SP1 (x86_64) – Kernel %r (%t).\niptables: ok\n Chain INPUT (policy ACCEPT 240M packets, 112G bytes)\n pkts bytes target prot opt in out source destination \n\nChain FORWARD (policy ACCEPT 0 packets, 0 bytes)\n pkts bytes target prot opt in out source destination \n\nChain OUTPUT (policy ACCEPT 240M packets, 112G bytes)\n pkts bytes target prot opt in out source destination\nselinux: UNAVAILABLE\nyum: UNAVAILABLE\nrpm: ok rpm-4.4.2.3-37.16.37\nopenssl: ok openssl-0.9.8h-30.27.11\ncurl: ok curl-7.19.0-11.24.25\nwget: ok wget-1.11.4-1.15.1\nnet-snmp: UNAVAILABLE\nnet-snmp-utils: UNAVAILABLE\nntpd: UNAVAILABLE\nruby: ok ruby-1.8.7.p72-5.24.2\npuppet: ok puppet-0.24.8-1.3.5\nnagios: UNAVAILABLE\nganglia: UNAVAILABLE\npassenger: UNAVAILABLE\nhadoop: UNAVAILABLE\nyum_repos: UNAVAILABLE\nzypper_repos: ok\n 2 | HDP-UTILS-1.1.0.16 | Hortonworks Data Platform Utils Version – HDP-UTILS-1.1.0.16 | Yes | No\n’, None)
(‘INFO 2015-08-02 15:10:10,683 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://10.32.241.20:8440\nINFO 2015-08-02 15:10:10,683 NetUtil.py:44 – DEBUG:: Connecting to the following url https://10.32.241.20:8440/cert/ca\nINFO 2015-08-02 15:16:19,429 main.py:51 – signal received, exiting.\nINFO 2015-08-02 15:16:29,784 shell.py:50 – Killing stale processes\nINFO 2015-08-02 15:16:29,784 shell.py:58 – Killed stale processes\nINFO 2015-08-02 15:16:29,784 main.py:141 – Connecting to the server at: https://10.32.241.20:8440\nINFO 2015-08-02 15:16:29,785 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://10.32.241.20:8440\nINFO 2015-08-02 15:16:29,785 NetUtil.py:44 – DEBUG:: Connecting to the following url https://10.32.241.20:8440/cert/ca\nINFO 2015-08-02 15:16:59,875 main.py:51 – signal received, exiting.\nINFO 2015-08-02 15:17:08,950 shell.py:50 – Killing stale processes\nINFO 2015-08-02 15:17:08,950 shell.py:58 – Killed stale processes\nINFO 2015-08-02 15:17:08,950 main.py:141 – Connecting to the server at: https://10.32.241.20:8440\nINFO 2015-08-02 15:17:08,951 NetUtil.py:68 – DEBUG: Trying to connect to the server at https://10.32.241.20:8440\nINFO 2015-08-02 15:17:08,951 NetUtil.py:44 – DEBUG:: Connecting to the following url https://10.32.241.20:8440/cert/ca\nINFO 2015-08-02 15:38:12,679 NetUtil.py:58 – Failed to connect to https://10.32.241.20:8440/cert/ca due to [Errno 104] Connection reset by peer\nINFO 2015-08-02 15:38:12,679 NetUtil.py:77 – Server at https://10.32.241.20:8440 is not reachable, sleeping for 10 seconds…\nINFO 2015-08-02 15:38:22,688 NetUtil.py:44 – DEBUG:: Connecting to the following url https://10.32.241.20:8440/cert/ca\nINFO 2015-08-02 15:38:22,689 NetUtil.py:58 – Failed to connect to https://10.32.241.20:8440/cert/ca due to [Errno 111] Connection refused\nINFO 2015-08-02 15:38:22,689 NetUtil.py:77 – Server at https://10.32.241.20:8440 is not reachable, sleeping for 10 seconds…\nINFO 2015-08-02 15:38:32,699 NetUtil.py:44 – DEBUG:: Connecting to the following url https://10.32.241.20:8440/cert/ca\n’, None)

STDERR
tcgetattr: Invalid argument
Connection to apjhana01.sin.XXX.corp closed.


Viewing all articles
Browse latest Browse all 3435

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>