Posts made by sbenson

@george1421 Two totally separate installations. No database restorations or anything. Nothing cloned at all. Both default.ipxe’s show the correct IP addresses

@george1421
We confirmed that the MHB network ranges both hit the MHB server x.x.57.42. SRO is currently hosted on x.x.76.44, and the Scope in SRO reflects the same.

Ideally we want SRO and MHB to be two separate servers, but sync the images between eachother. When I log into the MHB server it doesn’t show any of the images listed on SRO, it only shows the ones locally on MHB. To add to the confusion, I have added a list of ALL of our currently deployed machines to the SRO hosts. These also do not show up when logging into the MHB server.

They were both setup to be Full installs, I am unsure how to make one only a Storage Node.
The MHB server has a “SRO” storage node listed. Which is what I was told was required to get replication to work. Even after the “SRO” storage node had “Is Enabled unchecked” it was still pulling data from SRO.

Server

• FOG Version: 1.3.0-RC-36 Rev 6048
• OS: Ubuntu 16.04

Description

In our environment we have 2 fog Servers, one In Northern California(SRO) and one in Southern California(MHB). The fog server in SRO runs fine, speeds are great, 3 minute laptop deployments, gigabit speed, etc. Last Friday I was working with someone in MHB showing him how to use fog and the speeds were about 100mbps. He was plugged into a switch and guessed that the switch wasn’t Gig. Later I found out from out network admin that something was saturating the link between MHB and SRO(100mb link). We found that it was the fog server. I do have a Storage Node setup from MHB that(from my understanding) is supposed to sync images from SRO. Does the storage node just tell the machine to pull images from another server in the same node? Why when I till it to pull an image that is on the local machine is it pulling from the remote machine? Should I just disable the nodes and manually sync the images from SRO to MHB? Last Friday I disabled the Storage node and today I had the network guy message me saying that it’s happening again.

Was I wrong in understanding that FogReplicator was supposed to sync images from SRO to MHB?

How can I reliably sync the images from one machine to another?

Why when I point a host at a local image is it pulling an image with the same name from the remote host?

@Quazz Thanks, this will work, setting it to 87000 so it is just over 24hrs, that way I can unthrottle it and have the service start at 2am. Each image takes about 30 mins so I cannot imagine this being a problem at 7am when people start showing up. Thanks!

@Wayne-Workman This worked. Just making the parent /images folder as fog:root vs root:root. Thanks.

Is there a way to only enable replication between certain times?
IE. 11pm-6am?

The only thing I can think of is running a cron that stops and starts the service at those times. But that seems a little messy.

@Tom-Elliott Thank you for the clarification. I did run into an error though.

[12-08-16 11:30:22 pm]  * Found Image to transfer to 1 node
[12-08-16 11:30:22 pm]  | Image Name: W7P-HP6300
[12-08-16 11:30:23 pm]  | W7P-HP6300: No need to sync d1.fixed_size_partitions file to SyncMHB
[12-08-16 11:30:23 pm]  | W7P-HP6300: No need to sync d1.mbr file to SyncMHB
[12-08-16 11:30:23 pm]  | W7P-HP6300: No need to sync d1.minimum.partitions file to SyncMHB
[12-08-16 11:30:23 pm]  | W7P-HP6300: No need to sync d1.original.fstypes file to SyncMHB
[12-08-16 11:30:24 pm]  | W7P-HP6300: No need to sync d1.original.swapuuids file to SyncMHB
[12-08-16 11:30:24 pm]  | W7P-HP6300: No need to sync d1.partitions file to SyncMHB
[12-08-16 11:30:24 pm]  | W7P-HP6300: No need to sync d1p1.img file to SyncMHB
[12-08-16 11:30:24 pm]  | W7P-HP6300: No need to sync d1p2.img file to SyncMHB
[12-08-16 11:30:24 pm]  * Found Image to transfer to 1 node
[12-08-16 11:30:24 pm]  | Image Name: W7P-T460s
[12-08-16 11:30:26 pm]  * Starting Sync Actions
[12-08-16 11:30:26 pm]  | CMD:
                        lftp -e 'set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-total-rate 0:256000;set net:limit-rate 0:256000; mirror -c -R --ignore-time -vvv --exclude "dev/" --exclude "ssl/" --exclude "CA" --delete-first '/images/W7PT460s' \''/images/W7PT460s'\'; exit' -u fog,[Protected] 10.63.xxx.xxx
