Opened 9 years ago

Closed 9 years ago

#391 closed help (fixed)

problem with rsync from monsoon to puma when running REMCOMMS

Reported by: sgalde Owned by: ros
Component: MONSooN Keywords: monsoon umui
Cc: Platform:
UM Version: 7.4

Description

Hello, sorry to bother you.
I did have a umui job that submitted and ran on monsoon. But today when I try it it fails.
I don't believe I've changed anything in the umui (but doesn't everyone say that!)
Output in umbase/ext.out on monsoon looks:

mkdir -p /projects/nemo/sgalde/UM/xerfa/umbase/cfg
rsync -a --exclude=.* --delete-excluded --timeout=900 --rsh=ssh -oBatchMode=yes -v sgalde@puma.nerc.ac.uk:/home/sgalde/NEMO/FCM/xerfa/umbase/c
fg/bld.cfg /projects/nemo/sgalde/UM/xerfa/umbase/cfg
rsync: -oBatchMode=yes: invalid numeric value
rsync error: syntax or usage error (code 1) at main.c(1002)
mkdir -p /projects/nemo/sgalde/UM/xerfa/umbase/cfg
rsync -a --exclude=.* --delete-excluded --timeout=900 --rsh=ssh -oBatchMode=yes -v sgalde@puma.nerc.ac.uk:/home/sgalde/NEMO/FCM/xerfa/umbase/c
fg/ext.cfg /projects/nemo/sgalde/UM/xerfa/umbase/cfg
rsync: -oBatchMode=yes: invalid numeric value
rsync error: syntax or usage error (code 1) at main.c(1002)
mkdir -p /projects/nemo/sgalde/UM/xerfa/umbase
rsync -a --exclude=.* --delete-excluded --timeout=900 --rsh=ssh -oBatchMode=yes -v sgalde@puma.nerc.ac.uk:/home/sgalde/NEMO/FCM/xerfa/umbase/s
rc /projects/nemo/sgalde/UM/xerfa/umbase
rsync: -oBatchMode=yes: invalid numeric value
rsync error: syntax or usage error (code 1) at main.c(1002)

It sort of looks like there should be quotes around 'ssh -oBatchMode=yes', but I'm then not sure how this ever worked if that's the case.

Change History (2)

comment:1 Changed 9 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Steven,

I upgraded fcm early this morning so I guess that's the problem. I tested job submission to MONSooN at UM7.3 and Um7.4 and all was well. Unfortunately it was only a UM job and not a NEMO one. I've retracted the upgrade so you should be fine to submit again now. Sorry for that.

I'll take a copy of your job to try and figure out what fcm1.5 doesn't like about it.

Cheers,
Ros

comment:2 Changed 9 years ago by ros

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.