FOG Problems

• T

  UNSOLVED New Fog Server - /images location
  • Technolust  

  16
  0
  Votes
  16
  Posts
  33
  Views

  T

  @Sebastian-Roth That’s what I figured. Thank you!!!
• T

  SOLVED PXE Boot to different VLAN
  • Technolust  

  9
  0
  Votes
  9
  Posts
  56
  Views

  

  @Technolust FWIW, since you have a Windows 2012 DHCP server you might want to look over this wiki page if you need to support both uefi and bios systems in your environment: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
• 

  UNSOLVED Delayed Tasks don't work
  • Lenain  

  4
  0
  Votes
  4
  Posts
  35
  Views

  

  Hello @Sebastian-Roth, Thanks to take time for me, in apache2 error logs I have this but I don’t know if it’s linked: This error is after I create the delayed task. I’v tried delayed tasks (deploy and wake up) in the same day they are create and they work, I have create others for tomorrow. “What exactly is happening when you try”: The delayed tasks stay in “Scheduled Tasks” with a “yes” in “active” column. “Do you see an empty page or an error or what”: No error, no empty page. Just the task don’t start. I will tell you more tomorrow with the result of delayed tasks that I have create today.
• R

  Mobile users at FOG version 1.5.5
  • ragnurenson  

  3
  0
  Votes
  3
  Posts
  14
  Views

  R

  thx! I try this way.
• J

  UNSOLVED Web interface slowdown and FOG Client authentication issues
  • j_d  

  6
  0
  Votes
  6
  Posts
  64
  Views

  S

  @j_d said in Web interface slowdown and FOG Client authentication issues: So worst case, I re-image all the ones with authentication errors still. As I said, doing a “Reset Encryption Data” for all your hosts and they should’ve all synced back in. But now that you went the other way round I don’t think it’s still worth it. However, I noticed during the imaging, the web interface was once again very slow and giving me 503 errors. Completely fine after it finished. How many clients did you image? Multicast or unicast? This might be interesting to investigate some more but it’s probably not easy to figure out. That said, I have worked on improving “FOG speed” since 1.5.5 was released. So it would be interesting to see if those changes would help in your situation. Take a snapshot of your Hyper-V VM, pull the latest changes from github, checkout dev-branch and re-run the installer: cd /path/to/fogproject/ git pull git checkout dev-branch cd bin/ ./installfog.sh -y This will install PHP version 7.2 as well (CentOS still had PHP 5.6 in FOG version 1.5.5) which speeds up the whole web UI too. So code changes and PHP 7.2 should make a major difference for you.
• O

  UNSOLVED WOL in Task not working, but manually
  • okta  

  5
  0
  Votes
  5
  Posts
  29
  Views

  S

  @okta I just tested and for me WOL is working in each and every case (task with checked WOL, advanced task to wake up and wakeEmUp URL). I always see Magic Packets being sent out. FOG sends a batch of four Magic Packets. See the following picture of a Wireshark packet capture. When you schedule a normal or WOL task, do you see any errors in the apache error log? See my signature on where you find the logs.
• M

  UNSOLVED Unable to locate image store
  • MoonDancer  

  5
  0
  Votes
  5
  Posts
  17
  Views

  S

  @MoonDancer said in Unable to locate image store: error invalid Login Can you post a picture of that error? Have you ever logged in (or more important changed the password) of the Linux system account called fog? Please run grep -A1 -e FTP_PASS -e password /var/www/html/fog/lib/fog/config.class.php /opt/fog/.fogsettings on your FOG server console. It should print a password three times. Don’t post that here, just check if they all match up. If they do then see if the password really works. Go to another machine within your network (Windows client will do), open a command prompt and try to connect to your server via FTP using that password (I know it’s quite long!): C:\Windows\System32> ftp 10.113.2.169 Connected to 10.113.2.169. 220 (vsFTPd 3.0.3) Name (10.113.2.169:user): fog 331 Please specify the password. Password: 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> quit 221 Goodbye. I’m wondering if a FOG update would resolve my issues. Yes it actually might solve your issue. But as we don’t really know what’s exactly wrong it’s just like shooting in darkness. Might help but could cause other issues as well. Let’s see what you get from the stuff posted above and in the other thread and take it from there.
• M

  UNSOLVED Canceling Tasks
  • MoonDancer  

  12
  0
  Votes
  12
  Posts
  45
  Views

  S

  @MoonDancer Ok, I am a bit relieved. From what you where saying at first I thought you might have a very old setup. CentOS 7.5 is fairly new and a good Linux OS. Don’t run the FOG installer yet. We’ll guide you through that later on. Possible your FOG server was setup to run in a separated network without internet connection (numbers on the login page not loading). Some people want to have it this way. It is possible but needs some extra work to be done because you cannot install or update FOG without internet connection. To check internet connection please run the following commands on the CentOS server shell: ip a s ip r s cat /etc/resolv.conf ping -c 3 9.9.9.9 ping -c 3 ix.de Take a picture and post here. In the pictures I also see you have FOG version 1.5.4 - it’s printed in the lower right corner, when you are logged in to the web UI as well. About the missing buttons for canceling tasks: I can imagine the Konquerer used as browser is not set to run JavaScript or simply unable to render those properly. As the rest seems fine and the buttons are indeed added to that view via JavaScript it’s very likely to be the case. Simply use another browser (even on a different machine within the same network) and open that URL http://10.113.2.169/fog/
