• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. 88fingerslukee
    3. Posts
    8
    • Profile
    • Following 0
    • Followers 0
    • Topics 10
    • Posts 39
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by 88fingerslukee

    • RE: FOG Server cannot connect to storage node

      Thanks for the reply!

      Apache is definitely running. When I go to http://x.x.x.x/fog I get the following message:

      This is a storage node, please do not access the web ui here!

      I have another website on this server, what URL does the master node look to when determining the storage node info?

      I have put the correct mysql connections into the fogsettings file.

      Anything else I can look at?

      posted in Linux Problems
      8
      88fingerslukee
    • FOG Server cannot connect to storage node

      Hey everybody,

      I used to have this working but I had to reinstall my storage node instance and I can’t get the main server to see the storage node for some reason. I’m running the latest 1.5.8.28 on both servers. I am able to connect to MySQL from the remote host no problem with the username and password that are entered in .fogsettings. Also, the fogproject user has the proper password as defined in .fogsettings.

      I see the following when I go to FOG Configuration:

      Main Server FOG Version: 1.5.8.28
      Storage Node FOG Version: 503 Service Unavailable

      Any idea what this means? I don’t think it’s a mysql issue.

      thanks
      88

      posted in Linux Problems
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      @joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

      @88fingerslukee after double checking, the FOG Client does not force log offs; this means that any other user process can stop the log off. This indicates the problem is likely another program on the computer, that or a GPO policy is blocking it.

      Could you try running:
      shutdown.exe /l manually on a problematic machine and see what happens?

      This command works and logs me out. For some reason it isn’t happening automatically

      However, ultimately I would recommend using GPO to handle inactivity log outs. There are some known restrictions with the log out module (https://github.com/fogproject/fog-client#autologout)

      Can you tell me how I would do inactivity logouts via GPO? The reason I use Fog for this purpose is because there was never any other way to do this.

      posted in Bug Reports
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      @joe-schmitt said in AutoLogOut on Windows 10 - Service seems to hang:

      @Wayne-Workman thanks for pinging me about this. @88fingerslukee I’ll need to reproduce this issue before being able to properly address it; hopefully it should not take long.

      I run Avast Business Antivirus on the workstations. Both Windows 7 and Windows 10. It obviously doesn’t affect the Windows 7 machines.

      I also have GPOs. How do you want me to give you that information?

      posted in Bug Reports
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      Has anybody fixed this yet?

      posted in Bug Reports
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      @sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

      @88fingerslukee said in AutoLogOut on Windows 10 - Service seems to hang:

      Don’t know about other clients because I only have this one on Windows 10 as a test case.

      What I meant was “other machines” or do you only have one single PC?

      I have a bunch of Windows 7 machines that work just fine. It seems to be isolated to Windows 10.

      posted in Bug Reports
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      @sebastian-roth said in AutoLogOut on Windows 10 - Service seems to hang:

      @88fingerslukee Sorry for not getting back to you on this for so long. Somehow we must have overlooked this one.

      Do you still have that issue? Is it only with one or a couple of clients or do you have this reproducibly on all your clients happening. I don’t think there is any more log that you could provide. But the questions above would definitely help us.

      Yes, still having it. Don’t know about other clients because I only have this one on Windows 10 as a test case.

      posted in Bug Reports
      8
      88fingerslukee
    • RE: AutoLogOut on Windows 10 - Service seems to hang

      Awesome thanks.

      Is there a more detailed log that I can provide?

      posted in Bug Reports
      8
      88fingerslukee
    • AutoLogOut on Windows 10 - Service seems to hang
      Server
      • FOG Version: 1.4.1
      • OS: CentOS 6.8
      Client
      • Service Version: 0.11.12
      • OS: Windows 10
      Description

      I’m having an issue with the client not logging me out on Windows 10. The .fog_user log has stalled at the last attempt to logout but there are no error messages. The other log file (fog) is still updating. Here are the last lines of the fog_user log.

      `------------------------------------------------------------------------------
      ----------------------------------AutoLogOut----------------------------------

      6/23/2017 8:52 PM Client-Info Client Version: 0.11.12
      6/23/2017 8:52 PM Client-Info Client OS: Windows
      6/23/2017 8:52 PM Client-Info Server Version: 1.4.1
      6/23/2017 8:52 PM Middleware::Response Success
      6/23/2017 8:52 PM Bus Emmiting message on channel: Notification
      6/23/2017 8:52 PM Power Creating shutdown request
      6/23/2017 8:52 PM Power Parameters: /l
      ------------------------------------------------------------------------------`

      If I restart the service, the fog_user log starts logging again until the next time it tries to log out.

      posted in Bug Reports
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      @Tom-Elliott I’m not certain I understand what you’re saying here. Are you suggesting an issue with the motherboard’s implementation of iPXE or something to do with FOG?

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      @Tom-Elliott the BIOS has two different network boots, iPXE and Legacy LAN. Both of them exhibit the same behaviour

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      @Tom-Elliott no error logs at all. I only have ssl_error_log or access_log. Neither of them have anything relevant.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Unfortunately, no. I don’t use any plugins at all.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Okay, so totally weird. It must’ve worked at some point because I had to leave for a while but when I came back it was at the linux prompt. Here’s the lsblk command, sda is the system SSD.

      NAME    MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
      sdb       8:16    0   298.1G  0 disk
      └─sdb1    8:17    0   298.1G 0 part
        sda      8:0   0   238.5G  0 disk
      └─sda4    8:4   0    238G   0 part
      └─sda2    8:2   0   100M  0 part
      └─sda3    8:3   0   128M  0 part
      └─sda1    8:1   0   300M   0 part
      
      

      When I rebooted it went back to the open timeout. So I have no idea what the deal is here.

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Sorry, that was without the capture task . Here is what you actually asked for:

      #!ipxe
      set fog-ip 192.168.1.184
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 mac=xx:xx:xx:xx:xx:xx ftp=192.168.1.184 storage=192.168.1.184://files/images/dev/ storageip=192.168.1.184 osid=7 irqpoll hostname=HOST chkdsk=0 img=IMG imgType=n imgPartitionType=all imgid=10 imgFormat= PIGZ_COMP=-6 hostearly=1 pct=5 ignorepg=1 isdebug=yes type=up
      imgfetch init_32.xz
      boot

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      I get this:

      #!ipxe
      set fog-ip 192.168.1.184
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 ||
      colour --rgb 0x00567a 2 ||
      colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 ||
      cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://192.168.1.184/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0x00567a 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is registered as PSI1!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.keyreg Update Product Key
      item fog.deployimage Deploy Image
      item fog.multijoin Join Multicast Session
      item fog.quickdel Quick Host Deletion
      item fog.sysinfo Client System Information (Compatibility)
      choose --default fog.local --timeout 5000 target && goto ${target}
      :fog.local
      imgfetch ${boot-url}/service/ipxe/refind.conf
      chain -ar ${boot-url}/service/ipxe/refind.efi || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.memtest
      kernel memdisk iso raw
      initrd memtest.bin
      boot || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.keyreg
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param keyreg 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.deployimage
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.quickdel
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param delhost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://192.168.1.184/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      
      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      Okay, now it’s getting weird.

      When I create a capture task I get a TFTP Open Timeout error. So it’ll TFTP just fine into the menu without any task enabled but it has an issue with a task? How does that work?

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Chainloading Failed on EXIT - Hangs on REFIND_EFI

      No RAID. There are 2 drives, one SSD with Windows on it, the other as a general storage drive:

      System Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: CRUCIAL_CT256M225
      Drive Revision: 1819
      Drive Capacity: 244,198 MBytes (256 GB)
      Media Rotation Rate: SSD Drive (Non-rotating)

      Storage Drive:
      Drive Controller: Serial ATA 3Gb/s
      Drive Model: WDC WD3200AAKS-00L9A0
      Drive Revision: 01.03E01
      Drive Capacity: 305,245 MBytes (320 GB)

      posted in FOG Problems
      8
      88fingerslukee
    • Chainloading Failed on EXIT - Hangs on REFIND_EFI
      Server
      • FOG Version: 1.3.0-RC-25
      • OS: CentOS 6.8
      Client
      • Service Version:
      • OS: Windows Server 2012 R2
      • System Manufacturer: Gigabyte Technology Co., Ltd.
      • System Product: GA-78LMT-USB3 6.0
      Description

      This motherboard boots to the menu just fine but gives the Chainloading error when using the EXIT option. When using REFIND_EFI or SANBOOT it hangs with the blinking cursor in the top left corner. The GRUB options don’t work because it’s a Windows EFI installation.

      I have no “Secure Chip” or Secure Boot settings in the BIOS so this is why I’m posting a new thread. It seems my issue might be different than the others.

      I’d love to get this working as I have several of these motherboards in my install base. I’m happy to do some digging, just please let me know what I have to do.
      Here is my boot.php file from (http://x.x.x.x/fog/service/ipxe/boot.php)

      #!ipxe
      set fog-ip x.x.x.x
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      cpuid --ext 29 && set arch x86_64 || set arch i386
      goto get_console
      :console_set
      colour --rgb 0x00567a 1 ||
      colour --rgb 0x00567a 2 ||
      colour --rgb 0x00567a 4 ||
      cpair --foreground 7 --background 2 2 ||
      goto MENU
      :alt_console
      cpair --background 0 1 ||
      cpair --background 1 2 ||
      goto MENU
      :get_console
      console --picture http://x.x.x.x/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
      :MENU
      menu
      colour --rgb 0xff0000 0 ||
      cpair --foreground 1 1 ||
      cpair --foreground 0 3 ||
      cpair --foreground 4 4 ||
      item --gap Host is NOT registered!
      item --gap -- -------------------------------------
      item fog.local Boot from hard disk
      item fog.memtest Run Memtest86+
      item fog.reginput Perform Full Host Registration and Inventory
      item fog.reg Quick Registration and Inventory
      item fog.deployimage Deploy Image
      item fog.multijoin Join Multicast Session
      item fog.sysinfo Client System Information (Compatibility)
      choose --default fog.local --timeout 5000 target && goto ${target}
      :fog.local
      sanboot --no-describe --drive 0x80 || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.memtest
      kernel memdisk iso raw
      initrd memtest.bin
      boot || goto MENU
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reginput
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=manreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.reg
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.1.184/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=autoreg
      imgfetch init_32.xz
      boot || goto MENU
      :fog.deployimage
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param qihost 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.multijoin
      login
      params
      param mac0 ${net0/mac}
      param arch ${arch}
      param username ${username}
      param password ${password}
      param sessionJoin 1
      isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
      isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=x.x.x.x/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://x.x.x.x/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      

      thanks
      Lucas

      posted in FOG Problems
      8
      88fingerslukee
    • RE: Fog Installation Error - Cannot restart MySQL

      @Tom-Elliott

      I don’t know how to clarify that. What I know is that the installer fails at trying to restart mysqld. If I edit the mysqld init file adn re-run the installer, the init file is overwritten.

      Nothing else gets installed because of the failure.

      posted in FOG Problems
      8
      88fingerslukee
    • 1 / 1