FOGFTP: Login failed Version 4582
-
Afternoon all,
I’m banging my head against this one a little. On image upload on a newly created server (Centos 6.7) it gets as far as the final steps i.e. image has been uploaded but is sitting in /images/dev folder with mac address of host and on final reboot it throws error on client:
* FOGFTP: Login failed. Host <IPofFogServer>, Username: fog, Pass word dWp4+5JSvvN7, Error: ftp_login(): Login incorrect.- I’'ve amended the fog user on console
sudo passwd fog-
I’ve added this same password to the fog user in the web GUI.
-
I’ve added this same password to FOG Configuration> FOG Settings > TFTP Server > FOG_TFTP_FTP_PASSWORD
-
And because I’m using trunk and following instructions specifically relating to the passwords and file permissions from here, I’ve ensured the same password is added to both password fields (the one under dnsbootimage= and also in storageftppass=)
-
Lastly I’ve ensured ownership of /images and /images/dev is set to fog:root and assigned 777 permissions
I can use Filezilla from another machine (Windows) and can authenticate to the fog server with these same credentials
And yet on the client, the error is referring dWp4+5JSvvN7 which is the password which was set before I updated it to the new one…
The Apache log on the fog server shows
[Thu Sep 10 17:53:25 2015] [error] [client <IPofFogServer>] File does not exist: /var/www/html/service [Thu Sep 10 17:56:23 2015] [error] [client <IPofFogServer>] File does not exist: /var/www/html/status [Thu Sep 10 17:57:35 2015] [error] [client <IPofFogServer>] File does not exist: /var/www/html/service [Thu Sep 10 17:58:02 2015] [error] [client <IPofFogServer>] File does not exist: /var/www/html/status [Thu Sep 10 18:07:17 2015] [error] [client <IPofFogServer>] File does not exist: /var/www/html/statusOn the server the path to these files is actually as shown below - so above is omitting the “fog” from the path - is that normal?
/var/www/html/fog/service /var/www/html/fog/statusThe image being uploaded is associated with the host and to both of the 2 storage groups I have set up.
I know this error has been seen before but I’m pretty sure I’ve edited the password in all required places and have permissions set correctly and fact I can FTP to the server with those creds suggests FTP itself is ok.
One other thing which may or may not be relevant. On the storage nodes it now appears to auto-populate the Management Username and Management Password fields, presumably from /opt/fog/.fogsettings.
In past versions of FOG storage nodes should have the fogstorage user and password populated in here? I don’t appear to be able to change this.
Anyone have any helpful suggestions here please?
regards, Kiweegie.
-
What about the password on the storage node the image is going to? Those are FTP credentials, too.
What’s your web-root set as? here: Storage Management -> [your_storage_node] -> Web root
-
Hi Wayne, web root on main FOG server is /fog - I’ve not altered this so assume that is how it’s set during install. I have another working FOG server at another site and this is also set to /fog.
The storage node on which the image is going to has the same username and password as on every other storage node (which matches the console fog user, whats in /opt/fog/.fogsettings etc as stated above).
It doesn’t appear possible to change this password even if I wanted to - it reverts back to the above. This is where I suspect the issue to be coming from but don’t know how to change it.
On the working FOG server the Management Username and Management Password section under Storage Node are editable and show with a white background. On the problem server these sections show with a yellow background and are not editable. I can edit the password in there but on viewing the password later the original shows.
As workaround I’ve tried setting the same password on the storage node but this may be a red herring as the password on the client after image upload refers to a password which is not in use on any server.
regards Kiweegie
-
@Kiweegie the “yellow” you are reporting sounds to me like the browsers auto fill taking over. This does not mean that that field is not editable, it just means whatever username and password is being shown is automatically filling that/those fields.
To fix the auto fill for right now I believe you may need to remove that stored item.
-
@Tom-Elliott sigh… yes you’re quite right Tom. That has indeed solved the “problem”
please mark as resolved, i’m away for a cup of tea and a lie down in a darkened room…
regards Kiweegie
-
@Kiweegie You don’t need to go to that extent. You didn’t know. It happens to all of us.
-
@Tom-Elliott Thanks Tom. All working now with the sole exception that the uploaded image is still stuck in the /images/dev folder. I can manually move this to /images/imagename but is there something I can do to prevent this happening? I’m not seeing errors anywhere and I’ve corrected the password issue from earlier (cached creds in Chrome).
regards Kiweegie.
-
It won’t automatically move itself.
I’d recommend moving it yourself.
All you do is move the
/images/dev/<macname>to /images/<imagepathnamefromgui>Then you can retry by trying another capture.
-
Thanks Tom,
I did move it myself. Uploading a new image ended with the same result though. I’m happy to continue manually moving from /images/dev/macaddress to /images/imagename if necessary just wondered if this was down to something I’d done wrong…
regards, Kiweegie.
-
@Kiweegie said:
Thanks Tom,
I did move it myself. Uploading a new image ended with the same result though. I’m happy to continue manually moving from /images/dev/macaddress to /images/imagename if necessary just wondered if this was down to something I’d done wrong…
regards, Kiweegie.
The only reason that FOG wouldn’t move it itself would be due to FTP credentials…
Knowing now what credentials are set on the master storage node, try to connect via CLI using FTP with those credentials you have set. If it doesn’t work, there’s your problem.
