Error: Unable to communicate with server -- provider not yet setup

[BigBirdy]

Well I thought maybe a new thread with a different title might ellicit more responses. Fresh server install on a RHEL5 system. The only things that are really non-standard are that Bastille has been run on this machine and SSH runs on a non-standard port. The server installed fine and can monitor itself fine. I can also reach the server just fine at http://192.168.10.71:7080 so that port seems to be open just fine.

Installed the agent on another machine, and it can ping the server just fine

PING dev.squamish.ca (192.168.10.71) 56(84) bytes of data.
64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=1 ttl=64 time=4.95 ms
64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=2 ttl=64 time=0.617 ms
64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=3 ttl=64 time=0.238 ms
64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=4 ttl=64 time=0.180 ms

But when I try to launch the agent and go through the configuration, it is unable to connect to the server?

[root@vhs agent]# ./hq-agent.sh start
Starting agent
- Invoking agent
- Starting agent process
Agent successfully started

[ Running agent setup ]
What is the HQ server IP address: 192.168.10.71
Should Agent communications to HQ always be secure [default=no]:
What is the HQ server port [default=7080]:
- Testing insecure connection ... Failure
What is the HQ server IP address:

Ay suggestions?

[BigBirdy]

Resolved the issue, was an iptables firewall problem.

[jtravis_hyperic]

Johnny,

Are you able to telnet to the server, port 7080 from the box running
the agent? The Agent speaks over HTTP, so that quick test will let
you know if you have something misconfigured.

-- Jon


On Jun 23, 2007, at 11:08 AM, Johnny Stork wrote:

> Well I thought maybe a new thread with a different title might
> ellicit more responses. Fresh server install on a RHEL5 system. The
> only things that are really non-standard are that Bastille has been
> run on this machine and SSH runs on a non-standard port. The server
> installed fine and can monitor itself fine. I can also reach the
> server just fine at http://192.168.10.71:7080 so that port seems to
> be open just fine.
>
> Installed the agent on another machine, and it can ping the server
> just fine
>
> PING dev.squamish.ca (192.168.10.71) 56(84) bytes of data.
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=1 ttl=64
> time=4.95 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=2 ttl=64
> time=0.617 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=3 ttl=64
> time=0.238 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=4 ttl=64
> time=0.180 ms
>
> But when I try to launch the agent and go through the
> configuration, it is unable to connect to the server?
>
> [root@vhs agent]# ./hq-agent.sh start
> Starting agent
> - Invoking agent
> - Starting agent process
> Agent successfully started
>
> [ Running agent setup ]
> What is the HQ server IP address: 192.168.10.71
> Should Agent communications to HQ always be secure [default=no]:
> What is the HQ server port [default=7080]:
> - Testing insecure connection ... Failure
> What is the HQ server IP address:
>
> Ay suggestions?
>

[admin]

Johnny,

Are you able to telnet to the server, port 7080 from the box running
the agent? The Agent speaks over HTTP, so that quick test will let
you know if you have something misconfigured.

-- Jon


On Jun 23, 2007, at 11:08 AM, Johnny Stork wrote:

> Well I thought maybe a new thread with a different title might
> ellicit more responses. Fresh server install on a RHEL5 system. The
> only things that are really non-standard are that Bastille has been
> run on this machine and SSH runs on a non-standard port. The server
> installed fine and can monitor itself fine. I can also reach the
> server just fine at http://192.168.10.71:7080 so that port seems to
> be open just fine.
>
> Installed the agent on another machine, and it can ping the server
> just fine
>
> PING dev.squamish.ca (192.168.10.71) 56(84) bytes of data.
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=1 ttl=64
> time=4.95 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=2 ttl=64
> time=0.617 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=3 ttl=64
> time=0.238 ms
> 64 bytes from dev.squamish.ca (192.168.10.71): icmp_seq=4 ttl=64
> time=0.180 ms
>
> But when I try to launch the agent and go through the
> configuration, it is unable to connect to the server?
>
> [root@vhs agent]# ./hq-agent.sh start
> Starting agent
> - Invoking agent
> - Starting agent process
> Agent successfully started
>
> [ Running agent setup ]
> What is the HQ server IP address: 192.168.10.71
> Should Agent communications to HQ always be secure [default=no]:
> What is the HQ server port [default=7080]:
> - Testing insecure connection ... Failure
> What is the HQ server IP address:
>
> Ay suggestions?
>

[QuintonHoole]

Just out of interest, where did you get a version of Bastille for RHEL5. I see the standard Bastille distro does not support RHEL5.

Regards

Q

[BigBirdy]

Minor trick, just modified redhat-release file to look like RHEL4