Posts made by Cpasjuste

@Tom-Elliott

Thanks and no problem, we know what we sign for when we use the devel branch I’ll update in a few minutes and let you know.
Edit: i confirm that it’s fixed.

Just a little more information i just found : if i click the “force task to start” button in the “Task Management”, then the deploy task does start. By the way, if you need some testing just send me a mail. I do have a good linux and developement knowledge which may help to debug if needed.

@Tom-Elliott sure, here it is ! So i create a basic task (deploy), then it just loop on the “attempting to check in”. This task did work fine (same machine/image) a few hours ago just before i update to latest git (svn).

Hi,

Just a little message to say that i do have the same problem with SVN 6975 : i have an “attempting to check in” loop when trying to restore an image. It was working fine before i updated (i don’t remember which version i was previously but it was SVN 69xx).

I can confirm that latest svn work fine.

Cool, i’ll test right now. Don’t be sorry as we know what can happend if using svn

Hi, i do have the same problem with svn 2785. I also have this error on installing now :
[CODE] * Configuring Fresh Clam…cp: impossible d’évaluer «…/packages/clamav»: Aucun fichier ou dossier de ce type
chmod: impossible d’accéder à «/opt/fog/clamav»: Aucun fichier ou dossier de ce type
Failed!
[/CODE]

[quote=“Cpasjuste, post: 39741, member: 25902”]Yep i confirm that the deployment is now working, thanks (without re-uploading)[/quote]

Yep i confirm that the deployment is now working, thanks

Sure ! I’m on it, i’ll report tomorw

Edit : i should come more on the forum as i’m on this problem since 3 days now

Hi, i have the same problem. I’m also willing to try the svn version, but how does it will work ? We should still rebuild a new image or should we be able to just update fog server then re-deploy ?

Hi, is there any informations about this problem which occur on two different servers for me ?

Hi,

I can confirm that the second time deployement is always working correctly here.

I do have the same problem. Image (multiple partitions single disk) was done on 1.1. I updated to 1.2 (not sure if it is related) and now I do have this error too. The strange thing is I tried a second time without changing anything but this time it worked. But I did had the problem again this morning, I’ll try to redeploy tomorrow to see if the second deployement is working every times.

Note that the windows 7 image have 2 partition (~100mb boot and large data), only the first one give an error.