[12-08-16 11:30:26 pm]  * Started sync for Image W7P-T460s
mirror: Access failed: 550 Failed to change directory. (/images/W7PT460s)

Are there specific permissions the images folder needs? I have just left this as the default

@Tom-Elliott I think what you said made me realize how the Replication works.

Is it that the Master server has multiple nodes setup under the default group and it pushes the updates to them?

I was thinking I had to set the slaves to pull data from the master, so both sides needed to be setup. The Master acting as a master, accepting connections, and the Slaves needing the Master’s IP to pull data.

I had the Master setup with one Node, and the slave setup with the Master’s IP like it was going to try to pull data.

From what I gathered: The Master needs to have a node for each slave, and the slave servers need to have the master setup to allow the connection in?

Server

• FOG Version: 1.3.0-RC-22
• OS: Ubuntu 16.04.1 LTS

Client

• Service Version: not in use
• OS:

Description

I have the replication setup in the method I would think would be working.

On the Storage Node Management both sides have everything identical, except for the master has “Is Master Node” checked.

The Master node logs show

[12-08-16 8:46:32 pm]  * Starting Image Replication.
[12-08-16 8:46:32 pm]  * We are group ID: 1. We are group name: default
[12-08-16 8:46:32 pm]  * We are node ID: 1. We are node name: SyncSRO
[12-08-16 8:46:32 pm]  * Attempting to perform Group -> Group image replication.
[12-08-16 8:46:32 pm]  * Not syncing Image between groups
[12-08-16 8:46:32 pm]  | Image Name: W7E-HP600G2
[12-08-16 8:46:32 pm]  | There are no other members to sync to.
[12-08-16 8:46:32 pm]  * Not syncing Image between groups
[12-08-16 8:46:32 pm]  | Image Name: W7E-OS-Install
[12-08-16 8:46:32 pm]  | There are no other members to sync to.
...

and the slave node says

[12-08-16 8:23:38 pm]  *  | This is not the master node
[12-08-16 8:33:38 pm]  *  | This is not the master node

I have re-entered all of the settings, verified the passwords match, etc. I cannot seem to get this to work and there doesn’t seem to be a post/question with an example on how to set it up correctly.

Anyone mind showing me what they have setup? Or suggestions on how to fix mine. Thanks in advance.

Server

• FOG Version: 1.3.0-rc11 svn 5956
• OS: Ubuntu 16.04.1

Description

Fog’s home display is showing the wrong data for “Uptime” Before I refreshed the page it said 32 days. Now it says
System Uptime 2 days 0 hrs 0 mins

[08:13:23] sbenson@SRO-FOG-01[0]:~$ uptime
 08:16:09 up 2 days, 16:59,  1 user,  load average: 0.02, 0.07, 0.05

@Tom-Elliott the backup was my fault. To gain access to the internet I have to swap cables. When I did the “real” dhcp server gave that server a different ip. The database had the old info.

Ok, so there MIGHT be another issue with SSL and upgrading. I am running the upgrade and it says to go to http://192.168.76.10/fog/management to complete the schema upgrade.

upon doing so I get a “this connection is not secure”. I add the cert and it takes me to the standard dashboard. nothing that updates the schema. I am not sure if the update only shows up when there are actually changes that need to be made or not.

Edit: But it looks like my old IP is still listed inside the database.

@Wayne-Workman

Turning on debugging and I found this

