I’m struggling somewhat with the format of the API requests

I know I can list all snapin associations with (assume I’m sending correct token headers, just for clarity)

curl  http://localhost/fog/snapinassociation

and this returns

{ "count": 1, "snapinassociations": [ { "id": "6135", "hostID": "52", "snapinID": "2484" } ]

Now, what I want to do is to remove ALL snapins from hostID 52, but I can’t find a way to do this

The closest I’ve come is to do the above query, then parse the output and do

 curl -X DELETE http://localhost/fog/snapinassociation/6135/delete

But this feels clunky and I’m sure I’m missing something fundamental. The URIs aren’t quite making sense in my head, because I know I can create a snapin association with

curl  -X PUT -d '{"snapins":[2484]}' http://localhost/fog/host/52/edit

but I can’t clear them with

curl  -X PUT -d '{"snapins":[]}' http://localhost/fog/host/52/edit

What am I missing?

@Sebastian-Roth Here are some relevant screen grabs. At a guess, I’d say the dreaded T2 security chip might be the cause of the problem, it’s caused us no end of grief in other areas. (This is the fist Mac where I’ve had to user recovery mode to disable Secure Boot before I can boot from the USB stick, for example)

Here’s as much as I could capture of the output from the debug kernel. At least it’s not panicking now, but you can see that ‘sda’ is the USB drive, and there are no other discs. I’ve checked the disc isn’t encrypted and as far as I can tell it’s not in RAID mode.

@Sebastian-Roth I rebuilt the USB boot stick again having upgraded to FOG 1.5.5. here’s what I now get when I try to capture an image.

Note, I’ve already verified that ‘sda’ as far as the boot kernel is concerned, is the USB stick.

Hi,

I’ve been quite successful up to now imaging MacBooks using a USB Boot drive as described here
https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/3. But having recently bought a 2018 Macbook Pro I’m now getting the problem that it doesn’t recognise the built-in HDD at all.

I tried booting to the debug kernel but got a kernel panic. I tried rebuilding my USB boot stick again and now I get Invalid Operating System Version, so I’m going backwards

Can anybody help?

So I set up a new FOG 1.5.4 in a VM, using exactly the same procedure I used to install the live server (1.5.0) and although I still can’t log in to FTP using the fog user on that one, Images do get deleted from the hard drive when I delete them from the Web UI, so I think the FTP thing is not related to the problem. Bug in 1.5.0?

@Quazz I had to change the TFTP password, the others were correct. I have logged in as the fog user, but only since I found this problem. Nothing in the apache error logs at all.

@Sebastian-Roth Yes the password is correct, I can ‘su fog’ from the console using that password. I’m not sure how to debug FTP user issues. The conf file is identical to the one in the wiki. I have a normal user account and I can log in to FTP using that account, but when I try ‘fog’ I get

ftp xxxmyfogserverxxx
Connected to xxxmyfogserverxxx.
220 (vsFTPd 3.0.2)
200 Always in UTF8 mode.
User (xxxmyfogserverxxx:(none)): fog
331 Please specify the password.
Password:
530 Login incorrect.
Login failed.
ftp> Invalid command.
ftp>

Should add I’ve been through the FTP Config Wiki here

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

All of the listed crednetials match (fog user password, settings for storage node and tftp server, /opt/fog/.settings) HOWEVER I cannot log in to the FTP server using that password. Perhaps that’s the problem? How do I set the password on the FTP server?

I’m running a FOG server version 1.5.0 on CentOS7, having followed all the instructions on the FOG Wiki. Most things are working well except for one issue.

When I delete an image or a snapin using the Web UI, the image or snapin is removed from the database and no longer appears in the UI, but the files are left behind on disc. There are no errors in any of the fog logs or the apache log. None at all.

Is it a permission problem?

/opt/fog/snapins
-rwxrwxrwx  1 fog fog     11436711 May  3 06:23 Reaper_Install.zip
drwxrwxrwx. 3 fog apache        54 Jan  8  2018 ssl
-rwxrwxrwx  1 fog fog    303660395 Oct 11 07:03 TestHarness.zip
-rwxrwxrwx  1 fog fog         4667 Oct 11 07:00 Test.zip

/
drwxrwxrwx.  62 fog  root 4096 Oct 10 10:22 images

Everything under /images is owner/group root/root and all have rwxrwxwrx permissions.