|
John,
There may be a problem with the sshd configuration file.
If you have *ALLOBJ authority, you can try to start the SSHD server
manually
from QP2TERM.
In QP2TERM enter
/usr/sbin/sshd -ddd
Messages similar to the following will be displayed in QP2TERm If any
configuration errors were found.
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc/sshd_config: terminating, 1 bad
configuration options
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc/sshd_config line 113: Bad SSH2
cipher spec
You can still run the /usr/sbin/sshd -ddd in QP2TERM even if you do not
have
*ALLOBJ and it will still tell you if it any errors were found, but the
actual starting of the SSH daemon will fail for authority reasons.
If you're running at 7.2 or above the configuration file is located at
/QOpenSys/QIBM/UserData/SC1/OpenSSH/etc/sshd_config
IBM also places a backup copy of the configuration file at the following
path.
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/etc_template/sshd_config
If there are configuration errors, you could copy the backup copy to the
base copy.
Make sure to make a backup copy of the config file before making any
changes
and only modify the configuration if you're an administration responsible
for the ssh configuration.
Rob W
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of John
Yeung
Sent: Monday, April 1, 2024 9:18 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Why would SSHD not start, even if QUSRWRK is active?
A long time ago, it was my experience that failure to start SSHD was
usually
due to QUSRWRK not being started.
Today, after an IPL over the weekend, I tried
STRTCPSVR *SSHD
and got the usual
SSHD server starting.
message, but the server never came up. QUSRWRK is up and running, and in
fact other jobs are successfully running on that subsystem, but no
QP0ZSPWP,
and nothing showing function PGM-sshd.
What else can I check?
John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.