Hi Wilken,
 
even though your screenshots are not being displayed when send via the mailing 
list,
i am guessing that these are snapshots of rather large volumes (>100GB) ?
 
Are you using RBD on Ceph as your primary storage?
I remember from conversations with Swen that you might use some other storage.
 
Anyways, it might be the case that image file conversion to qcow2 format/file 
is taking place and the process within Cloudstack is timing out, while the 
process itself is still running and finishing.
 
This will result in an error in Cloudstack (timeout while waiting) but the 
snapshot still to finish correctly after longer time and be ready to use.
 
At least thats the case for RBD on Ceph:
https://github.com/apache/cloudstack/issues/9408
https://github.com/apache/cloudstack/issues/5660
 
But my guess could be wrong not seeing the images and not exactly knowing which 
primary storage you are using.
 
Best regards,
Stephan
 

> W. Verleger - proIO GmbH <w.verle...@proio.com> hat am 12.11.2024 14:19 CET 
> geschrieben:
>  
>  
> 
> Hi,
> 
>  
> 
> We are receiving a lot of event errors while  volume snapshot creation (once 
> per day!) even though the volume snapshots will be created eventually.
> 
>  
> 
>  
> 
> I can see the volume snapshot in ACS:
> 
>  
> 
> And in the secondary storage:
> 
>  
> 
> I can not find any log entries except for api log showing the same as in the 
> ACS event dashboard.
> 
> Also wondering about the time zone different. Everything (server and 
> recurring backup time) is set to Europe/Berlin / CET.
> 
>  
> 
> Are there any known issues regarding this in 4.19.1.2?
> 
> Is there any way to troubleshoot this?
> 
>  
> 
> Thank you!
> 
> 
> 
> 
> ---------------------------------------------
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
> 
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. 
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben, 
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet. 
> 
> This e-mail may contain confidential and/or privileged information. 
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify 
> the sender immediately and destroy this e-mail.  
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden. 
> 
> 

Reply via email to