• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. zln1996
    3. Posts
    Z
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 19
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by zln1996

    • RE: Problems with fog homepage

      @KnightRaven There are no words to describe how happy I am right now. I finally got it working and I’m in fog again and everything looks okay! Knight I want to thank you so much for your help you had me on the right path all along, however, I did have to do a few extra steps. I’m going to explain so if anyone has this issue later on and they stumble upon this post hopefully it will help them out.

      First thing is the reason I could never get mysqld to start is during the installation of mySQL it never created the directory /var/run/mysqld so that’s why it would never start a mysql instance. So using these commands you can accomplish that.

      mkdir -p /var/run/mysqld
      chown mysql:mysql /var/run/mysqld
      

      Once that was done, make sure all instances of regular mysql is gone. I used killall mysql and then to verify killall -9 mysql Then I ran the following command

      mysqld_safe --skip-grant-tables --skip-networking &
      

      Once that is done you’ll need to open a different terminal. And do the following:

      mysql -u root
      

      If all is well you should now be in the database once more, here I checked for the user account like you mentioned Knight, but mine seemed to still be in there. So if the user is there use the following commands (this is what I had to do in my case, since my root user still existed)

      use mysql;
      update user set authentication_string=PASSWORD('<YOURPASSWORDHERE>') where user='root';
      flush privileges;
      \q
      

      So now your password should be updated, so now to verify kill all of the mysqld instances and start the regular mysql ones. This can be accomplished by the following.

      killall mysqld
      service mysql start
      #now you can check your new password...
      mysql -u root -p
      #Enter your password and you should be brought to the following prompt...
      mysql>
      

      After that I was able to get to the fog homepage and update my schema, and now I’m back in with everything in tact. After this was done I followed Tom’s advice and disabled automatic updates because I’m really tired of Ubuntu breaking everything lol.

      I hope this helps any future readers, so you don’t have to go through this madness like I did. Turn off automatic updates as soon as you can, because from my experience it only causes issues, and if you have to update your Ubuntu fog machine prepare for problems.

      I also want’s to extend one last thanks to @KnightRaven @Tom-Elliott and @george1421 for their help on this, you guys rock!

      Along with everyone else’s references here is the one I used: https://askubuntu.com/questions/489098/unable-to-reset-root-password-of-mysql

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @KnightRaven This is driving me insane lol, Ubuntu absolutely hates me. I completely removed sql and reinstalled it, and it still denies access to everything. The only other thing I can think of doing is saving my images then installing Ubuntu and fog again.

      Any ideas? Or does this seem like the only other option?

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @KnightRaven Okay thanks man, I’m about to try those things and see if it works for me. If it doesn’t I may resort to uninstalling mySQL.

      Maybe @Tom-Elliott could answer, whether or not, my fog database should stay intact if I uninstall and then re-install mySQL?

      Also Knight, what commands did you run to uninstall mySQL and re-install it? The ones I found seem to get rid of anything SQL related.

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @KnightRaven Thanks for the help man! I am definitely not in anyway a SQL pro lol, so I tried what you did. I used the command sudo service mysql stop and then ran the first command. When I attempted to run the second command I receive this error: ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2) I then checked the status of the mysql service and it was still stopped. I also attempted the command in the article you provided /etc/init.d/mysql stop mysqld_safe --skip-grant-tables but that was also to no avail. I even attempted to replace “stop” with “start” in that command but that didn’t work either. :L

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @Tom-Elliott ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY ''; that one actually executed the first failed, but like I said after this command I still was unable to get to the homepage of fog, and now I can’t seem to login to my sql database.

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @Tom-Elliott I did the steps you provided, the second command worked on that post, but now it’s still a blank screen and I can’t get into the mySQL database.

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @george1421 Okay thanks for your help man, I really appreciate you looking at this with me!

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      @george1421 I do see a re-direct occuring no matter what i put in for example: http://<server-ip>/asdfasdf it adds “?node=schema” don’t know if that helps any. As for the error logs see below, I have omitted the server ip intentionally. The error there may be because I was messing around with the settings in that article, so after you told me to check the log out I restarted the apache2 service and tried to pull the page up, but the error never showed up again in the error log.

      [Wed May 17 17:19:29.081733 2017] [php7:error] [pid 29225] [client x.x.x.x:37264] PHP Fatal error: Uncaught Error: Call to a member function lastInsertId() on boolean in /var/www/fog/lib/db/pdodb.class.php:443\nStack trace:\n#0 /var/www/fog/lib/fog/fogcontroller.class.php(527): PDODB->insertId()\n#1 /var/www/fog/lib/fog/hookmanager.class.php(176): FOGController->save()\n#2 /var/www/fog/lib/fog/fogpagemanager.class.php(82): HookManager->processEvent(‘SEARCH_PAGES’, Array)\n#3 [internal function]: FOGPageManager->__construct()\n#4 /var/www/fog/lib/fog/fogbase.class.php(457): ReflectionClass->newInstanceArgs(Array)\n#5 /var/www/fog/management/index.php(23): FOGBase::getClass(‘FOGPageManager’)\n#6 {main}\n thrown in /var/www/fog/lib/db/pdodb.class.php on line 443
      [Wed May 17 17:35:14.867060 2017] [mpm_prefork:notice] [pid 29220] AH00169: caught SIGTERM, shutting down
      [Wed May 17 17:35:14.959750 2017] [mpm_prefork:notice] [pid 29342] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2k configured – resuming normal operations
      [Wed May 17 17:35:14.959797 2017] [core:notice] [pid 29342] AH00094: Command line: ‘/usr/sbin/apache2’

      Edit: After about 18 mins the above error populated to the apache error log.

      posted in FOG Problems
      Z
      zln1996
    • RE: Problems with fog homepage

      I never set up a redirect for fog, I would always key in the whole server address. In the location Tom specified in his first post in the article you shared i don’t have an index.php I do have an index.html. I attempted to do what Wanderson posted but the issue is still occuring. I don’t necessarily believe it’s an issue with the update itself as this was a problem before I upgraded fog.

      posted in FOG Problems
      Z
      zln1996
    • Problems with fog homepage

      Hi,

      I was experiencing an issue with our fog server not loading the homepage, so I updated to the current stable build. The problem persisted so I went ahead and updated to the most current release. The issue is when I try to go to http://<server-ip>/fog/management I get an error in firefox that it would keep redirecting forever. I know after you update fog, you need to update the schema, and I have experienced database connection issues in the past could this be what the problem is? Fog is running on a 16.04 Ubuntu machine. Any help with this would be greatly appreciated!

      Thanks

      posted in FOG Problems
      Z
      zln1996
    • RE: When trying to boot to hard disk from PXE menu I get a blinking cursor.

      @george1421 Thank you though! I believe we may be okay since most of our computer’s in the organization are new so they should all use ipxe.efi. We will be doing a migration to Server 2012, sometime in the near future, luckily I’m a lot more familiar with 2012’s interface and layout. Could you point me to that article still? I would like to see it before going live with the migration.

      Also just wanted to thank you again for the help!

      posted in FOG Problems
      Z
      zln1996
    • RE: When trying to boot to hard disk from PXE menu I get a blinking cursor.

      @george1421 No Windows 2008 R2.

      posted in FOG Problems
      Z
      zln1996
    • RE: When trying to boot to hard disk from PXE menu I get a blinking cursor.

      @george1421 Okay that’s where my confusion was, the only boot file that I knew of was undionly.kpxe I didn’t know there was one designed for UEFI. So now when I boot into PXE using UEFI instead of legacy it works now that I’ve configured the server to send ipxe.efi.

      Sorry for not being clear earlier yes it is an UEFI system.

      So i changed the FOG_EFI_BOOT_EXIT_TYPE to refind efi and it boots to windows! Sanboot made it loop in the fog menu and exit gave the same “chainloading failed” screen.

      Now I’m gonna test deploying an image and make sure it goes through the entire thing!

      Thanks for the help guys!

      Update:

      It worked! Completely unattended! Thank you guys so much for the help!!!

      posted in FOG Problems
      Z
      zln1996
    • RE: When trying to boot to hard disk from PXE menu I get a blinking cursor.

      Hey Tom and George,

      The UEFI BIOS version is N1EET52W. As for the boot file I’m using undionly.kpxe and the way I have the BIOS to boot is both UEFI and Legacy where Legacy is first. The reason for this is because when I have it set to UEFI first and try to PXE boot it won’t ever load the PXE menu, but on Legacy it works.

      I switched the exit type to rEFInd and get the same blinking cursor.

      Using grub it states “Starting CMAIN()…” and then just a blinking cursor it’s been that way for about 5 mins now, so I’m writing this post while monitoring it.

      posted in FOG Problems
      Z
      zln1996
    • When trying to boot to hard disk from PXE menu I get a blinking cursor.
      Server
      • FOG Version: 1.3.0-RC-8
      • OS: Ubuntu 16.04
      Client
      • Service Version: Not sure I’m assuming the same.
      • OS: Windows 10
      • Specific Machine: Lenovo ThinkPad P50
      Description

      So we have FOG in our environment and testing has been going well thus far, however setting the PC’s to boot into PXE first, won’t allow the PC to boot to it’s hard drive after the PXE menu.

      I have tried using the ‘sanboot’ and ‘exit’ exit types. With sanboot is when I get the black screen with a blinking cursor and with exit it states that chainloading failed and the system restarts.

      Also to note that after an image task the OS will load, but upon reboot when it goes to the FOG PXE screen and tries to load from hard disk is when I’m having issues.

      Any help would be awesome! Thanks

      posted in FOG Problems
      Z
      zln1996
    • RE: TFTP Issues

      Well… This is embarrassing.

      Good news I fixed it, i get into the PXE menu now! 😄

      I do have a different question now, when I click boot from hard disk in the pxe menu it doesn’t load the operating system, any ideas for that?

      For the issue relating to TFTP this is what happened:

      I set up a packet scan on both the DHCP and PXE server and after analyzing the packets i noticed there were two different packets sending a different option 66 and option 67. One was right pointing to the FOG server and Undionly.kpxe the other however pointed to the DHCP server. Apparently an old image deployment software was still working even though the options weren’t configure anymore. I removed these and everything worked great!

      posted in FOG Problems
      Z
      zln1996
    • RE: TFTP Issues

      @Wayne-Workman Nope Ubuntu was a clean install. I’ll start looking through that article right now.

      The output of ls -lahRt /tftpboot is:

      /tftpboot:
      total 6.6M
      drwxr-xr-x 27 root root 4.0K Aug 31 23:58 ..
      drwxr-xr-x  5 fog  root 4.0K Aug 31 13:47 .
      -rw-r--r--  1 root root  429 Aug 31 13:47 default.ipxe
      -rw-r-xr-x  1 fog  root 198K Aug 31 13:47 intel.efi
      -rw-r-xr-x  1 fog  root 842K Aug 31 13:47 ipxe.iso
      -rw-r-xr-x  1 fog  root  26K Aug 31 13:47 libutil.c32
      -rw-r-xr-x  1 fog  root 197K Aug 31 13:47 realtek.efi
      -rw-r-xr-x  1 fog  root  29K Aug 31 13:47 menu.c32
      -rw-r-xr-x  1 fog  root  43K Aug 31 13:47 pxelinux.0
      -rw-r-xr-x  1 fog  root  30K Aug 31 13:47 vesamenu.c32
      -rw-r-xr-x  1 fog  root  93K Aug 31 13:47 realtek.kkpxe
      -rw-r-xr-x  1 fog  root  93K Aug 31 13:47 realtek.pxe
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 intel.kkpxe
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 intel.kpxe
      -rw-r-xr-x  1 fog  root 196K Aug 31 13:47 snp.efi
      -rw-r-xr-x  1 fog  root 334K Aug 31 13:47 ipxe.krn
      -rw-r-xr-x  1 fog  root 194K Aug 31 13:47 snp7156.efi
      drwxr-xr-x  2 fog  root 4.0K Aug 31 13:47 i386-7156-efi
      drwxr-xr-x  2 fog  root 4.0K Aug 31 13:47 i386-efi
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 intel.pxe
      -rw-r-xr-x  1 fog  root 335K Aug 31 13:47 ipxe.kpxe
      drwxr-xr-x  2 fog  root 4.0K Aug 31 13:47 pxelinux.cfg
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 undionly.kpxe
      -rw-r-xr-x  1 fog  root 195K Aug 31 13:47 intel7156.efi
      -rw-r-xr-x  1 fog  root  26K Aug 31 13:47 memdisk
      -rw-r-xr-x  1 fog  root 195K Aug 31 13:47 realtek7156.efi
      -rw-r-xr-x  1 fog  root  93K Aug 31 13:47 realtek.kpxe
      -rw-r-xr-x  1 fog  root 194K Aug 31 13:47 snponly7156.efi
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 undionly.pxe
      -rw-r-xr-x  1 fog  root 921K Aug 31 13:47 ipxe7156.efi
      -rw-r-xr-x  1 fog  root 121K Aug 31 13:47 ldlinux.c32
      -rw-r-xr-x  1 fog  root  92K Aug 31 13:47 undionly.kkpxe
      -rw-r-xr-x  1 fog  root 196K Aug 31 13:47 snponly.efi
      -rw-r-xr-x  1 fog  root 335K Aug 31 13:47 ipxe.kkpxe
      -rw-r-xr-x  1 fog  root 184K Aug 31 13:47 libcom32.c32
      -rw-r-xr-x  1 fog  root 926K Aug 31 13:47 ipxe.efi
      -rw-r-xr-x  1 fog  root  840 Aug 31 13:47 boot.txt
      -rw-r-xr-x  1 fog  root 335K Aug 31 13:47 ipxe.pxe
      -rw-r-xr-x  1 fog  root  43K Aug 31 13:47 pxelinux.0.old
      
      /tftpboot/i386-7156-efi:
      total 1.5M
      drwxr-xr-x 5 fog root 4.0K Aug 31 13:47 ..
      drwxr-xr-x 2 fog root 4.0K Aug 31 13:47 .
      -rw-r-xr-x 1 fog root 157K Aug 31 13:47 intel.efi
      -rw-r-xr-x 1 fog root 157K Aug 31 13:47 realtek.efi
      -rw-r-xr-x 1 fog root 156K Aug 31 13:47 snp.efi
      -rw-r-xr-x 1 fog root 156K Aug 31 13:47 snponly.efi
      -rw-r-xr-x 1 fog root 836K Aug 31 13:47 ipxe.efi
      
      /tftpboot/i386-efi:
      total 1.5M
      drwxr-xr-x 5 fog root 4.0K Aug 31 13:47 ..
      drwxr-xr-x 2 fog root 4.0K Aug 31 13:47 .
      -rw-r-xr-x 1 fog root 158K Aug 31 13:47 intel.efi
      -rw-r-xr-x 1 fog root 158K Aug 31 13:47 realtek.efi
      -rw-r-xr-x 1 fog root 158K Aug 31 13:47 snp.efi
      -rw-r-xr-x 1 fog root 841K Aug 31 13:47 ipxe.efi
      -rw-r-xr-x 1 fog root 158K Aug 31 13:47 snponly.efi
      
      /tftpboot/pxelinux.cfg:
      total 12K
      drwxr-xr-x 5 fog root 4.0K Aug 31 13:47 ..
      drwxr-xr-x 2 fog root 4.0K Aug 31 13:47 .
      -rw-r-xr-x 1 fog root  160 Aug 31 13:47 default
      
      posted in FOG Problems
      Z
      zln1996
    • RE: TFTP Issues

      Hey Wayne,

      Thanks for the quick response.

      I followed this guide here: https://wiki.fogproject.org/wiki/index.php?title=Tftp_timeout…

      I ran the command: service tftpd-hpa status and received this:
      tftpd-hpa.service - LSB: HPA’s tftp server
      Loaded: loaded (/etc/init.d/tftpd-hpa; bad; vendor preset: enabled)
      Active: active (running) since Fri 2016-09-02 11:31:54 EDT; 2h 24min ago
      Docs: man:systemd-sysv-generator(8)
      CGroup: /system.slice/tftpd-hpa.service
      └─4566 /usr/sbin/in.tftpd --listen --user root --address :69 -s /tftp

      To my knowledge the update went successful i followed the procedure on the wiki using the GIT method.

      Another thing On my windows machines (including the DHCP server) I’ve installed TFTP and issued the command tftp <ip address of FOG> GET undionly.kpxe and they receive the file, with no problem at all.

      posted in FOG Problems
      Z
      zln1996
    • TFTP Issues

      Hello,

      After reading countless posts and the entire troubleshooting guide I still can’t get TFTP to work. I’ll try to include everything I have tested and tried so far and the error messages I’m receiving. A little back story we have a mixed environment some laptops and some desktops, the weird thing is we’re getting different errors on both systems.

      Problems on Desktop:

      Client receives IP address and then states
      TFTP.
      PXE-T01: File not found.
      PXE-E3B: TFTP Error - File Not found
      PXE-M0F: Exiting PXE ROM.

      Problems on Laptops:

      Client receives IP address and then states
      TFTP.
      PXE-M0F: Exiting Intel Boot Agent

      Here are some specs I’m running:

      FOG Machine:

      OS: Ubuntu 16.04
      I have upgraded to the latest trunk. (update was performed on 8/30)

      DHCP Server:

      OS: Windows Server 2008 R2
      Option 66: is the ip of the Fog server
      Option 67: undionly.kpxe

      The Laptops are Lenovo P50’s.

      In the laptops BIOS I have secure boot turned off, using both UEFI and Legacy but Legacy first.

      The Desktops vary but all are HP ProDesk’s of some form.

      My main concern is trying to get the laptops able to capture images and deploy. We are going to a mobile setup, so desktops won’t be an issue much longer and we already have an inefficient way to image desktops but this wont work for the laptops.

      We are testing on one subnet inside one physical location right now, but a little network background may help.

      All clients are on the 192.168.39.x VLAN they are all connected to the same switch on 192.168.39.x. Spanning Tree is enabled on this switch but I’m not sure if that is causing an issue or not, I haven’t been able to test changing that option.

      I’m at a loss as to where the problem now resides any advice would be awesome.

      Sorry for the long post, hope this is a good starting place though, if you need any more information please let me know.

      posted in FOG Problems tftp pxe
      Z
      zln1996
    • 1 / 1