Re: [opendx-users] Re: Connection to X server failed - Error during initializatioin

2004-09-23 Thread David Thompson
This could be an OS limitation. You may need to investigate things 
like ulimit and see what a single process can use for memory.


David


It appears that OpenDX was asking for more memory than the OS allows.
Once I set the memory option to 2010 and not anything higher, then
the error Connection to server baal failed goes away.

Strangely, though, 2010 MB seems not enough as I get this error on
execute...

Out of memory cannot expand data segment...

...which is the whole reason I bought 4GB of RAM in the first place.
But I think I saw somebody else's thread on this and I will look into
that now.

Thanks to all,

Gan

David Thompson wrote:
As a work around, you can always set the DXHOST environment 
variable. Look at that for starters.


David


Okay, I have added baal as a 2nd alias after baal.amalekite.net in
my /etc/hosts so that I now only get...

ERROR - Connection to server baal failed - Error during initialization.

...and not any other connection error. I can do this...

baal: {1} ping -c 1 baal
PING baal.amalekite.net (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=0.155 ms

baal.amalekite.net PING Statistics
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.155/0.155/0.155/0.000 ms
baal: {2}

...so it's nothing to do with /etc/hosts. Yet all my other X programs
work as befofe. Is there some log in OpenDX which would tell me what
to look for next? why it fails to connect?

TIA

Gan

Gan Uesli Starling wrote:


Machine baal is the same as localhost. The /etc/hosts file
lists it as baal.amalekite.net but I can add baal, of course.
It had always connected before as localhost. All of my other
X utilities, blackbox, IceWM, mozilla, thunderbird, NEdit,
Sodipodi etc, etc...all work fine.
Gan
Mattijs Janssens writes:


Your machine (baal) is not in /etc/hosts?
Mattijs
Gan Uesli Starling wrote:


I made an oops in the first report.
Under the window which says...
ERROR -- Connection to server baal failed -- Error during initialization.
...is another window which says...
ERROR -- Unable to resolve baal, connecting locally.
...it never used to say...
ERROR -- Connection to server baal failed -- Connecting locally
...I had just misremembered that part. I have also attached my
XFree86 log if that is informative.
TIA
Gan

Gan Uesli Starling wrote:

I just upgraded my PC with a new Intel D875PBZ motherboard, a 
3.2GHz P4 and 4 GB RAM. The sad part is that the upgrade cost 
a fortune and I did it ONLY for OpenDX. And so far as I can 
tell, OpenDX is the only program

that is having a problem with itor so it seems.
Everything EXCEPT OpenDX continues to work as before. But on 
running a program in OpenDX I now get this error...

Connection to server baal failed - Error during initialization
...whereas I had used to get...
Connection to server baal failed - Connecting locally
...and it would just work.
I have just uninstalled/reinstalled OpenDX on my NetBSD 
1.6.2_RC4 box to no better result. It does the same.

What to do next???
Thanks,
Gan




--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us







--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us



--
.
David L. Thompson   Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED]5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472


Re: [opendx-users] Re: Connection to X server failed - Error during initializatioin

2004-09-22 Thread Gan Uesli Starling

Okay, I have added baal as a 2nd alias after baal.amalekite.net in
my /etc/hosts so that I now only get...

ERROR - Connection to server baal failed - Error during initialization.

...and not any other connection error. I can do this...

