• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Data Migration form FOG 0.32 to 1.2

    Scheduled Pinned Locked Moved
    FOG Problems
    4
    39
    12.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Mathieu Cohen
      last edited by

      So do I need to create an FTP on my ftp server using Fog’s credential pointing to the node? how exactly is FTP connection will work on a machine or folder location that is not sitting in FTP?

      1 Reply Last reply Reply Quote 0
      • W
        Wolfbane8653 Developer
        last edited by

        WOW. Mass confusion…

        What is the set up your are trying to accomplish?

        1 Reply Last reply Reply Quote 0
        • M
          Mathieu Cohen
          last edited by

          haha sorry about that 😛

          FOG-server and DB are sitting on a Ubuntu 13.10 VM.
          Image node is on an NFS share sitting on a Windows 2003 server (will be upgraded to 2008 R2 or 2012R2 soon enough)

          Basically I just want to get rid of that error message when doing the download from the basic tasks.

          1 Reply Last reply Reply Quote 0
          • JunkhackerJ
            Junkhacker Developer
            last edited by

            the storage location MUST have access to both NFS and FTP. without FTP you will get the error you just did, and after uploads the server will not be able to move the image from the /images/dev/<mac address> location to /images/<image name>

            signature:
            Junkhacker
            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

            1 Reply Last reply Reply Quote 0
            • W
              Wolfbane8653 Developer
              last edited by

              [url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]

              If you notice in the tutorial there is an ftp program that is required it is called [B][SIZE=13px][FONT=sans-serif][COLOR=#000000]Filezilla[/COLOR][/FONT][/SIZE][/B]. You may want to look over the guide again and check your settings.

              1 Reply Last reply Reply Quote 0
              • M
                Mathieu Cohen
                last edited by

                Ok I changed the node location to another server we have NFS and FTP setup already. Im uploading the image and will test the download after.

                Stay tuned for the update! 😉

                ps: sorry for all those questions -_-

                1 Reply Last reply Reply Quote 0
                • M
                  Mathieu Cohen
                  last edited by

                  Nope! definitely we need to look at something else. Same error. Something changed though, no more errors after upload to change file name as I was getting before. Before after upload I would get those errors but image would still be moved from dev to /images after. Now it moves and no errors show up.

                  BUT the download error coming from the link in Host management still is a no go. FTP is enabled, user has full control and is even owner of the /images folder as well as its parent.

                  1 Reply Last reply Reply Quote 0
                  • W
                    Wolfbane8653 Developer
                    last edited by

                    In the tutorial it is only used for a secondary storage node. I’m guessing you wish to have the windows node as the primary. You will need to make that change to the storage management section if not done so already.

                    1 Reply Last reply Reply Quote 0
                    • M
                      Mathieu Cohen
                      last edited by

                      Yes the node was set to master already. Also I changed the node from the windows 2003 server to a freenas server.

                      1 Reply Last reply Reply Quote 0
                      • Tom ElliottT
                        Tom Elliott
                        last edited by

                        Alright

                        I’m getting lost in your setup Mathieu.

                        I’m all about customization, but you’re not sure where things are failing, and we haven’t a clue about your particular setup.

                        Why not restart and start simple first. Meaning, install fog and test it on a completely localized setup first. Ensure things work and work properly. Then start integrating the customizations.

                        One, you’ll learn a TON more about how fog works and what’s happening. Two you learn about many of the limitations.

                        I’ve never heard of people just adding and changing things in such a fashion before.

                        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        1 Reply Last reply Reply Quote 0
                        • M
                          Mathieu Cohen
                          last edited by

                          Tom, sorry if this confused you. The initial set up was already tested on local (Ubuntu 13.10 VM) and was working. nothing really has changed besides putting the master Node on a freenas (with FTP & NFS) and giving full control of the loaction to the fog user (which was put as the user to use in the node management on the GUI)

                          Since then, everything is still working fine, comunication between Fog and the node is fine, image uploads are going to the dev folder then after upload is finished it’s being transfered to the main /images folder. the ONLY issue is whenever we try to proceed a download from the host management page, it fails automatically giving out the error I posted above. BUT using the quick download from the host list in task management works.

                          Do you need more information?

                          1 Reply Last reply Reply Quote 0
                          • 1
                          • 2
                          • 2 / 2
                          • First post
                            Last post

                          219

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.3k

                          Posts
                          Copyright © 2012-2024 FOG Project