topic Re: XFree86 server aborting with signal 11 in Operating System - Linux

XFree86 server aborting with signal 11

Karfich — Mon, 16 Oct 2000 12:16:02 GMT

> Hello to all,
>
> We have about 10 PC's configured all the same way as
Xterminals connecting
> to 5 different Xclients, running the same application.
> We use
> Suse Linux Version 2.2.10
> Gcc Version 2.7.2.3
> Xfree86 3.3.4 because of the problems I upgraded to 3.3.6
>
> Hardware:
> HP VL6/333 MHz
>
> Graphic: Cirrus Logic GD5465 (on board)
>
>
> Two of them are crashing about once a day. We cannot
reproduce a certain
> situation when they crash.
>
> I tried several things:
>
> Editing XF86Config:
> Section "Device"
> Option "noaccel" User
> complain they cannot work with this option, makes them
feel like drunken
>
>
>
> Changing the PC (until now not the mouse and not the
keyboard) Does
> not help.
>
> Upgrading to Xfree86 3.3.6 Does
> not help.
>
> Switching from one Xclient to another
Does not help
>
>
> We have error messages in /var/log/X:0msgs
>
> Have a look in the attachment.
>
> Thanks for your Ideas.
>
> Natascha
>

Re: XFree86 server aborting with signal 11

Andreas Voss — Mon, 16 Oct 2000 13:09:31 GMT

Hi,

have a look at your hostname configuration.
Try a nslookup to 146.216.20.73.
Did you get the hostname ?
If not check /etc/hosts or if you have DNS (server) check the DNS configuration.

Regards

Re: XFree86 server aborting with signal 11

Albert E. Whale, CISSP — Mon, 16 Oct 2000 13:49:16 GMT

Make sure that all X Clients which connect to other devices are correctly defined in DNS, both forward and reverse lookup need to operate properly.

Give that a whirl.

If that doesn't work, I would investigate the level of Netscape you are using. MIT-Cookies are related to Web Browsers.

HTH!

Re: XFree86 server aborting with signal 11

Karfich — Mon, 16 Oct 2000 13:55:35 GMT

On my XClient nslookup works well.
On my XServer nslookup is not installed, but
I can ping my own IP-adress.
The /etc/hosts looks good, I can see
127.0.0.1 localhost and
the correct IP and Hostname.

Re: XFree86 server aborting with signal 11

Albert E. Whale, CISSP — Mon, 16 Oct 2000 14:01:05 GMT

Karfich,

You should install BIND (which includes DNS and nslookup) on the XServer. It is recommended.

Since your Clients are able to perform nslookups, so should your Server. This will also maintain a constant information source for IP Addresses and Hostnames.

This should be performed before attempting any further diagnostics.

Re: XFree86 server aborting with signal 11

Karfich — Mon, 16 Oct 2000 14:14:07 GMT

Hello Albert,
I am not using Netscape at all, it is even not installed. But I wondered also about the MAGIC COOKIE Authentification message.
Perhaps I have to force the system to make theauthentification with xhost ? (how can I do this ?)
Ciao
Natascha

Re: XFree86 server aborting with signal 11

Karfich — Mon, 16 Oct 2000 14:19:51 GMT

Ok I will install BIND and tell you the result.
Thanks to all for your fast response.

Ciao Natascha

Re: XFree86 server aborting with signal 11

Albert E. Whale, CISSP — Mon, 16 Oct 2000 15:02:44 GMT

Good Point regarding the Cookie.

Xhost, XServer, XClient security has developed and evloved arount the IP Address/FQDNS name.

Installing DNS should relieve your problem. The mere fact that the Clients use DNS and the Server does not is an issue, and possible source of the MIT-COOKIE (which come to think of it is an X Windows issue, not Http).

Hope that helps.