Thank you for this information. I will have to come back to this at a later date though. I really do want to continue with this but our school district is in the middle of preparing machines and we’re relying on FOG heavily right now. I am not a Linux user so everything is new to me right now, so if we lose FOG, it will set us back a bit. Once projects are done I will come back to this. Thanks again.
X
Posts made by xburnerx00
-
RE: Problems after adding storageposted in FOG Problems
-
RE: Problems after adding storageposted in FOG Problems
[root@fogserver ~]# pvs PV VG Fmt Attr PSize PFree /dev/sda3 centos lvm2 a-- 464.56g 4.00m[root@fogserver ~]# vgs VG #PV #LV #SN Attr VSize VFree centos 1 4 0 wz--n- 464.56g 4.00m[root@fogserver ~]# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home centos -wi-ao---- 10.00g images centos -wi-ao---- <426.81g root centos -wi-ao---- 20.00g swap centos -wi-ao---- 7.75g -
RE: Problems after adding storageposted in FOG Problems
Thank you for the reply. Here are the requested commands.
[centos@fogserver ~]$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=3929676k,nr_inodes=982419,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,seclabel,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,perf_event) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,freezer) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,cpuacct,cpu) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,pids) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,net_prio,net_cls) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,hugetlb) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,devices) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,seclabel,cpuset) configfs on /sys/kernel/config type configfs (rw,relatime) /dev/mapper/centos-root on / type xfs (rw,relatime,seclabel,attr2,inode64,noquota) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14665) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel) mqueue on /dev/mqueue type mqueue (rw,relatime,seclabel) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) /dev/sdb1 on /images2 type xfs (rw,relatime,seclabel,attr2,inode64,noquota) /dev/sda2 on /boot type xfs (rw,relatime,seclabel,attr2,inode64,noquota) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) /dev/mapper/centos-home on /home type xfs (rw,relatime,seclabel,attr2,inode64,noquota) /dev/mapper/centos-images on /images type xfs (rw,relatime,seclabel,attr2,inode64,noquota) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) tmpfs on /run/user/1002 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=789420k,mode=700,uid=1002,gid=1002) tmpfs on /run/user/42 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=789420k,mode=700,uid=42,gid=42) gvfsd-fuse on /run/user/1002/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1002,group_id=1002) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)[centos@fogserver ~]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 3.8G 0 3.8G 0% /dev tmpfs 3.8G 26M 3.8G 1% /dev/shm tmpfs 3.8G 10M 3.8G 1% /run tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup /dev/mapper/centos-root 20G 8.3G 12G 42% / /dev/sdb1 466G 35G 432G 8% /images2 /dev/sda2 1014M 386M 629M 39% /boot /dev/sda1 200M 12M 189M 6% /boot/efi /dev/mapper/centos-home 10G 597M 9.5G 6% /home /dev/mapper/centos-images 427G 356G 72G 84% /images tmpfs 771M 36K 771M 1% /run/user/1002 tmpfs 771M 12K 771M 1% /run/user/42[centos@fogserver ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 200M 0 part /boot/efi ├─sda2 8:2 0 1G 0 part /boot └─sda3 8:3 0 464.6G 0 part ├─centos-root 253:0 0 20G 0 lvm / ├─centos-swap 253:1 0 7.8G 0 lvm [SWAP] ├─centos-home 253:2 0 10G 0 lvm /home └─centos-images 253:3 0 426.8G 0 lvm /images sdb 8:16 0 465.8G 0 disk └─sdb1 8:17 0 465.8G 0 part /images2 -
Queues not going in orderposted in Bug Reports
FOG: 1.5.9-RC1
Server: CentOS 7Right now I have a queue of about 40 machines. The machines in queue show this screen
The queue is working, just not in order. Whichever machine detects an opening first, it takes it, instead of the next one that I set up in order. If I remember right, the machine would show which number they are by having the “There are ## before me.” Is there a way to get the queue back in order?
I think this may be related to a database issue I had here.
Thank you
-
RE: Problems after adding storageposted in FOG Problems
@xburnerx00 said in Problems after adding storage:
storage=192.168.10.200:/images2/ storageip=192.168.10.200
Thank you for the reply.
Yes, this line change to the GRUB file seems to have worked, but it causes another issue. Now when I try to deploy an image that is stored in the original storage node, FOG says that the original storage node cannot be found, because I think it is only looking in the second storage node. Is there a way to change the GRUB on the usb where it would look through both storages for images?
I’m thinking I change the line to this, just not sure.
storage=192.168.10.200:/images storage=192.168.10.200:/images2/ storageip=192.168.10.200Thank you.
-
RE: Problems after adding storageposted in FOG Problems
This is the grub.cfg on the USB. Where do I put the line? Near the top with the lines that say set? Do I add ‘set’? before the lines you asked me to try? Are the lines two separate lines? Sorry, for all the questions.
set myfogip=192.168.10.200 set myimage=/boot/bzImage set myinits=/boot/init.xz set myloglevel=4 set timeout=-1 insmod all_video menuentry "1. FOG Image Deploy/Capture" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "2. Perform Full Host Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=manreg echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "3. Quick Registration and Inventory" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=autoreg echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "4. Client System Information (Compatibility)" { echo loading the kernel linux $myimage loglevel=$myloglevel initrd=init.xz root=/dev/ram0 rw ramdisk_size=275000 keymap= web=$myfogip/fog/ boottype=usb consoleblank=0 rootfstype=ext4 mode=sysinfo echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "5. Run Memtest86+" { linux /boot/memdisk iso raw initrd /boot/memtest.bin } menuentry "6. FOG Debug Kernel" { echo loading the kernel linux $myimage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=275000 keymap= boottype=usb consoleblank=0 rootfstype=ext4 isdebug=yes echo loading the virtual hard drive initrd $myinits echo booting kernel... } menuentry "7. FOG iPXE Jumpstart BIOS" { echo loading the kernel linux16 /boot/ipxe.krn echo booting iPXE... } menuentry "8. FOG iPXE Jumpstart EFI" { echo chain loading the kernel insmod chain chainloader /boot/ipxe.efi echo booting iPXE-efi... } -
RE: Problems after adding storageposted in FOG Problems
@Sebastian-Roth said in Problems after adding storage:
storage=192.168.10.200:/images2/ storageip=192.168.10.200
Thank you for the reply.
Where exactly do I add this line? On the grub.cfg file on my USB boot? That is the only place I remember making changes on the drive when I followed the instructions from here.
-
Problems after adding storageposted in FOG Problems
Server OS: CentOS 7
FOG Version: 1.5.9-RC1I recently installed a new hard drive to expand storage for images on the master FOG node. I followed the instructions here: Adding additional image storage space to FOG server. Everything seems fine with the install so I did a test image.
FOG captured the image to the new storage node and the target machine restarted and booted normal. One problem is in the Tasks menu, the machine stayed “In-Progress” (No screen shot of that.) I cancel it and check Images and it shows…
I figured it is a bug so we’ll see when the image is deployed. I set the task to target machine, machine picks up task, but I get this error…
Tasks shows that the task is stuck in progress…
This is where I am stuck.
Deployment of another image that is stored on the original storage space deployed with no problems.
Thank you.
-
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
Yes, the Dell Latitude 3189 are laptops that do not have internet ports and we had to use USB adapters. At that time, the version of FOG didn’t like same MACs for multiple machines. So the way I got around that was deleting the hosts since it was tied to a MAC from a USB and I was more concerned with just getting them imaged. I guess I deleted them prematurely. Unless I just overlooked something completely and did something wrong.
As for the deploy task ones, I’m not sure why they were stuck in there. They may have been ones that seemed to be giving me imaging problems and I turned off the machine before canceling it in the task menu.
-
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
MariaDB [fog]> SELECT * FROM hosts WHERE hostID IN ( 515, 401, 513, 529, 532, 584 ); Empty set (0.00 sec) MariaDB [fog]> SELECT * FROM images WHERE imageID IN ( 32, 33, 13 ); +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ | imageID | imageName | imageDesc | imagePath | imageProtect | imageMagnetUri | imageDateTime | imageCreateBy | imageBuilding | imageSize | imageTypeID | imagePartitionTypeID | imageOSID | imageFormat | imageLastDeploy | imageCompress | imageEnabled | imageReplicate | imageServerSize | +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ | 13 | DellOP3050 | | DellOP3050 | 0 | | 2019-07-17 15:31:36 | fog | 0 | 524283904.000000:204800.000000:104857600.000000:16777216.000000:9948450.000000:40748851200.000000: | 1 | 1 | 9 | 0 | 2020-05-11 12:54:12 | 6 | 1 | 1 | 19663157396 | | 32 | Dell Latitude 3189 | | DellLatitude3189 | 0 | | 2020-03-14 09:27:01 | fog | 0 | 554692608.000000:104857600.000000:16777216.000000:25425911808.000000: | 1 | 1 | 9 | 0 | 2020-03-14 11:52:34 | 6 | 1 | 1 | 14588521696 | | 33 | HP 400 G1 | | HP400G1 | 0 | | 2020-05-13 07:39:14 | fog | 0 | 554692608.000000:104857600.000000:16777216.000000:8306813.000000:34024706048.000000: | 1 | 1 | 9 | 5 | 2020-05-13 08:05:09 | 6 | 1 | 1 | 16054171954 | +---------+--------------------+-----------+------------------+--------------+----------------+---------------------+---------------+---------------+----------------------------------------------------------------------------------------------------+-------------+----------------------+-----------+-------------+---------------------+---------------+--------------+----------------+-----------------+ 3 rows in set (0.00 sec) -
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
@Tom-Elliott said in Storage Group Activity data displaying wrong information:
UPDATE tasks SET taskStateID = 4 WHERE taskID IN (‘756’,‘905’,‘754’,‘771’,‘777’,‘908’);
Yes, thank you, that worked.
Any idea on what may have caused this, and how to avoid in the future?
-
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
MariaDB [fog]> SELECT * FROM tasks WHERE taskStateID IN ( 0, 1, 2, 3 ); +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ | taskID | taskName | taskCreateTime | taskCheckIn | taskHostID | taskImageID | taskStateID | taskIsDebug | taskCreateBy | taskForce | taskScheduledStartTime | taskTypeID | taskPCT | taskBPM | taskTimeElapsed | taskTimeRemaining | taskDataCopied | taskPercentText | taskDataTotal | taskNFSGroupID | taskNFSMemberID | taskNFSFailures | taskLastMemberID | taskWOL | taskPassreset | taskShutdown | +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ | 756 | AutoRegTask - IS-STU-SL-03 | 2020-03-14 13:15:35 | 2020-03-14 13:28:02 | 515 | 32 | 1 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | | 905 | Deploy Task - HS-103-SD-17 | 2020-05-13 12:30:18 | 0000-00-00 00:00:00 | 401 | 33 | 1 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | | 754 | Deploy Task - IS-STU-SL-16 | 2020-03-14 13:08:01 | 2020-03-14 13:12:05 | 513 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000014 | 4.20GB | 00:00:50 | 00:05:04 | 3.264 GiB | 14.12 | 23.680 GiB | 1 | 1 | | 0 | 0 | | | | 771 | AutoRegTask - IS-STU-SL-21 | 2020-03-14 16:05:24 | 2020-03-14 16:07:06 | 529 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000074 | 1.85GB | 00:00:11 | 00:00:03 | 415.80 MiB | 74.05 | 529.00 MiB | 1 | 1 | | 0 | 0 | | | | 777 | AutoRegTask - IS-STU-SL-18 | 2020-03-14 16:27:08 | 2020-03-14 16:28:24 | 532 | 32 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000061 | 25.17MB | 00:00:55 | 00:00:35 | 23.26 MiB | 60.50 | 100.00 MiB | 1 | 1 | | 0 | 0 | | | | 908 | AutoRegTask - HS-104-SD-13 | 2020-05-13 12:49:04 | 2020-05-13 12:50:03 | 584 | 13 | 3 | 0 | fog | 0 | 0000-00-00 00:00:00 | 1 | 0000000000 | | | | | | | 1 | 1 | | 0 | 0 | | | +--------+----------------------------+---------------------+---------------------+------------+-------------+-------------+-------------+--------------+-----------+------------------------+------------+------------+----------+-----------------+-------------------+----------------+-----------------+---------------+----------------+-----------------+-----------------+------------------+---------+---------------+--------------+ 6 rows in set (0.00 sec) Hard to see for me, but I see tasks that were set back in March 14, 2020 and May 15, 2020. MariaDB [fog]> SELECT * FROM multicastSessions WHERE msState IN ( 0, 1, 2, 3 ); Empty set (0.00 sec)I’ve never done Multicast sessions so I would think this should be empty.
-
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
Updated 1.5.7 to 1.5.9-RC1
-
RE: Storage Group Activity data displaying wrong informationposted in FOG Problems
@xburnerx00
Forgot to add version.Version 1.5.9-RC1 -
Storage Group Activity data displaying wrong informationposted in FOG Problems
On the dash board it’s showing I have queued and active tasks but that’s not true. Is there a way to reset this and show correct information?
-
RE: Problem with FOS USB bootposted in General Problems
Great point on flexibility @george1421, any idea on how to get the ipxe jumpstarters working? I have been using the USB to capture and deploy but I think I may need them eventually and it would be nice to use all features available if needed.
-
RE: Problem with FOS USB bootposted in General Problems
Thanks @Sebastian-Roth, changing those settings worked. The FOS USB works now. I was able to register and capture a test image from a laptop that does not have ethernet ports. I tested 3 different USB Ethernet dongles and they were all recognized. Saves me headaches of working on two different models of laptops numbering into the 200’s without ethernet ports.
Concerning the iPXE jumpstarters, I have the machines I tested on set to Legacy BIOS. Unless I am missing something, I do not see the reason why to use those now that the USB is working. As long as I can register a machine and capture/deploy now, I think that’s all I need. Right?
-
Problem with FOS USB bootposted in General Problems
I created a FOS USB using a CentOS7 server running FOG 1.5.7 following the instructions provided here. I followed the steps specifically for CentOS7.
I can boot into the menu and upon selection it starts the process and then it errors out.
I also get these errors when I choose FOG iPXE Jumpstart BIOS or FOG iPXE Jumpstart EFI
Some guidance would be appreciated.
Thank you.
-
RE: Image not compressingposted in FOG Problems
Very true. I submitted a request for a few more hdd. I wanted ssd but people in charge dont think they’re worth it for old machines.
Thanks again.
