@astrugatch Yes, as it’s signed by the CA, it shouldn’t have any issues. Though you may need to have it initially recreate the private cert as it likely created it using the IP. Just a good to know thing for the future. (Particularly on fresh installs.) It would mean, however, that you’d have to update all your clients which could prove problematic in general.

Could be simpler just to remove the IP checking during fresh install. Or, maybe we could add a Hostname item as an inline option (or add to the /opt/fog/.fogsettings file of course) the builds a cert using the IP and allows an alternate name within the cert using the hostname.

Of course this is just thoughts being spewed out sorry.

@thegiantcat What’s the installer’s error log look like?

It should show us more information as to why backing up is failing.

I am a little confused too. Is your FOG Server also your PROXY machine?

What version of FOG are you running?

Have you tried troubleshooting FTP information?
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@fogger1 The links that are provided are the init’s in the most current state we have. The good thing is now that the init’s are separated from the main elements of FOG, and changes aren’t quite as frequent as the main elements, the init’s being provided should work with any 1.5.x version of FOG and even the 1.6 as the backend “functional” pieces aren’t being modified at the same scale between the two versions. So they’re not provided for 1.5.4, they’re whatever the most current version is. The init’s are not labelled in the same fashion as our normal releases which is why it’s important for the distinction here. The init’s in the links are what are provided for 1.5.5 and 1.5.5.2 (which is the most current dev-branch version).

@Sebastian-Roth The problem with the password was the complexity requirements that were enabled.

It would require 3 of the 4 main common things, but the first/last character of the password did not count toward the system’s configured password complexity requirements.

I used one that it suggested and updated the fields where needed.

This is not a common thing of course.

The other part of the problem was the old ‘two versions’ of FOG installed on the machine.

Essentially both /var/www/fog and /var/www/html/fog were individual installations. My guess is it was using the /var/www/html/fog version for display, but the fog configuration page was coming from the link.

Moved both the /var/www/fog/ and /var/www/html/fog folders and ran the installer and all completed properly.

Tested the use of FOG Configuration and updated the passwords where needed. All was working properly now.

@Sebastian-Roth no there’s no option to use the old style GUI. Although theming should work but would take a lot of effort.

@kboutelle There’s the problem.

