Posts made by Wayne Workman

Wayne Workman

@barnzy said in HTTP 500: Internal Server Error:

I went to /var/www/fog/lib/fog/config.class.php to find that there was a password that I had set in the setup, once I had cleared this password I checked the mysql connection again and it was working!

Ofcourse that file is editable, but we don’t recommend people to edit it. Set the correct parameters inside of /opt/fog/.fogsettings and then re-run the installer. ELSE, the very-next-time you run the installer, it’ll be broke again because the installer will set the settings inside of /opt/fog/.fogsettings.
See this as a reference: https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

However, kudos to you for using the troubleshooting article in the wiki!

Wayne Workman

@tvigneau Try this: http://x.x.x.x/fog/management where x.x.x.x is your fog server’s IP.

Wayne Workman

@edition What’s the end goal you want to accomplish with fog in this scenario? If it’s just hostnames - and you’re already kicking around the idea of a user identifying themselves as mandatory - make setting the hostname mandatory too and be done with it.

Wayne Workman

I helped a bit with this remotely. I couldn’t figure out what was wrong with the DB in the time I had, so we opted to drop the database and re-run the installer. Then re-created one of the storage nodes and replication is working - so it was something to do with the database.

@Developers I did find an issue with creating a new location for the first time in 1.4.4 release - it appears to be some sort of gui bug that won’t let you create a new location. I’m going to confirm this when I get some time and if it’s a thing, I’ll make a bug thread (unless it’s already known about?).

Wayne Workman

@breit You need to add the disk/space to the correct logical volume. And it’s not that fog can’t see it, it’s that you’ve not added the space to the correct logical volume or you’ve not extended the filesystem yet. After adding the space, you also need to extend that partition’s filesystem to use all available space. All of this is in the Linux OS, nothing to do with fog.

Use this command: df -h
If you don’t see the extra space using that command, then you’re not done. Fog has nothing to do with it.

Wayne Workman

@breit You have to either expand the partition or if you’re using logical volume management, you can add another partition to your volume group. If you search around in the forums, lots of people have done this, and there are tutorials here too. But this isn’t something FOG Specific - this is just Linux disk management.

in either case, ABSOLUTELY snapshot your fog VM before doing this. If it’s not a VM, backup your images and database first!

Wayne Workman

@edition This isn’t really going to work the way you want to do it. FOG uses the MAC address to determine what hostname & other stuff to apply. With users carrying around disks, this just doesn’t work.

Wayne Workman

@szeraax I think this was fixed in the dev branch. Try the latest release candidate and see if the problem goes away? Instructions on doing that are here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

Wayne Workman

@andyb2000 is your plugin in fog’s repo? If it’s useful, you can donate the code - and then we all (as a community) will try to maintain it (or you can still).

Wayne Workman

@greg-plamondon Why do you need to replace it? Sounds like a dumb question but it’s not. Is the file just not there? Is the file incorrect? Does the file have the correct permissions? Does the file have the correct ownership?

Wayne Workman

@developers @moderators There were a ton of failures last night. Not sure why. When I get home this evening I’ll check it out.

Wayne Workman

@julianh Couple things:

Make sure the new card gets the same IP as the old card, same subnet mask.
inside of /opt/fog/.fogsettings update the interface field to the new card’s device name.
inside of web gui -> storage management -> whatever nodes update your interface name.

@george1421 can you think of anything else?

Wayne Workman

@szeraax Also so you’re aware, I vaguely remember a way to pass arguments directly into the snapin itself. This may be cleaner for you, maybe not. Search around in the forums and you’ll probably find it. I think the post is made by the user @joe-schmitt He’s the guy that made the new fog client.

Wayne Workman

@kafluke does your snapin do something that would prevent the client from completing the task? At any rate - all snapin troubleshooting generally should start by examining the fog.log file - generally located at: C:\fog.log and it should just tell you what’s happening.

Wayne Workman

@szeraax This is the link: https://news.fogproject.org/simplified-api-documentation/
Right now, news.fogproject.org is broke. I’ve messaged our senior devs and they should get it fixed relatively quick.

You may also look at this entire thread, as it deals heavily with the API: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines

Wayne Workman

@szeraax said in Is it possible to pass variables to snapins?:

Is this possible?

Yes but not the way you’re thinking. FOG has an API, so from your powershell script just call the API and get the info you need for the host the script is running on.

Wayne Workman

@imagingmaster21 said in Renaming Images:

Also any best practices with this?

Best practices is to name it right the first time
You can change the name in the GUI no problem, but don’t mess with the path unless you actually change the path on the disk too.

Wayne Workman

@george1421 said in 6- to 12-port switch recommendations?:

you might want to consider a multicast stream

George is right. I had this in the back of my mind, but just wanted to address the switch question. Multicast should be used here no matter what switch you buy.

Wayne Workman

@uofadevil said in Image upload & deploy taking a long time:

When I saw that the drive on a freshly imaged laptop had the bitlocker encryption I almost put a hole in the suspended ceiling tile above my chair!

Now that is funny! Thanks for letting us know.

Wayne Workman

@wayne-workman Yes, with fog too. It does fine for an un-managed switch. Also - Cisco is not cheap. This is just a very small unmanaged switch. There are cheaper ones available but they are less quality. Look I’m no salesman I don’t care what switch you buy.

I don’t know how much you know about networking or network devices but I’m going to educate you anyways. You should realize the model I recommended is nothing more than a switch. No wifi, no routing, no vlans, no dns, no dhcp, no no no. Just a switch. This is a small-business grade device that performs a single function. 50 dollars is actually high for an unmanaged switch - crap ones made by other companies go for much less. Like these for example:

So as you can see, 50 bucks is quite high, not cheap.
Also, with all this said - it is what it is. A low-end small-business grade un-managed switch. It will not perform like a 3,100 dollar Cisco Catalyst switch.