# unable to test the log aggregator on awx v10.0.0

**URL:** <https://forum.ansible.com/t/unable-to-test-the-log-aggregator-on-awx-v10-0-0/32691>\
**Category:** AWX Project\
**Tags:** ubuntu, awx, kubernetes\
**Created:** [April 15, 2020, 1:40pm UTC](https://forum.ansible.com/t/unable-to-test-the-log-aggregator-on-awx-v10-0-0/32691 "2020-04-15T13:40:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SANCHIT\_KHANDELWAL](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@SANCHIT\_KHANDELWAL](https://forum.ansible.com/u/SANCHIT_KHANDELWAL)\
**Post date:** [April 15, 2020, 1:40pm UTC](https://forum.ansible.com/t/unable-to-test-the-log-aggregator-on-awx-v10-0-0/32691/1 "2020-04-15T13:40:17Z")

</div>

Hi All,

Hope you are doing well.

I am receiving the attached error when I am trying to add the details of logstash on logging page and test it on AWX v10.0.0.

I have also attached the snap of logging page for the reference.

root@master:~# kubectl get pods --all-namespaces -o wide  
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES  
awx awx-0 4/4 Running 0 10d 192.168.184.13 ubuntu-worker   
awx awx-1 4/4 Running 0 6d1h 192.168.184.27 ubuntu-worker   
awx awx-postgresql-postgresql-0 1/1 Running 0 10d 192.168.184.10 ubuntu-worker   
awx kubewatch-5b6b8b7994-6rv99 1/1 Running 0 7d8h 192.168.184.23 ubuntu-worker   
awx logstash-0 1/1 Running 0 24h 192.168.184.38 ubuntu-worker   
awx nginx-deployment-6b474476c4-lbjdk 1/1 Running 0 7d8h 192.168.184.24 ubuntu-worker   
awx nginx-deployment-6b474476c4-wz25t 1/1 Running 0 7d19h 192.168.184.22 ubuntu-worker   
awx web 1/1 Running 0 6d2h 192.168.184.26 ubuntu-worker   
cert-manager cert-manager-85db5c4c87-5wzsj 1/1 Running 0 4d21h 192.168.184.29 ubuntu-worker   
cert-manager cert-manager-cainjector-7959549c78-km5xf 1/1 Running 0 4d21h 192.168.184.28 ubuntu-worker   
cert-manager cert-manager-webhook-5c8696f555-ngg5v 1/1 Running 0 4d21h 192.168.184.30 ubuntu-worker   
default kubewatch 0/2 ContainerCreating 0 7d8h ubuntu-worker   
ingress-nginx nginx-ingress-controller-5bb8fb4bb6-zjfw5 1/1 Running 0 6d2h 192.168.184.25 ubuntu-worker   
kube-system calico-kube-controllers-5fc5dbfc47-8xmhg 1/1 Running 0 11d 192.168.219.67 master   
kube-system calico-node-xhdhx 1/1 Running 0 7d19h 192.168.101.226 master   
kube-system calico-node-xl97b 1/1 Running 0 11d 192.168.101.245 ubuntu-worker   
kube-system coredns-66bff467f8-4c7xd 1/1 Running 0 11d 192.168.219.65 master   
kube-system coredns-66bff467f8-k6bhx 1/1 Running 0 11d 192.168.184.1 ubuntu-worker   
kube-system etcd-master 1/1 Running 0 11d 192.168.101.226 master   
kube-system kube-apiserver-master 1/1 Running 0 11d 192.168.101.226 master   
kube-system kube-controller-manager-master 1/1 Running 0 11d 192.168.101.226 master   
kube-system kube-proxy-5mktb 1/1 Running 0 11d 192.168.101.245 ubuntu-worker   
kube-system kube-proxy-tbb7c 1/1 Running 0 11d 192.168.101.226 master   
kube-system kube-scheduler-master 1/1 Running 0 11d 192.168.101.226 master

root@master:~# kubectl get svc --all-namespaces -o wide  
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR  
awx awx-postgresql ClusterIP 10.98.239.31 5432/TCP 10d app=postgresql,release=awx-postgresql,role=master  
awx awx-postgresql-headless ClusterIP None 5432/TCP 10d app=postgresql,release=awx-postgresql  
awx awx-web-svc NodePort 10.97.41.36 80:30034/TCP 10d name=awx-web-deploy  
awx docker-hello-world-svc ClusterIP 10.108.180.245 8088/TCP 6d2h app=docker-hello-world  
awx logstash ClusterIP 10.98.126.103 8080/TCP 24h [app.kubernetes.io/instance=logstash,app.kubernetes.io/name=logstash](http://app.kubernetes.io/instance=logstash,app.kubernetes.io/name=logstash)  
awx logstash-headless ClusterIP None 8080/TCP 24h [app.kubernetes.io/instance=logstash,app.kubernetes.io/name=logstash](http://app.kubernetes.io/instance=logstash,app.kubernetes.io/name=logstash)  
awx web ClusterIP 10.102.96.212 8080/TCP 6d2h run=web  
cert-manager cert-manager ClusterIP 10.108.102.105 9402/TCP 4d21h [app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=cert-manager](http://app.kubernetes.io/instance=cert-manager,app.kubernetes.io/name=cert-manager)  
cert-manager cert-manager-webhook ClusterIP 10.98.214.234 443/TCP 4d21h [app.kubernetes.io/instance=cert-manager,app.kubernetes.io/managed-by=Tiller,app.kubernetes.io/name=webhook,app=webhook](http://app.kubernetes.io/instance=cert-manager,app.kubernetes.io/managed-by=Tiller,app.kubernetes.io/name=webhook,app=webhook)  
default kubernetes ClusterIP 10.96.0.1 443/TCP 11d   
ingress-nginx ingress-nginx LoadBalancer 10.100.171.250 192.168.101.226 80:30198/TCP,443:31961/TCP 6d2h [app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/part-of=ingress-nginx](http://app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/part-of=ingress-nginx)  
kube-system kube-dns ClusterIP 10.96.0.10 53/UDP,53/TCP,9153/TCP 11d k8s-app=kube-dns

Kindly suggest if I have missed something or anything that can be done to resolve the above stated error.

Thanks,  
Sanchit

> **(attachments)**
>
> ![Error_logstash_awx10.PNG](https://us1.discourse-cdn.com/ansible/original/2X/0/026d94ee1205fe93293017d03fec447b849e2f6f.png)  
> ![Logging_Page.PNG](https://us1.discourse-cdn.com/ansible/original/2X/3/34437f1897ce25654639b7af4ab68837e7a7498b.png)

---

<div class="post-metadata">

**Author:** ![Ankit2](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@Ankit2](https://forum.ansible.com/u/Ankit2)\
**Post date:** [April 16, 2020, 8:24am UTC](https://forum.ansible.com/t/unable-to-test-the-log-aggregator-on-awx-v10-0-0/32691/2 "2020-04-16T08:24:19Z")

</div>

I have the same issue. It was working fine till last version however it stopped all of a sudden when migrated to AWX v10.0.0.

---

<div class="post-metadata">

**Author:** ![Ankit2](https://avatars.discourse-cdn.com/v4/letter/a/ea5d25/32.png) [@Ankit2](https://forum.ansible.com/u/Ankit2)\
**Post date:** [April 16, 2020, 12:42pm UTC](https://forum.ansible.com/t/unable-to-test-the-log-aggregator-on-awx-v10-0-0/32691/3 "2020-04-16T12:42:01Z")

</div>

I am also facing this issue and it looks like a bug. I am using Splunk and AWX is deployed using Docker on Linux but getting the same error. I have raised a bug for this.

[https://github.com/ansible/awx/issues/6726](https://github.com/ansible/awx/issues/6726)
