大网数据广告活动
服务器运维问答

How to properly debug XMLRPC fails

· 52CE 我爱测

I have an Odoo instance runing on Ubuntu server and I want to query the XMLRPC api from a Windows machine in the same subnet. The two can normally communicate and it all works ok, but if I set the client script to run every 5 min…

问题原文

原帖链接 · user568021 · CC BY-SA 3.0

I have an Odoo instance runing on Ubuntu server and I want to query the XMLRPC api from a Windows machine in the same subnet. The two can normally communicate and it all works ok, but if I set the client script to run every 5 minutes in Windows Scheduler it starts to experience problems.

socket.error: [Errno 10061] No connection could be made because the target machine actively refused it

If I wait for some short time, disable the Scheduled Task and I don't touch the script it starts working again, but only for a few calls, then the error comes back.

So for some reason the Ubuntu machine is denying if there are too many calls. I just can find out on which level these rules are. I don't use firewall.

root@oddo9:~$ ufw status
Status: inactive 
root@oddo9:~$

Also no iptables

root@oddo9:~$ iptables -L
Chain INPUT (policy ACCEPT) target     prot opt source    
destination

Chain FORWARD (policy ACCEPT) target     prot opt source              
destination

Chain OUTPUT (policy ACCEPT) target     prot opt source               
destination

There's also no output from Odoo, so I have no idea how to debug this problem.

已采纳解答

原帖链接 · user568021 · CC BY-SA 3.0

I discovered what was wrong. We had two machines with the same IP in our subnet so there was the conflict. Client was trying to connect to some other machine, which did not even listen for XMLRPC protocol.

I thought that it works if I wait let's say 15 minutes, but no.. it just randomly worked for a call or two. It all makes sense now.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-07-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。