[Users] Fwd: Re: Help: Problem uploading the ISO file on engine

[David Li]

The ovirt-iso-uploader log only has one line:

2014-01-13 19:08:05::INFO::engine-iso-uploader::1067::root:: Start uploading CentOS-6.4-x86_64-netinstall.iso 


This is version 3.3.2-1.el6

My immediate question is how I can kill the upload process without rebooting the engine box? So I can try to reproduce the problem again.  
It's probably in a "sleep but not interrupt" state. None of the usual kill -9 commands worked. My NFS ISO domain has also been put in the "inactive" state most likely due to this problem. 


Thanks.

David


----- Original Message -----
> From: Sandro Bonazzola <sbonazzo at redhat.com>
> To: david_li at sbcglobal.net
> Cc: 
> Sent: Tuesday, January 14, 2014 2:05 AM
> Subject: Fwd: Re: [Users] Help: Problem uploading the ISO file on engine
> 
> 
> 
> 
> -------- Messaggio originale --------
> Oggetto: Re: [Users] Help: Problem uploading the ISO file on engine
> Data: Tue, 14 Jan 2014 11:04:37 +0100
> Mittente: Sandro Bonazzola <sbonazzo at redhat.com>
> A: Sven Kieske <S.Kieske at mittwald.de>,  "users at ovirt.org" 
> <users at ovirt.org>
> 
> Il 14/01/2014 08:32, Sven Kieske ha scritto:
>>  Hi,
>> 
>>  which engine version?
>>  anything in engine.log?
> 
> +1
> 
>>  (I honestly don't know if there's any logging
>>  for the iso uploader?).
> 
> yes there is, in /var/log/ovirt-iso-uploader dir.
> 
>> 
>>  I never encountered such a problem.
> 
> Same here. Can you reproduce using -v flag when running iso uploader?
> 
> 
> 
>> 
>>  HTH
>> 
>>  Am 13.01.2014 20:45, schrieb David Li:
>>>  Hi,
>>> 
>>>  I copied a Centos netinstall ISO file to a directory on my engine 
> machine to get ready for installation. Then I used 
>>> 
>>>  engine-iso-uploader upload -i ISO_DOMAIN 
> CentOS-6.4-x86_64-netinstall.iso 
>>> 
>>>  to upload or put it into the proper ISO domain directory. However this 
> command now totally stuck. Even kill -9 won't be able to do anything. 
> Moreover now my ISO domain in the DC seems dead or becomes inactive too. 
>>> 
>>>  What happened? Is there any way to recover from this point without 
> rebooting everything? 
>> 
> 
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>