[TYPO3-caretaker] Ping/HTTP-Test takes ages

[Martin Ficzel]

Am 15.08.11 11:24, schrieb Marc Wöhlken:
> Hi!
> Just set up caretaker server (forge version) on TYPO3 4.5.4 and a
> version 4.4.9 client system.
> The strange thing is that ping- and http-test test take really long when
> performed by caretaker.
>
> --+ Caretaker Root [root] updateAggregatorNode
>    |--+ My- Webserver [instancegroup_1] updateAggregatorNode
>    |  |--+ www.xyz.de [instance_2] updateAggregatorNode
>    |  |  |--+ Basic tests [instance_2_testgroup_1] updateAggregatorNode
>    |  |  |  |--+ Ping<  100ms [instance_2_test_2]
>    |  |  |  |  | Ping command took 7237.5609874725 milliseconds
>    |  |  |  |  +->  Error (updatedTestResult)
>    |  |  |  |--+ Insecure Extensions [instance_2_test_3]
>    |  |  |  |  | No suspect Extensions are found
>    |  |  |  |  +->  OK (updatedTestResult)
>    |  |  |  |--+ HTTP-Response [instance_2_test_4]
>    |  |  |  |  | HTTP Test of http://www.xyz.de/index.php returned a warning
>    |  |  |  |  |  - HTTP-Request took 378.497 milliseconds returned an
> timeout-warning
>    |  |  |  |  +->  Warning (updatedTestResult)
>    |  |  |  +->  Error updateAggregatorNode [instance_2_testgroup_1]
>    |  |  +->  Error updateAggregatorNode [instance_2]
>    |  +->  Error updateAggregatorNode [instancegroup_1]
>    +->  Error updateAggregatorNode [root]
>
> When measuring ping time from colsole it's about 50ms - 70ms.
>
> Any idea why the timings are so different? Is this a typical behavior?
> Can I provide additional info to help find a solution?

Hello Marc,

did you configure the ping command in the extension configuration properly. The ping test 
does not parse the response of the ping command but measures the time it takes to excute 
the single ping command. Usually that is no problem for us since we only want to detect 
real slow behavior.

Regards Martin