Re: Can't get http server started after 7.2 upgrade

These are for V7R3 and you probably already have been through them, just
just in case:
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_
73/rzaie/rzaietroublewebadmin.htm#rzaietroublewebadmin__admin



On Sun, Apr 1, 2018 at 1:53 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

There is for any Zend PHP instances though it's not Zend specifically the
issue is an Apache change (includoptional vs include.) IBM however makes
any needed changes in the *ADMIN server.

I have done a number of i 7.2 upgrades recently without issue so there's
likely something that hiccuped or potentially a custom config option

that's

now in error.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/1/2018 2:12 PM, Jon Paris wrote:

Wasn't there some small config change needed for 7.2 Larry? I seem to
recall something had to be changed and until we did we had a similar
problem. Have search my email but can't find anything.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Apr 1, 2018, at 1:54 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

But *ADMIN provides Navigator for i and DCM among other things! You
really do want this to run.

Logical next step is to open a PMR with IBM and then send in the admin
data collector using QMGTOOLs. Generally IBM can resolve straightaway

from

that.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 4/1/2018 12:52 PM, David Gibbs wrote:

On 4/1/18 7:34 AM, Bradley Stone wrote:

I also assume this is a normal HTTP server, not *ADMIN, right?

It won't start *ALL and it won't start *ADMIN. Same error both time.
I could easily disable, or remove, the non *ADMIN config's as we don't
use them except for testing.
david

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--

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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD