Well, installed latest cumulative and group PTFs, and got an error that the ADMIN server failed to start. It's pleasantly explicit in the joblog:

Cause . . . . . : Directive SSLEngine is not a recognized HTTP server
directive. The HTTP server did not start.

Cause . . . . . : HTTP Server instance ADMIN failed because of a
configuration error on line 15 in configuration file

Of course, I didn't add that configuration line; IBM did. I'm not sure why it would be broken all of a sudden.

<VirtualHost *:2010>
RewriteEngine On
RewriteOptions Inherit
RewriteRule ^/$ %{HTTP_HOST} [C]
RewriteRule ^(.*):.*$ https://$1:2005/ibm/console [R,L]
SSLEngine On
SSLClientAuth Optional

For fun, I commented out the line in error and got:
Directive SSLAppName is not a recognized HTTP server directive.
Directive SSLClientAuth is not a recognized HTTP server directive.

After removing all those, I see ports 2001, 2002, 2006, 2008, 2010, 2011, 2017 are listening.

Connecting to port 2001 redirects to /ibm/console which generates an Internal Server Error reply.

Nothing new, interesting, or explicit in joblog, so I'll have to resume troubleshooting when I have more time available.
Sean Porterfield

-----Original Message-----
From: Porterfield, Sean
Sent: Friday, May 16, 2014 09:45
To: 'Midrange Systems Technical Discussion'
Subject: RE: Navigator for i vrs. System i Navigator

Tim Rowe wrote: "There was a comment about SSL, The Navigator runs under SSL, always has, always will."

Your definition of "always" may differ from mine. I used to access http://system:2001 or https://system:2010 with the same results other than SSL (with port 2001 only being used the very first time when I configured SSL eons ago). When port 2005 was introduced to the mix, I did not get redirected and had to provide credentials unencrypted on port 2001 or manually adjust my URL to a specific destination on port 2005. I could not access https://system:2005 directly (as a complete URL). That was long ago, in Internet time.

The areVerify.sh was helpful, thanks for that. No problems on my production system, but it did find some things that I've fixed on the backup system. I disabled IPV6 a while ago, so that's not related to my issue.

I can't speak to performance, since I haven't successfully accessed it since the dark ages referred to in my first paragraph above. I'm guessing that was on 6.1 rather than 7.1, but I don't recall. With my systems currently on TR6 and SF99368 at group 20, I'm sure I can expect better results after patching.
Sean Porterfield

-----Original Message-----
From: Tim Rowe


Right now, the Navigator GUI is sensitive to IPV6 configuration issues, if a DNS server is not set correctly, Navigator will experience time out issues waiting on the DNS. There are no error messages, just a slow responding interface. Best way to see if that is what is going on run the following command. Go into 'QSH' Enter - /QIBM/ProdData/OS/OSGi/templates/bin/areVerify.sh -network This will run the network verifier for the Application Runtime Expert.
Review the out put, if there is a network configuration concern, it will be signified. How you can contact your network folks to get this corrected.



This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page