Topics created by dylan123

@dylan123 Reading a bit more about the apparmor stuff I found this: https://stackoverflow.com/a/49583958

I read in another SO thread comment that the apparmor=“DENIED” message probably isn’t the reason that MySQL (or in my case MariaDB) wasn’t starting, as it’s only a warning.

Confirmed by this bug report:

On the affected system, there was no noticeable impact (yet?) other than the denials, so I’d say it’s low impact.

Spinning up a VM with Ubuntu 18.04 I saw that quite true it has those log messages in /var/log/syslog on my VM as well but the DB is running perfectly fine. So just for the records: Those apparmor=“DENIED” message don’t cause an impact on the DB and can be ignored.

Check all the information George and Daniel posted as well as my suggestion on the mysql logs.

@george1421 it worked
finally it was a wrong placed host kernel that caused the trouble …
Thanks for the good help, we keep enjoying your system and appreciate your service!great!

You also have to ask your self “What are the risks of having nfs on your fog server configured this way?” Is the data contained in your images a high value target? Do they conain PII or PCI or regulated data? How could the data contained in these multi-gigabyte images be used against your company or for financial gains of the hackers?

Yes the fog server’s nfs shares are a bit open. You can restrict access with NFS v3 to a range or subnet of IP addresses. NFSv4 could be implemented but other than ticking off a check box what is the real value of the activity? What are you trying to protect?

I can’t answer these questions for you, its based on what your company is trying to protect and the risks of doing something vs nothing.

@dylan123 I think this is very hard to debug not sitting right in front of the machines myself. You need to know that everything is this chain could be the bottle neck. So the best you can do is cross test things to hopefully nail it down. That means testing at least on three different clients in the exact same scenario (same network switch, no other things running over the network or on the FOG server at the same time). See if they all behave the same. If so, then you need to look into network or FOG server to find the issue. If they all go different speeds, then note down the numbers (start, end, average speed), redo the test again and see what you get. Possibly you can nail down one host that is different than the other two. Do a badblocks and memtest on that machine. As well see if that one has slightly different hardware.

Some of those features are under the compatibility test option. There is the advanced menu, I’m not sure what’s in it, but you can have it show up for all hosts by toggling that option in the settings.

@Tom-Elliott said in Single disk, resizable - failed to set disk guid:

@dylan123 So the issue, if you’d like it fixed for now (I’ll relook at this code though).

Can you open the file, and add the /dev/sda components?

In other words make the file read as:

/dev/nvme0n1 dcfabb9e-4507-415e-b9a9-e437017df63b /dev/nvme0n1p1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590 /dev/nvme0n1p2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988 3:2de320a9-99b6-4191-aeeb-1c15e96fae1d /dev/nvme0n1p4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

Hey @Tom Elliott, tried the above code and that worked perfectly!

Will download the new init’s as suggested and see if that works also, thanks.

@Joe-Schmitt said in Adding Machine to Domain using Active Directory:

@dylan123 said in Adding Machine to Domain using Active Directory:

So I’ve attempted to deploy an image onto the domain

Images should never be pre-joined to the domain, Active Directory is fundamentally incompatible with handling that scenario. Either use setupcomplete.cmd in sysprep to join the domain, or the FOG Client.

Yeah wasn’t the first thing I tried, more was testing it just to see if it made a difference.

Wasn’t aware the FOG Client was required to make the active directory feature work. Have since installed and tested, can confirm it worked.

Thanks for your help Joe.

@Wayne-Workman said in Surface 3 - Unable to obtain DHCP:

@dylan123 I added the link to your solution post in the wiki. One day I (or someone else) can go through it all and make a formal article.

Sounds great, happy to help if required in more detailed instructions if needed 🙂

@Tom-Elliott said in Surface 3 - Unable to obtain DHCP:

@dylan123 So if you added has_usb_nic=1 to the FOG_KERNEL_ARGS field in fog settings, this would be the reason you “didn’t have to add it back”. This “flag” doesn’t automatically set itself, so the only way to have it “preset” is if you entered this in FOG Configuration Page->FOG Settings->Expand All->FOG_KERNEL_ARGS

Think I was half correct with what I said, I must have had the host with the mac still added. Interestingly though, I’ve found I don’t need that command for the surface 3s.

So basically in the config > fog settings > fog_kernel_args section, that’s blank. In my host section, it only contains two laptops that are both the HP models I’ve been previously working with, no surfaces. I can then turn on any surface 3 and it will boot to the fog menu where I can either quick register it (not much point) or deploy the surface 3 image I took yesterday.
*I did a quick register of the surface 3 given I thought it automatically added the has_usb_nic=1 to the arg section however it didn’t. It still added the surface to my list of hosts though I then tried with a surface 4, it booted to the fog section but when I selected ‘quick register’ I got then ‘unable to obtain DHCP address’ type error message which suggests for the surface 4, I need to have the has_usb_nic=1 argument.

Just thought it was interesting how that worked, probably come across that though with other people that have been trying to image surfaces.

Glad I took two different kind of images.

Single disk clone - Went through the process, on boot the file I created was still there, the only difference was it had uninstalled a lot of the drivers such as the NIC…

Multiple partition clone - Seems to have worked!

Thanks again for the help guys, much appreciated

@Sebastian-Roth - it is - ill start a different thread tho as it doesnt look the same to you
0_1486081090166_fog_error.JPG