>>> On 5/27/2016 at 08:57 AM, Grzegorz Powiedziuk <[email protected]> >>> wrote: > One other thing you could try (saved me many times) but a bit trouble some > is doing some stracing.
This was something I was going to suggest as well. > 1. ssh to the user@server and let it sit on the login > 2. on the server, do ps auxwww |grep sshd and look for a new spawned > process Personally I would just pick the "top most" ssh process started at boot time _before_ trying to connect over the network. -snip- > 3. strace -p 36203 &> logfile.x I would probably try strace -f -p 36203 -s500 -o strace.sshd You'll need to break out of it using ^c since the process won't terminate on its own. -snip-> 5. Now examine the the trace by looking at the logile.x (it will be a big > file). If you don't have terminal server access you'll probably need to access it via FTP since scp is not likely to work. Which raises a perhaps interesting question. From the 3270 console are you able to ssh/scp _out_ of the system? That would at least allow you to send things off the system to some place you can use "normal" tools. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
