cannot connect

Submitted by xstation on November 6, 2006 - 14:00.

I installed agent and server on the linux host

I have now arrived at the point in the howto where i am in the bixdata connections
screen where i place my IP from my router which in this case is 192.168.1.64

but the log shows
Launched BixDesktop
Connecting to 192.168.1.64:7071
Connecting to 192.168.1.64:7071
Can't connect to 192.168.1.64:7071
Connecting to 192.168.1.64:7071
Connecting to 192.168.1.64:7071
Can't connect to 192.168.1.64:7071

i log in as alex
and password

which is the same as i would when i log in on the linux os


Submitted by jed on November 6, 2006 - 14:45.

Did you make that alex account on the bixserver? Try just connecting as guest. The desktop doesn't connect to the server through your shell account.


Submitted by xstation on November 7, 2006 - 01:41.

ok thanks for your reply.

Itried connecting as guest but still cannot connect

Launched BixDesktop
Connecting to 192.168.1.64:7071
Connecting to 192.168.1.64:7071
Can't connect to 192.168.1.64:7071


Submitted by bixdata on November 7, 2006 - 16:59.

On your machine 192.168.1.64

do you have a firewall?
perhaps bixagent is not running on 192.168.1.64
(check with ps aux | grep bixagent)
Try to install a bixagent on the same box as bixdesktop, and see if you can connect.

Almost always this is a problem because agent is not running, or the machine you are trying to reach is behind a firewall / nat.


Submitted by xstation on November 8, 2006 - 01:07.

i have a router at which has a firewall i installed .

bixagent and bixserver are on my linux box as is the bixdeasktop.
there is no firewall on the linux server only on the router.

alex 3279 0.0 0.1 2888 820 pts/0 S+ 07:57 0:00 grep bixagent

i am trying to follow the howto here:http://howtoforge.com/vmware_xen_management_bixdata

i have only one box so have installed bixagent and server on same box
have vmware os win2003 as guest


Submitted by jed on November 8, 2006 - 06:30.

Is that the output of "ps aux | grep bixagent"? that means bixagent isn't running. what happens when you try to start the agent?


Submitted by xstation on November 8, 2006 - 16:09.

if you look at the howto i am following http://howtoforge.com/vmware_xen_management_bixdata i have reached the part where it says "The first thing I'll do is connect to my BixServer"

are you suggesting to start bixagent? if so how to do that please?


Submitted by bixdata on November 8, 2006 - 20:22.

To start a bixagent on unix

Just do

cd bixdata/bixagent
./bixagent &

On windows just run from menu


Submitted by xstation on November 9, 2006 - 03:03.

ok this is what i got how should i proceed remember i am following the howto as mentioned in my last post. should i loginto to the bixserver ?
you can see the 192.168.1.64 below which is my router.

The other entry are a little strange as i have vmware onlinux with windows 20003 guest which has a NAT connection with IP address of 172.16.0.128 and default gateway
of 172.16.0.2

vmware was NOT runing when i issued the command
alex@xstation:~/bixdata/bixagent$ ./bixagent &

alex@xstation:~$ cd bixdata/bixagent
alex@xstation:~/bixdata/bixagent$ ./bixagent &
[1] 12018
alex@xstation:~/bixdata/bixagent$ BixAgent version 2.6; Copyright 2004 - 2006 (http://www.bixdata.com)
Using data path: /home/alex/bixdata/bixagent/data/
Warning, missing x509 or private key file. Generating new files
Public Key Signature D076D089B885ACB86B2CAC63D4F7736F6E2C1237
SMART :: Unable to obtain read access to /dev/hda (13) [-1]
SMART plugin :: Unable to enable native SMART support
sh: /usr/local/sbin/smartctl: No such file or directory
Authentication disabled
Own default port 17070
Auto enumerating interfaces
Found Interface 127.0.0.1
Creating listener on 127.0.0.1:17070
Found Interface 192.168.1.64
Creating listener on 192.168.1.64:17070
Found Interface 172.16.0.1
Creating listener on 172.16.0.1:17070
Found Interface 172.16.163.1
Creating listener on 172.16.163.1:17070


Submitted by Anonymous on November 13, 2006 - 02:56.

Connect to BixServer IP address using BixDesktop, add BixAgent IP address to BixServer in the Situation Room.

Test that you can connect to BixAgent by running BixDesktop and connecting to BixAgent IP address.


Submitted by xstation on November 13, 2006 - 10:06.

when i launch destop it automatically starts up after login this the server

tomtically Launched BixDesktop
Connecting to 192.168.1.64:17070
Connecting to 192.168.1.64:17070
Connected to 192.168.1.64:17070
Requesting process list

i assume as server

alex@xstation:~$ cd bixdata/
alex@xstation:~/bixdata$ ./rundesktop.sh
Using data path: /home/alex/bixdata/bixdesktop/data/
Public Key Signature D909AEFFC246658C781D80D8C5A5C529B1CA33DA

he situation room how to
issue command to agent? or what do i do and how to do it.


Submitted by Anonymous on November 14, 2006 - 08:26.

Just add your BixAgent IP address to the Situation Room (by clicking the +), you can add 1 IP address for every machine, or network device.

Follow the howtoforge from there.

or Watch the demo: http://www.bixdata.com/static/Bix%20Demo%201/Bix%20Demo%201.html