|
Just in case anyone runs across this error, I thought I'd make a note of it for the list. This is especially scary (but in the long run just annoying) for machines that typically run 24/7 for weeks or months at a time. So let's say you decide to do some scheduled downtime, and then you bring your machine back online. Suddenly the HTTP server just doesn't come up! You don't see any logs or anything. When you watch it in WRKACTJOB, all the jobs come up, then immediately go into EOJ and end. If you look carefully in QHST, you'll see several errors: TCP7428, TCP7402 and finally TCP7429, whose error text says "Failure in SSL_Init rc=-24 and errno=3021". This is the critical message; the rc=-24 tells you what really happened - your SSL certificate expired sometime since your last IPL! In my case, the certificate had expired sometime before, but you don't get nasty messages. And once you know it's an expired cert, it's a piece of cake to fix - you simply go in and renew the cert and then assign it to the HTTP application. I spent more time figuring out what was wrong than fixing it once I knew. Anyway, that's my little goodie for today. I'll close with the IBM address for SSL errors (V5R1 InfoCenter): http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/rzaiw/r zaiwsslre.htm Joe
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.