wget failure on client's image

[Tom Elliott]

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

[jdmg94]

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

[Sebastian Roth]

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)

[jdmg94]

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

so usually I get

fogserver/management

instead of

fogserver/fog/management

[Wayne Workman]

@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

[jdmg94]

@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

[Wayne Workman]

@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?

[jdmg94]

@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?

[Wayne Workman]

@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?

[Tom Elliott]

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

[Wayne Workman]

@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.