* Backing up database.........................................+ return 0
+ [[ -d /home//fog_web_1.3.0-RC-10.BACKUP ]]
+ [[ ! -d /home//fogDBbackups ]]
++ date +%Y%m%d_%I%M%S
+ wget --no-check-certificate -O /home//fogDBbackups/fog_sql_1.3.0-RC-10_20160920_031708.sql http://192.168.76.169//fog//maintenance/backup_db.php '--post-data=type=sql&fogajaxonly=1'
+ errorStat 4
+ local status=4
+ [[ 4 != 0 ]]
+ echo 'Failed!'
Failed!
+ [[ -z '' ]]
+ exit 1

http://192.168.76.169/fog/status/bandwidth.php?type=sql&fogajaxonly=1 is unable to connect
where
http://127.0.0.1/fog/status/bandwidth.php?type=sql&fogajaxonly=1 does work, but provides back

{"dev":"Unknown","rx":0,"tx":0}

EDIT: This is my fault. I am in a devel environment and I am swapping cables as to not mess up the current DHCP server(overlapping ranges, etc). It looks like my IP has changed. The database issue is on my end

define('FOG_VERSION', '1.3.0-RC-10');
        define('FOG_SCHEMA', 234);
        define('FOG_BCACHE_VER', 100);
-        define('FOG_SVN_REVISION', 5954);
+        define('FOG_SVN_REVISION', 5955);
        define('FOG_CLIENT_VERSION', '0.11.5');

I was looking to force SSL and found that you can run the install with a -S. I attempted this and had an error restarting apache

* Setting up SSL FOG Server...................................OK
* Restarting Apache2 for fog vhost............................Failed!

Upon looking into the problem I found that line 9 of the apache conf for fog had a syntax error

Sep 20 14:39:38 Fog-Dev apache2[18425]: AH00526: Syntax error on line 9 of /etc/apache2/sites-enabled/001-fog.conf:
Sep 20 14:39:38 Fog-Dev apache2[18425]: Invalid command '-e<VirtualHost', perhaps misspelled or defined by a module not included in th

Looking into the config file I found this trainwreck.

-e<VirtualHost *:443>\n\tKeepAlive Off\n\tServername 192.168.76.169\n\tDocumentRoot /var/www/html/\n\tSSLEngine On\n\tSSLProtocol all -SSLv3 -SSLv2\n\tSSLCipherSuite ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA\n\tSSLHonorCipherOrder on\n\tSSLCertificateFile /var/www/html/fog//management/other/ssl/srvpublic.crt\n\tSSLCertificateKeyFile /opt/fog/snapins/ssl//.srvprivate.key\n\tSSLCertificateChainFile /var/www/html/fog//management/other/ca.cert.der\n</VirtualHost>

I can manually fix this(I think), but the install script should have this fixed.
EDIT1:
Update functions.sh. It’s missing a space.

sed -i 's/-e"/-e "/' trunk/lib/common/functions.sh

EDIT2:
After the update to functions.sh it successfully starts apache, but now has and error backing up the database.

* Resetting SSL Permissions...................................OK
* Setting up SSL FOG Server...................................OK
* Restarting Apache2 for fog vhost............................OK
* Changing permissions on apache log files....................OK
* Backing up database.........................................Failed!

@Matthieu-Jacquart @Quazz On completion of pushing the image does it expand the disks, or is that left to me?

I have a new laptop with a 250gb SSD(or something close to that) running windows 7. I tried imaging the laptop and I accidentally left it on “Single Disk - Resizable”. Is this going to cause a problem for that machine, or after imaging does it expand the disk back to the full size?

Is there a benefit/drawback to using "Single Disk Resizable/Multiple Partition Image - Single Disk (Not Resizable)?

@george1421 Confirmed it was the cruft left over when the machine was being installed(it didn’t like 2 IP’s assigned to one interface I guess).

Next quick question. Is there a way to convert a clonezilla image to work with FOG?

Unfortunately that machine is in a devel environment. But I see what the problem is. During install it said the IP of the server was 192.168.76.169\n10.254.254.10. It is giving me a login error with the username of “192.168.76.169\n10.254.254.10”. I thought I fixed all of those entries in the database. Let me see if there is another location with that crufy data

@george1421 said in Could not boot: Input/Output error(http://ipxe.org/1d0c6539):

What that will do is tell FOG to create the iPXE menu specifically for that target computer (where you’ve told it to capture/deploy). You need the mac address of that specific target in the form of 00:00:00:00:00:00 post the output here.

#!ipxe
set fog-ip 192.168.76.169
set web-root fog
set boot-url http://${fog-ip}/${web-root}