We’ll keep track of this on github:
https://github.com/FOGProject/fogproject/issues/328
https://github.com/FOGProject/fos/issues/28

Would you share a screen shot of the error you see on the Dells?
Also what model of Dells do you have issues with and lastly what version of FOG are you using?

Sebastian, thank you. That was it exactly.

@mkeane What do you see in the fog-client log now??

@SBrady I myself have been bitten by web filter issues before on my linux FOG box, so no worries there haha! If you need any additional help or if you run into any other issues, please feel free to open another thread.

nfs addresses have to be written like 192.168.1.2:/nfs (notice the :)

@Sebastian-Roth @george1421 Thank you both. I am most likely eventually going to move to using FOG dhcp so I am not going to go too crazy with this. Was just curious as to if this was a known issue with a workaround. Just using our hq dhcp for the time being for testing.

@Polar-Bear said in Fog 1.5.7 can not capture second image (Debian 10 'Buster'):

For me it is a mystery, on my part I have repeated same steps without any deviation and if earlier it produced described error now it works fine.

We have seen this exact error reported by other users and I am still unable to reproduce the problem and find the real cause of this. Not really sure what to do about it. Seems to be something that does not occur for everyone (obviously) but it’s still around. I even don’t know if it’s something fixed by a reboot or not.

And this time when I was creating new image in web interface I found that now instead of dashes ‘-’ replacing spaces ’ ’ it has removed them!!! Does anybody working on code right now?

I suppose what you are referring to is in management/js/fog/fog.image.js and has not been changed since August 2017 as you see in the github commit history. Which version of FOG did you use before?

@blong10 The fog server really doesn’t do a lot in the imaging process. I would give it at least 4GB of ram to release some of the memory constraints though. The only thing the fog server does is move the image from the network to the disk. It doesn’t process the image at all. Depending on the number of FOG Clients you have a 2 vCPU VM with 4GB of RAM is sufficient.

@doggiebone said in Isolated Network - Operation not supported:

resolv.conf kept being over written but I found an article that sort it out.

This almost sounds like your FOG server’s IP address is being set by dhcp? If that’s the case you need to set it static or you will have problems since the IP address is hard coded into the configuration when the FOG server is installed.

Well done on the rest of getting it setup.

@tbaumann Again: Also make sure SELinux and firewall on the FOG server are disabled and TFTP is running! https://wiki.fogproject.org/wiki/index.php?title=CentOS_7#CentOS_7_pre-config

@RyanBair We have way too little information to be sure but from what I read between the lines I expect this to be an issue with an Ubuntu installation that is being upgraded to FOG 1.5.7 where the database moved from MySQL to MariaDB.

Please try the following and see if that fixes it for you:

sudo -i apt-get remove mariadb-client mariadb-server mv /var/lib/mysql /var/lib/mysql-mariadb cp -a /var/lib/mysql-5.7 /var/lib/mysql apt-get install mysql-client mysql-server systemctl start mysql

See if your images show up again.

@weidongyan said in Cannot log into the fog server management:

I changed the fogproject 's password. After changing it, I cannot log into the Web UI any more.

Again you are mixing up two different things here. Please read my last message very carefully.

@chunter2 I am not sure either. The old client was kind of history already when I joined the project as a developer.

Maybe @Tom-Elliott knows more about this.

@Sebastian-Roth I agree we need a system with a dual nvme drive so we can compare. I have a pdf of what all the short names really mean that I’ll link in too. I’m suspecting the field you pointed to will tell us how many and then there are other fields that will tell use more details about the drive. Also in the nvme list command I’m interested in seeing if the name space field changes if there are more drives as well as the interaction when these disks change ordinal position in respect to what udev assigns them.

@bogle said in Newbie getting started:

Do you guys use sysprep in the process of creating your golden image

Yes you need it, if you want to have one image for multiple hardware platforms.

@psmith10 said in Image deploy error - No Drive Number Passed:

but the Ubuntu image (on the SSD) was not deployed.

Did you see an error message or something else in the output scrolling past that would give us a hint on why? As well you might do a debug deploy and check the messages there.

I found it.

The setting was called “QUICKREG PENDING MAC FILTER”

I took the USB NIC MAC out of there and everything worked again.

@yas1 George is right, FOG is doing DNS queries mostly as part of a routine check to see if hosts are up. If you don’t like this you can disable the whole service in the web UI (FOG Configuration -> FOG Settings -> FOG Linux Service Enabled -> PINGHOSTGLOBALENABLED) or increase the service sleep/inactive time (FOG Configuration -> FOG Settings -> FOG Linux Service Sleep Times -> PINGHOSTSLEEPTIME) or you can take the big hammer and just disable the whole Linux service (systemctl stop FOGPingHosts ; systemctl disable FOGPingHosts).

I think that’s why every device in the database is shown as offline(“unknown”).

While this is related it’s not the fact that FOG cannot resolve it’s name but that it cannot connect to port 445 on your host(s). The word “ping” might be a bit misleading here, it’s not a standard ICMP ping we are doing but a kind of Windows specific check to see if TCP port 445 is available. Both checks definitely have drawbacks but some years ago the FOG devs decided to go the port 445 way and this is still the case today.

If you got hooked up by the idea to use the host status more there is also a plugin you can enable called “host status”.

that worked, I added the other lines from that section also.

Thanks, Moe. make as solved please

use-host-decl-names on; ddns-update-style interim; ignore client-updates; next-server 10.10.2.58; authoritative;