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.

cant find VNC service under actions in ambari view

Solved Go to solution
Highlighted

cant find VNC service under actions in ambari view

New Contributor

I am using instructions mentioned here https://github.com/hortonworks-gallery/ambari-vnc-service to setup VNC server for hortonworks sanbox. but I cant find the VNC service under actions in ambari view can anyone help me with this?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: cant find VNC service under actions in ambari view

Super Mentor

@chaitanya Kandula

Do you see any error in "/var/log/ambari-server/ambari-server.log" ? If yes then can you please share the log?

Have you logged in to ambari server as "admin" user?

9 REPLIES 9

Re: cant find VNC service under actions in ambari view

Super Mentor

@chaitanya Kandula

Do you see any error in "/var/log/ambari-server/ambari-server.log" ? If yes then can you please share the log?

Have you logged in to ambari server as "admin" user?

Re: cant find VNC service under actions in ambari view

New Contributor

ambari-server.txt

@Jay Kumar SenSharma I dont see any logs written today, yes I logged in as admin, Please find the attached log

22 Oct 2017 21:38:05,485 INFO [main] Configuration:3002 - Reading password from existing file 22 Oct 2017 21:38:05,494 INFO [main] Configuration:3487 - Hosts Mapping File null 22 Oct 2017 21:38:05,494 INFO [main] HostsMap:60 - Using hostsmap file null 22 Oct 2017 21:38:05,869 INFO [main] ControllerModule:221 - Detected POSTGRES as the database type from the JDBC URL 22 Oct 2017 21:38:05,899 INFO [main] ControllerModule:539 - Searching package org.apache.ambari.server for annotations matching [interface org.apache.ambari.server.EagerSingleton, interface org.apache.ambari.server.StaticallyInject, interface org.apache.ambari.server.AmbariService] 22 Oct 2017 21:38:06,051 INFO [main] ClasspathScannerUtils:54 - Checking package [org.apache.ambari.server] for binding candidates. 22 Oct 2017 21:38:06,549 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.controller.logging.LogSearchDataRetrievalService 22 Oct 2017 21:38:06,557 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.state.services.AlertNoticeDispatchService 22 Oct 2017 21:38:06,558 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.state.services.AmbariServerAlertService 22 Oct 2017 21:38:06,559 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.state.services.CachedAlertFlushService 22 Oct 2017 21:38:06,659 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.state.services.MetricsRetrievalService 22 Oct 2017 21:38:06,660 INFO [main] ControllerModule:581 - Registering service class org.apache.ambari.server.state.services.RetryUpgradeActionService 22 Oct 2017 21:38:06,669 INFO [main] ControllerModule:609 - Searching package org.apache.ambari.server.notifications.dispatchers for dispatchers matching interface org.apache.ambari.server.notifications.NotificationDispatcher 22 Oct 2017 21:38:06,715 INFO [main] ControllerModule:649 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher 22 Oct 2017 21:38:06,725 INFO [main] ControllerModule:649 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher 22 Oct 2017 21:38:06,733 INFO [main] ControllerModule:649 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher 22 Oct 2017 21:38:06,734 INFO [main] ControllerModule:649 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AmbariSNMPDispatcher 22 Oct 2017 21:38:06,735 INFO [main] ControllerModule:673 - Searching package org.apache.ambari.server.checks for classes matching class org.apache.ambari.server.checks.AbstractCheckDescriptor 22 Oct 2017 21:38:06,923 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.HostsMasterMaintenanceCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesMaintenanceModeCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.HostMaintenanceModeCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.HostsRepositoryVersionCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.SecondaryNamenodeDeletedCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesNamenodeHighAvailabilityCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesNamenodeTruncateCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesMapReduceDistributedCacheCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesTezDistributedCacheCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.HostsHeartbeatCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ComponentsInstallationCheck 22 Oct 2017 21:38:06,924 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ServicesUpCheck 22 Oct 2017 21:38:06,925 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.ClientRetryPropertyCheck 22 Oct 2017 21:38:06,925 INFO [main] ControllerModule:709 - Registered pre-upgrade check class org.apache.ambari.server.checks.YarnRMHighAvailabilityCheck 22 Oct 2017 21:38:06,925 INFO [main] ControllerModule:709 - Registered pre-upgrade check class