• R

  UNSOLVED WebUI Fog Configuration page displays php
  • Reagan  

  17
  0
  Votes
  17
  Posts
  128
  Views

  S

  @Reagan Well now I know what’s going on. Thanks for posting the picture of the log. The installer doesn’t finish and so never gets to copy the new web interface stuff. to /var/www/html/fog. So no wonder you were always stuck with 1.5.4!!! Did you notice it stopped on “Setting up fog password … Failed!”?? Please take a look at the installer error_log directory. There should be a second text file with detailed installer output. Copy and paste that (or at least the last 20 lines of it) to the forums. I can’t imagine why it would fail at that point.
• H

  UNSOLVED Not able to TFTP boot. Invalid Argument Error
  • hancocza  

  43
  0
  Votes
  43
  Posts
  497
  Views

  H

  @Sebastian-Roth Thanks for checking it out. In the meantime, I ended up migrating the database to another build, and then instead of installing fog with https, I stuck with a normal install, and then reconfigured the apache2 config to redirect to https and use my certificates. Everything is working correctly now, but eventually it’d be nice to run it all in https again.
• A

  SOLVED Chainloading failed
  • Andrew Seals  

  14
  0
  Votes
  14
  Posts
  32
  Views

  

  @Andrew-Seals The standards for the ipxe boot loaders are: BIOS: undionly.kpxe (kkpxe only if you have problems with kpxe. UEFI: ipxe.efi (or sndonly.efi if you have problems iwht ipxe.efi) If your environment has to support both uefi and bios systems and you have a Windows 2012 or newer dhcp server or a linux dhcp server you can setup dynamic boot file assignment by following here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
• M

  UNSOLVED server crush need help!!
  • mstrolo  

  9
  0
  Votes
  9
  Posts
  38
  Views

  

  @mstrolo Good thing we have a wiki article addressing this exact issue: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database
• M

  SOLVED Limit Bandwith
  • maouu  

  6
  0
  Votes
  6
  Posts
  29
  Views

  S

  @maouu If this is checked and we release a new client version (within a FOG server update) it will update itself on the clients too. I’d recommend leaving that option set as it will save you a lot of work. If you don’t update the FOG server there will be no automatic client update either. As well we have not updated the fog-client package in the last releases so this is not something that happens very often right now.
• A

  SOLVED Error while installing FOG on Ubuntu 18.04
  • andreiv  

  6
  0
  Votes
  6
  Posts
  525
  Views

  S

  @Rhywden said in Error while installing FOG on Ubuntu 18.04: enp6s0 Do you have an IP configured on that interface enp6s0 before running the installer?? FOG does not do this for you! IP needs to be set beforehand.
• Q

  UNSOLVED Access Control Plugin assigning users fails
  • quinniedid  

  5
  0
  Votes
  5
  Posts
  41
  Views

  

  @quinniedid I don know but is easy to check it :) don t use spaces in one role. You can see the entries in the database in the rule* and role* tables
• 

  SOLVED [SOLVED] Partition resizing problem
  • arnaudrigole  

  9
  0
  Votes
  9
  Posts
  100
  Views

  Q

  @arnaudrigole I am glad you found a solution that worked for you, though I’m still interested in trying to at least guess at why the other partition scheme gave problems. Was there a difference in disk size in the SATA vs nVME SSDs? Perhaps the nVME SSD is smaller and the OEM partitition at the end of the disk was out of range, though we’d expect a different error for that.
• T

  SOLVED High CPU Centos7 1.5.4
  • Troye Johnson  

  11
  0
  Votes
  11
  Posts
  76
  Views

  S

  @Troye-Johnson I’d wait for 1.5.6 as we have improved things like client communication in the dev-branch a fair bit. Not sure when we get to the next release though.
• S

  SOLVED Problem with HTTPS upgrade
  • sbenson  

  86
  0
  Votes
  86
  Posts
  9060
  Views

  F

  @Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server. like this: iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing || :testing set pxeserver:ipv4 FOG-IP set next-server ${pxeserver} chain tftp://FOG-IP/default.ipxe exit Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here! Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …
• H

  SOLVED Group Tasking Issue - Snapins
  • hancocza  

  6
  0
  Votes
  6
  Posts
  43
  Views

  H

  @Sebastian-Roth Awesome, thank you!
• B

  SOLVED Snapin Client will not start the Snapin Process - A power operation is pending, aborting module
  • BSZAdmin  

  3
  0
  Votes
  3
  Posts
  21
  Views

  B

  Hi Sebastian, it works thx. i forget that there was a scheduled reboot ;) sometimes it is so easy but it costs a lot of time ;)) Thanks :)