- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- OS signal SIGSEGV received
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
Forums
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
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
11-22-2002 03:38 AM
11-22-2002 03:38 AM
OS signal SIGSEGV received
I have problem with application :
An alarm has been detected by Genesys Solution Magement Layer.
Alarm Reaction: BO_TServer_Crash_OS_Signal_EMAIL
Alarm Condition:
ID: 149
Name: ERS_TServer_BCK_BO_Crash_OSSignal
category: Critical
Application:
ID: 285
Name: ERS_TServer_BCK_BO
Type: TServer
Message:
ID: 2024
Msg description:
OS signal SIGSEGV received
can I resolve this problem?
I have see on itrc that the cause of problem can parameters kernel .
thanx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 03:48 AM
11-22-2002 03:48 AM
Re: OS signal SIGSEGV received
increase maxdsize / maxdsize_64bits
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 03:49 AM
11-22-2002 03:49 AM
Re: OS signal SIGSEGV received
increase maxdsize / maxdsize_64bit
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 03:55 AM
11-22-2002 03:55 AM
Re: OS signal SIGSEGV received
maxdsiz_64bit
maxtsiz_64bit
maxssiz_64bit
maxdsiz
maxssiz
maxtsiz
These kernel parameters default have some values like 64M.
The reason for having the parameters as low is to avoid processes running away from taking too much memory.
It depends on the application you use.
How much is your system having.
you can also decrease the amount of buffer cache as it is too high 50% half of the memroy(dbc_max_pct)
Revert
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 03:59 AM
11-22-2002 03:59 AM
Re: OS signal SIGSEGV received
increase maxdsize / maxdsize_64bits
:) I couldn't help myself
Ta Gideon
Mike [no points please] Fisher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 04:16 AM
11-22-2002 04:16 AM
Re: OS signal SIGSEGV received
problems.
maxdsiz_64bit
maxtsiz_64bit
maxssiz_64bit
maxdsiz
maxssiz
maxtsiz
These kernel parameters default have some values like 64M.
The reason for having the parameters as low is to avoid processes
running away from taking too much memory.
It depends on the application you use.
How much is your system having.
you can also decrease the amount of buffer cache as it is too high 50%
half of the memroy(dbc_max_pct)
Revert
Thanks
jimmy
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2002 04:25 AM
11-22-2002 04:25 AM