Fog Version: 1.5.7
Server OS: Debian 10.0

I set up a new server yesterday to begin imaging some win 10 laptops and after getting the server set up and I started capturing the image from the base laptop and I left it to go over night. I have not touched the web server password and thus it should be the default still. However when I try to log in the page just resets and does not let me log in. I still have access to the Debian CLI.

Update: I was not able to start deploying the image from the PXE boot menu. It asked me for the GUI user and pass and the default make the screen freeze on Attempting to Register Host

It turns out one of our nodes was down and as soon as it went back up replication resumed for all of our nodes

Server

• FOG Version: 1.4.2 (with fix)
• OS: Debian 8

Client

• Service Version:
• OS:

Description

Our Images are not replicating to our nodes for some reason. Here is our image replicator log:

[07-20-17 3:02:06 pm] * Deleting remote file: /images/postdownloadscripts/
[07-20-17 3:02:06 pm] | CMD:
			lftp -e 'set xfer:log 1; set xfer:log-file "/opt/fog/log/fogreplicator..transfer.Pastore FogNode.log";set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-total-rate 0:1280000; mirror -c -r -R --ignore-time -vvv --exclude ".srvprivate" "/images/postdownloadscripts" "/images/postdownloadscripts"; exit' -u fog,[Protected] 131.128.50.238
[07-20-17 3:02:06 pm] * Started sync for Image postdownloadscripts
[07-20-17 3:03:37 pm] * Type: 2, File: /var/www/html/fog/lib/service/fogservice.class.php, Line: 274, Message: fclose() expects parameter 1 to be resource, boolean given, Host: 131.128.54.239, Username: fog
[07-20-17 3:12:06 pm] * Starting Image Replication.
[07-20-17 3:12:06 pm] * We are group ID: 1. We are group name: default
[07-20-17 3:12:06 pm] * We are node ID: 1. We are node name: Ecc-FogServer
[07-20-17 3:12:06 pm] * Attempting to perform Group -> Group image replication.
[07-20-17 3:12:06 pm] | Replicating postdownloadscripts
[07-20-17 3:12:06 pm] * Found Image to transfer to 3 nodes
[07-20-17 3:12:06 pm] | File Name: postdownloadscripts
[07-20-17 3:12:06 pm] | Replication already running with PID: 29715
[07-20-17 3:12:06 pm] | 235 0 /images/postdownloadscripts/fog.postdownload 
[07-20-17 3:12:06 pm] | Files do not match.
[07-20-17 3:12:06 pm] * Deleting remote file: /images/postdownloadscripts/
[07-20-17 3:12:06 pm] | CMD:
			lftp -e 'set xfer:log 1; set xfer:log-file "/opt/fog/log/fogreplicator..transfer.Pastore FogNode.log";set ftp:list-options -a;set net:max-retries 10;set net:timeout 30; set net:limit-total-rate 0:1280000; mirror -c -r -R --ignore-time -vvv --exclude ".srvprivate" "/images/postdownloadscripts" "/images/postdownloadscripts"; exit' -u fog,[Protected] 131.128.50.238
[07-20-17 3:12:06 pm] * Started sync for Image postdownloadscripts
[07-20-17 3:13:37 pm] * Type: 2, File: /var/www/html/fog/lib/service/fogservice.class.php, Line: 274, Message: fclose() expects parameter 1 to be resource, boolean given, Host: 131.128.54.239, Username: fog

Works fine thank you for your help!

@Tom-Elliott Okay it seems to have worked. It’s past the error and is deploying now

@Tom-Elliott We’re re-capturing the image as an MPS now

@Quazz

total 93G
drwxrwxrwx 2 root root 4.0K Jul 13 12:22 .
drwxrwxrwx 8 fog  root 4.0K Jul 13 12:22 ..
-rwxrwxrwx 1 root root 1.0M Jul 13 11:15 d1.mbr
-rwxrwxrwx 1 root root 303M Jul 13 11:15 d1p1.img
-rwxrwxrwx 1 root root  93G Jul 13 12:22 d1p2.img
-rwxrwxrwx 1 root root  190 Jul 13 11:15 d1.partitions

@Tom-Elliott Sorry haha we’re running 1.4.2 (with the web root fix)

Server

• FOG Version: 1.5.2
• OS: Debian

Client

• Service Version:
• OS: Windows 10

Description

Trying to capture and deploy an image, it captures fine and then when we try to deploy it we get this error message.
Our other images also seem to have this error despite working previously,

We built a base image with the fog client (smart installer for windows) captured and deployed it and we can connect it to active directory after deployment, but after we start building on top of this image we cant get it to join our domain using active directory. any possible solutions for this type of problem?

I figured it out. We messed around with our sql password. I just fixed it an now it works. So I can’t capture images from a node right?

@george1421 I just updated to be safe but it still says this

@george1421
The issue is with imaging, because there is a chainloading error. Could it be that the server and the node are on different versions of fog? 1.4.1 and 1.4.2?

@Wayne-Workman @george1421
The DHCP SHOULD already be set up, and it seems like it is because the computers PXE boot to the fog node. The problem is that the node cannot connect to our main server for some reason. We can’t seem to get it to appear on the dash.

Server

• FOG Version: 1.4.1 (with fix)
• OS: Debian 8.8

Client

• Service Version:
• OS:

Description

Trying to set up a deployment node in a remote leased space which has a different DHCP server and is on a different subnet that will still connect to our main server. The DHCP has a specified PXE boot ip and we can’t easily change that. We set up the node to have a static ip on that ip and followed the rest of the node set up instructions. The computers in that lab connect to the node but have a chainloading error boot loop and the node does not appear in the gui dashboard storage node disk usage tab.

@bretfred
Check my post for the fix

@Tom-Elliott

Fixed for my fresh install!

@ddeatrich
I’m also getting this error but I didn’t think much of it either

@george1421
This might make sense because I’m replacing a pre-existing network of nodes but i just turned them off and it didn’t fix my issue I can post the error log if that helps.

@george1421
ddeatrich was the one who posted that