GIT 8056: Task remains in active status after image capture completes. "Uploaded" shows No Data



  • The capture task appears to have completed as the computer rebooted. The Task management on the web shows the task as still active though nothing is happening. Checking the image information it shows the Client Image to be 150gb, but the uploaded size is No Data. /Images folder contains /dev and /postdownloadscripts. /dev has all my partition images inside. I recall reading about this but don’t recall what the issue is. 0_1465494627223_Logs.zip



  • @Wayne-Workman Thanks for the link. My mistake, great support on this forum :)



  • @mrdally204 said in GIT 8056: Task remains in active status after image capture completes. "Uploaded" shows No Data:

    Maybe it is documented to not make your default user on the server “fog” or to not change the password after the fact, but I obviously missed that.

    It is, that’s here:
    https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Local_.22fog.22_user


  • Senior Developer

    @mrdally204 While it’s not directly mentioned (maybe I’m wrong?) I wouldn’t recommend adding things (users, packages, etc…) unless otherwise instructed for any installation that contains it’s own software package. This mainly because we really you don’t know exactly what is going to happen during the installation. That’s just a matter of personal opinion though.

    That all said, if you do feel you need to create your own fog user and then install, you can. Just make sure to add the password='YOURPASSWORD' line to the /opt/fog/.fogsettings file.

    If /opt/fog/.fogsettings file doesn’t exist (fresh install usually), then create it:

    mkdir -p /opt/fog/; echo "password='YOURPASSWORD'" > /opt/fog/.fogsettings

    As a safety measure I’d also run the installer with: (for fresh installs)
    password='YOURPASSWORD' ./installfog.sh -y



  • This is a nonissue. Once the passwords were adjusted to match everything worked as I expected it to. Now that I understand how it works I’m less confused as to why it broke. However, when setting up this headless server for use specifically for a fog server I created a user “fog” and used my own password. When my password was not working after the fog server install, I logged in as root to change the password back to what I wanted and specified while installing Ubuntu. This is where the disconnect was. Maybe it is documented to not make your default user on the server “fog” or to not change the password after the fact, but I obviously missed that. Thanks for instructing me on the fix and helping me understand why it broke :) I won’t make the same mistake next time



  • @mrdally204 the existing task that is currently stuck in task management should complete without problem after you correct the password issue. You will need to let the reference image upload again though.



  • @Wayne-Workman What I meant was, once the password was corrected where it needed to be would the partitions be moved to their proper location and complete the imaging process the way Fog expects it to. Or will I need to correct all the password locations, delete the task and resulting img files, and start over with a capture?



  • @mrdally204 there are many places where are the password needs to be updated if you want it to be something different. Not changing it in all of the specified places will only cause this exact same problem to happen again the next time you update or rerun your installer.

    All of these locations for passwords relevant to FTP are in that Wiki article titled troubleshoot FTP.

    For the task you can just simply delete it using the web interface if you like.



  • @Wayne-Workman Thanks Wayne. I did indeed change my “fog” users password manually with the root user. All I should have to do is modify the password in the Storage management option on the web? Once I fix this password issue, will the task complete or is it stuck forever?



  • It sounds like you are having an FTP issue. If you search the fog Wiki for troubleshoot FTP you will find an article that has many troubleshooting steps and lots of information in it that should help you solve this problem.


 

441
Online

41.8k
Users

12.3k
Topics

116.1k
Posts