- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- /sbin/sh corruption
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
02-27-2002 11:33 AM
02-27-2002 11:33 AM
/sbin/sh corruption
I have an HP E class running 10.20 which has experienced corruption of /sbin/sh. There's no indication that anything has changed (date, ownership or chksum) yet when attempting to login at the console or telnet as root we receive 'no shell'. The console starts scrolling with the typical getty errors since a respawn of the console isn't possible. Once we provide a 'new' copy of the shell all is back to normal. Anyone have any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 11:43 AM
02-27-2002 11:43 AM
Re: /sbin/sh corruption
Try things like 'file', 'what', 'strings', etc. to see if anything is different. Had you installed any patches or anything recently that could have caused this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 11:53 AM
02-27-2002 11:53 AM
Re: /sbin/sh corruption
My first question is where are you getting your new copy. Bear in mind that you must have a version from /sbin that is staically linked. The one in /usr/bin won't work. If this is a recurring problem, some process must be copying to /sbin/sh, perhaps an arrant script with stdout redirected to /sbin/sh. In any event, you need to hunt this down quickly.
Patrick's idea is sound. I wouls save a copy of the bad version and examine it with every tool I could find. In addition to those mentioned, I would add od -c /sbin/sh | pg.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 12:01 PM
02-27-2002 12:01 PM
Re: /sbin/sh corruption
I know 11.x doesn't use the shells file any more.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 12:16 PM
02-27-2002 12:16 PM
Re: /sbin/sh corruption
So, does it appear /sbin/sh wasn't actually changed? The date / time stamp, size, and checksum didn't change?
When you say you provide a 'new' copy of the shell, do you mean you copy a shell to /sbin/sh or do you mean you enter the "sh" command?
Could the /etc/passwd entry for root's shell be bungled?
I don't believe /etc/shells would cause a problem for logging in. It would for ftp access.
Darrell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 12:48 PM
02-27-2002 12:48 PM
Re: /sbin/sh corruption
The copy is /sbin/sh from another 10.20 machine. After moving the copied one into place logins are possible again.
/etc/passwd for root lists /sbin/sh as the default shell.
No new patches have been loaded recently, in fact, nothing has been added to the machine before or since this started. Basically it functions as a mailhost.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2002 02:14 PM
02-27-2002 02:14 PM
Re: /sbin/sh corruption
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2002 09:25 AM
03-04-2002 09:25 AM
Re: /sbin/sh corruption
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2002 11:13 AM
03-04-2002 11:13 AM
Re: /sbin/sh corruption
I found this document that seems to have fixed the problem. You can find this on Veritas's knowledge base searching for "no shell".
Ben
Symptom:
The following error: /sbin/sh get
Exact Error Message:
/sbin/sh get
Solution:
This is an OnlineJFS problem.
The fix is to apply this patch from HP: PHKL_19530.
This patch has been replaced by patch PHKL_20356.
If this problem is encountered check to see if one of these patches have
been installed: PHKL_19530 or PHKL_20356.
If
--------------------------------------------------------------------------------
Tech
Tech
Tech
Last Updated: August 31 2001 05:59 PM GMT
This information in this Tech
Products: NetBackup DataCenter 3.4, 3.4.1
NetBackup (UNIX Platforms) 3.1.1, 3.2
Subject: NetBackup DataCenter - Application - Compatibility
NetBackup DataCenter - Application - Informational
NetBackup DataCenter - Application - Patch
NetBackup v3.2 and prior (UNIX Platforms) - Application - Compatibility
NetBackup v3.2 and prior (UNIX Platforms) - Application - Informational
NetBackup v3.2 and prior (UNIX Platforms) - Application - Patch
Languages: English
Operating Systems: HP-UX 10.2