cloud_scheduler doesn't start...

[miccloud]

Hi,
I have downloaded and installed cloudscheduler.
After the installation, I have edited my .conf file.
They are here:
http://hermes.pin.unifi.it/cloud_resources.conf
http://hermes.pin.unifi.it/cloud_scheduler.conf

But when I launch cloud_scheduler start I have this error:

Traceback (most recent call last):
File "/usr/local/bin/cloud_scheduler", line 1046, in <module>
main()
File "/usr/local/bin/cloud_scheduler", line 856, in main
log_formatter = logging.Formatter(config.log_format)
AttributeError: 'module' object has no attribute 'log_format'

What may be wrong?

Thank you in advance.
MP

[miccloud]

I forgot to specify that I downloaded it from
http://github.com/hep-gc/cloud-scheduler/tarball/master

Thank you.

On Sep 20, 10:25 pm, miccloud <michelepo...@gmail.com> wrote:
> Hi,
> I have downloaded and installed cloudscheduler.
> After the installation, I have edited my .conf file.

> They are here:http://hermes.pin.unifi.it/cloud_resources.confhttp://hermes.pin.unifi.it/cloud_scheduler.conf

[Patrick Armstrong]

Hmm. Did you have a different version of cloud scheduler installed
previously? It sounds like you have an old version of the
cloudscheduler modules, but a current version of the main cloud
scheduler executable.

What's your output from running "cloud_scheduler --version"?

[miccloud]

Hi,
I have removed this version and installed another version that I
previously used.

If I type cloud_scheduler --version now I have returned
Cloud Scheduler 0.6

It works well (ami are launched), but I have a problem.
When cloud_scheduler try to shutdown the running AMI, I have this
error returned on cloudscheduler.log file:
.....
2010-09-20 23:20:53,935 - ERROR - Couldn't destroy vm because: The
instance 'i-89734ee3' does not have an 'ebs' root device type and
cannot be stopped.
2010-09-20 23:20:53,935 - ERROR - (cleanup) - Destroying VM failed in
attempt to clear uneeded VM. Leaving VM.
.....

What is wrong?
Thanks a lot.

On Sep 20, 11:15 pm, Patrick Armstrong <patri...@uvic.ca> wrote:
> Hmm. Did you have a different version of cloud scheduler installed  
> previously? It sounds like you have an old version of the  
> cloudscheduler modules, but a current version of the main cloud  
> scheduler executable.
>
> What's your output from running "cloud_scheduler --version"?
>
> On 20-Sep-10, at 1:30 PM, miccloud wrote:
>
> > I forgot to specify that I downloaded it from
> >http://github.com/hep-gc/cloud-scheduler/tarball/master
>
> > Thank you.
>
> > On Sep 20, 10:25 pm, miccloud <michelepo...@gmail.com> wrote:
> >> Hi,
> >> I have downloaded and installed cloudscheduler.
> >> After the installation, I have edited my .conf file.

> >> They are here:http://hermes.pin.unifi.it/cloud_resources.confhttp://hermes.pin.unif...

[Patrick Armstrong]

On 20-Sep-10, at 2:22 PM, miccloud wrote:

> Hi,
> I have removed this version and installed another version that I
> previously used.
>
> If I type cloud_scheduler --version now I have returned
> Cloud Scheduler 0.6

Huh. This still sounds like you have old stuff lying around. The
current version is 0.8.

> It works well (ami are launched), but I have a problem.
> When cloud_scheduler try to shutdown the running AMI, I have this
> error returned on cloudscheduler.log file:
> .....
> 2010-09-20 23:20:53,935 - ERROR - Couldn't destroy vm because: The
> instance 'i-89734ee3' does not have an 'ebs' root device type and
> cannot be stopped.
> 2010-09-20 23:20:53,935 - ERROR - (cleanup) - Destroying VM failed in
> attempt to clear uneeded VM. Leaving VM.
> .....
>
> What is wrong?
> Thanks a lot.

Huh. That's really strange. Is there any chance you can make your AMI
public? Or at least, tell me a bit more about it?

--patrick

[miccloud]

Any suggestions?

Thanks in advance.

On Sep 21, 10:21 am, miccloud <michelepo...@gmail.com> wrote:
> Hi,
> this is the AMI: ami-cd0be2a4 .
> I have modified an Ubuntu AMI, installed the program that I need, and
> saved it into a bucket.
> After I have registered it.
>
> Thanks a lot.
> Michele.

[Patrick Armstrong]

On 21-Sep-10, at 1:41 PM, miccloud wrote:

> Any suggestions?

Looks like it was a bug to me. You can try the dev branch on github
now. It should work better for you.

--patrick

[miccloud]

Thanks Patrick.
Can you post me the correct link where I can download it?
Have I to remove the current version? How?
Or I just install the version that I download?

Thanks.

[Patrick Armstrong]

Yeah, if you just install the newer version on top, that should be fine.

The cloud scheduler github project is at http://github.com/hep-gc/cloud-scheduler/
You can look at the dev branch here: http://github.com/hep-gc/cloud-scheduler/tree/dev
And you can get a tarball of this branch here: http://github.com/hep-gc/cloud-scheduler/archives/dev

--patrick

[miccloud]

I have done this step:
1- download cloudscheduler .tar.gz at http://github.com/hep-gc/cloud-scheduler/archives/dev
2- unpacked the tar.gz and launched sudo python setup.py install
3- I have returned this output:

...........
user@server:/opt/hep-gc-cloud-scheduler-c1b4e52$ sudo python setup.py
install
running install
running build
running build_py
creating build
creating build/lib.linux-i686-2.6
creating build/lib.linux-i686-2.6/cloudscheduler
copying cloudscheduler/job_management.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/config.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/info_server.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/cluster_tools.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/cloud_management.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/__init__.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/utilities.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/__version__.py -> build/lib.linux-i686-2.6/
cloudscheduler
copying cloudscheduler/nimbus_xml.py -> build/lib.linux-i686-2.6/
cloudscheduler
creating build/lib.linux-i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorCollector.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorTransferd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorNegotiator.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorStartd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorVMgahp.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorJobRouter.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorDagman.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorDbmsd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorTt.wsdl -> build/lib.linux-i686-2.6/
cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorEventd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorMaster.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorCredd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorGridmanager.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorHad.wsdl -> build/lib.linux-i686-2.6/
cloudscheduler/wsdl
copying cloudscheduler/wsdl/README -> build/lib.linux-i686-2.6/
cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorShadow.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorStartdFactory.wsdl -> build/
lib.linux-i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorLeaseManager.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorKbdd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorStarter.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorSchedd.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorDcskel.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
copying cloudscheduler/wsdl/condorCgahp.wsdl -> build/lib.linux-
i686-2.6/cloudscheduler/wsdl
running build_scripts
creating build/scripts-2.6
copying and adjusting cloud_scheduler -> build/scripts-2.6
copying and adjusting cloud_status -> build/scripts-2.6
changing mode of build/scripts-2.6/cloud_scheduler from 644 to 755
changing mode of build/scripts-2.6/cloud_status from 644 to 755
running install_lib
running install_scripts
copying build/scripts-2.6/cloud_status -> /usr/local/bin
copying build/scripts-2.6/cloud_scheduler -> /usr/local/bin
changing mode of /usr/local/bin/cloud_status to 755
changing mode of /usr/local/bin/cloud_scheduler to 755
running install_egg_info
Writing /usr/local/lib/python2.6/dist-packages/Cloud_Scheduler-0.9.egg-
info
.....

4- So I have edited /etc/cloudsceduler/cloud_resources.con and
cloud_scheduler.conf
They are here:
http://hermes.pin.unifi.it/cloud_scheduler.conf
http://hermes.pin.unifi.it/cloud_resources.conf

5- After I have typed:
sudo cloud_scheduler start

6- But I have returned this errors and cloudscheduler doesn't start:
user@server:/opt/hep-gc-cloud-scheduler-c1b4e52$ sudo cloud_scheduler
start

