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

    Upload first image till 99%

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    6
    2.3k
    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
      Mark Hofland
      last edited by

      Hi all,

      This is the first time I’m using a FOG server on CentOS 6.4.

      Everything went fine with the installation. So I tried to upload my first image to the FOG server.
      Well, it does till 99% in the task manager, and then it stops, and I don’t get any messages back on the Web interface.
      I checked the file and directory rights for the image and dev folders, they are fine.
      The only thing I noticed, that in /var/log/messages there was a line (see below) while the task on the fog web interface shows 80%
      xinetd[1822]: EXIT: tftp status=0 pid=4186 duration=905(sec).

      And the task runs till 99%.

      I don’t have any idea wha’ts wrong.

      any suggestions?

      regards,

      Mark

      1 Reply Last reply Reply Quote 0
      • M
        Mark Hofland
        last edited by

        [quote=“Mark Hofland, post: 14124, member: 10812”]Hi all,

        This is the first time I’m using a FOG server on CentOS 6.4.

        Everything went fine with the installation. So I tried to upload my first image to the FOG server.
        Well, it does till 99% in the task manager, and then it stops, and I don’t get any messages back on the Web interface.
        I checked the file and directory rights for the image and dev folders, they are fine.
        The only thing I noticed, that in /var/log/messages there was a line (see below) while the task on the fog web interface shows 80%
        xinetd[1822]: EXIT: tftp status=0 pid=4186 duration=905(sec).

        And the task runs till 99%.

        I don’t have any idea wha’ts wrong.

        any suggestions?

        regards,

        Mark[/quote]
        Update:
        I waited fo 10 minutes and just copied the uploaded 99% file from the DEV folder to the IMAGE folder and renamed it to the right image name. Imported another host, created a deploy task on that host with the image name I renamed the file to. The client starts downloading and the deploy task stops also at 99%. Client reboots automaticly and just starts Windows. So The imag file is ok, only the tasks are stopping at 99%.

        Strange

        Regards,

        Mark

        1 Reply Last reply Reply Quote 0
        • S
          Sebastian M.
          last edited by

          What does it say on the machines display?

          1 Reply Last reply Reply Quote 0
          • M
            Mark Hofland
            last edited by

            [quote=“Sebastian M., post: 14139, member: 229”]What does it say on the machines display?[/quote]
            You mean the FOG’s display or the client’s display? On the FOG’s display I see the task stops at 99% and on the client display I don’t see anything, just a black screen.

            1 Reply Last reply Reply Quote 0
            • M
              Mark Hofland
              last edited by

              [INDENT]Problem solved. I discovered that it was the FTP credentials being used for the storage server.

              I went to the Storage Management section. list all storage nodes and selected the one the one that is being used (in my case it was the ‘default member’).

              Checked the username and password there and maked sure there was a corresponding user account on the fog server with the right access priviliges on the images folder shown in fog managment.

              In my case it was set to username ‘fog’ with a very long password. I don’t know how this ended up as ‘fog’ instead of ‘fogstorage’ but it appeared to have been configured with some randomly generated password.[/INDENT]

              1 Reply Last reply Reply Quote 0
              • S
                Sebastian M.
                last edited by

                I think it is a hash for the pass instead of displaying the real password.

                The wrong pass was the same problem for me but not showing in the error you got.

                Nice to know, that the problem is solved now 😉

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

                171

                Online

                12.1k

                Users

                17.3k

                Topics

                155.3k

                Posts
                Copyright © 2012-2024 FOG Project