Re: cant find VNC service under actions in ambari view

Super Mentor

@chaitanya Kandula

It is strange to see no recent logging from ambari-server side on the log.

Is it possible if you can try to restart the ambari server once, and then see if the new logs are getting generated there?

# ambari-server restart<br>

.

Once we login to the ambari-server host using SSH then we can check the log at the following location:

# ls -l /var/log/ambari-server/ambari-server.log

.

Currently ambari views does not have capability to show the ambari-server logs. Unless it it pushed to HDFS. If you push the ambari-server.log to HDFS then using Ambari File View you can take a look at the logs.

Re: cant find VNC service under actions in ambari view

New Contributor

@Jay Kumar SenSharma when I type vi /var/log/ambari-server/ambari-server.log its giving me an alert about Found aswap file (attached an image explaining the alert). i am trying to use the ambari file view to open the ambari-server.log but its telling failed to transition to undefined and some logs.(attached error-message.jpg). please see if thats giving you any clue, unfortunately, there is only one link that explains this configuration and following that I am unable to deploy the VNC service and I am fortunate that you are responding I am reallylog-file-status.jpgerror-message.jpg thankful to you.

Re: cant find VNC service under actions in ambari view

Super Mentor

@chaitanya Kandula

Regarding the ".swp" error while opening ambari-server.log indicates that some other "root" user has opened that file in "vi" editor hence it is not allowing you to open it. You can follow the screenshot that you shared which also shows some force remedies to fix this. Or else check with the other user who has opened this file for writing to close it.

It can also happen if you have opened multiple SSH session to the ambari server host and in one terminal you opened the ambari-server.log in vi editor and forgot to close it.

.

Regarding the other error "sandbox.hortonworks.com:50070 Connection refused" this indicates that your NameNode might not be running. So please check if that port is opened by NameNode process?

Following command will list the process ID that has opened the port 50070, If you do not see that port is opened then it means either your NameNode is not running or It might be running with some errors (so please check the NameNode logs)

# netstat -tnlpa | grep 50070

.

Better try to restart the NameNode from amabri UI and then check if the port 50070 is opened completely or not?

.

Re: cant find VNC service under actions in ambari view

Super Mentor

@chaitanya Kandula

As based on your previous screenshots, it looks like some other process/user is holding lock on the ambari-server.log Hence because you are using HDP sandbox so it will be easy to stop the sandbox completely (shutdown) and then try restarting it it will cause all the existing file locks will be released.

Also please check if your HDP Sandbox has enough Disk space?

# df -h

.

Re: cant find VNC service under actions in ambari view

New Contributor

@Jay Kumar SenSharma I restarted the server and I dont see any new logs can you suggest me any work around?

Re: cant find VNC service under actions in ambari view

New Contributor

@Jay Kumar SenSharma I reinstalled the sandbox and I am now seeing VNC service but I am getting a different error this time

logs.txt

Re: cant find VNC service under actions in ambari view

Contributor

@chaitanya Kandula Just to compliment @Jay Kumar SenSharma 's answer in case you still find your file opened by multiple processes and gives you such type of error you may use the below-mentioned command to check the process using that file and then killing it to resume back normally.

lsof <file-name>

lsof /var/log/ambari-server/ambari-server.log

Once, your sandbox is up and running check if your ambari server has come up properly or not.

ambari-server status

If it is up and running you will find the log file in the same location.

I would suggest stop the ambari services, move the older files to some temporary location and then start the services to have a fresh look at the problem.

mbari-server stop
mkdir -p /tmp/AmbariLogBackup
mv /var/log/ambari-server/* /tmp/AmbariLogBackup
ambari-server status
ambari-server start

Once your ambari log creation problem is sorted try to perform the steps so that error messages will be logged into it.

Also, do attach it here so that we can have a look at the problem

Thanks.

SKS

Don't have an account?
Coming from Hortonworks? Activate your account here