My original question:
>I have a SPARCstation 10 running Solaris 2.3 with OpenWindows and
>Premier Motif 1.2.4A.
>I recently replaced a defective disk, reloaded my filesystems, and when I
>attempt to start OpenWindows (as a user or as root) I get the following
>Binding Unix socket: Invalid argument
>Fatal server error:
>Cannot establish unix listening socket
>/usr/openwin/bin/xinit: Server error.
>I thought it was /tmp/.X11 related directories, but apparently xinit
>recreates those, as well as the sockets within them, if they're not there.
>Here's a copy of the piece of the truss where I think the problem is
>occuring. Apparently it's passing an invalid argument to an operation on
>Has someone seen this before? What do I do to get OpenWindows to start up?
Thanks to all who responded:
email@example.com (Brett Lymn)
firstname.lastname@example.org (Casper Dik)
email@example.com (Tim Evans)
firstname.lastname@example.org (Jerry Weber)
email@example.com (Mark Cain)
> You will get these errors if you do not have permission to write the
> directories. Clean out /tmp and make sure that it is mode 1777.
> I recently saw this. Check the permissions on /devices/pseudo/tl*.
> If they're not, make them readable/writable by all.
> The only time I have seen this error was when we initially install 2.3 and
> try to start openwin without patches. Does the openwin patch show up with
> Have you checked if /dev/ticotsord exists and is a link to
> ../devices/pseudo/clone@0:ticotsord? And that the destination exists
> crw-rw-rw- 1 root sys 11, 9 Dec 23 1993 \
> I'd be tempted to do a reboot with the -r option just in case something
> needs to be reconfigured after the filesystem reload.
There isn't one yet. The problem has not yet been resolved, and these are the
only answers I have received. I have found a work-around to my problem: I do
not run OpenWindows right now. This isn't much of a work-around, though.
The /tmp permissions are as Brett said they should be. There are no
/devices/pseudo/tl*, Tim - it's 2.3, not 2.4. I never experienced the problem
that Jerry had; my problem occured after restoring off of a backup after
we put a new drive in. The only thing that comes to mind is that something
could have been corrupted in the backup tape (ugh!). The 'ls -l' on the
/dev/ticotsord came back exactly as Mark said it would, the destination
definitely is there, and a 'boot -r' didn't help.
If anyone has any more ideas, I'd love to hear them. Thanks for the quick
and helpful responses!!!
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:18 CDT