Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.11.1 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

Connection timeout to deb.ocsinventory-ng.org

Hello,

When trying to install OCS agent from a datacenter, I have a connection issue.

The connection times out via curl :

curl -vvvv http://deb.ocsinventory-ng.org/pubkey.gpg
* Expire in 0 ms for 6 (transfer 0x559151446d60)
* Expire in 1 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 1 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 1 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 1 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 1 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
* Expire in 0 ms for 1 (transfer 0x559151446d60)
*   Trying 137.74.216.245...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x559151446d60)
* connect to 137.74.216.245 port 80 failed: Connection timed out
* Failed to connect to deb.ocsinventory-ng.org port 80: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to deb.ocsinventory-ng.org port 80: Connection timed out
 

When doing a TCP traceroute (some machine names are obfuscated) :

sudo traceroute -T deb.ocsinventory-ng.org
traceroute to deb.ocsinventory-ng.org (137.74.216.245), 30 hops max, 52 byte packets
 1  xxxx.xxxx.xxx (192.168.200.252)  0.167 ms  0.163 ms  0.177 ms
 2  192.168.204.251 (192.168.204.251)  0.654 ms  0.589 ms  0.548 ms
 3  89.30.31.241 (89.30.31.241)  4.321 ms  4.491 ms  4.632 ms
 4  xxx.xxx.xxx (89.30.0.154)  0.886 ms  1.004 ms  1.062 ms
 5  xxx.xxx.xxx (89.30.32.72)  2.883 ms  2.855 ms  2.842 ms
 6  xxx.xxx.xxx (89.30.15.48)  1.027 ms  1.091 ms  1.412 ms
 7  91.196.184.166 (91.196.184.166)  1.381 ms  1.352 ms  1.309 ms
 8  ovh.par.franceix.net (37.49.236.144)  1.651 ms  1.542 ms  1.572 ms
 9  * * *
10  * * *
11  * * *
12  be102.rbx-g1-nc5.fr.eu (94.23.122.146)  5.589 ms be103.rbx-g4-nc5.fr.eu (54.36.50.229)  18.985 ms  5.240 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Looking at the TCP trace, it looks like the call stops at be102.rbx-g1-nc5.fr.eu which is an OVH where the ocsinventory server are.

Also the call works locally and in other datacenters.

Example of a working tcp traceroute from another datacenter :

sudo traceroute -T deb.ocsinventory-ng.org
traceroute to deb.ocsinventory-ng.org (137.74.216.245), 30 hops max, 52 byte packets
 1  xxx.xxxx.xxx (192.168.210.251)  0.373 ms  0.333 ms  0.342 ms
 2  192.168.214.251 (192.168.214.251)  1.928 ms  2.118 ms  2.098 ms
 3  89.30.98.57 (89.30.98.57)  3.135 ms  2.911 ms  3.098 ms
 4  xxx.xxx.xxx (89.30.0.125)  4.848 ms  2.986 ms  3.106 ms
 5  xxx.xxx.xxx (89.30.15.26)  4.769 ms  4.745 ms  4.717 ms
 6  xxx.xxx.xxx (89.30.15.23)  4.681 ms  11.462 ms  11.452 ms
 7  91.196.184.166 (91.196.184.166)  11.414 ms  10.437 ms  10.291 ms
 8  ovh.par.franceix.net (37.49.236.144)  10.274 ms  9.495 ms  8.972 ms
 9  * * *
10  * * *
11  * * *
12  be103.rbx-g4-nc5.fr.eu (54.36.50.229)  32.219 ms  32.213 ms  32.170 ms
13  * * *
14  * * *
15  * * *
16  137.74.216.245 (137.74.216.245)  5.400 ms  5.514 ms  5.433 ms
17  137.74.216.245 (137.74.216.245)  5.461 ms  5.414 ms  5.306 ms
 

Do you have any idea what can block the call ?

Many thanks.

in OCS Inventory NG agent for Unix by (160 points)

2 Answers

0 votes
it's NOT mandatory to have an agent with the same level than the server ! The unique restriction is the agent have to be UNDER or EQUAL than the server.

So, I recommand, the better and the simpler, to use the agent available for your distribution.

(And therefore, upgrade your server each year ...)

Example : for Debian 11 Buster, OcsInventory Agent is 2.8, but for Debian 12 Bookworm agent is 2.10, so if you want have Debian 12 agent, the server need to be 2.10 or upper ...

(IMHO, there is nothing on 'deb.ocsinventory...' due Debian repository give agent efficiently ...)
by (17.9k points)
edited by
0 votes
Hi jacquesh,

thanks for the workaround, but that does not tell me why I can access deb.ocsinventory-ng.org from one datacenter but not from another one.

Any idea ?

Thanks
by (160 points)
 
Powered by Question2Answer
...