Couldn't contact X server - error - Thread - go-pugleaf

Thread View: alt.soft-sys.tooltalk

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Bjarne.Nordberg Thu, 30 Jul 1992 07:57

Couldn't contact X server - error

Author: Bjarne.Nordberg
Date: Thu, 30 Jul 1992 07:57

26 lines
1228 bytes

Always when I run my ToolTalk applications, they print out the
message:

Couldn't contact X server

after registering or sending messages.
I am only running locally on one machine, although I'm connected
to a large network.

It takes very long time (25-30s), to send a tt message with this bug.
Sometimes these lines go with it:

Xlib:  connection to "134.138.8.59:0.0" refused by server
Xlib:  Client is not authorized to connect to server

There is no delay in this case.

It appears to be some configuration information regarding tt which
is not maintained properly (old info not erased).

- Does anyone have a fix or workaround for this problem?

--
Bjarne Nordberg (Bjarne.Nordberg@eua.ericsson.se)
Ellemtel AB           ..   ..
PO Box 1505, S-125 25 ALVSJO, Sweden

Re: Couldn't contact X server - error

Author: Brian Holtz
Date: Thu, 30 Jul 1992 23:40

50 lines
2227 bytes

In article <1992Jul30.075728.28453@eua.ericsson.se> euabin@eua.ericsson.se
(Bjarne.Nordberg) writes:

>Always when I run my ToolTalk applications, they print out the
>message:
>
>Couldn't contact X server
>
>after registering or sending messages.
>I am only running locally on one machine, although I'm connected
>to a large network.
>
>It takes very long time (25-30s), to send a tt message with this bug.
>Sometimes these lines go with it:
>
>Xlib:  connection to "134.138.8.59:0.0" refused by server
>Xlib:  Client is not authorized to connect to server
>
>There is no delay in this case.
>
>It appears to be some configuration information regarding tt which
>is not maintained properly (old info not erased).

Bingo.  There was a bug in ToolTalk 1.0 (OWv3.0) in which, if a client
crashed while joined to a file, that client's session was still
recorded as interested in that file.

This bug is fixed in ToolTalk 1.0.1 (OWv3.0.1, SunOS 5.0, Solaris
2.0), and in the ToolTalk patch for 4.x (patch 100626).

>- Does anyone have a fix or workaround for this problem?

If you don't have the patch, then:

If you have ToolTalk 'objects' on the file, try:
  ttmv -L file file-
  ttrm -L file
  ttmv -L file- file
(This can't hurt, but I'm not 100% sure it will fix it, either.)

If you don't have any ToolTalk 'objects' on the file (or if you do and
you don't mind losing them), you can solve it by tt_file_destroy()ing
the file.  ttrm -L <file> does the same thing as tt_file_destroy().

A more drastic step is to remove all the ToolTalk data for the entire
filesystem, via rm -r /mountpoint/TT_DB.  If you do so, be sure to
restart the ToolTalk database server (rpc.ttdbserverd) on that
machine.
--
Brian Holtz

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads