Troubleshoot FTP - Revision history

Wayne-workman.28155: /* Credentials / Passwords */

2016-08-17T17:03:41Z

‎Credentials / Passwords

Wayne-workman.28155: /* Credentials / Passwords */

2016-08-17T17:03:20Z

‎Credentials / Passwords

Wayne-workman.28155: Changed terminology to use capture instead of upload.

2016-07-08T04:19:15Z

Changed terminology to use capture instead of upload.

Wayne-workman.28155: /* You must first upload an image to create a download task */

2016-06-11T20:10:55Z

‎You must first upload an image to create a download task

Wayne-workman.28155: /* Beware, your browser's auto-fill! */

2016-05-25T22:06:35Z

‎Beware, your browser's auto-fill!

Wayne-workman.28155 at 22:04, 25 May 2016

2016-05-25T22:04:21Z

Wayne-workman.28155: /* FTP's roles in FOG */

2016-05-19T16:31:15Z

‎FTP's roles in FOG

Wayne-workman.28155: /* FTP_Put(): Could not create file */

2016-05-03T00:53:16Z

‎FTP_Put(): Could not create file

Wayne-workman.28155: /* Fedora 20/21: */

2016-05-03T00:41:39Z

‎Fedora 20/21:

Wayne-workman.28155: /* Fedora 20/21 */

2016-05-03T00:41:26Z

‎Fedora 20/21

@@ Line 266: / Line 266: @@
 * <font color="red">Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME</font> & <font color="red">FOG_TFTP_FTP_PASSWORD</font>
-*The local 'fog' user's password on the Linux FOG server
+*The local '<font color="red">fog</font>' user's password on the Linux FOG server
 * Server file: <font color="red">/opt/fog/.fogsettings</font> -> password (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)

@@ Line 262: / Line 262: @@
 There are a few places where all the credentials (on a standard install) should match exactly.
-*Web Interface -> Storage Management -> [Your storage node] -> Management Username & Management Password
+* <font color="red">Web Interface -> Storage Management -> [Your storage node] -> Management Username</font> & <font color="red">Management Password</font>
-*Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME & FOG_TFTP_FTP_PASSWORD
+* <font color="red">Web Interface -> FOG Configuration -> FOG Settings -> TFTP Server -> FOG_TFTP_FTP_USERNAME</font> & <font color="red">FOG_TFTP_FTP_PASSWORD</font>
 *The local 'fog' user's password on the Linux FOG server
-*/opt/fog/.fogsettings -> password (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)
+* Server file: <font color="red">/opt/fog/.fogsettings</font> -> password (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)
-*/opt/fog/.fogsettings -> username (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)
+* Server file: <font color="red">/opt/fog/.fogsettings</font> -> username (For recent FOG Trunk versions only. 1.2.0 does not have this setting. 1.3.0 will though.)
 All of those should match (again, on a standard installation).

@@ Line 4: / Line 4: @@
 == FTP's roles in FOG ==
-The primary purpose is moving & renaming image files in the /images/dev folder to the /images folder at the end of an image capture. FTP is not used for image upload or download because NFS is faster. FTP is also used to download kernels and delete images. FTP is also used to report "Image Size: ON SERVER". FTP is also used to ensure the image you wish to deploy exists before starting an image deployment. FTP is also what's used for image replication in multi-server setups.
+The primary purpose is moving & renaming image files in the /images/dev folder to the /images folder at the end of an image capture. FTP is not used for image capture or deployment because NFS is faster. FTP is also used to download kernels and delete images. FTP is also used to report "Image Size: ON SERVER". FTP is also used to ensure the image you wish to deploy exists before starting an image deployment. FTP is also what's used for image replication in multi-server setups.
 FTP should be able to read, write, and delete in /images/dev and /images.
@@ Line 299: / Line 299: @@
 == Interface ==
-The interface defined within storage management for the storage node you are using must be correct for image moving at the end of an upload (from dev to images).
+The interface defined within storage management for the storage node you are using must be correct for image moving at the end of a capture (from dev to images).
 At CLI, you can find the correct interface name by typing <font color="red">ip addr show</font> In the output will be the correct interface name. This is pictured below. In a multi-interface system, there will be multiple interfaces listed. You'll just need to pick the right one. Looking at the IP address assigned to the interface is the first way to determine the correct interface.
@@ Line 387: / Line 387: @@
 === Images stuck in /images/dev ===
-Images upload and are stored in /images/dev/[mac address of host] and they're never moved to /images
+Images captures and are stored in /images/dev/[mac address of host] and they're never moved to /images
-Error messages on client at end of upload, being close to completed:
+Error messages on client at end of capture, being close to completed:
 *FTP move failed
@@ Line 408: / Line 408: @@
 '''NOTE:'''
-Moving images from /images/dev to /images happens during image upload. After attempting to correct the issue, try to re-upload and see if your image gets moved.
+Moving images from /images/dev to /images happens during image capture. After attempting to correct the issue, try to re-capture and see if your image gets moved.
 === Updating Database...Failed ===
@@ Line 419: / Line 419: @@
 Computer will reboot in 1 minute</pre>
-This error is only seen in FOG 1.3.0 and up due to the complete re-write of the upload & download scripts.
+This error is only seen in FOG 1.3.0 and up due to the complete re-write of the capture & deploy scripts.
 Pictured below:
@@ Line 430: / Line 430: @@
 This can be FTP Credentials and Permissions related, please look to the Credentials and Permissions section above.
-=== Large Image - Connection time out during Delete, Upload, and Replication ===
+=== Large Image - Connection time out during Delete, Capture, and Replication ===
 At first glance, this problem looks a lot like the above problem, because it will cause images to be "stuck in /images/dev", however this specific probelm is not credentials related. It's file-system related.
-If your /images directory is '''formated with the ext3''' filesystem you probably run into an issue where deleting the old image in /images/[image name] takes a very long time (minutes with 100GB+ images) and therefore the FTP connection times out and does not rename/move the newly uploaded image from /images/dev/[mac address] to /images/[image name], or may not delete the image from /images.
+If your /images directory is '''formated with the ext3''' filesystem you probably run into an issue where deleting the old image in /images/[image name] takes a very long time (minutes with 100GB+ images) and therefore the FTP connection times out and does not rename/move the newly captured image from /images/dev/[mac address] to /images/[image name], or may not delete the image from /images.
 '''Solution:'''
@@ Line 442: / Line 442: @@
-=== Images won't finish uploading, won't go past "Clearing ntfs flag" ===
+=== Images won't finish capturing, won't go past "Clearing ntfs flag" ===
 [[File:Clearing.ntfs.flag.png]]

@@ Line 363: / Line 363: @@
 [[File:YouMustFirstuploadAnImageToCreateDownloadTask.png]]
-FTP is used to validate that an image exists before creating an image task. When an image does exist, but can't be verified as existing, you will receive the above error. This can be caused by incorrect credentials, permissions, or when the storage node's FTP Path field is blank or incorrect. It's possible that Firewall could be blocking FTP as well.
+FTP is used to validate that an image exists before creating an image task. When an image does exist, but can't be verified as existing, you will receive the above error. This can be caused by incorrect credentials, permissions, or when the storage node's FTP Path field is blank or incorrect. It's possible that Firewall or SELinux could be blocking FTP as well.
 From what the FOG Community has seen in the forums, most people who receive this error have mismatched credentials.

