HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- HPE 9000 and HPE e3000 Servers
- >
- SAM error on adding modem
HPE 9000 and HPE e3000 Servers
1835022
Members
2400
Online
110073
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-06-2002 02:30 AM
03-06-2002 02:30 AM
SAM error on adding modem
hello
I have a D class running 10.20 with eisa mux
trying to add a modem to port a2 using sam and get the following error (this happens after typing baud rate, Working... appears on screen the error box)
unexpected exit: process LANG=C LC_ALL=C /usr/bin/lbin/samx -C -p 3411 /usr/sam/lib//tm.ui exited with non-zero exit status sh:6417 Memory Fault (core dumped)
have run swconfig all appears okay, checked inittab and removed any old devices on this mux
anyone have any ideas for next step before I reinstall SAM
thanks
Paul Gold
CP Ships
I have a D class running 10.20 with eisa mux
trying to add a modem to port a2 using sam and get the following error (this happens after typing baud rate, Working... appears on screen the error box)
unexpected exit: process LANG=C LC_ALL=C /usr/bin/lbin/samx -C -p 3411 /usr/sam/lib//tm.ui exited with non-zero exit status sh:6417 Memory Fault (core dumped)
have run swconfig all appears okay, checked inittab and removed any old devices on this mux
anyone have any ideas for next step before I reinstall SAM
thanks
Paul Gold
CP Ships
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 03:55 PM
03-07-2002 03:55 PM
Re: SAM error on adding modem
Paul,
Apply the latest SAM/OBAM patch for your system. I have seen this before and applying/reapplying the SAM patch fixed the problem.
Latest SAM patch is:
PHCO_22268
Best Regards,
Eric
Apply the latest SAM/OBAM patch for your system. I have seen this before and applying/reapplying the SAM patch fixed the problem.
Latest SAM patch is:
PHCO_22268
Best Regards,
Eric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2002 07:04 PM
03-07-2002 07:04 PM
Re: SAM error on adding modem
From technical knowledge DB ..
Use this checklist to resolve the error:
1) Check for an offending entry in /etc/inittab:
The most common error in the inittab refers to the ups.
ups::respawn:rtprion 0 /usr/lbin/ups_mond ---> change this to:
ups::respawn:rtprion 0 /usr/lbin/ups_mond -f /etc/ups_conf
A clean copy of the inittab resides in /usr/newconfig/etc/inittab.
To rule out a problem with the /etc/inittab try the following:
# cp /etc/inittab /tmp/inittab.old
# cp /usr/newconfig/etc/inittab /etc/inittab
Check for the error.
2) Check for an offending entry in /etc/gettydefs.
To rule out a problem with the /etc/gettydefs try the following:
# cp /etc/gettydefs /tmp/gettydefs.old
# cp /usr/newconfig/etc/gettydefs /etc/gettydefs
Check again for the error.
3) Check for an unconfigured fileset.
# swlist -l fileset -a state |more
If a fileset comes back as INSTALLED but not CONFIGURED then issue the following:
# swconfig \*
4) Check for the latest SAM patch and libc patch version. [PHCO_19046/PACHRDME/English]s700_800 10.20 Cumulative SAM/ObAM Patch
[PHCO_20441/PACHRDME/English] s700_800 10.20 libc cumulative patch
Use this checklist to resolve the error:
1) Check for an offending entry in /etc/inittab:
The most common error in the inittab refers to the ups.
ups::respawn:rtprion 0 /usr/lbin/ups_mond ---> change this to:
ups::respawn:rtprion 0 /usr/lbin/ups_mond -f /etc/ups_conf
A clean copy of the inittab resides in /usr/newconfig/etc/inittab.
To rule out a problem with the /etc/inittab try the following:
# cp /etc/inittab /tmp/inittab.old
# cp /usr/newconfig/etc/inittab /etc/inittab
Check for the error.
2) Check for an offending entry in /etc/gettydefs.
To rule out a problem with the /etc/gettydefs try the following:
# cp /etc/gettydefs /tmp/gettydefs.old
# cp /usr/newconfig/etc/gettydefs /etc/gettydefs
Check again for the error.
3) Check for an unconfigured fileset.
# swlist -l fileset -a state |more
If a fileset comes back as INSTALLED but not CONFIGURED then issue the following:
# swconfig \*
4) Check for the latest SAM patch and libc patch version. [PHCO_19046/PACHRDME/English]s700_800 10.20 Cumulative SAM/ObAM Patch
[PHCO_20441/PACHRDME/English] s700_800 10.20 libc cumulative patch
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP