Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

syslog.log

Francois Bariselle_3
Regular Advisor

syslog.log

Hi,

My B132L Workstation HP-UX 10.20 boot without error message in /etc/rc.log but I have this message on the screen:

The X server can not be started on display regulus:0...

I check in syslog.log and I found this error message:

Apr 5 08:36:32 regulus vmunix: System Console is on the ITE
Apr 5 08:36:32 regulus vmunix: Networking memory for fragment reassembly is restricted to 10526720 bytes
Apr 5 08:36:32 regulus vmunix: Swap device table: (start & size given in 512-byte blocks)
Apr 5 08:36:32 regulus vmunix: entry 0 - auto-configured on root device; SCSI: dev = 0x1f006000, O_SYNC I/O cannot be forced to media with this disk!
Apr 5 08:36:32 regulus vmunix: Immediate Reporting will be performed; FUA bit cleared from cdb.
Apr 5 08:36:32 regulus vmunix: See scsi_disk(7) and scsictl(1m) manpages.

Help me please.

Frank.
Fais la ...
10 REPLIES
Steve Steel
Honored Contributor

Re: syslog.log

Hi

If you are running cde try
/usr/contrib/bin/X11/dr_dt
correct any faults

look in /var/dt/Xerrors for faults
or /var/vue/Xerrors


Check that mouse is attached.
Also keyboard
tail /etc/rc.log for other faults.


o_sync i/o cannot be forced to media with this disk.
Immediate reporting will be performed;
FUA bit cleared from cdv.

THIS COMES FROM OLD DISK FIRMWARE WHICH SHOULD BE UPDATED


Steve Steel

If you want truly to understand something, try to change it. (Kurt Lewin)
Francois Bariselle_3
Regular Advisor

Re: syslog.log

Hi Steve,

I found this error in /var/dt/Xerror.log:

Fri Apr 5 09:02:48 2002
error (pid 1116): Server for display regulus:0 can't be started.
Unable to open the Graphics Resource Manager.
The error occurred during GRM initialization.
The X11 server must be able to communicate with the
Fatal server error:
GRM process.
XIO: fatal IO error 232 (Connection reset by peer) on X server "regulus:0.0"
after 0 requests (0 known processed) with 0 events remaining.


Frank.
Fais la ...
Francois Bariselle_3
Regular Advisor

Re: syslog.log

Hi Steve,

Dr_dt finished with:

0 ERROR messages
4 WARNING messages

Frank
Fais la ...
Tom Danzig
Honored Contributor

Re: syslog.log

Could be a hostname to IP resolution issue.

Confirm your system can resolve "regulus" to an IP address.
Francois Bariselle_3
Regular Advisor

Re: syslog.log

Thanks for all,

I resolve my problem with:

rm /dev/crt*
reboot -r

Frank.
Fais la ...
Helen French
Honored Contributor

Re: syslog.log

Helen French
Honored Contributor

Re: syslog.log

S.K. Chan
Honored Contributor

Re: syslog.log

Found this from Technical DB .. hope it helps.

The problem is caused by the fact that the X server can't connect with the Graphics Resource Manager daemon process which
manages offscreen memory, fonts and miscellaneous graphics resources for Starbase and X programs. The GMR daemon process must be able to start up for X and Starbase to run correctly.

The permissions on the grmd program itself and the directories which it writes into must be correct. The following is a list of the correct permissions on the relevant files:

ll /usr/lib/grmd
-r-sr-sr-x 1 daemon sys 40972 Feb 17 11:00 /usr/lib/grmd
ll -d /usr/spool/sockets
drwxrwxr-x 4 root sys 1024 Apr 13 00:55 /usr/spool/sockets
ll /usr/spool/sockets
drwxrwxr-x 2 bin sys 1024 Jul 6 09:26 X11


Pedda Amato
Occasional Visitor

Re: syslog.log

Hi,
I have the same problem but unfortunately I still can not get my GRM started. i have changed the permissions to reflect the ones here, I can do a nslookup on both the hostname and the ip address.
I did find an error message abit different now in /var/dt/Xerrors which states:
error (pid 1988): Server for display wiluna:0 can't be started.
Please, any suggestions would be great....

Hoefnix
Honored Contributor

Re: syslog.log

Niel,

Check your settings in the /etc/X11/X0screens if it reflects your config.
The file explains itself in comments.

Regards,
Peter