Problems with Administering Clusters

I get a warning that the object store credentials are out of sync

You might get a warning notification in the Big Data Cloud Console, indicating that object store credentials are out of sync. This occurs if the Cloud Storage password specified when a cluster was created is changed later outside of Oracle Big Data Cloud. The password needs to be updated. See Update Cloud Storage Credentials.

I need to view the status of running services

There are two ways to view the status of a cluster and the associated services:

Big Data Cloud Console: You can view the status of services on the Status page in the cluster console. Two views are available on the Status page: an overall summary on the Services tab, and the same information broken down by host on the Hosts tab. See View Cluster Component Status.
Ambari user interface: You can view detailed information about each service through the Ambari user interface. Open port 8080 and navigate to the Ambari server host. See related information in Access Big Data Cloud Using Ambari and Enable Access Rules.

Services aren’t being restarted properly after life cycle operations

If services aren’t being restarted properly after life cycle operations such as cluster start/stop, scale-out, patch-apply, and patch-rollback, the most likely cause is that ambari-agent has either terminated or has not been able to start. See I need to control the Ambari-agent service.

I need to modify the Ambari Web inactivity timeout

Ambari Web automatically logs users out after a period of inactivity and redirects to the login page. This inactivity timeout is configurable for Operators and Read-Only users.

The value of the inactivity timeout is specified in seconds. By default, the inactivity timeout is set to 3600 seconds (one hour) for all users. To disable the inactivity timeout feature, set the value to 0.

To change the inactivity timeout:

Ensure the Ambari server is completely stopped before making any changes to the inactivity timeout.
Open the /u01/bdcsce/etc/ambari-server/conf/ambari.properties file on the Ambari server host with a text editor.

Find the following two properties for the inactivity timeout setting. Both are initially set to 3600 seconds.

Property	Description
`user.inactivity.timeout.default`	Sets the inactivity timeout (in seconds) for all non-Read-Only users.
`user.inactivity.timeout.role.readonly.default`	Sets the inactivity timeout (in seconds) for all Read-Only users.

Set these properties to a desired timeout value in seconds.
Save the changes and restart the Ambari server.

I need to control the Ambari-agent service

To control the Ambari-agent service, SSH into each node and execute the following commands as root:

To get the status of the Ambari agent:
```
ambari-agent status
```
To start the Ambari agent:
```
ambari-agent start
```
To stop the Ambari agent:
```
ambari-agent stop
```
To restart the Ambari agent:
```
ambari-agent restart
```

Also see Access Big Data Cloud Using Ambari.

I need to control the Ambari-server service

To control the Ambari-server service, SSH into node 1 and execute the following commands as root:

To get the status of the Ambari server:
```
ambari-server status
```
To start the Ambari server:
```
ambari-server start
```
To stop the Ambari server:
```
ambari-server stop
```
To restart the Ambari server:
```
ambari-server restart
```

Also see Access Big Data Cloud Using Ambari.