Select Menu

Ads

Random Posts

Powered By Blogger
Powered By Blogger

Blog Archive

Search This Blog

Blog Archive

Thirupal Boreddy. Powered by Blogger.

My Blog List

Followers

Lorem 1

Technology

Circle Gallery

Shooting

Racing

News

Lorem 4

» » Restarting SSH broker in the event of a hang

Restarting SSH broker in the event of a hang.
Pre requirements:
This should only be attempted in the event of outbound connections hanging.

• If you are having problems performing a direct SSH connection “into” a system, this is not the correct procedure.

• You should attempt to make an SSH connection to a few other systems first, to ensure they all hang, before running with this. If ANY of the connections work, this is not a broker hang problem, but a problem on the specific system you need to connect to.


Steps to restart the broker:
• Ensure you are logged onto the system as the affected user

• "ps -aef | grep -i broker" take note of the PID on the ssh broker process

• Try command “ssh-broker-g3 –exit” to stop the process

• "ps -aef | grep -i broker" to check that it is now gone

Note: if the “ssh-broker-g3 –exit” command did not work, try it a 2nd, and maybe even a 3rd time before going to the kill option.

• If the broker process will not go, a “kill -9 PID” will need to be used

Note: A new broker will start up the first time the user attempts an outbound SSH connection, so the connection can be tested at this point.

About Oracle DBA World

WePress Theme is officially developed by Templatezy Team. We published High quality Blogger Templates with Awesome Design for blogspot lovers.The very first Blogger Templates Company where you will find Responsive Design Templates.
«
Next
Newer Post
»
Previous
Older Post

No comments

Leave a Reply

QUERY FOR CPU USAGE

select  a.target_name as HOST, to_char(a.rollup_timestamp,' dd-Mon-yy::hh24:mi') as "DAY-TIME", sum(c.cpu_count) as ...