I’m on CentOS 7 using FOG 1.5.0. Can anyone tell me how to schedule image replication for after hours? It’s killing our daytime bandwidth to have it replicate to so many storage nodes during work hours. I’ve read that I need to use a cron job to start the service and then another cron job to stop it. Can anyone tell me the exact Linux commands to do this? I’m a Windows guy and this particular Linux command is evading me.
Posts made by kafluke
-
How do I schedule FOG image replication for after hours?
-
RE: Help me understand Storage Nodes
The problem seams to have self resolved. This can be closed. FYI, nobody changed any settings. It just started pulling from the correct node on its own.
-
RE: Help me understand Storage Nodes
I’ve gone ahead and disabled all other storage nodes except the master until I can get this figured out. It’s trying to pull images from nodes where those images don’t even exist???
-
Help me understand Storage Nodes
Please help me understand how FOG chooses what storage node to pull the image from. I thought that if you assigned a storage node to a specific location and then assign a host to that location that it would only pick from that storage node. Here’s my situation.
I have one master node and I am building up over 30 remote storage nodes. I have 3 “child” nodes in the same storage group as the master and the master is correctly replicating images to the three child nodes. I have assigned each child node to a specific location.
Whenever I image a new system now it seems to randomly pull the image from any one of the 3 child nodes. It doesn’t matter if I tell the host to only use a specific location, it still pulls the image from one of the other nodes. What am I doing wrong?
-
RE: Lost network config on Linux image after deploying
This has been resolved. I updated to FreePBX 14 (CentOS 7) on the golden image and it correctly sets up the NIC’s on the imaged machines. Thanks for the help
-
RE: Replication not working. Says storage node "does not appear to be online"
Okay I feel really stupid. Replication was not working because the server system time was not set correctly. Go ahead and marked this solved
-
RE: Replication not working. Says storage node "does not appear to be online"
@wayne-workman Yes it has been set to permissive on both servers
-
RE: Replication not working. Says storage node "does not appear to be online"
@george1421 It’s a VM running CentOS 7 and I ran the installer and chose “storage” when prompted. Yes I can ping both ways
-
RE: Replication not working. Says storage node "does not appear to be online"
@tom-elliott Web interface says 1.5.0. I checked out dev-branch and installed today.
-
Replication not working. Says storage node "does not appear to be online"
I just tried my first storage node config. I built a VM using CentOS 7 and latest FOG trunk build. Everything seemed to go smoothly during the install and when I was done the storage node immediately showed up on my master FOG server. I created a group and location and assigned one image to it for replication testing. I called the storage node “Park City Fog VM Server” and here is what the log shows:
[03-05-18 7:33:49 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:48 pm] | Image Name: Windows 7 Pro Generic 64-bit
[03-05-18 7:33:48 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:48 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:48 pm] | Image Name: FreePBX 13 Generic
[03-05-18 7:33:48 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:48 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:47 pm] | Image Name: Dell Optiplex 7050 Win10 Pro 3-1-18
[03-05-18 7:33:47 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:47 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:46 pm] | Image Name: Dell Optiplex 7040 Win10 Pro 3-5-18
[03-05-18 7:33:46 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:46 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:45 pm] | Image Name: Dell Latitude E7270 Win10 Pro 3-1-18
[03-05-18 7:33:45 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:45 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:44 pm] | Image Name: Dell Latitude E5470 Win10 Pro 1-3-18
[03-05-18 7:33:44 pm] * Found Image to transfer to 1 node
[03-05-18 7:33:44 pm] Park City Fog VM Server does not appear to be online.
[03-05-18 7:33:40 pm] | Image Name: Dell Latitude E5450 Win10 Pro 3-1-18Why does it say that it’s offline? I can putty into the node just find and like I said it automatically talked to the FOG master server and added itself as a node so they must be talking to each other.
-
RE: Lost network config on Linux image after deploying
@george1421 I’m going to try and build a golden image using FreePBX 14 (the latest stable build) and see if the issue persists
-
RE: Lost network config on Linux image after deploying
@george1421 FreePBX 13 is what we’re using. Here is a screenshot of the golden image that I want to capture and then deploy:
And here is the image deployed. Notice the missing IP’s. I need to be able to deploy this remotely to a site and then take over using SSH but they aren’t getting any DHCP IP’s:
I did try deleting the file “70-persistent-net.rules” and rebooting but it didn’t do anything
-
RE: Lost network config on Linux image after deploying
@sebastian-roth I believe that FreePBX is a version of CentOS which is Red Hat based. I try some of your suggestions and report back. Thanks.
-
RE: Lost network config on Linux image after deploying
@Sebastian-Roth , are you saying that in my captured image I already have static naming setup or that I need to first have that setup before I capture? I’ve ready various articles and I’m not sure I follow the logic. This is the last piece that I need to get right before I can start imaging our PBX systems all over the country. Need to have network access after the deploy.
-
Lost network config on Linux image after deploying
After capturing and then deploying a Linux image with FOG I have lost all my network configs. I am trying to build up a base image for FreePBX (CentOS) so that I can image to any fresh hardward. Upon testing, everything works but I lose all the network config. The original image has eth0 and eth1 with DHCP. When I deploy that image to fresh hardware (exact same type of machine as original) the OS shows eth2 and eth3 and they both have NO IP’s and no network access. Any thoughts?
-
RE: First time capturing CentOS Linux image - Drive won't shrink
Okay that was it. Thanks. I reset my image using ext4
-
RE: First time capturing CentOS Linux image - Drive won't shrink
What now? How do I get FOG to shrink when capturing?
-
RE: First time capturing CentOS Linux image - Drive won't shrink
oot@localhost ~]# lvdisplay --- Logical volume --- LV Path /dev/VolGroup/lv_root LV Name lv_root VG Name VolGroup LV UUID 8eSY96-2DZs-XcRb-P5Yk-6cLC-NgKo-khI0x7 LV Write Access read/write LV Creation host, time localhost.localdomain, 2018-01-31 13:10:22 -0500 LV Status available # open 1 LV Size 50.00 GiB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Path /dev/VolGroup/lv_home LV Name lv_home VG Name VolGroup LV UUID wCyqEP-KrM4-Qcfr-5JwM-2i6H-Z3Id-DFuQ9X LV Write Access read/write LV Creation host, time localhost.localdomain, 2018-01-31 13:10:36 -0500 LV Status available # open 1 LV Size 411.41 GiB Current LE 105321 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 --- Logical volume --- LV Path /dev/VolGroup/lv_swap LV Name lv_swap VG Name VolGroup LV UUID rJ669N-nuiy-VzhY-qjpm-QzXc-ljpm-piiPrV LV Write Access read/write LV Creation host, time localhost.localdomain, 2018-01-31 13:11:33 -0500 LV Status available # open 1 LV Size 3.86 GiB Current LE 988 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 [root@localhost ~]# vgdisplay --- Volume group --- VG Name VolGroup System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 465.27 GiB PE Size 4.00 MiB Total PE 119109 Alloc PE / Size 119109 / 465.27 GiB Free PE / Size 0 / 0 VG UUID idHhLk-uM2L-x78s-UkET-3NnG-IaOs-ig2qae [root@localhost ~]# pvdisplay --- Physical volume --- PV Name /dev/sda2 VG Name VolGroup PV Size 465.27 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 119109 Free PE 0 Allocated PE 119109 PV UUID N3L3CC-tvY8-ueht-ydt2-Kj8o-O6pD-zdmxTd [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 77.7M 0 part /boot └─sda2 8:2 0 465.3G 0 part ├─VolGroup-lv_root (dm-0) 253:0 0 50G 0 lvm / ├─VolGroup-lv_swap (dm-1) 253:1 0 3.9G 0 lvm [SWAP] └─VolGroup-lv_home (dm-2) 253:2 0 411.4G 0 lvm /home [root@localhost ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup-lv_root 50G 6.7G 40G 15% / tmpfs 1.9G 0 1.9G 0% /dev/shm /dev/sda1 64M 31M 29M 52% /boot /dev/mapper/VolGroup-lv_home 405G 144M 385G 1% /home
-
RE: First time capturing CentOS Linux image - Drive won't shrink
@tom-elliott I think so yes. How do I tell?