- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Fixing sshd after someone hosed /var
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
тАО08-04-2010 05:13 PM
тАО08-04-2010 05:13 PM
Fixing sshd after someone hosed /var
So now when I try to connect with ssh I get "connection refused" and nothing in the syslog about the connect.
Doing some google I found /sbin/init.d/secsh start but it just tells me.
/var/empty must be owned by root and not group or world-writable.
EXIT CODE: 255
From the bits and pieces I have learned they were trying to cleanup the printers in sam and so tried to do a save/restore of the printer config to make sure its clean.
Doing the restore though apparently caused the printers list to be empty so they restored from tape to get the devices back.
Apparently breaking ssh. Grrr.
So how can I get this fixed? Running "ps -ef | grep sshd" shows me that sshd is still running.
root 19916 24414 1 18:12:22 pts/te 0:00 grep sshd
Thank you.
- Tags:
- sshd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 06:14 PM
тАО08-04-2010 06:14 PM
Re: Fixing sshd after someone hosed /var
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 06:28 PM
тАО08-04-2010 06:28 PM
Re: Fixing sshd after someone hosed /var
i wish somehow u could assign 10 point to yourself.
BR,
Kapil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2010 06:43 PM
тАО08-04-2010 06:43 PM
Re: Fixing sshd after someone hosed /var
> "connection refused" and nothing in the
> syslog about the connect.
There's nothing in the log because sshd is
not running ("Connection refused"), so it
can't log anything.
> Running "ps -ef | grep sshd" shows me that
> sshd is still running.
>
> root 19916 24414 1 18:12:22 pts/te 0:00 grep sshd
That's your grep command, not the sshd
itself. What _that_ shows is that sshd is
_not_ running, which is consistent with that
"Connection refused" complaint above.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2010 07:56 PM
тАО08-08-2010 07:56 PM
Re: Fixing sshd after someone hosed /var
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-08-2010 09:03 PM
тАО08-08-2010 09:03 PM
Re: Fixing sshd after someone hosed /var
> grep command.
The usual trick in this case is to use a
simple regular expression which won't match
itself. For example:
grep [s]shd
I find it to be a trick worth remembering.