MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

Re: *ADMIN instance of HTTP server failing on startup



fixed

Jack:

Looking at the logs for yesterday I see the following entries in the
error_log.Q114032300 file:

[Sun Mar 23 00:03:35 2014] [error] QZISI No WAS Instance to start
[Sun Mar 23 00:03:35 2014] [notice] ZSRV_MSG0385: Apache/2.2.11 (i5) with
large file support configured -- resuming normal operations.
[Sun Mar 23 00:03:38 2014] [error] ZSRV_MSG0252: SSL initialization
operation failed, return code error = 107.
[Sun Mar 23 00:04:43 2014] [notice] QZISI termination processing
[Sun Mar 23 00:04:43 2014] [notice] QZISI is_server_term SKIPPED 2
[Sun Mar 23 00:04:43 2014] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.
[Sun Mar 23 14:43:22 2014] [error] QZISI No WAS Instance to start
[Sun Mar 23 14:43:22 2014] [notice] ZSRV_MSG0385: Apache/2.2.11 (i5)
configured -- resuming normal operations.
[Sun Mar 23 14:43:25 2014] [error] ZSRV_MSG0252: SSL initialization
operation failed, return code error = 107.
[Sun Mar 23 14:44:32 2014] [notice] QZISI termination processing
[Sun Mar 23 14:44:32 2014] [notice] QZISI is_server_term SKIPPED 2
[Sun Mar 23 14:44:32 2014] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.
[Sun Mar 23 16:24:24 2014] [error] QZISI No WAS Instance to start
[Sun Mar 23 16:24:24 2014] [notice] ZSRV_MSG0385: Apache/2.2.11 (i5) with
large file support configured -- resuming normal operations.
[Sun Mar 23 16:24:27 2014] [error] ZSRV_MSG0252: SSL initialization
operation failed, return code error = 107.
[Sun Mar 23 16:25:32 2014] [notice] QZISI termination processing
[Sun Mar 23 16:25:32 2014] [notice] QZISI is_server_term SKIPPED 2
[Sun Mar 23 16:25:32 2014] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.
[Sun Mar 23 16:50:03 2014] [error] QZISI No WAS Instance to start
[Sun Mar 23 16:50:03 2014] [notice] ZSRV_MSG0385: Apache/2.2.11 (i5) with
large file support configured -- resuming normal operations.
[Sun Mar 23 16:50:05 2014] [error] ZSRV_MSG0252: SSL initialization
operation failed, return code error = 107.
[Sun Mar 23 16:51:11 2014] [notice] QZISI termination processing
[Sun Mar 23 16:51:11 2014] [notice] QZISI is_server_term SKIPPED 2
[Sun Mar 23 16:51:11 2014] [notice] ZSRV_MSG0387: SIGTERM received.
Shutting down.

Nothing that tells me what I didn't already know.

Jim


On Mon, Mar 24, 2014 at 10:35 AM, Jack Kingsley <iseriesflorida@xxxxxxxxx>wrote:

Take a look in this directory.

/qibm/UserData/HTTPA/admin/logs/




On Mon, Mar 24, 2014 at 12:31 PM, Jim Essinger <dilbernator@xxxxxxxxx
wrote:

Greetings!

I am working with IBM service on an issue that we have not been able to
resolve, so I thought I would put his out on the Midrange and WEB lists
to
see if anyone has had this issue and found a fix for it, or can give me
some guidance.

Hardware - 720 (E4C) partitioned 3 ways.
IBM i5/OS V7.1 with Technology Refresh 7 and the latest PTFs (as of
Sunday,
March 23rd).

For the last month we have not been able to start the *ADMIN instance of
the HTTP server. When the command to start is used, the instance starts
several jobs in the QHTTPSVR subsystem. Several of these jobs take LOTS
of
CPU time, borrowing from other partitions on the same 720 (E4C) box.

I receive an email from a job monitoring for instance failures almost
immediately. The monitor is looking for messges HTP8080, HTP8081, and
HTP8082 to show up in the QSYSOPR message queue.

Then all but two of the started jobs ABEND with no joblog. The two left
running are ADMIN1 and ADMIN4.

I applied the latest PTFs, and that did not fix anything.

Yesterday I deleted licensed program 5770DG1, did an IPL, reinstalled
5770DG1, applied the latest PTF group (#26) for SF99368:IBM HTTP SERVER
FOR
I, then IPLed again.

Still have the same issue. I have looked for logs, and not found any
with
useful debug information. JOBLOG are not being created, or have less
than
useful information.

Anyone seen this or have some suggestions on where to go from here?

We need to use the Digital Certificate Manager to update some
certificates
that are expiring fairly soon. We are able to update HTTP configuration
files for our existing web sites directly, but without the DCM we are not
able to export information to get a certificate updated.

I am open to any and all suggestions and/or questions.

Blessings!

Jim Essinger
Western Power Sports
Boise, ID
--
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.


--
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.







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

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact