@Quazz While I do understand the good intend in this I think it’s very hard to maintain. We see enough issues with trying to make it work in the different distros. Adding the Stream PHP versions will be a nightmare I reckon.

@Sebastian-Roth That’s true, though we could always just backup the current inits on the client side and add a “restore original inits” button.

Reading through some of the forums, I saw the post about updating fog. I updated from 1.5.3 to 1.5.4 and that seems to have resolved the issue.

Thanks

@george1421

https://forums.fogproject.org/topic/9888/remove-your-webroot-redirect-to-fog-when-going-to-rc4/9

This post seems to solve the issue.

@Tom-Elliott Thanks for the very fast assistance! Awesome work as usual.

Found and fixed. Will be available for RC 10. Sorry it was left unknowingly.

@Tom-Elliott Thanks, that would be really helpful to a lot of people I feel. It’s of course possible to setup a putty session or something, but having keymaps in debug mode sounds awesome.

@george1421 I was simplying using mount -t nfs, no other modifiers, so yeah, specifying the protocol is probably what does it.

Still much to learn about Linux and such, heh.

After updating FOG to the latest (seemed to be a pretty big update), it succeeded in deploying it with the task (no idea if it would have done this automatically yet though)

Moved to General and marked as solved.

I’m not going to “hide” this errors as I stated earlier. One, using the @ method to hide/block errors is really really slow (albeit slow is relative here).

Also, hiding errors makes it way too difficult to track an issue. We are using hiding in a few area’s, but only on min/max functions as them throwing an error is not really important as all they typically throw for is the item is not an array or no value was returned in which case our internals already know what to do.

For what it’s worth. I don’t think this is a bug really. The message you’re seeing is coming from an error of another program. I can redirect all the output, but sometimes I think having these bits of information can help more readily than hinder actions.

@Wayne-Workman Yes, force people to set a MySQL root password when installing. But it would still fail if people have MySQL server pre-installed (with empty password)… Other than that I don’t think we have any chance to hook into the auth_socket thing. See if you can find anything related to php and auth_socket

Good catch man! Marking this solved.

@Sebastian-Roth Confirmed.

@Quazz said:

@ch3i I’m literally facepalming right now

^^

@Tom-Elliott Issue resolved after installing gcc and running the installer again, thanks!

@Quazz Found, confirmed, fixed, and pushed.

Thanks for reporting.

@Tom-Elliott Thanks for the quick response. After updating to the latest it was able to start capturing the image and no more errors show up when booting the device.

@Tom-Elliott Thanks for the quick help, can confirm it is fixed.