@jjacobs Definitely see if you can get the hardware IDs for us. Possibly there is some driver issue that we can figure out and fix. But as well I am asking you again to give the kernel parameter has_usb_nic=1
a try. We have seen USB ethernet adapters that need a reconnect.
Posts made by Sebastian Roth
-
RE: Dell Precision 5530 PXE Boot problem (Maybe the USB cable is bad)
-
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat said in Issues during installation on Debian 9.6 stretch:
Unfortunately due to the location, this machine has to go through a proxy to access the internet, is it possible to skip this step in the installation?
Sure you can manipulate the scripts but you could also just run the installer like this:
./installfog.sh --exitFail
(actually means “don’t exit on failure”)Strange that “no_proxy” wouldn’t properly work. Have you tested to set to
no_proxy="localhost,127.0.0.1,x.x.x.x"
where x.x.x.x is the FOG server IP? -
RE: Active Directory after image deployment not working.
@astrugatch On the one hand side this is a great idea! You just need to keep in mind that if you install FOG with HTTPS the generated certificate will have the IP address as common name (CN) and the current FOG client is not happy connecting to the hostname then. Just something I stumbled upon recently and thought I might share this here just in case.
-
RE: Hosts drop out of Multicast Session on Partition switch
@Critchleyb said in Hosts drop out of Multicast Session on Partition switch:
That explains why some clients were dropping on partition changes, though it is interesting to me that the transfer begun so all of the clients checked in, but then instantly timed out on deploy.
Not exactly sure if that is true. Did you actually see each and every client starting the transfer (partclone window filling up with more text and figures)? If not then I expect those clients to have been to slow to join. I forgot to mention something very important. The MaxWait you set in the FOG settings is only used for the very first partitions. Partition two, three and so on have a timeout of 10! We decided to do this because clients should be pretty much “in sync” deploying the first partition and shouldn’t take long to join the session for the next partition. And on the other hand, let’s say you have one out of 16 clients having a major issue and not being able to join the session. You’d have a long wait delay between every partition if MaxWait of 600 would be used for all partitions.
About the switch and multicast stuff… This is a huge and a bit complex topic. Can’t give you an appropriate answer to that just now. Most switches handle multicast fairly well without config adjustment. The more different components are involved the higher the chance you need to manually adjust configs to make it work properly.
-
RE: Hosts drop out of Multicast Session on Partition switch
@Critchleyb Let’s keep the most obvious question in focus here. Why do some of your clients timeout at all? UPDcast does some re-sending of lost packets and has some wait time (will get to that later) but seems like something within your network (or the clients itself) seem to drop/reject packets or simply can’t keep up with it. As I don’t know your network structure and setup I have no idea what could be causing this. We’d probably need to capture packets using tcpdump on the FOG server or one of the clients (mirror port on the switch) and take a close look at it in Wireshark.
Is it always the same clients dropping out or always different ones? I would advice you to test in smaller groups, e.g. try four in a multicast session and if those work nicely try another batch of four different ones. Note down which ones work fine and which cause problems.
Now about the timeout…
The FOG setting MaxWait is set to 600, however as i understand it, this is the time it will wait to start the session and doesn’t affect the amount of time UDPCast will wait for a host during an active task.
You need to know that every partition is a single UDPcast session. The FOG multicast manager starts a command like this:
udp-sender ... d1p1.img ; udp-sender ...d1p2.img ; ....
- one upd-sender command for each partition running one after the other. You are right the--max-wait
parameter is only telling udp-sender to wait for clients before it starts.Looking through the man page I found an interesting option that you might give a try -
--retries-until-drop
:How many time to send a REQACK until dropping a receiver. Lower retrycounts make “udp-sender” faster to react to crashed receivers, but they also increase the probability of false alerts …
Edit
/var/www/html/fog/lib/service/multicasttask.class.php
, jump to line 491 and add a new line to make it look like this:sprintf(' %s', $duplex), ' --ttl 32', ' --nokbd', ' --nopointopoint', ' --retries-until-drop X', ); $buildcmd = array_values(array_filter($buildcmd));
I couldn’t figure out what the default for this value is. Maybe try a value of 100 and then work your way down. Just an idea. Could also try 5 at first and work your way upwards.
As well I found an interesting comment in the man page about dropped packets:
Be aware that network equipment or the receiver may be droppingpackets because of a bandwidth which is too high. Try limiting itusing “max-bitrate”.
The receiver may also be dropping packets because it cannot write the data to disk fast enough. Use hdparm to optimize disk access onthe receiver. Try playing with the settings in/proc/sys/net/core/rmem_default
and/proc/sys/net/core/rmem_max
, i.e. setting them to a higher value.You could adjust those values on the clients in a
postinitscript
. -
RE: ADK provisioning package settings won't apply after an PXE Boot
@cristianvalente Welcome to the forums. May I ask, how is your question related to the FOG project?
-
RE: Host won't join Domain after admin password change.
@deckerta said in Host won't join Domain after admin password change.:
I realised that the new password was not automatically changed in all my hosts.
Do I have to do that manually?Yeah, as far as I know the global setting will only be used for new hosts to be added but it won’t populate out to all the existing hosts.
Thanks for the log. Here we got the error:
FOG::HostnameChanger Der Index und die Länge müssen sich auf eine Position in der Zeichenfolge beziehen.
Parametername: lengthGerman for:
FOG::HostnameChanger Index and length must refer to a location within the string.
Param name: lengthJust a guess but I think this could be caused by some special character. But we won’t fix the old client so I won’t waste the time to look into it. You might just try different special characters within your password to see if you can figure out which one is causing this. Please keep us posted.
-
RE: Dell Latitude 5590 issues after imaging
@george1421 @jflippen Well I am more than happy to add those things if possible. I don’t have the hardware to test around - only using VMs for testing.
Please open new topics for those issues and give more information and I will look into it.
-
RE: Clients PXE booting from another subnet
@jgiovann said in Clients PXE booting from another subnet:
Perhaps I should step back and not run dnsmasq in the first place, i.e. simplify the setup ? In fact if I stop the dnsmasq service (on the FOG server), I can boot into the FOG menu
Yes, as you seem to have your other DHCP server setup correctly now you don’t need dnsmasq anymore. I don’t think it causes the issue you have right now but better disable the service.
About the issue on registration. On boot the client checks if it can reach the FOG server via HTTP. You can manually do that. Boot up a Windows client in the 192.168.2.0 network and open the FOG web UI URL in the browser. Does it work?
-
RE: Host won't join Domain after admin password change.
@deckerta Maybe upload to some cloud space and post a link here.
-
RE: Dell Latitude 5590 issues after imaging
@lschnider said in Dell Latitude 5590 issues after imaging:
Also i never have been able to get these laptops to pxe boot in UEFI.
What exactly do you mean by that? Please post pictures. As @jflippen mentions you need to use a different iPXE binary to PXE boot UEFI clients -
ipxe.efi
. What is serving DHCP in your network? -
RE: Storage Node: Database Connection Unavailable
@Jeffrey-Boulais Well than probably the database credentials are not correct. Check
/var/www/html/fog/lib/fog/config.class.php
for the DB credentials and then try using those to connect with the command line client:mysql -u root -p
-
RE: Power Management Schedule
@emryz Sorry for the late reply! You should see those in the power management view of the host: web UI -> Hosts -> select one host -> Power Management tab -> scroll down. Maybe check if they are still stored in the database. From the FOG server command line run:
shell> mysql -u root -p Password: ... mysql> use fog; ... mysql> SELECT * FROM powerManagement;
See if that yields any results.
Edit: Corrected my post to not confuse anyone. Got this wrong the first time I looked into it.
-
RE: Dell Latitude 5590 issues after imaging
@lschnider UEFI and legacy BIOS are very different. You can’t just switch from one to the other and hope that it might just work out of the box. If your source image is legacy BIOS, than you need to have something called MBR and a partition marked as active. FOG does capture and deploy the MBR for you - usually doing a fine job. But if you have UEFI there is a UEFI boot manager entry and a boot partition with an executable binary to boot from. As of now FOG will capture and deploy the boot partition for you but won’t do it for the UEFI boot manager entry.
-
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat At the “Backing up database” stage it sends a HTTP web request to the FOG web server asking to deliver a DB backup. This can fail for various reasons. Could be the proxy or other things. You probably want to set
no_proxy=127.0.0.1,x.x.x.x
(whilex.x.x.x
is your FOG server IP).But could be other things as well. First check web server state via
systemctl status apache2
. Running? Then you might check the logs,/var/log/php-fpm*.log
and the error logs mentioned in my signature. -
RE: FOG update to 1.5.5 doesn't allow passphrase entry for SSL/TLS key
@hancocza Can you please take a picture or screenshot of where exactly it hangs?! I still have no clue whatsoever…
-
RE: Host won't join Domain after admin password change.
@deckerta You are right there! Usually it does not take long at all. But as I did not see anything useful in the logs I though of giving it a bit more time.
We don’t actually support such old FOG versions anymore. But I was hoping to be able to give you a quick hint. I myself have not used the old client much and never debugged errors on it. This was before I joined the FOG team. So either someone else has an idea or you might think about updating your server and clients at some point.
-
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat Here we go. This has nothing to do with Debian. Someone messed with the installer scripts.
If this is from github you can reset the local repo to install FOG 1.5.5 like this:
cd /etc/fogproject git reset --hard git pull git checkout master
If the git commands fail, you probably just have an extracted archive there. Then simply leave that stuff or better delete and clone fresh from github:
cd /root git clone https://github.com/FOGproject/fogproject cd fogproject ...
-
RE: Host won't join Domain after admin password change.
@deckerta Nothing about domain join in the log. But we only see it logging for good two minutes. So maybe the join just has not been tried yet. Let it run for at least 20 minutes and post log file again.
-
RE: Issues during installation on Debian 9.6 stretch
@thegiantcat Well that’s interesting. Can you please run
grep -A 10 "configureMySql" /etc/fogproject/bin/lib/common/functions.sh
and post result here.By the way,
/etc
is not exactly a great place to use for keeping this kind of data.