• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. AlexPDX
    3. Posts
    • Profile
    • Following 1
    • Followers 0
    • Topics 9
    • Posts 59
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by AlexPDX

    • RE: Snapin replication no working

      I did’nt knew if i should make a new post or not…but im haveing kind of…the same isuie…
      My Snapin Replication dose not work 😞 …i managed to start my images replication with : systemctl restart FOGImageReplicator ( cent os7 ) and now all is goog …but the same restart did not work for snapin replication 😞 and i get this 😞 :

      code_text
      ```[root@HQ-FOG log]# systemctl status FOGSnapinReplicator
      ● FOGSnapinReplicator.service - FOGSnapinReplicator
         Loaded: loaded (/usr/lib/systemd/system/FOGSnapinReplicator.service; enabled; vendor preset: disabled)
         Active: failed (Result: start-limit) since Tue 2020-02-25 13:13:29 EET; 1h 54min ago
        Process: 20377 ExecStart=/usr/bin/php env /opt/fog/service/FOGSnapinReplicator/FOGSnapinReplicator (code=exited, status=1/FAILURE)
       Main PID: 20377 (code=exited, status=1/FAILURE)
      
      Feb 25 13:13:28 HQ-FOG: Unit FOGSnapinReplicator.service entered failed state.
      Feb 25 13:13:28 HQ-FOG: FOGSnapinReplicator.service failed.
      Feb 25 13:13:29 HQ-FOG: FOGSnapinReplicator.service holdoff time over, scheduling restart.
      Feb 25 13:13:29 HQ-FOG: Stopped FOGSnapinReplicator.
      Feb 25 13:13:29 HQ-FOG: start request repeated too quickly for FOGSnapinReplicator.service
      Feb 25 13:13:29 HQ-FOG: Failed to start FOGSnapinReplicator.
      Feb 25 13:13:29 HQ-FOG: Unit FOGSnapinReplicator.service entered failed state.
      Feb 25 13:13:29 HQ-FOG: FOGSnapinReplicator.service failed.
      
      
      ...now where did i go wrong ?
      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: Interface not ready, waiting for it to come up

      Ok so i’v managed to get things working ( edited the interface in Fog Storage and Multicast )
      now what do i have to do so what ALL my images from Master Node to be replicated to the Storage Node ?
      now i got this … :

      [root@HQ-FOG fog]# tail -f /var/log/fog/log/fogreplicator.log
      [02-24-20 2:54:53 pm]  | Image Name: Win10x64MBR-Default
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.fixed_size_partitions (Server_114)
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.mbr (Server_114)
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.minimum.partitions (Server_114)
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.original.fstypes (Server_114)
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.original.swapuuids (Server_114)
      [02-24-20 2:54:54 pm]   # Win10x64MBR-Default: No need to sync d1.partitions (Server_114)
      [02-24-20 2:54:55 pm]   # Win10x64MBR-Default: No need to sync d1p1.img (Server_114)
      [02-24-20 2:54:55 pm]   # Win10x64MBR-Default: No need to sync d1p2.img (Server_114)
      [02-24-20 2:54:55 pm]  * All files synced for this item.
      

      I have 1 Gropu with 1 Master Node (111) and 1 Storage Node (114)
      …can i just copy > paste( or transfer via FTP) the folders with images name from Master Node to Storage Node…or this should be done automaticly ?

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: Need Guidance Other Than FOG Wiki page.

      Hy …first of all I advise you to use CentOS 7 … Debian gave me many problems on this side of FOG :
      -web page did not want to start
      -TFTP server did not want to turn on …

      posted in General Problems
      AlexPDXA
      AlexPDX
    • RE: Interface not ready, waiting for it to come up

      @george1421 said in Interface not ready, waiting for it to come up:

      @AlexPDX said in Interface not ready, waiting for it to come up:

      “ens160” … Master Storage has “eth0” interface

      The value eth0 is wrong. The values need to match the physical names of the interfaces installed. In the case of the master node this value needs to be ens160.

      Ok 10x i will change this now in Master Node and come back with a log from Master Node 111
      …the logs from early wore from Storage Node 114

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: Interface not ready, waiting for it to come up

      @george1421 said in Interface not ready, waiting for it to come up:

      On your fog server, what is the output of this command ip addr show

      [root@fognode ~]# ip addr show
      1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
      valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
      valid_lft forever preferred_lft forever
      2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:50:56:9d:44:74 brd ff:ff:ff:ff:ff:ff
      inet 192.168.192.114/24 brd 192.168.192.255 scope global noprefixroute ens160
      valid_lft forever preferred_lft forever
      inet6 fe80::250:56ff:fe9d:4474/64 scope link
      valid_lft forever preferred_lft forever

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: Interface not ready, waiting for it to come up

      @george1421 said in Interface not ready, waiting for it to come up:

      On your fog server, what is the output of this command ip addr show

      Then in the web ui,

      Fog Configuration -> Fog Settings -> Multicast settings -> UPDCAST INTERFACE

      “ens160” … Master Storage has “eth0” interface
      …the Fog Node has “ens160” interface

      and

      Storage -> Default storage node -> Interface ?

      Multicast has to be the same as Master or as Node ?

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • Interface not ready, waiting for it to come up

      [root@fognode ~]# tail -f /var/log/fog/fogreplicator.log
      [02-21-20 3:43:38 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:43:48 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:43:58 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:08 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:18 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:28 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:38 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:48 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:44:58 pm] Interface not ready, waiting for it to come up: 192.168.192.111
      [02-21-20 3:45:08 pm] Interface not ready, waiting for it to come up: 192.168.192.111

      …now why is this showing up now ?

      Fog 1.5.8
      Master Fog and Node IP 111 Interface eth0
      Fog Node IP 114 Interface ens160
      …what more should i provide ?

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: Pushbullet

      @AlexPDX said in Pushbullet:

      I don’t understand what exactly dose PushBullet to the FOG ? i’v linked my acount to the Fog PushBullet…so what do i do next ?

      Now i see 🙂 it sends u the information of deploy , capture and snapins done on hosts 🙂

      posted in General
      AlexPDXA
      AlexPDX
    • RE: Pushbullet

      I don’t understand what exactly dose PushBullet to the FOG ? i’v linked my acount to the Fog PushBullet…so what do i do next ?

      posted in General
      AlexPDXA
      AlexPDX
    • RE: Storage Group and Storage Node explained for dummies

      Alsow … i hope it fixed the Windows Export Keys …and wouldn’t it be great to make a “connection” between Windows Keys Plugin and each Host ? 🙂
      ![0_1582207871801_WindowsKeysExport.jpg](Uploading 100%)

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • RE: Storage Group and Storage Node explained for dummies

      @george1421 said in Storage Group and Storage Node explained for dummies:

      @AlexPDX said in Storage Group and Storage Node explained for dummies:

      can we just update the 1.5.6 or 7 instalation ? Will it keep the setings like Hosts, Storage Nodes, Snapins and Images ?

      Upgrading keeps the data in the database so you can go from one version to the next without data loss.

      10x …and one more thing … will the 1.5.8 keep remembering the Windows Keys in the Host ?
      I have faced this problem several times. I added a new host and after clicking on the update … when i went back to that host, he no longer had the windows key 😐

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • RE: Storage Group and Storage Node explained for dummies

      @Sebastian-Roth said in Storage Group and Storage Node explained for dummies:

      @AlexPDX If you want to do a complete reinstall anyway you should wait a few more hours as we will release FOG 1.5.8 with a lot of fixed bugs and stuff very soon!

      …can we just update the 1.5.6 or 7 instalation ? Will it keep the setings like Hosts, Storage Nodes, Snapins and Images ?

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • RE: Storage Group and Storage Node explained for dummies

      @Sebastian-Roth okydoky 🙂 …till then il just backup all my snapins and images

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • RE: Storage Group and Storage Node explained for dummies

      @Sebastian-Roth 10x dude …im on it now …i think i will reinstal the Master Node from scratch (don’t know why but the replication and logging has stuped on the master node)
      Clean CentOS and Clean FOG Normal Instal with 2 celan Fog nodes.
      I guess i should make a backup of /images , export the images first and hope they will work after importing them to the clean instal…

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • Storage Group and Storage Node explained for dummies

      First of all, I want to thank everyone for the effort made in this Project, which is getting better and better with each update. You will achieve perfection with the help of both users and programmers 🙂
      I am using FOG for almost 8 months and now i want to expand it to other locations.

      Can someone explain me what is the actual meaning of a STORAGE GROUP and STORAGE NODE ?
      In my understanding … an Group is like…an Town…and an Node is like a shop in that Town.So you could have 4 or 6 shops in 3 towns…i hope i understand the meaning and working of Storage Group and Storage Node corectly first of all.
      The comapny that i work for has 1 HeadQuarter (New York for example) and 2 other locations in other Towns (one in LA and another in San Francisco).
      The conection is done by VPN from each location (LA and SF) directly to NY HQ, HQ handels the DHCP and DNS and everything.
      So i guess will have to set up FOG 1.5.7 like this :
      I prefered to use CentOS 7 minimal instalation on everything…so :
      Normal FOG instal in the HQ (NY) with Storage Group Default and Storage Node Default (lets name it like this because here is where all my images are stored)
      Then i will have to instal Fog Storage Node in each location ( LA and SF ), provide the HQ STORAGENODE MYSQLPASS from the HQ and add them to in Fog Storage Node meniu.
      Then create other 2 Storage Groups (beaside DEFAULT of course) named LA and SF and asign the Storage Node (LA and SF) to the desired Locations ( from the Location Plugin ) and asign the Storage Node to the Storage Group(lest short Storage Group an Storage Node to SN and SG) so, SN LA to SG LA and SN SF to SG SF.
      The idea is that , when i deploy/capture an image , depending on the Location , the task wil be done from that location.

      Other things i dont understand exactly are :

      1 How to replicate images and snapins from HQ to the other 2 locations , groups , nodes…is it done automaticly or can i do it a force task. If i have to modify images from HQ , how do i make the changes on the other 2 locations , nodes (i’v tested one time in the same LAN with Normal instal and a Storage Node , but the loging stoped working after 2 days even if the replication box is checked on the Master FOG HQ 😞 ) ?

      [root@fognode ~]# tail -f /var/log/fog/fogreplicator.log
      [02-18-20 7:47:42 am] * | This is not the master node
      [02-18-20 7:57:42 am] * | This is not the master node
      [02-18-20 8:07:42 am] * | This is not the master node
      [02-18-20 8:17:42 am] * | This is not the master node
      [02-18-20 8:27:42 am] * | This is not the master node
      [02-18-20 8:37:42 am] * | This is not the master node
      [02-18-20 8:47:42 am] * | This is not the master node
      [02-18-20 8:57:42 am] * | This is not the master node
      [02-18-20 9:07:43 am] * * Image replication is globally disabled
      [02-18-20 9:17:43 am] * * Image replication is globally disabled

      2 Can i use just the Default Group and add only 2 Storage Nodes …and if i want to image one host from LA, that image will go from LA Fog Storage Node , not the HQ , because they are in the same Group ?

      …i know im asking like a lot of questions , but i love the FOG , i just dont know , exactly , how it works 😞 … and i think there are others how search questions for dummies 🙂
      And the las thing , excuse my misspells 🙂 Me not actualy American 🙂 me is from Romania 🙂

      posted in Tutorials
      AlexPDXA
      AlexPDX
    • RE: kernel panic-not syncing: VFS: unable to mount root fs on unknown block(1,0)

      It’s done …I have completely installed the virtual machine but also the fog server with the latest version, at the moment it seems that everything works just fine, I managed to capture the image of windows 10 with MBR, also did a full inventory of the work station , i deployed it on another workstation … momentarily I’m with kernel 4.19.36 … I’m thinking to update it at 4.19.48 … but I doubt it will not come up with the same problem … however i will try anyway 🙂
      10x for the help ! …specialy @george1421 but also @Tom-Elliott ( apparently the problem started from the location where my images are saved…bad cfg )

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: kernel panic-not syncing: VFS: unable to mount root fs on unknown block(1,0)

      @george1421 :

      #!ipxe
      set fog-ip 192.168.192.111
      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.192.111/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)
      item FOG_1.5.5 FOG Server
      choose --default FOG 1.5.5 --timeout 3000 target && goto ${target}
      :fog.local
      chain -ar ${boot-url}/service/ipxe/grub.exe --config-file="rootnoverify (hd0);chainloader +1" || goto MENU
      :fog.memtest
      kernel memdisk initrd=memtest.bin iso raw
      initrd memtest.bin
      boot || goto MENU
      :fog.reginput
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 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=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 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
      param sysuuid ${uuid}
      :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
      param sysuuid ${uuid}
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :FOG_1.5.5
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://192.168.192.111/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      

      and …

      #!ipxe
      set fog-ip 192.168.192.111
      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.192.111/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 Windows10-CLEAN!
      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)
      item FOG_1.5.5 FOG Server
      choose --default FOG 1.5.5 --timeout 3000 target && goto ${target}
      :fog.local
      exit || goto MENU
      :fog.memtest
      kernel memdisk initrd=memtest.bin iso raw
      initrd memtest.bin
      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
      param sysuuid ${uuid}
      :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
      param sysuuid ${uuid}
      :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
      param sysuuid ${uuid}
      :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
      param sysuuid ${uuid}
      :fog.sysinfo
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 loglevel=4 mode=sysinfo
      imgfetch init_32.xz
      boot || goto MENU
      :FOG_1.5.5
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://192.168.192.111/fog/ consoleblank=0 rootfstype=ext4 storage=192.168.192.111:/images/ storageip=192.168.192.111 loglevel=4
      imgfetch init_32.xz
      boot || goto MENU
      :bootme
      chain -ar http://192.168.192.111/fog/service/ipxe/boot.php##params ||
      goto MENU
      autoboot
      

      [Mod note] Fixed post for readability -geo

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • RE: kernel panic-not syncing: VFS: unable to mount root fs on unknown block(1,0)

      I did not expose myself correctly … my bad : )  … I use the IBM Blate server for virtual machines … each one has its own separate work … and I have taken resources from the server to create a Fog Server. I followed the instalation steps exactly … and this error occurred while trying to capture a workstation with windows 10 MBR

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • kernel panic-not syncing: VFS: unable to mount root fs on unknown block(1,0)

      Hello…im geting this error with FOG 1.5.6
      im using IBM Blade Server with virtualisation…all of the other machines seam to work fine with no problems
      20190618_120118.jpg

      posted in FOG Problems
      AlexPDXA
      AlexPDX
    • 1 / 1