I think that fixed it. I do have split scope dhcp setup on two servers, and only changed the options on one of them. I changed them in both and it seems to be working fine now.
Feel free to call me an idiot 
As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?
@AUTH-IT-Center - Thanks for pointing me in the right direction! I knew it was something simple. I had been looking at some of the wiki stuff and forum posts, but they both were a few years out of date, so I wanted to double check before I broke something else! Thanks again for your help!
Hi Everyone,
I am having an issue with migrating to a new Fog Server. We had a really old Fog Server that I am trying to replace and to be quite honest, I set up the new fog server months ago and did not document everything that I had done (I know). The web interface is up and working and it looks like I had imported all of our hosts and imported our Fog settings from the old server. I updated the new server’s Fog settings to point to the new Fog Server’s IP address, and I was able to register a new machine. I then tried to upload an image to the new server and it finished the imaging process showing the task was completed on the machine, but then it got to the updating the database and then gave me this error: “Error Returned: Type: 2, File: /var/www/fog/lib/fog/fog.tftp.class.php, Line 470, Message: ftp_login(): Login incorrect., Host: 10.40.22.69 Username: fogproject”
I would assume that it has something to do with importing the old settings and it not matching what I set for the password setting the new server up, but am not sure. If I go to the TFTP section in the web interface, there is a password set there, but it is a long string of random characters. Is there a way to change the TFTP FTP password on the server and the web interface to fix this issue?
Any help would be appreciated!
Yes. Taking the “/” out of the name fixed my issue.
Thank you guys for all the hard work in developing and maintaining this awesome project.
HAHA… Ok so this is twice now that I have asked for help on the forums and it has been a stupid simple fix. I am going home.
I changed the name, and it pushed up successfully.
Thanks for your help!
When I first got this error message, I was trying to update an existing image. I thought maybe it was having trouble overwriting the current image, so I created a new image in the fog web interface, and told it to capture, but still received the error message.
Here is the output of ls -al /images /images/dev
I connected to it using filezilla and the fog credentials listed in the storage management page. I can upload files into /images. I created just a test text file and it created fine. I edited it and saved it. I then deleted it.
I can see the image that I tried to push up in /images/dev, so I think the image process worked ok, but am not sure about why it failed to update the database at the end.
Thanks!
I have a little over 162 gb free. I pulled down an image yesterday, and it imaged fine and updated the database fine at the end of imaging. It seems that this issue is only when I try to push and image up to the server.
Thanks!
I just updated from 1.40 to 1.42 and tried to capture an image after updating. The image capture completes successfully, but when it tries to update the database, it fails with the following screens.
I saw the troubleshooting FTP wiki article and verified that I can connect to /images with the fog account and password that is listed in storage management. I can create a test file to this directory, edit it, and delete it. This username and password match in all of the areas listed in the wiki
I enabled all permissions on the /images directory using the following
sudo chmod -R 777 /images
I also set the ownership of /images using this:
sudo chown -R fog:root /images
Any help would be appreciated.
Thanks!
I think that fixed it. I do have split scope dhcp setup on two servers, and only changed the options on one of them. I changed them in both and it seems to be working fine now.
Feel free to call me an idiot
As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?
