- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: sshd errors in syslog.
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
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
тАО03-16-2015 06:08 AM
тАО03-16-2015 06:08 AM
we are running 11vi3 patched to 2014 on bl890's and we are getting this message in the syslog ..ALOT could someone explain what this means? is this just ssh resetting or are we haveing an issue??
Sep 24 21:00:52 server01 sshd[23242]: Received SIGHUP; restarting.
Sep 24 21:00:52 server01 sshd[27657]: Server listening on :: port 22.
Sep 24 21:00:52 server01 sshd[27657]: Server listening on 0.0.0.0 port 22.
Sep 24 21:03:34 server01 sshd[10810]: SSH: Server;Ltype: Kex;Remote: 199.204.56.21-50383;Enc: aes256-ctr;MAC: hmac-sha1;Comp: none
thanks for any help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2015 08:15 AM
тАО03-16-2015 08:15 AM
Re: sshd errors in syslog.
It does appear as if SSH is being killed and restarted.
I can duplicate your messages by issuing a 'kill -HUP' command against the /opt/ssh/sbin/sshd process.
If this is occurring regularly that would seem abnormal to me.
I don't see anything similar in HP's knowledge base or via a Google search that indicates this is a widespread issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2015 08:56 AM
тАО03-16-2015 08:56 AM
Re: sshd errors in syslog.
It is happening on alot of my server , 10 so far about every hour on the hour...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2015 09:17 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2015 06:44 PM - edited тАО03-16-2015 06:47 PM
тАО03-16-2015 06:44 PM - edited тАО03-16-2015 06:47 PM
Re: sshd errors in syslog.
SIGHUP means that the connection has been terminated. In the "good old days", a network connection was between a terminal or another computer using a modem, but line noise or a bad connection would cause the modem to hang up. So the communication program would receive the HUP (hangup) signal, SIGHUP. For modern systems, a SIGHUP is usually caused by severe network problems. A bad switch or router, or more commonly, half-duplex for 100 Mbit or faster connections. For all the LAN connections (lan0, lan1, lan2...), check the conection like this:
# lanadmin -x 0
Speed = 1000 Full-Duplex.
Autonegotiation = On.
# lanadmin -x 1
Speed = 10000 Full Duplex.
# lanadmin -x 2
Current Config = 100 Full-Duplex AUTONEG
The format will be different for different versions of HP-UX and LAN cards.
The key word is Full Duplex. Anything that says Half Duplex is unless you are running 25-30 year old hardware with 10 Mbit links. To verify the Half Duplex issue, change -x to -g as in lanadmin -g 0
The bottom half (after Index) of the listing will be all zeros for a healthy link.
If the duplex is correct, look at your switch and router logs, specifically for arp, broadcast or discovery storms which will affect multiple systems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2015 05:47 AM
тАО03-25-2015 05:47 AM
Re: sshd errors in syslog.
This is something our vendor setup..not sure why but they are causing it via cfengine, will have to figure out if we still need this or not..
thanks for the help.
solved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2015 10:37 PM
тАО04-07-2015 10:37 PM
Re: sshd errors in syslog.
It's possible the SIGHUP signal abnormaly shuts down the SSHD, and generates a "core dump" file, if you can read and investigate it, will can get more info.
http://renatomartini.net
http://www.iti.gov.br