You have /images and /images2 mounting to the same File system ID. I believe nfs will use the 1st instance (in your case it’s mounting /images rather than your new share /images2.

Edit the /etc/exports file.

For your /images and /images/dev lines, prepend them with a # symbol. This will comment those lines.

That, or change the fsid of the /images2 and /images2/dev to have 2 and 3 respectively.

Then restart the nfs service, systemctl restart nfsd

@Sebastian-Roth everything I’ve found on this issue refers to using the disks uuid to identify which one to apply it to. That doesn’t help us much as every drive on a system would have its own uuid. So how do we identify which is which? I know it doesn’t help anything. Everything from Serial to Pata and nvme aren’t guaranteed to be a persistent naming scheme for Linux. Luckily SATA and PATA seem to follow the channel pattern on how they’re connected and named. With NVME being on a pcie channel this makes enumeration dependent on how fast a disk feels like revealing itself to the system.

I know I seem distant and all these days, but this really sounds like a 4K advanced disk problem.

What makes me say this?

The nvme was a 512gb disk, I assume and it’s just a guesstimate. The sata disk is also a 512gb disk, guesstimate.

But look at the layout variances in reported disk size. One shows as about 465GB (sda) while the nvme shows at 477GB (nvme).

The oversized for each partition would seem, too me, to come from calculating disk sectors at a larger size than the actual disk can use.

I very well could be wrong of course and welcome any suggestions.

@sebastian-Roth I think we need to try figuring out a suitable mechanism to upscale to 4K only (less needed as most advanced disks will allow reappropiation of the sectors into 512B) as well as downscale 4K back to 512B. I don’t know of a good approach to do such a thing yet but it seems more and more people are looking to image cross spectrum.

@Sebastian-Roth I think it’s worth it. I can’t imagine a scenario where you’d be putting an image on an iscsi target.

@nehsa said in Create scheduledtask via POST to API:

“minute”: “30”,
“hour”: “5”,
“dayOfMonth”: “",
“month”: "”,
“dayOfWeek”: “*”,

This all depends on the type of task this is to do:

The json elements that you can set:

{
    "name": 'Some Name',  // Optional
    "description": 'Some Description', // Optional
    "type": "C", // C = Cron, S = Single
    "taskType": 1, // ID of the task type, 1 = deploy, 2 = capture, 3 = debug do not use this one, 4 = memtest, 5 = test disk, 6 = disk surface test, 7 = recover, 8 = multicast, 10 = inventory, 11 = password reset, 12 = all snapins, 13 = single snapin, 14 = wake up, 15 = debug deploy, 16 = debug capture, 17 = deploy no snapins, 18 = fast wipe, 19 = normal wipe, 20 = full wipe
    "minute": 30,
    "hour": 5,
    "dayOfMonth": '*',
    "month": '*',
    "dayOfWeek": '*',
    "isGroupTask": 0, // 0 = host only, 1 = group task
    "hostID": 1, // If is grouptask is 1 this will be the group id, otherwise the relevant hostID
    "shutdown": 0, // 0 = restart, 1 = shutdown
    "other1": "",
    "other2": "-1", // Snapins either the id of the individual snapin, or -1 for all.
    "other3": "fog", // The username who created the task
    "other4": true, // Wake On Lan?
    "other5": "",
    "scheduleTime": "", // Only used for delayed time in which case you will need a valid unix timestamp in the future.
    "isActive": 1, // 0 or false would mean the task is not active currently.
    "imageID": 1 // The image ID in the case it's an imaging task. Can be any imageID you want.
}

@Critchleyb

1.5.X and even 1.6.X are based on bootstrap. Some of the elements for fine tuning are defined in the default/fog.css file, but majority of the items are generic and using the bootstrap information directly.

If you need to customize particular things, and you know the class/ids you need to modify, you’ll want to edit the default/fog.css (though for your own environment I’d recommend creating your own custom something like critchleyb/fog.css and make your changes there.

@MarkG Apple may not have a GUI interface to display the hardware IDs.

http://teczd.com/2015/09/23/osx-get-system-info-from-command-line/

In particular: SPNVMeDataType

@mparlette you can set the location inline with
storageLocation=“/home/images” ./installfog.sh -y

@george1421 wont

@Rebelman said in Fog Menu loop:

s

What’s the output of mysql statement:

SELECT settingKey,settingValue FROM globalSettings WHERE settingKey IN ('FOG_EFI_BOOT_EXIT_TYPE','FOG_KERNEL_ARGS','FOG_KERNEL_DEBUG','FOG_KERNEL_LOGLEVEL','FOG_KERNEL_RAMDISK_SIZE','FOG_KEYMAP','FOG_KEY_SEQUENCE','FOG_MEMTEST_KERNEL','FOG_PXE_BOOT_IMAGE','FOG_PXE_BOOT_IMAGE_32','FOG_PXE_HIDDENMENU_TIMEOUT','FOG_PXE_MENU_HIDDEN','FOG_PXE_MENU_TIMEOUT','FOG_TFTP_PXE_KERNEL','FOG_TFTP_PXE_KERNEL_32') ORDER BY settingKey;

There should be 15 values returned, and I’m suspecting one of these keys is missing. Please copy and paste the statement into your shell to get the return, then copy and paste the return values into a posting so we can see what’s going on a little easier.

To make things easier to see (and for us to easily view the items more directly) the values in order would be something like:

1. FOG_EFI_BOOT_EXIT_TYPE
2. FOG_KERNEL_ARGS
3. FOG_KERNEL_DEBUG
4. FOG_KERNEL_LOGLEVEL
5. FOG_KERNEL_RAMDISK_SIZE
6. FOG_KEYMAP
7. FOG_KEY_SEQUENCE
8. FOG_MEMTEST_KERNEL
9. FOG_PXE_BOOT_IMAGE
10. FOG_PXE_BOOT_IMAGE_32
11. FOG_PXE_HIDDENMENU_TIMEOUT
12. FOG_PXE_MENU_HIDDEN
13. FOG_PXE_MENU_TIMEOUT
14. FOG_TFTP_PXE_KERNEL
15. FOG_TFTP_PXE_KERNEL_32

I suspect something between 1-12 is actually missing, causing the MENU_TIMEOUT value to to be put in place of the MENU_HIDDEN value (timeout is usually defaulted to 3 - 5 seconds) which is triggering the boot menu to think it is a hidden item.

@george1421 I’m using ipxe.pxe as the boot file. Not replacing the version VB’s NIC’s are set too. (Though I imagine that would work well too.)

@salted_cashews and @Sebastian-Roth

I believe the problem is coming from the second -d

Particularly in the naming of the image, it appears to be doing:

zstdmt -d /images/PPS_v9.0R2 Then get’s a second -d from the -dev_CentOS/d1p1.image

So it’s literally, I think, doing:

zstdmt -d ev_CentOS/d1p1.img

Does this make sense?

I think the - in the image name is causing issues parsing into the zstdmt command. The reason it doesn’t impact the Ciara_CentOS-BASEmk3 is because, likely, there is no argument for -B is it just uses it like a normal string.

Maybe we need to add some quoting to the scripting?

It can open .gz, but you’re right. By default, we use XZ compression for the init’s.

Even more odd is the fog/images/init.gz being the configuration path from the old 0.32 versions (and earlier) when it referenced the init from /tftpboot/fog/images/init.gz

Did you follow configuration from a very old tutorial?

@Sebastian-Roth If my memory serves me correctly we did encode all of this for a little while, but too my knowledge we’ve moved away from encoding special characters in preference of using proper sanitization of inputs into the database. That’s not to say everything was fixed, but I’m pretty sure we moved away from this particularly because the & would get encoded as &amp, then the & in the &amp would get encoded, and so on and so forth.