deployment problem..

Hi,
i m trying to deploy edition from unix box to windows box.
i am getting several problems in that.

The deployment is faliing for a perticular folder in a branch.
This is what the source log says.
LIB: 2007-05-13 16:21:31 Cannot read from socket.
LIB: 2007-05-13 16:21:31 ERROR: Failed to deploy local_directory[0]: .
LIB: 2007-05-13 16:21:31 ERROR: Failed 1 directories
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 After PRECOMMIT, res=-1
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 exiting dotask
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 entering awaiting-rollback
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 exiting awaiting-rollback
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 entering rollback
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 ROLLBACK is not applicable for non transactional deployment
LIB: 2007-05-13 16:21:31 ERROR: Could not read phase start message.
LIB: 2007-05-13 16:21:31 Receiver-ERROR: .
LIB: 2007-05-13 16:21:31 ERROR: Failed to deploy local_directory[0]: .
LIB: 2007-05-13 16:21:31 ERROR: Failed 1 directories
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 exiting rollback
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 entering awaiting-cleanup
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 exiting awaiting-cleanup
ENG: 2007-05-13 16:21:31 EDT GMT-04:00 Thread-20615 entering cleanup
LIB 00019: 2007-05-13 16:21:34 ERROR: Could not read content size from remote.
LIB 00022: 2007-05-13 16:21:34 ERROR: Could not read server status, client OK.
LIB: 2007-05-13 16:21:34 [Sun May 13 16:21:34 2007] opendeploy 20070513.3167.2 root COMPLETED /default/main/portal_production/EDITION/portal_production_05092007_21h17m56s/ .portal_prod_migrate_edition.main.10.202.148.86 negril3 10.202.148.86
LIB: 2007-05-13 16:21:34 [Sun May 13 16:21:34 2007] 20070513.3167.2 STATS DEPLOYMENT /default/main/portal_production/EDITION/portal_production_05092007_21h17m56s/ -- .portal_prod_migrate_edition.main.10.202.148.86 OK
LIB: 2007-05-13 16:21:34 File Content transferred: 91300888 bytes
ENG: 2007-05-13 16:21:34 EDT GMT-04:00 Thread-20615 After CLEANUP, res=1
ENG: 2007-05-13 16:21:34 EDT GMT-04:00 Thread-20615 exiting cleanup
ENG: 2007-05-13 16:21:34 EDT GMT-04:00 Thread-20615 entering task-failed
ENG: 2007-05-13 16:21:34 EDT GMT-04:00 Thread-20615 still waiting for 0
LIB: 2007-05-13 16:21:34 LOGFILE=[/www/negril3/interwoven/OpenDeployNG/log/src.portal_prod_migrate_edition.main.negril3.to.10.202.148.86.log]
LIB: 2007-05-13 16:21:34 Locale=[English_UnitedStates.US-ASCII@Binary]
ENG: 2007-05-13 16:21:34 EDT GMT-04:00 Thread-20615 PostDisConnect Dnr still waiting for 0

Another with some files which contains " in their name in other branch.
i make the diff between two areas and i came to know about these files with ".
how can i make the config file to ignore this character...

also,
is there any way, we can deploy the contents of soft link from unix to winodws.
any help is apprecited.

Env: unix box: Teamsite 6.5 on sunos 5.8
OD source : v6.0.2
OD reciever:v6.1.0

thanks in advance,
amit

Find more posts tagged with

Comments

13adam13

Hey Amit,

Sorry to see that you all are still working on the migration.

As far as ignoring the files with the ", you can probably add an exclude filter for it. that will ignore the file, though, which means you won't get it as part of the migration process.

For the other issue, of not being able to deploy an edition, I would expect that the error in the log file

LIB: 2007-05-13 16:21:31 Cannot read from socket.

means that OD cannot read from the file system the path specified. You might make sure that the edition name is correct and that the mount is available to be read from.

Also, adding the attribute followLinks to the transferRules element should allow you to deploy the contents of a symlink.

nipper

try to see if you can connect via telnet to the OD receiver

telnet OD-receiver 20014

Amit_LnT

hey adam,
nice to see ur message..
hmm..still migrating the stuff..
the firewall issues got biggg time to resolve.. and its huge list of editions.. Smiley Happy

just to elaborate more on this..
i believe the OD is not deploying the file when it finds " character.
to exclude, i mean OD should ignore this char in file name and deploy the file normaly. i want those files to be on target servers.

About that socket problem. I have tried it twice and the edition name name is proper. its able to deploy it for all folders but only failing for a perticular folder on source. the folder has a permission 555.

about the soft link, i will try the one u told for.

and telnet OD-receiver 20014 is working.. from source machine..

help is appreciated..

thanks to all,
amit

Amit_LnT

hi frnds..
i think.. i traced the problem here.. the source contains the folder name as prn and windows doent allow you to create a folder with this name.

is there any way, so that i can rename the source folder with something else when it is getting deployed at target.

thanks in advance..
amit

Adam Stoller

hi frnds..
i think.. i traced the problem here.. the source contains the folder name as prn and windows doent allow you to create a folder with this name.

is there any way, so that i can rename the source folder with something else when it is getting deployed at target.

thanks in advance..
amit

Heh - that's funny - but I just verified it on a windows server I have access to - (nothing to do with OD) you cannot name a folder or file "prn" on Windows (don't you just love advanced OS's? ;-)

If your target servers are going to be Windows - then you should rename the directory on the source side to avoid the complexity and confusion - and then you don't have to worry about trying to special-case it within a deployment configuration file (you'd essentially have to deploy the contents of the "prn" directory to an explicitly named target area folder [not named "prn"] - not worth the effort IMO)

Amit_LnT

hey fish,
thanks for the suggestion.
But i am trying to deploy the editions from the unix to windows box.
and so i can not rename the source folder.
Also, i have one problem with the source file name containig special char like (",<,>,*) which windows doesnt allow as part of file name.
any suggestion on that..

thanks,
amit

ISCBorisB

Heh - that's funny - but I just verified it on a windows server I have access to - (nothing to do with OD) you cannot name a folder or file "prn" on Windows (don't you just love advanced OS's? ;-)

MS justifies this idiocy by reserving so called "device names". The following is the excerpt from here.

Do not use the following reserved device names for the name of a file: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4,
COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names
followed by an extension, for example, NUL.tx7.

Adam Stoller

hey fish,
thanks for the suggestion.
But i am trying to deploy the editions from the unix to windows box.
and so i can not rename the source folder.
Also, i have one problem with the source file name containig special char like (",<,>,*) which windows doesnt allow as part of file name.
any suggestion on that..

thanks,
amit

I cannot tell you how to fix the past.
For the future - you should be making sure that all files and directories are named according to a standard or policy - such that those names will not contain odd punctuation characters -- hyphen [-], underscore [_] and dot [.] are probably the only legitimate punctuation characters to be included in filenames and directories that are being managed via CMS.

Some of it is user-training - but a lot of it can be done through proper programming of customizations (workflow and templating).

Things like the 'prn' directory - well that's a live-and-learn type of issue - you now know that it's bad so you should fix it in the current system - but if you have to deploy from an older edition, make a special deployment configuration for it and, as I suggested you will need to deploy the contents of the source-directory "prn" into some other target directory ("prnx" ?) - but of course if this is a web-related directory and you have links pointing to files within the "prn" directory - you're pretty much SOL and need to plan a much bigger resolution to the problem.