Environment
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3 Content
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1
Novell ZENworks 11 Configuration Management Support Pack 2 - ZCM 11 SP2
Situation
Linux-based Satellite server
Content sync fails with timeout error
Content sync fails with timeout error
Resolution
Increase the default connection-timeout and socket-timeout (parameters in milliseconds) e.g., to 200 seconds:
1. Open /etc/opt/novell/zenworks/conf/xplatzmd.properties in a text editor.
2 Add the connection-timeout parameter as connection-timeout=200000 and socket-timeout parameter as socket-timeout=200000
1. Open /etc/opt/novell/zenworks/conf/xplatzmd.properties in a text editor.
2 Add the connection-timeout parameter as connection-timeout=200000 and socket-timeout parameter as socket-timeout=200000
Cause
The default setting for the content replication timeout is already set to 240 seconds (CDPWebCallWaitTimeout=240000), see TID 7005887 for this, but the general connection timeout settings do have a lower value which might cause the connection to be closed before the Primary server can respond with missing content information.
The default value for connection-timeout and socket-timeout is 20000 (20 seconds) in ZCM 10.3.4 and 100000 (100 seconds) in ZCM 11.x. These settings are now covered in ZCM 11 documentation, scroll down to section 29.1.1 'Manually Configuring the Web Service Timeout Advanced Content Replication Setting'.
The default value for connection-timeout and socket-timeout is 20000 (20 seconds) in ZCM 10.3.4 and 100000 (100 seconds) in ZCM 11.x. These settings are now covered in ZCM 11 documentation, scroll down to section 29.1.1 'Manually Configuring the Web Service Timeout Advanced Content Replication Setting'.
Additional Information
Excerpt from a ZCM 10.3.4 Linux Satellite server's /var/opt/novell/zenwork/logs/LocalStore/zmd-messages.log :
"...
[Debug] [05/15/2012 12:21:46.404] [] [17776] [ZenworksAgent] [135] [ResourceManager] [Pinging URI https://xxx.xxx.xxx.xxx:443/zenworks-ping/ with timeout of 20000 ms] [] []
[Debug] [05/15/2012 12:22:06.425] [] [17776] [ZenworksAgent] [135] [ResourceManager] [SocketTimeoutException returned bytesTransfered: 0, Reason: null, Message: connect timed out] [] []
...
[Debug] [05/15/2012 12:22:06.435] [] [17776] [ZenworksAgent] [135] [SoapUtility] [Call for uri 'https://xxx.xxx.xxx.xxx:443/zenworks-contentservice/' complete, time: 20034, results were NULL.] [] []
...
[Debug] [05/15/2012 12:22:26.461] [] [17776] [ZenworksAgent] [135] [SoapUtility] [Marking the uri 'https://xxx.xxx.xxx.xxx:443/zenworks-contentservice/' as bad because of connect timed out] [] []
..."
"...
[Debug] [05/15/2012 12:22:06.425] [] [17776] [ZenworksAgent] [135] [ResourceManager] [SocketTimeoutException returned bytesTransfered: 0, Reason: null, Message: connect timed out] [] []
...
[Debug] [05/15/2012 12:22:06.435] [] [17776] [ZenworksAgent] [135] [SoapUtility] [Call for uri 'https://xxx.xxx.xxx.xxx:443/zenworks-contentservice/' complete, time: 20034, results were NULL.] [] []
...
[Debug] [05/15/2012 12:22:26.461] [] [17776] [ZenworksAgent] [135] [SoapUtility] [Marking the uri 'https://xxx.xxx.xxx.xxx:443/zenworks-contentservice/' as bad because of connect timed out] [] []
..."