Re: *ADMIN instance of HTTP server failing on startup

We now have the issue resolved.

I asked about the "7 Step Plan" and he said they usually only do that when
*ADMIN is not listening on the correct port.

When I spoke with IBM service yesterday I also pointed out that the
instance was throwing the "Error 107 means the certificate has expired".
(Thank you Jack!)

IBM got onto our system, made a config change to stop *ADMIN being SSL and
then it started back up. I now have the option to run the "Configure SSL
for ADMIN" wizard and secure it once again.

Do you run your HTTP servers with SSL enabled on your admin instance? What
are the up and down sides?

Thanks for your help!

Jim Essinger
Western Power Sports
Boise, ID


On Tue, Mar 25, 2014 at 5:54 AM, <rob@xxxxxxxxx> wrote:

I've had a somewhat similar experience. I couldn't get to the 2001 port
on one of my 11 lpars. And, no, it was not just really slow. Even though
I had some (but not all) of the ADMIN* jobs running none was monitoring
port 2001. After checking to see if there was a configuration change to
use a different port (there wasn't) IBM ran:

A) End the QHTTPSVR subsystem
B) Run the following CL commands:

QSYS/CALL PGM(QSYSDIR/QLWINSTALL)
QSYS/CALL PGM(QSYSDIR/QLWINSTADM)
QSYS/CALL PGM(QSYSDIR/QLWINSTLP)
QSYS/CALL PGM(QSYSDIR/QIWSIEX01) PARM(V7R1M0 V7R1M0)
QSYS/CALL PGM(QSYS/QLWIMIG) PARM(*AUTH *SS03)
QSYS/CALL PGM(QSYS/QLWIMIG) PARM(*AUTH *DG1)

That was copied and pasted directly out of pmr 84168,082,000

Apparently it's not unheard of.

See IBM technote N1011802 at:
http://www-01.ibm.com/support/docview.wss?uid=nas8N1011802

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.