opened 01:26AM - 01 Oct 24 UTC
![image](https://github.com/user-attachments/assets/117c5806-ac1d-441e-871e-5007…8865b93b)
![image](https://github.com/user-attachments/assets/e5e77fa2-ea86-4791-8f5b-d8dd374d52f2)
No logs
**Validate Ansible**
```
frappeuser@b1:~/frappe-bench$ ansible-playbook -i **hostname or ipserver**, /home/frappeuser/frappe-bench/apps/press/press/playbooks/ping.yml -u root
PLAY [Ping Server] **********************************************************************************************************************************************************************
TASK [Gathering Facts] ******************************************************************************************************************************************************************
[WARNING]: Platform linux on host **hostname or ipserver** is using the discovered Python interpreter at /usr/bin/python3.12, but future installation of another Python interpreter could
change the meaning of that path. See https://docs.ansible.com/ansible-core/2.17/reference_appendices/interpreter_discovery.html for more information.
ok: [n1.fp.matizo.com.br]
TASK [ping : Ping] **********************************************************************************************************************************************************************
ok: [n1.fp.matizo.com.br]
TASK [ping : Gather Facts] **************************************************************************************************************************************************************
ok: [n1.fp.matizo.com.br] => {
```
```
ansible all -i "n1.fp.site.com.br," -m ping -u root
n1.fp.matizo.com.br | SUCCESS => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python3.12"
},
"changed": false,
"ping": "pong"
}
```
```
ansible all -i "65.231.xx.xx," -m ping -u root
65.231.xx.xx | SUCCESS => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python3.12"
},
"changed": false,
"ping": "pong"
}
```
```
frappeuser@b1:~/frappe-bench$ supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache RUNNING pid 205014, uptime 21:48:29
frappe-bench-redis:frappe-bench-redis-queue RUNNING pid 205015, uptime 21:48:29
frappe-bench-web:frappe-bench-frappe-web RUNNING pid 205016, uptime 21:48:29
frappe-bench-web:frappe-bench-node-socketio RUNNING pid 205017, uptime 21:48:29
frappe-bench-workers:frappe-bench-frappe-build-worker-0 RUNNING pid 205030, uptime 21:48:29
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING pid 205024, uptime 21:48:29
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 205018, uptime 21:48:29
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING pid 205019, uptime 21:48:29
frappe-bench-workers:frappe-bench-frappe-sync-worker-0 RUNNING pid 205029, uptime 21:48:29
frappeuser@b1:~/frappe-bench$ bench doctor
-----Checking scheduler status-----
Workers online: 4
-----fp.matizo.com.br Jobs-----
frappeuser@b1:~/frappe-bench$
```
any tips?