Definitely was useful to get access to the machine. That particular partition layout turned out to be not very easy to handle and FOG stumbled! Those DELL partitions are quite an issue. But I think Tom and I have fixed it all. @plegrand Please upgrade to the very latest version. Then re-upload and try deploy again! Please test both of your machines to see if this is really the same issue.
Best posts made by Sebastian Roth
-
RE: FOG restore only one partition
-
RE: Improve documentation
@JJ-Fullmer said in Improve documentation:
Not sure if that’s worth it for the flash videos of the pre 1.0 fog gui.
I don’t think it’s worth it. We need to create a new one anyway.
-
RE: FOG Project call for engagement
@jmeyer said in FOG Project call for engagement:
What kind of documentation is needed ?
We are working on moving all our documentation from the wiki to https://docs.fogproject.org/en/latest/ - lots of work to do. Help is highly appreciated.
Is there still any plan to make a ready to use VM ?
Not from my side because it would mean keeping another part up to date and support it in the forums. But if you are really keen and want to have a go, your call.
-
RE: FOG 1.3 persistent groups
@george1421 I am sorry but I still don’t actually get what you want to achieve with “persistent groups”… Do you mean kind of “persistent settings throughout a group”?
-
RE: Migrate Hosts from 1.2 to dev-trunk
I had a closer look at the code and I think we can add a fairly simple check to see if the imported product key data is already encrypted or not (then encrypt it before writing to database). What do you think about this @Tom-Elliott? I guess we will see more and more people wanting to migrate their 1.2.0 server to a new machine…
diff --git a/packages/web/lib/fog/fogpage.class.php b/packages/web/lib/fog/fogpage.class.php index 7ab7654..2f0cfa8 100644 --- a/packages/web/lib/fog/fogpage.class.php +++ b/packages/web/lib/fog/fogpage.class.php @@ -991,6 +991,13 @@ abstract class FOGPage extends FOGBase { if ($Item->getManager()->exists($data[$iterator])) throw new Exception(sprintf('%s %s: %s',$this->childClass,_('already exists with this name'),$data[$iterator])); foreach (array_keys((array)$this->databaseFields) AS $i => $field) { if ($Item instanceof Host) $i++; + if (isset($field) && $field === 'productKey') { + $test_encryption = $this->aesdecrypt($data[$i]); + if ($test_base64 = base64_decode($data[$i])) { + $data[$i] = $this->aesencrypt($test_base64); + } + elseif (empty($test_encryption) || !mb_detect_encoding($test_encryption,'UTF-8',true)) { + // importated productKey data seams to be not encrypted, so we do it + $data[$i] = $this->aesencrypt($data[$i]); + } + } $Item->set($field,$data[$i],($field == 'password')); } if ($Item instanceof Host) { diff --git a/packages/web/lib/fog/host.class.php b/packages/web/lib/fog/host.class.php index decef5e..2c7841f 100644 --- a/packages/web/lib/fog/host.class.php +++ b/packages/web/lib/fog/host.class.php @@ -19,8 +19,8 @@ class Host extends FOGController { 'ADPassLegacy' => 'hostADPassLegacy', 'productKey' => 'hostProductKey', 'printerLevel' => 'hostPrinterLevel', - 'kernel' => 'hostKernel', 'kernelArgs' => 'hostKernelArgs', + 'kernel' => 'hostKernel', 'kernelDevice' => 'hostDevice', 'pending' => 'hostPending', 'pub_key' => 'hostPubKey',
The change in host.class.php is fixing a minor bug that I found while testing this. hostKernel and hostKernelArgs are in reverse order in the database. Usually the wrong order in that array does not cause any trouble I suppose. But when you create your own CSV file according to the DB structure and try to import you’ll end up with kernel and kernelArgs being “swapped”.
@jayphizzle The exported CSV from FOG 1.2.0 was kind of minimalistic (only
"mac", "name", "ip", "description", "imageID"
). So you need to generate a proper CSV from your 1.2.0 database via mysql select statement. Try this via phpmyadmin or mysql cli:SELECT hostMAC.hmMAC,hosts.hostName,hosts.hostDesc,hosts.hostIP,hosts.hostImage,hosts.hostBuilding,hosts.hostCreateDate,hosts.hostLastDeploy,hosts.hostCreateBy,hosts.hostUseAD,hosts.hostADDomain,hosts.hostADOU,hosts.hostADUser,"",hosts.hostADPass,hosts.hostProductKey,hosts.hostPrinterLevel,hosts.hostKernelArgs,hosts.hostKernel INTO OUTFILE '/tmp/result.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' FROM hostMAC,hosts WHERE hostMAC.hmHostID=hosts.hostID;
Examine the SQL statement carefully and you’ll see that it dumps the results into the file /tmp/results.csv on your server.
#wiki Marking this to go to the wiki at some point because I am sure we’ll see people moving from 1.2.0 as soon as a new version is officially released! Keeping my fingers crossed that most people will migrate by installing “on top” where no export/import of the database is needed!!
-
RE: Improve documentation
@Jurgen-Goedbloed said in Improve documentation:
Can we agree on the starting point that, when coping things from the wiki to the new documentation that we will only focus on the current (1.5.9) version? So all parts that refer to old versions will not be copied and that we will also use screenshots of the current version. I think this will help a lot in understanding and recognition for new Fog users.
Absolutely I would say! We encourage people to update to the latest official version over and over in the forums. So it’s fair enough to only provide documentation for that as well.
-
RE: ipxe issue 3c126
@kortnor chainloading boot.php is failing because the kind of minimalistic iPXE that comes with VirtualBox does not include things like
cpuid
andcolor
that we use in our iPXE scripts. But as we can see in the displayed banner on the screenshot it should have TFTP support (I am sure it has!).From the iPXE source code to me this looks like the TFTP server is sending back an answer (so this is not a network connection issue) but the code sent back is what makes iPXE unhappy! Is this the TFTP server installed by the FOG install script or do you use a different one?
Add dumping network traffic to the client VM (https://www.virtualbox.org/wiki/Network_tips) and start it up. After you see the error in the client VM shut it down. Please upload that PCAP file to the forum here and I’ll have a look what TFTP error code this is.
-
RE: Improve documentation
The theme used by jupyter is called pydata-sphinx-theme. The more I look at it the more I like it. What do you think @JJ-Fullmer @Jurgen-Goedbloed @Wayne-Workman?
-
RE: Mac OS X resizeable disk support
@PioDer AFAIK there is no open source tool to resize HFP+ filesystems (like
resize2fs
that we use to resize EXT filesystems). I don’t think we will be able to port OS Xdiskutil
to linux any time soon. Please let us know if you know other tools that can resize HFS+!Are you able to image your OS X clients with non-resizable images? Why do you need resizable? You could just image as non-resizable and expand using
diskutil
in Mac OS X after cloning… -
RE: Apache Error on Trunk 4991
I am sure Tom will take care of this in a minute… Sounds like a code issue.
-
RE: NVMe madness
@Fog_Newb Finally found some time to work on this. At first I was hoping to come up with kind of a logic that would detect disk size and select the correct disk according to this. As I said we have this working for images set to multiple disk type.
But half way into it I figured that my solution would only work for deployments where we have the size information from capturing beforehand. But this wouldn’t solve the issue of NVMe drives switching position on capturing in the first place.
The only way we can solve this is by telling FOS to look for a disk of certain size when running a task. So far we only allowed the host setting Host Primary Disk to name a Linux device file to use - e.g.
/dev/nvme0n1
. But now I added the functionality for you to specify disk size (byte count) using this same field.So you just need to do is download the modified init.xz and put into
/var/www/html/fog/service/ipxe/
directory (rename the original file beforehand) and set Host Primary Disk to an integer value matching exactly the byte count of the disk (value you get fromblockdev --getsize64 /dev/...
).Please give it a try and let me knwo what you think,
-
RE: Mount and Extract files from images
Hmmmmm. I will give this a try on Debian over the weekend… Will let you know. Thanks fro testing and reporting so far.
-
RE: Multicast Session can't be cancelled?
I am pretty sure this is solved in current trunk! Marking solved.
-
RE: FOG API Question
@Chris-Whiteley Enabled the FOG API both in FOG Configuration as well as user’s settings? Using both API tokens?
-
Custom host initrd setting
While I am not saying that we need this I am wondering why it is not possibly to specify a custom initrd image within the host settings but only a custom kernel? Does it take much to add custom initrd setting?
-
RE: Unable to Fog Image pulled from Large Size HDD to Small Size HDD
@chetansays Please post the contents of /images/<img-name>/d1.partitions here in the forum. As well it would be helpful if you could post a picture and/or the exact text of the error message you see! We have worked on the resizable image scripts and you might want to upgrade to the very latest version to see if it works for you.
-
RE: Improve documentation
@Jurgen-Goedbloed @JJ-Fullmer We have the DNS entry now. https://docs.fogproject.org/en/latest/
-
RE: Select multiple partition to deploy/capture
@ch3i @Thiago Be aware, this is untested and I am not absolutely sure if it works!! … but as far as I can remember you should be able to capture the image as normal, then edit your image definition in the FOG web gui (set to the single partition you want to deploy) and run a deploy job. There was an issue with deploying single partitions some time ago but I am pretty sure Tom and I have fixed this. Please give it a try and let us know. Keep in mind to change back the image definition to full disk when you are done with deploying the single partition because on the next upload it would then upload the single partition only…
-
RE: High CPU usage from multiple httpd processes version 5800
@Kiweegie I vaguely remember @Wayne-Workman having seen a fog user password change after running the installer script at some point. Maybe this is related? https://forums.fogproject.org/topic/6649/storage-node-installation-resets-local-fog-user-s-password-to-something-wrong
Cannot actually find the commit that was made to fix this but from what Tom says I thought this was fixed somewhere around version 63xx. Maybe not? Please keep an eye on this and let us know!