Task:
Confirm AAP services are running and checking log locations.
AAP Controller:
1. Login
$ ssh myadminid@aapdev.mindwatering.net
<enter pwd>
$ sudo su -
<enter pw
(or, pbrun su -, if applicable)
2. Check the AAP Controller services:
[root@appdev ~]# supervisorctl status
<confirm services running>
example:
tower-processes:awx-callback-receiver RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-daphne RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-dispatcher RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-rsyslog-configurer RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-rsyslogd RUNNING pid 2745, uptime 52:00:05
tower-processes:awx-uwsgi RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-ws-heartbeat RUNNING pid 2745, uptime 52:01:01
tower-processes:awx-wsrelay RUNNING pid 2745, uptime 52:01:01
[root@appdev ~]# automation-controller-service status
<confirm status>
Notes:
- This wrapper actually reports on the service status of multiple systemctl status results.
- All should be active (running)
- Services:
- - automation-controller.service
- - redis.service
- - nginx.service
- - supervisord.service
- - receptor.service
3. Check the AAP Logs:
[root@appdev ~]# cd /var/log/supervisor
[root@appdev ~]# tail awx-callback-receiver.log
<view content for errors>
[root@appdev ~]# tail awx-daphne.log
<view content for errors>
[root@appdev ~]# tail awx-dispatcher.log
<view content for errors>
[root@appdev ~]# tail rsyslog-configurer.log
<view content for errors>
[root@appdev ~]# tail awx-rsyslog.log
<view content for errors>
[root@appdev ~]# tail awx-uwsgi.log
<view content for errors>
[root@appdev ~]# tail awx-wsbroadcast.log
<view content for errors>
[root@appdev ~]# tail awx-ws-heartbeat.log
<view content for errors>
[root@appdev ~]# tail awx-wsrelay.log
<view content for errors>
[root@appdev ~]# tail failure-event-handler.sterr.log
<view content for errors>
[root@appdev ~]# tail rsyslog-4xx-recovery.stderr.log
<view content for errors>
[root@appdev ~]# tail supervisord.log
<view content for errors>
AAP Hub:
1. Login
$ ssh myadminid@aapdevhub.mindwatering.net
<enter pwd>
$ sudo su -
<enter pw
(or, pbrun su -, if applicable)
2. Check the AAP services:
[root@appdevhub ~]# systemctl status pulp*
<confirm status>
- or run individually -
[root@appdevhub ~]# systemctl status nginx.service --no-pager
<confirm status>
[root@appdevhub ~]# systemctl status rdis.service --no-pager
<confirm status>
[root@appdevhub ~]# systemctl status pulpcore.service --no-pager
<confirm status>
[root@appdevhub ~]# systemctl status pulpcore-resource-manager.service --no-pager
<confirm status>
[root@appdevhub ~]# systemctl status pulpcore-api.service --no-pager
<confirm status>
[root@appdevhub ~]# systemctl status pulpcore-worker@1.service --no-pager
<confirm status>
Generate Log Bundle for RedHat Support:
1. Install sos if not installed on each VM/node used for reporting:
[root@appdev ~]# yum install sos
Notes:
The old package sos-collector is part of the main sos package w/RedHat 8.4 and later. No need to install separately.
The command sos collect uses the SSH-keys between the primary and secondary controllers, and from the primary Controller to the Hub and/or the EDA controller, etc.
If the cluster-type is set, then entering just sos collect will automatically retrieve all the node members of "this" cluster.
To collect on the primary Controller for all the controllers:
[root@appdev ~]# sos collect
To collect logs for a specific list of hosts:
[root@appdev ~]# sos collect --nodes=appdev.mindwatering.net,appdevhub.mindwatering.net,appdeveda.mindwatering.net
previous page
|