@steveballantyne said:

I have not modified any php files.
…
I had to do some ugly hacks in several PHP files

Did you mean you didn’t modify php.ini files in your first statement? To be able to help you best we need to know exactly if you use the code provided by us or a modified version (which would be a lot harder to debug as I don’t know your modifications). Possibly installing LAMP did modify the php.ini file? Just a wild guess. Take a look and see if it has those options set (on Ubuntu that should be in /etc/php5/apache2/php.ini - restarting apache is needed if you change php.ini settings).

In the past I have connected to a NAS that has all my images on it. To make this work though…

There are a few articles in the wiki on how to connect NASs to your FOG server. Please give that a shoot!

One thing I wanted to ask — when I am installing the Debian/Ubuntu OS, should I NOT check LAMP server?

It’s not needed but should not hurt either as FOG still tries to install those and therefore would update the packages if needed. Although I have to admit that we cannot actually test all those different setups (like pre-installed LAMP). I have done it with pre-installed LAMP a couple of times in my auto installer setup! So I think this should be fine…

@jayphizzle Use a group, as you said. That’s how I do it.

@Sebastian-Roth Yeah thanks got it now pffft. its not in /var/www/fog but in /var/www/html/fog. Weird thing is these two maps are duplicates. I’m dumb lol.

Thank you everyone

@Sebastian-Roth i will do that
thanks a lot for help 🙂

@Mentaloid said in Multicast from second storage group:

I have already written a bit of a bodge script that checks multicast tasks on my main FOG server, and starts the UDPCAST process on the storage server if the image is found locally (storage group and image = local)

Now you have to share the script.

@moses Groups have never had persistent settings. Whatever you seen before, you’re mistakenly thinking it’s a group - it was not. Maybe it was your browser’s auto-filll, maybe.

Not trying to be harsh, but groups in fog are not persistent - at least from the pending 1.3.0 release and earlier.

2.0 WILL have persistent group settings though.

-edited. replied to wrong person lol.

@couldcareless there’s always a reason and the simplest is usually the truth gotta love occums razor.

Remoted in. Found an error in the schema-page and fixed it. THen found that the DB connections weren’t operating properly and fixed that. All is updated in the codebase too.

@Arrowhead-IT said in Quick Question re Changing Fog 1.2 IP address:

I think that if you just change the ip in the fog settings it might just take care of the rest for you.

This is true for a new install. For existing though, the IPs in the DB are not touched. This is by design.

@Tom-Elliott said in Image upload error:

@Sebastian-Roth We found what the problem was.

Problem was the partition was not “shutdown” properly as Windows 10 allows for “fastbooting”

I found out the ntfs-3g driver can accept a cool parameter in hopes to fix this. Added this to the inits and uploaded. John has confirmed this works for Upload and the device still boots. Just waiting to hear back if a download works after all this.

Well now I’m super curious if it will solve the FastBooting issues I’ve seen and solved with other methods…

@Kaix Then please open the following URL in your browser and post the full output here: http://192.168.1.171/fog/service/ipxe/boot.php?mac=d0:50:99:95:90:86

This has been resolved with latest revisions and some other work by Tom

Thanks Tom and everyone! The update has resolved the error with my kernel download. Not sure what got flubbed up to begin with, but resolved.

CPU seems to be looking more normal as well, after deleting all the hosts and re-adding as they check in.

Can be marked as solved.

Thank you so much.
It’s working.

Hi george1421,

Thanks for the reply. It sounds like FOG is capable of doing what I need if I am able to figure it out, as I’ve no time frame for getting this done I might have a play with it and test some configurations out.

Thanks

Noel

Please upload the client log file.

@kverkiss said in Communication ERROR: operation timed out, could not authenticate, obj error:

@Jbob Thanks for the information!

The problem has been resolved. Thanks for all help.

Ok this worked by recreating the keys. Install worked fine and server seems to be working well.
Only thing I have noticed is several labs worth of Desktops had invalid tokens so I’ve needed to “Reset Encryption Data” to get them talking back to the server again.

Aside from that all is working well 🙂

Thanks again.

The FTP credentials issue is likely the issue with replication as well.

@moses Probably a bug… but update to the latest and recheck if it’s still an issue please.

This is a fine example of a minor bug. This is the type of stuff we warn people about when telling them of FOG Trunk.