baal: {1} ping -c 1 baal
PING baal.amalekite.net (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=0.155 ms

baal.amalekite.net PING Statistics
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.155/0.155/0.155/0.000 ms
baal: {2}

...so it's nothing to do with /etc/hosts. Yet all my other X programs
work as befofe. Is there some log in OpenDX which would tell me what
to look for next? why it fails to connect?

TIA

Gan

Gan Uesli Starling wrote:

Machine baal is the same as localhost. The /etc/hosts file
lists it as baal.amalekite.net but I can add baal, of course.
It had always connected before as localhost. All of my other
X utilities, blackbox, IceWM, mozilla, thunderbird, NEdit,
Sodipodi etc, etc...all work fine.
Gan
Mattijs Janssens writes:


Your machine (baal) is not in /etc/hosts?
Mattijs
Gan Uesli Starling wrote:


I made an oops in the first report.
Under the window which says...
ERROR -- Connection to server baal failed -- Error during 
initialization.

...is another window which says...
ERROR -- Unable to resolve baal, connecting locally.
...it never used to say...
ERROR -- Connection to server baal failed -- Connecting locally
...I had just misremembered that part. I have also attached my
XFree86 log if that is informative.
TIA
Gan

Gan Uesli Starling wrote:

I just upgraded my PC with a new Intel D875PBZ motherboard, a 3.2GHz 
P4 and 4 GB RAM. The sad part is that the upgrade cost a fortune and 
I did it ONLY for OpenDX. And so far as I can tell, OpenDX is the 
only program

that is having a problem with itor so it seems.
Everything EXCEPT OpenDX continues to work as before. But on running 
a program in OpenDX I now get this error...

Connection to server baal failed - Error during initialization
...whereas I had used to get...
Connection to server baal failed - Connecting locally
...and it would just work.
I have just uninstalled/reinstalled OpenDX on my NetBSD 1.6.2_RC4 
box to no better result. It does the same.

What to do next???
Thanks,
Gan



--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us


Re: [opendx-users] Re: Connection to X server failed - Error during initializatioin

2004-09-22 Thread David Thompson
As a work around, you can always set the DXHOST environment variable. 
Look at that for starters.


David


Okay, I have added baal as a 2nd alias after baal.amalekite.net in
my /etc/hosts so that I now only get...

ERROR - Connection to server baal failed - Error during initialization.

...and not any other connection error. I can do this...

baal: {1} ping -c 1 baal
PING baal.amalekite.net (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=0.155 ms

baal.amalekite.net PING Statistics
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.155/0.155/0.155/0.000 ms
baal: {2}

...so it's nothing to do with /etc/hosts. Yet all my other X programs
work as befofe. Is there some log in OpenDX which would tell me what
to look for next? why it fails to connect?

TIA

Gan

Gan Uesli Starling wrote:

Machine baal is the same as localhost. The /etc/hosts file
lists it as baal.amalekite.net but I can add baal, of course.
It had always connected before as localhost. All of my other
X utilities, blackbox, IceWM, mozilla, thunderbird, NEdit,
Sodipodi etc, etc...all work fine.
Gan
Mattijs Janssens writes:


Your machine (baal) is not in /etc/hosts?
Mattijs
Gan Uesli Starling wrote:


I made an oops in the first report.
Under the window which says...
ERROR -- Connection to server baal failed -- Error during initialization.
...is another window which says...
ERROR -- Unable to resolve baal, connecting locally.
...it never used to say...
ERROR -- Connection to server baal failed -- Connecting locally
...I had just misremembered that part. I have also attached my
XFree86 log if that is informative.
TIA
Gan

Gan Uesli Starling wrote:

I just upgraded my PC with a new Intel D875PBZ motherboard, a 
3.2GHz P4 and 4 GB RAM. The sad part is that the upgrade cost a 
fortune and I did it ONLY for OpenDX. And so far as I can tell, 
OpenDX is the only program

that is having a problem with itor so it seems.
Everything EXCEPT OpenDX continues to work as before. But on 
running a program in OpenDX I now get this error...

Connection to server baal failed - Error during initialization
...whereas I had used to get...
Connection to server baal failed - Connecting locally
...and it would just work.
I have just uninstalled/reinstalled OpenDX on my NetBSD 
1.6.2_RC4 box to no better result. It does the same.

What to do next???
Thanks,
Gan



--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us



--
.
David L. Thompson   Visualization and Imagery Solutions, Inc.
mailto:[EMAIL PROTECTED]5515 Skyway Drive, Missoula, MT 59804
Phone : (406)756-7472


Re: [opendx-users] Re: Connection to X server failed - Error during initializatioin

2004-09-22 Thread Gan Uesli Starling

It appears that OpenDX was asking for more memory than the OS allows.
Once I set the memory option to 2010 and not anything higher, then
the error Connection to server baal failed goes away.

Strangely, though, 2010 MB seems not enough as I get this error on
execute...

Out of memory cannot expand data segment...

...which is the whole reason I bought 4GB of RAM in the first place.
But I think I saw somebody else's thread on this and I will look into
that now.

Thanks to all,

Gan

David Thompson wrote:
As a work around, you can always set the DXHOST environment variable. 
Look at that for starters.


David


Okay, I have added baal as a 2nd alias after baal.amalekite.net in
my /etc/hosts so that I now only get...

ERROR - Connection to server baal failed - Error during initialization.

...and not any other connection error. I can do this...

baal: {1} ping -c 1 baal
PING baal.amalekite.net (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=0.155 ms

baal.amalekite.net PING Statistics
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.155/0.155/0.155/0.000 ms
baal: {2}

...so it's nothing to do with /etc/hosts. Yet all my other X programs
work as befofe. Is there some log in OpenDX which would tell me what
to look for next? why it fails to connect?

TIA

Gan

Gan Uesli Starling wrote:


Machine baal is the same as localhost. The /etc/hosts file
lists it as baal.amalekite.net but I can add baal, of course.
It had always connected before as localhost. All of my other
X utilities, blackbox, IceWM, mozilla, thunderbird, NEdit,
Sodipodi etc, etc...all work fine.
Gan
Mattijs Janssens writes:


Your machine (baal) is not in /etc/hosts?
Mattijs
Gan Uesli Starling wrote:


I made an oops in the first report.
Under the window which says...
ERROR -- Connection to server baal failed -- Error during 
initialization.

...is another window which says...
ERROR -- Unable to resolve baal, connecting locally.
...it never used to say...
ERROR -- Connection to server baal failed -- Connecting locally
...I had just misremembered that part. I have also attached my
XFree86 log if that is informative.
TIA
Gan

Gan Uesli Starling wrote:

I just upgraded my PC with a new Intel D875PBZ motherboard, a 
3.2GHz P4 and 4 GB RAM. The sad part is that the upgrade cost a 
fortune and I did it ONLY for OpenDX. And so far as I can tell, 
OpenDX is the only program

that is having a problem with itor so it seems.
Everything EXCEPT OpenDX continues to work as before. But on 
running a program in OpenDX I now get this error...

Connection to server baal failed - Error during initialization
...whereas I had used to get...
Connection to server baal failed - Connecting locally
...and it would just work.
I have just uninstalled/reinstalled OpenDX on my NetBSD 1.6.2_RC4 
box to no better result. It does the same.

What to do next???
Thanks,
Gan




--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us







--

 Mistera Sturno - Rarest Extinct Bird

 (+)__   Gan Uesli Starling
  ((__/)=-Kalamazoo, MI, USA
   `||`
++http://starling.us