Jim. thanks.  Yes something did go awry with installation.  I had done

All the 'is it plugged in' checks you suggest (I had initially had an issue

with the passwordless ssh).  In the end, the problem turned out to be that

I must have been logged in as root at some point during the install because

various directories were owned by root (e.g. the log dir) and could not

be rwx by user ducc.  Chown fixed the problem.

 

-Dan 

 

===========================================================================

Dan,

     I need more information.  The lack of logs tells me something went 

awry with the

     installation.

 

     First off, some 'is it plugged in' checks -

 

    - did you run ducc_post_install error free?

    - if you run check_ducc -c does it show errors, or clean configuration?

    - do you have passwordless ssh set up?

           To verify, ssh to your ducc userid on your centos machine; it 

should work without a

           password prompt.  This is a necessary check even if you only 

have one machine, and

           is the most common cause of this problem  for me (because I 

disable ssh on my

          laptop when I'm not testing DUCC on it and forget!)

Jim

 

On 11/18/14, 3:37 PM, Dan Heinze wrote:

> I've read the "DUCC stuck Waiting for Resources on Amazon..." thread.

> I have a similar problem.  I did my first install of DUCC yesterday on a

> CentOS 6.5 VM with 9GB RAM.  No problems with the install. ./start_ducc -s

> seems to work fine, but when I look at ducc-mon Reservations, I find that

> Job Driver is stuck "Waiting for Resources", I have given it hours, but it

> just stays stuck there.  Also, nothing is being written to the logs... the

> ${DUCC_HOME}/logs directory is empty.  Any help will be appreciated.

> 

> -Dan

> 

 

Reply via email to