← Older revision		Revision as of 22:06, 25 May 2016
Line 292:		Line 292:

	Often times, when people change a setting in storage management besides the username and password for a node, most web browsers will "auto-fill" the username and password in without you knowing. So if all you've changed is the interface name or replication bandwith or some other setting, it's possible your browser has auto-filled the username and password and when you click "Save", this incorrect auto-filled username and password is stored.		Often times, when people change a setting in storage management besides the username and password for a node, most web browsers will "auto-fill" the username and password in without you knowing. So if all you've changed is the interface name or replication bandwith or some other setting, it's possible your browser has auto-filled the username and password and when you click "Save", this incorrect auto-filled username and password is stored.
		+
		+	The reason for your browser doing this is because of how it's designed. It assumes one set of credentials per site. However, FOG has many sets of credentials, and typically very few of them are the same.

	There are some ways to avoid this. First is to be careful, don't needlessly click the save button if you haven't changed anything. Second, watch the username. In most cases, it should be <font color="red">fog</font>. Watch the password length too. Another way to guarantee (mostly) that auto-fill doesn't fill in these fields is to use your browsers incognito or privacy mode. In incognito or privacy mode, all of your normal browser settings are not used, instead you have a blank slate so auto-fill does not happen.		There are some ways to avoid this. First is to be careful, don't needlessly click the save button if you haven't changed anything. Second, watch the username. In most cases, it should be <font color="red">fog</font>. Watch the password length too. Another way to guarantee (mostly) that auto-fill doesn't fill in these fields is to use your browsers incognito or privacy mode. In incognito or privacy mode, all of your normal browser settings are not used, instead you have a blank slate so auto-fill does not happen.

← Older revision		Revision as of 22:04, 25 May 2016
Line 288:		Line 288:

	<font color="red">Note:</font> For FOG Trunk/FOG 1.3.0 users, if the password field inside of the <font color="red">/opt/fog/.fogsettings</font> file is set incorrectly, every time you re-run the FOG installer, it will set the local fog user's password to this incorrect password. It's important to set the password correctly in '''all''' of the above listed areas.		<font color="red">Note:</font> For FOG Trunk/FOG 1.3.0 users, if the password field inside of the <font color="red">/opt/fog/.fogsettings</font> file is set incorrectly, every time you re-run the FOG installer, it will set the local fog user's password to this incorrect password. It's important to set the password correctly in '''all''' of the above listed areas.
		+
		+	== Beware, your browser's auto-fill! ==
		+
		+	Often times, when people change a setting in storage management besides the username and password for a node, most web browsers will "auto-fill" the username and password in without you knowing. So if all you've changed is the interface name or replication bandwith or some other setting, it's possible your browser has auto-filled the username and password and when you click "Save", this incorrect auto-filled username and password is stored.
		+
		+	There are some ways to avoid this. First is to be careful, don't needlessly click the save button if you haven't changed anything. Second, watch the username. In most cases, it should be <font color="red">fog</font>. Watch the password length too. Another way to guarantee (mostly) that auto-fill doesn't fill in these fields is to use your browsers incognito or privacy mode. In incognito or privacy mode, all of your normal browser settings are not used, instead you have a blank slate so auto-fill does not happen.

	== Interface ==		== Interface ==

@@ Line 375: / Line 375: @@
 '''Solutions:'''
-This error happens when the FTP credentials that are set for a specific function are valid for connecting via FTP, but the credentials supplied have no permission on the files/directories that are to be manipulated. This is not necessarily a credentials issue but can be resolved by supplying credentials that have permissions over the files/directories in question. Otherwise, the user-name that is being used can be given permissions over the files/directories in question in whatever way that is appropriate. Please see above for examples on how to set permissions, and how to change FTP credentials for the different areas.
+This error happens when the FTP credentials that are set for a specific function are valid for connecting via FTP, but the credentials supplied have no permission on the files/directories that are to be manipulated. This is not necessarily a credentials issue but can be resolved by supplying credentials that have permissions over the files/directories in question. Otherwise, the user-name that is being used can be given permissions over the files/directories in question in whatever way that is appropriate. This error can also occur if the file its downloading could not be moved to another location or could not be deleted. Please see above for examples on how to set permissions, and how to change FTP credentials for the different areas.
 === Images stuck in /images/dev ===

@@ Line 179: / Line 179: @@
 == FTP Settings File ==
-=== Fedora 20/21: ===
+=== Fedora 20/21/22/23: ===
 Location:
@@ Line 213: / Line 213: @@
 <pre>man vsftpd.conf</pre>
 === Ubuntu ===

@@ Line 148: / Line 148: @@
 == FTP Service ==
-=== Fedora 20/21 ===
+=== Fedora 20/21/22/23 ===
 *Check the status of FTP with