Posts made by salted_cashews
RE: Plan to upgrade from 1.4.4 to the latest stable build, am I headed in the right direction?
@Sebastian-Roth Oh sounds promising. Is there an approximate ETA/date? I’m in no rush but we’re still on 1.4.4 and we just feel it’s time.
Plan to upgrade from 1.4.4 to the latest stable build, am I headed in the right direction?
And I believe all I must do is install git at this point? Is that still the most accurate install guide? Is it possible to install without Git? Is there anything that I should look out for in doing this upgrade other than the stuff stated in the links posted? I’ll make backups of fog via the shell script, snapshot the vm, and backup the dhcpd.conf file (as it is not managed by FoG). Is there anything else?
Thanks as always!
RE: Trying to run the backup script, receive this error.
@Sebastian-Roth Well I feel silly, I should’ve done that to start. Apologies for the stupid question, thanks and once backups are done updates are next on the list.
Trying to run the backup script, receive this error.
The command I ran is displayed at the bottom. The target is a NAS device mounted via the command “sudo mount -t cifs //IPadd/sharename /fogbackups/ -o username=name”. The mount point was created using “sudo mkdir /fogbackups/”.
What I’m trying to do is a full backup of the FOG server, while it still provides DHCP (via isc) to a network location using this script.
RE: Cancellation of a task via the web GUI does not cancel the task and reboot the host.
The client has a SSH server instance running. But you can’t connect to it without setting a password beforehand. So for debugging issues you could schedule a task as debug, start up the client, hit ENTER twice to get to the shell and then set root password and login via SSH to do fancy stuff.
Interesting, I’ve used debug mode before and I love it, I hadn’t thought about trying this though this could prove useful.
Surely old images that were not fully captured and moved to their destination path. But the name of the dir is not random. It’s the MAC address (without colons) of the client you captured the image from. Should be save to delete as long as there is no task running. If you run another capture for the same host this directory will be deleted (and reused) anyway.
Ah! That makes sense and I hadn’t thought about the MAC address.
You might think about updating at some point. As long as things are fine for you with 1.4.4 that’s ok. But if you hope to see something fixed you need to update to the latest version as we don’t backport any changes. Just so you know.
Indeed! We’ve been working on backups and updates but because our FOG server is used so frequently we’ve just not had the downtime available. I’ve ran tests on the newest FOG version, does it come with the option to revert to the old GUI? I know there’s an option in 1.4.4 to change the web interface style.
Cancellation of a task via the web GUI does not cancel the task and reboot the host.
The task is removed from the Active Tasks GUI page, but if I reschedule another task or go to the host’s physically connected display it seems as if the task continues to run. Is there a way to prevent this from happening further, or is simply hard-rebooting the host the only option? Strangely a network scan reveals it’s accessible via SSH and I can get a login prompt when trying to connect over port 22 via SSH. What’s this about?
Also, within the /images/dev/ directory I find what seem to be remnants of old/cancelled tasks. They usually have a random string of characters like so: “/images/dev/b8ac6f942356/”. Are these safe to delete? I understand this is a sort of temporary proxy directory for image capture before completion and transfer to the /images/image-name/ directory.
The FOG version in use is 1.4.4, I apologize for the flurry of questions but appreciate the time taken to answer them.
RE: How does FOG operate at 0% capacity when capturing?
@Wayne-Workman Interesting, I found our problem was the initial setup of the Ubuntu server that hosts FOG was set to allow auto-updates. This will come in handy for future installs, thanks!