press icon indicating copy to clipboard operation
press copied to clipboard

Proxy Server Broken Setup Server or Ping Ansible.

Open raugustos1 opened this issue 1 year ago • 4 comments

image

image

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.site.com.br]

TASK [ping : Ping] **********************************************************************************************************************************************************************
ok: [n1.fp.site.com.br]

TASK [ping : Gather Facts] **************************************************************************************************************************************************************
ok: [n1.fp.site.com.br] => {
 ansible all -i "n1.fp.site.com.br," -m ping -u root

n1.fp.site.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.site.com.br Jobs-----
frappeuser@b1:~/frappe-bench$ 

any tips?

raugustos1 avatar Oct 01 '24 01:10 raugustos1

Found any solution for this, I am also facing same issue, no entries in Error Log as well

samkit5495 avatar Oct 08 '24 03:10 samkit5495

Hi, I am facing the same issue as well, there is also no Error Log Any helps from team?

cryptomancer1257 avatar Dec 03 '24 02:12 cryptomancer1257

Hi, any solution for this issue.

RijinRaju avatar Dec 12 '24 07:12 RijinRaju

Still happen. Need help with this issue.

asaura08 avatar Dec 19 '24 15:12 asaura08