Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
OD deployment error
System
We're seeing intermittent deployment issues while deploying content from TeamSite to web servers.
The deployment is filelist based, where content will be picked up from workarea and deployed to multiple web servers. The deployments are symmetric key-SSL encrypted.
The error in OD source logs is:
******************
LIB: 2009-11-20 00:41:47 ERROR: Could not read remote status
LIB: 2009-11-20 00:41:47 Cannot read from socket.
LIB: 2009-11-20 00:41:47 ERROR: Failed to deploy local_directory[.] of area[/.iwmnt/default/main/BRANCH1/WORKAREA/WA1] for filelist[/iw-home/webserver_filelist.xyz.txt]
LIB: 2009-11-20 00:41:47 ERROR: Failed 1 of 1 filelists
ENG: 2009-11-20 00:41:47 EST GMT-05:00 Thread-7567 After PRECOMMIT, res=-1
ENG: 2009-11-20 00:41:47 EST GMT-05:00 Thread-7567 exiting dotask
ENG: 2009-11-20 00:41:47 EST GMT-05:00 Thread-7567 entering awaiting-rollback
ENG: 2009-11-20 00:42:29 EST GMT-05:00 Thread-7567 still waiting for 1
ENG: 2009-11-20 00:42:29 EST GMT-05:00 Thread-7567 exiting awaiting-rollback
ENG: 2009-11-20 00:42:29 EST GMT-05:00 Thread-7567 entering rollback
LIB 00024: 2009-11-20 00:42:29 ERROR: Could not send phase start message.
LIB: 2009-11-20 00:42:29 Receiver-ERROR: M-^?/[M-PM-^?/[M-hM-^?/[M-TM-ZM-gM-u|.
******************
The last line of error looks strange. I still need to check receiver logs, but wanted to check if anyone has faced this issue?
OD Base: 6.2.0 on Solaris 10
OD Receivers: 6.2.0 on W2K3 SP2
Thanks!
Find more posts tagged with
Comments
Migrateduser
Did you ever find out what caused this problem?
Thanks.
smwangi
Looks like receiver is down or connection to receiver host is not stable
Migrateduser
There were issues with the network and check point firewall session timeout on one of the new Web server.
The Network Admin increased the session timeout and it's working fine now.
Migrateduser
Thanks for the updates.
Our problem was on the receiver, and the SELinux security settings for our opendeploy user.