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

wget failure on client's image

Scheduled Pinned Locked Moved Solved
Bug Reports
4
13
2.2k
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.
  • J
    jdmg94
    last edited by jdmg94 Mar 31, 2016, 4:29 PM Mar 31, 2016, 3:18 PM

    Hello guys,

    I’m currently on the latest trunk, and i’m trying to register my hosts/send inventory and I always get stuck on this point

    0_1459437425607_e28dc53b-95f0-4a7b-9687-0c4a55fd8d7a.jpg

    0_1459437429340_ee717447-fe6b-413f-b6ec-36b261552f3b.jpg

    This wget line is the one that causes the trouble, I can ping my fog server, but this line here won’t get through

    Here’s the error message:

    0_1459463383983_IMG_20160331_160551 (1).jpg

    sorry for the potato quality, I’m on a temporary phone right now

    1 Reply Last reply Reply Quote 0
    • J
      jdmg94
      last edited by jdmg94 Mar 31, 2016, 9:34 AM Mar 31, 2016, 3:34 PM

      I tried running that line from a different server to check on the syntax

      this is what I got

      0_1459438517913_Capturew1.PNG

      1 Reply Last reply Reply Quote 0
      • T
        Tom Elliott
        last edited by Mar 31, 2016, 3:54 PM

        just a guess, but you access fog with:
        10.54.0.230/fog/management/index.php

        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

        J 1 Reply Last reply Mar 31, 2016, 4:13 PM Reply Quote 0
        • J
          jdmg94 @Tom Elliott
          last edited by Mar 31, 2016, 4:13 PM

          @Tom-Elliott well my virtual host is set to have the fog folder as document root, maybe that’s causing a conflict there?

          1 Reply Last reply Reply Quote 0
          • S
            Sebastian Roth Moderator
            last edited by Sebastian Roth Mar 31, 2016, 10:37 AM Mar 31, 2016, 4:35 PM

            Usually we have DocumentRoot set to /var/www …

            The wget syntax error is probably because you used ‘0’ (zero) but the command is using ‘O’ (upper case OOOOH) - meaning output to - (stdout)

            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

            J 1 Reply Last reply Mar 31, 2016, 8:15 PM Reply Quote 0
            • J
              jdmg94 @Sebastian Roth
              last edited by Mar 31, 2016, 8:15 PM

              @Sebastian-Roth my document root is /var/www/html/fog/

              so usually I get

              fogserver/management
              

              instead of

              fogserver/fog/management
              
              W 1 Reply Last reply Apr 1, 2016, 2:47 PM Reply Quote 0
              • W
                Wayne Workman @jdmg94
                last edited by Apr 1, 2016, 2:47 PM

                @jdmg94 What happens if you try this from a debug session (maybe try a Linux Live disk too)?

                version=$(wget -qO - http://10.54.0.230/fog/service/getversion.php)
                echo $version
                

                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!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

                J 2 Replies Last reply Apr 1, 2016, 4:31 PM Reply Quote 0
                • J
                  jdmg94 @Wayne Workman
                  last edited by jdmg94 Apr 1, 2016, 10:42 AM Apr 1, 2016, 4:31 PM

                  @Wayne-Workman so here’s my setup

                  I have a server with 2 nics, eth0 is on a vlan that has all the test computers on it, this vlan has no internet connection nor has it access anywhere else but its own computers.

                  eth1 is on a vlan that has internet and access to my desktop, which is the one I do ssh on.

                  when I run the script you sent on a server outside the test vlan I get a “7013” response
                  but when I run the same file on a client computer on the test vlan I just get a blank response.

                  I can ping the server, but I don’t really know what could be causing the trouble here.

                  I just realized I have a typo, my bad it works on both vlans, response is 7013

                  W 2 Replies Last reply Apr 1, 2016, 4:40 PM Reply Quote 0
                  • W
                    Wayne Workman @jdmg94
                    last edited by Apr 1, 2016, 4:40 PM

                    @jdmg94 And you have “eth0” set as the interface name inside the node’s storage management area?

                    Also - the blank response you said you got, did it result in a blinking-cursor type of thing?

                    I’ve had a very, very similar issue twice now with this sort of result. But my issues were getting to the main server which is being run inside of VMWare…

                    Is this server virtualized? And does the eth0 link have to go through a router to get to it’s clients or is there just switches between?

                    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!
                    Daily Clean Installation Results:
                    https://fogtesting.fogproject.us/
                    FOG Reporting:
                    https://fog-external-reporting-results.fogproject.us/

                    1 Reply Last reply Reply Quote 0
                    • J
                      jdmg94 @Wayne Workman
                      last edited by Apr 1, 2016, 4:43 PM

                      @Wayne-Workman BTW, vi is as buggy as it can get on the debugging interface on the clients side, could you guys consider switching to nano instead?

                      T 1 Reply Last reply Apr 1, 2016, 4:55 PM Reply Quote 0
                      • W
                        Wayne Workman @jdmg94
                        last edited by Wayne Workman Apr 1, 2016, 10:46 AM Apr 1, 2016, 4:45 PM

                        @jdmg94 said in wget failure on client's image:

                        I just realized I have a typo, my bad it works on both vlans, response is 7013

                        Oh ok.

                        You might now ensure your Web Server settings are correct. Like the web root.

                        Web Interface -> FOG Configuration -> FOG Settings -> Web Server -> FOG_WEB_ROOT
                        Also is the original issue still present? Did you have a typo in the wget command or what?

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        1 Reply Last reply Reply Quote 0
                        • T
                          Tom Elliott @jdmg94
                          last edited by Apr 1, 2016, 4:55 PM

                          @jdmg94 vi is not buggy. It works perfectly fine. What do you mean “buggy”?

                          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

                          W 1 Reply Last reply Apr 1, 2016, 5:06 PM Reply Quote 0
                          • W
                            Wayne Workman @Tom Elliott
                            last edited by Apr 1, 2016, 5:06 PM

                            @Tom-Elliott I’ve used it lately on a low-resolution monitor and an older computer in a debug session, and I’ve noticed I can’t see the bottom line where you normally can see where you type in commands for Vi. It’s like the screen is mis-aligned or something. Of course, paying very close attention to what you type and knowing what your doing and you don’t need to see that line, but still it’s weird. Mind you, that low-res monitor works perfectly fine with showing the bottom line at the shell prompt in a debug session.

                            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!
                            Daily Clean Installation Results:
                            https://fogtesting.fogproject.us/
                            FOG Reporting:
                            https://fog-external-reporting-results.fogproject.us/

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

                            147

                            Online

                            12.0k

                            Users

                            17.3k

                            Topics

                            155.2k

                            Posts
                            Copyright © 2012-2024 FOG Project