Traceback (most recent call last):
File "/usr/local/bin/cloud_scheduler", line 1046, in <module>
main()
File "/usr/local/bin/cloud_scheduler", line 856, in main
log_formatter = logging.Formatter(config.log_format)
AttributeError: 'module' object has no attribute 'log_format'

7- This is the output for cloud_scheduler --version:
Cloud Scheduler 0.6

What am I doing wrong?

Thanks a lot.
MP.

On Sep 22, 12:02 am, Patrick Armstrong <patri...@uvic.ca> wrote:
> Yeah, if you just install the newer version on top, that should be fine.
>

> The cloud scheduler github project is athttp://github.com/hep-gc/cloud-scheduler/

[Andre Charbonneau]

Hi,
Maybe you are picking another cloud_scheduler in your PATH by
accident. What do you get when you run the following command? :

which cloud_scheduler

Regards,
Andre

[miccloud]

Hi,
I have typed
which cloud_scheduler
and the output is:
/usr/local/bin/cloud_scheduler

What can I do?
Thanks.

On Sep 22, 4:14 am, Andre Charbonneau <4433...@gmail.com> wrote:
> Hi,
> Maybe you are picking another cloud_scheduler in your PATH by
> accident.  What do you get when you run the following command? :
>
>   which cloud_scheduler
>
> Regards,
>   Andre
>

[miccloud]

I have tried to re-copy cloud_scheduler from /build/scripts-2.6 folder
in /usr/local/bin but I have the same error when I do:
sudo cloud_scheduler start

May have remained some files from the previous version that were not
replaced with the new installation?

Thanks in advance.

[Patrick Armstrong]

Hmm. Weird. My transcript for installing on Ubuntu looked like this:

http://gist.github.com/592458

Which version of Ubuntu are you running? I used 10.4. Are you
installing with sudo? What happens when you run cloud scheduler from
the directory you untarred? (eg do wget http://path/to/
tarball.tar.gz ; tar xzf tarball.tar.gz ; cd tarball ; ./
cloud_scheduler)

Have you tried "sudo python setup.py install --force"? that should
overwrite any previous install.

--patrick

[miccloud]

Ok! I have tried
sudo python setup.py install --force and after few tests it seems to
work.
Tomorrow I will try more test.

Now sudo cloud_scheduler --version take me Cloud Scheduler 0.9.

Another question:
Is +VMKeepAlive working in this version?
How I have to set it? If yes, I have to write Minutes or hours?
And in this mode:
+VMKeepAlive= "xx"
or
+VMKeepAlive= xx ?

I think I remember that it leave AMI's ON for a maximum period of
inactivity, and after shutdown. Is that right?

Thank you so much.
M.P.

On Sep 22, 10:08 pm, Patrick Armstrong <patri...@uvic.ca> wrote:
> Hmm. Weird. My transcript for installing on Ubuntu looked like this:
>
> http://gist.github.com/592458
>
> Which version of Ubuntu are you running? I used 10.4. Are you  
> installing with sudo? What happens when you run cloud scheduler from  

> the directory you untarred? (eg do wgethttp://path/to/

[Michael Paterson]

miccloud wrote:
> Ok! I have tried
> sudo python setup.py install --force and after few tests it seems to
> work.
> Tomorrow I will try more test.
>
> Now sudo cloud_scheduler --version take me Cloud Scheduler 0.9.
>
> Another question:
> Is +VMKeepAlive working in this version?
> How I have to set it? If yes, I have to write Minutes or hours?
>

Minutes

> And in this mode:
> +VMKeepAlive= "xx"
>

In quotes:
ie +VMKeepAlive= "20"

> or
> +VMKeepAlive= xx ?
>
> I think I remember that it leave AMI's ON for a maximum period of
> inactivity, and after shutdown. Is that right?
>

that's right, once the machine becomes 'idle' and stops running jobs it
will stay alive for the specified VMKeepAlive time then shutdown.