- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: X-server can not be started
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
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
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
10-09-2011 02:39 AM
10-09-2011 02:39 AM
Re: X-server can not be started
The screenshot you attached contains an interesting error message:
config: ran out of internal memory(malloc)
This suggests there is not enough RAM+swap space to configure the kernel.
Please run "dmesg |grep Physical": if the system has not produced too many kernel messages since the last time it was rebooted, the output should be a line that indicates the amount of RAM memory in the system.
Please run "swapinfo -tam" and copy & paste the output to this thread. Knowing your amount of system RAM and swap should allow us to evaluate your current configuration and make better suggestions for next steps.
Adding more swap space should allow you to successfully configure a new kernel. The outputs of "vgdisplay" and "bdf" would help in deciding where to place the new swap space.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2011 04:19 AM
10-09-2011 04:19 AM
Re: X-server can not be started
First thing i did when receiving this HP was run the bdf. As you shell see the results are fine. But I also suspect that you point to the problem.
I attached as per your request the commands' display.
Thank you,
Yali
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2011 08:08 PM - edited 10-09-2011 08:12 PM
10-09-2011 08:08 PM - edited 10-09-2011 08:12 PM
Re: X-server can not be started
>The screenshot you attached contains an interesting error message:
>config: ran out of internal memory(malloc)
> This suggests there is not enough RAM+swap space to configure the kernel.
I noticed that too. But it appears to be a strings(1) output from the core or executable, I.e. useless and counterproductive.
>Please run "swapinfo -tam". Knowing your amount of system RAM and swap
There seems to be 6 Gb free, so if that malloc message was the problem, it would be maxdsiz being too small.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 09:19 AM
10-10-2011 09:19 AM
Re: X-server can not be started
So, what next? Can I supply more information that should help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 09:25 AM
10-10-2011 09:25 AM
Re: X-server can not be started
>Can I supply more information that should help?
Where did you get those config error messages?
What is your maxdsiz kernel value?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 12:47 AM
10-11-2011 12:47 AM
Re: X-server can not be started
Those config error messages come from the "strings" command to the /etc/config file.
I tried to attached it but I couldn't (see above).
Sorry, but I don't know what is the maxdsize and how to find out its value?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 01:23 AM
10-11-2011 01:23 AM
Re: X-server can not be started
>Those config error messages come from the "strings" command to the /etc/config file.
Don't do that. That gives a list of ALL possible messages, not the one you got,
>but I don't know what is the maxdsiz and how to find out its value?
/usr/sbin/kmtune -q maxdsiz # for 11.11
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 02:11 AM
10-11-2011 02:11 AM
Re: X-server can not be started
Oppsss, Ok.
Parameter Current Dyn Planned
===============================================
maxdsiz 3221225472 - 3221225472
What does this parameter mean?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 02:12 AM
10-11-2011 02:12 AM
Re: X-server can not be started
Also in SAM - Kernel Configuration - Configurable Parameters.
Mine is set to (hex) 0xc0000000 (or 3*1024*1024*1024)
V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 02:30 AM
10-11-2011 02:30 AM
Re: X-server can not be started
>What does this parameter mean?
Your value is 3 Gb, plenty enough. Unless you have maxdsiz too large or have used ulimit to make it smaller.
/usr/sbin/kmtune -q maxssiz # for 11.11
ulimit -a