- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- syslog.log
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 05:41 AM
тАО04-05-2002 05:41 AM
syslog.log
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 05:53 AM
тАО04-05-2002 05:53 AM
Re: syslog.log
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 05:58 AM
тАО04-05-2002 05:58 AM
Re: syslog.log
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 06:07 AM
тАО04-05-2002 06:07 AM
Re: syslog.log
Dr_dt finished with:
0 ERROR messages
4 WARNING messages
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 06:43 AM
тАО04-05-2002 06:43 AM
Re: syslog.log
Confirm your system can resolve "regulus" to an IP address.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 08:02 AM
тАО04-05-2002 08:02 AM
Re: syslog.log
I resolve my problem with:
rm /dev/crt*
reboot -r
Frank.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 08:03 AM
тАО04-05-2002 08:03 AM
Re: syslog.log
Check this out:
http://us-support.external.hp.com/cki/bin/doc.pl/sid=bc13218a08783501bf/screen=ckiDisplayDocument?docId=200000045025972
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 08:06 AM
тАО04-05-2002 08:06 AM
Re: syslog.log
Another try :
http://us-support.external.hp.com/cki/bin/doc.pl/sid=bc13218a08783501bf/screen=ckiDisplayDocument?docId=200000049809718
HTH,
Shiju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2002 08:29 AM
тАО04-05-2002 08:29 AM
Re: syslog.log
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2004 03:44 PM
тАО02-09-2004 03:44 PM
Re: syslog.log
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....