Hi,

Try to run again ./installfog.sh.

Regards,
Ch3i.

Just remember, hostnames cannot contain spaces as @jamesb found out.

@Jbob
Thanks Man great job!

While old I figure it pertinent that this is fixed in current svn. Was fixed at some point int he 3300’s.

I’ve changed around the kernels and this error should not be present unless you’re using the 4.0.1 kernel. Hopefully you can agree and atest to this as well.

Based on what I’m seeing and it appearing to show up randomly, I’m going to solve this issue. I think its more likely related to sourceforge and not getting the whole file properly.

@ch3i
Thanks for your help.

Fixed in 3410 ty.

[FONT=arial][COLOR=#222222]3409 fixed the download in IE.[/COLOR][/FONT]

It’s absolutely fixed in 3407

Tom patched this up just now. Something about background processes… I have no idea.

It’s fixed in the latest revision.

[quote=“Tom Elliott, post: 47184, member: 7271”]I don’t think it has anything to do with the client.

pmonstad, try clearing your cache.

I run CentOS as my “testing” system and am not seeing the same issue.[/quote]

You are right, Tom. Clearing the cache solved the problem.

Fixed with svn 3388 thank you!

Just ran into this too. Giving it a poke.

EDIT:
The drive had Windows 10 on it before, and it worked. After running a fast wipe through FOG, I could no longer get any tasks to work (same error as above). More fiddling inbound.

Glad to see it worked. I re-wrote most of the files in v0.7.3 and ended up breaking everything…

Win 7

Heh! You’re going to love this.

Twelve servers later, I check my source document.

I copy and paste my commands into the CLI … I had accidentally highlighted the CR+LF after the last command. So it’s piped into the CLI to appear, invisibly mind you, after the prompt. But it doesn’t actually enter itself at that prompt. So that when I enter “y” then <enter>, it has actually received CR+LF Y <enter> and fails out.

Doh!

Yeap thanks

Ok updated to SVN 3348 still seeing the resize issue it is still intermittent and may or may not affect the same machine twice in a row. I ran a debug task on one that failed and manually ran the resize command as you can see in the pic attached the command not so much fails as sees the partition as already ok even though its still at the deployed size.

[url=“/_imported_xf_attachments/1/1956_2015-05-04 08.24.04.jpg?:”]2015-05-04 08.24.04.jpg[/url]