Upload never gets moved out of the /images/dev/#### folder
-
@TThax Your problem is absolutely related to FTP not being able to do what it’s supposed to do.
Let’s go back to the basics… Did it ever work? When did it stop working?
-
It used to work on my old FOG server. The computer took a dump, so I made a new one. I set it up the same way as the old one, except I used Ubuntu 14.04 instead of 12.xx. I copied a couple of images from the old hard drive onto this one, did the permissions change and all that, and new images have never successfully transferred on this machine.
-
@TThax 14.04 would work better with fog trunk. Seeing how you currently do not have a working fog server, would you be willing to update and try it out?
-
Forgive my ignorance, but how do I do that? Also, will I lose my current images?
-
@TThax said:
Forgive my ignorance, but how do I do that? Also, will I lose my current images?
Pick a method from here, I’d recommend git or svn: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk
You shouldn’t loose anything, db data, images, configuration in /opt/fog/.fogsettings. it all gets carried over.
-
Ok, upgrade complete. In the Image Management screen, it shows Image size: ON CLIENT, but now there isn’t even a column for Image Size: ON SERVER. How would I know if it is recognizing the images?
-
@TThax In fog 1.3.0, that feature is turned off by default to improve performance of the image management page. You can turn it on inside FOG Configuration -> FOG Settings -> General Settings -> FOG_FTP_IMAGE_SIZE
-
Still having an ftp issue… When I enabled that option, in that column I get:
FOGFTP: Login failed. Host: 10.1.1.42, Username: fog, Password: , Error: ftp_login(): Login incorrect.
I checked FOG Configuration -> FOG Settings -> TFTP Server FOG_TFTP_FTP_USERNAME and FOG_TFTP-FTP_PASSWORD and those are correct.
/opt/fog/.fogsettings did not change anything with this update, and on the troubleshoot ftp page, it says FOG 1.3 should have storageftpuser & storageftppass is it a different file path for an updated .fogsettings file, or do I need to update the old file somehow?
-
@TThax said:
FOGFTP: Login failed. Host: 10.1.1.42, Username: fog, Password: , Error: ftp_login(): Login incorrect.
If that’s the actual error and you haven’t edited it,
Your issue is… somehow you have no password stored in your storage settings.
Look inside of Storage Management -> [your storage node name] -> Password.
Really watch to make sure auto-compete isn’t changing things when you update that password.
-
The strange thing is that the password was correct, but I went ahead and deleted and retyped it, and now it works. So bizarre. Thanks so much for your help! I bet the next upload works just fine.
-
@TThax said:
The strange thing is that the password was correct, but I went ahead and deleted and retyped it, and now it works. So bizarre. Thanks so much for your help! I bet the next upload works just fine.
Good lord, if that was the problem the whole time, that makes me feel really dumb.
Well, enjoy fog trunk! Fee free to comment on your experience, don’t hesitate to come report bugs or ask for help (not saying you’ll have a lot, but it’s just good manners to make you feel welcome).
-
It makes me feel really dumb too, but in fairness, the password WAS correct there. I just deleted and retyped it and it worked.
-
@TThax Web browsers auto-fill functionality is the cause of this most of the time. It’ll fill in a blank field with what should be there, most of the time… but it’s not actually set.
Those fields in fog are configured to tell browsers to not auto-fill them, but Chrome seems to not care about these requests.
-
Good to know!
Also, I have now uploaded 3 images and they are all working perfectly. Thanks again for all of your help!
-
Actually, one more quick question. When I do a full host registration now, and I select the image number. It isn’t saving what image I selected, and I have to go into host management and select it in there. What would cause that?
-
@TThax use the
?to get the image listing. upgrading fog resets the image numbers. If using one of the listed numbers doesn’t work, it’s a bug. Post the issue in bug reports. (This is a fine example of what a “minor” bug is)
