Jim,

The logging job failed issue was NOT QHTT* authority, but my nightly save locking the IFS objects.
Our IFS save window changed (earlier) since we upgraded from P7 to P9, save runs faster.
I had to stop/start all the HTTP instances so the logging jobs would be started, two for each instance.
Stop/start is instantaneous, only a second.
I did adjust the save window, no longer any errors on the logging job.

QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
QTMHHTTP BCI .0 PGM-QZSRLOG SIGW

I'm still looking for the root cause for why the HTTP jobs hung on a stop request.

Paul

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, January 29, 2019 9:15 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] HTTP instance starts/fails following a recycle

Dollars to donuts authority for the QHTT* user profiles is the problem. Not near a system at the moment but those two IBM supplied profile have to read all the config files and it looks like the real error is not having authority to write/change the directory that would contain the logs.

Jim Oberholtzer
Agile Technology Architects



On Jan 29, 2019, at 3:13 PM, Steinmetz, Paul via WEB400 <web400@xxxxxxxxxxxxxxxxxx> wrote:

Jim,

I checked the HTTP logs, nothing there.
These are straight HTTP.
Normally they end in less than 5 seconds, (actually instantly)

This was the first time the recycle was called since we migrated from P7 to P9. (1/27)
Possibly some authority was no restored that caused the end to hang up.
But this job runs a user with super high authority, so would think not an authority issue.

Related but not the cause.
Every night a midnight when the HTTP logging jobs auto recycle, I'm seeing one of these for each HTTP instance.

Message ID . . . . . . : HTP8435
Date sent . . . . . . : 01/28/19 Time sent . . . . . . : 00:00:00

Message . . . . : Logging job for HTTP server BRCWEBLIVE failed.

Cause . . . . . : Logging job for HTTP server BRCWEBLIVE failed. See the
job log for job 001274/QTMHHTTP/BRCWEBLIVE for more information.
Recovery . . . : Correct the problem identified in the job log and try the
request again.

From the logging job joblog.
The logging jobs run under user QTMHHTTP, which has minimal authority.

HTP8424 Diagnostic 10 01/28/19 00:00:00.795704 QZSRAPR QHTTPSVR *STMT QZSRCORE QHTTPSVR *STMT
From module . . . . . . . . : QZSRSNDM
From procedure . . . . . . : sendMessageToJobLog_CCSID
Statement . . . . . . . . . : 27
To module . . . . . . . . . : ZSRVMSG
To procedure . . . . . . . : send_log_open_failure_msg
Statement . . . . . . . . . : 15
Message . . . . : Error occurred opening log file
/www/brcweblive/logs/access_log.Q119012800. No such path or directory.
Cause . . . . . : Log file /www/brcweblive/logs/access_log.Q119012800 could
not be opened by the HTTP server. The directory or a component of path name
/www/brcweblive/logs/access_log.Q119012800 does not exist. This error can
also occur if the server does not have the appropriate object access
permissions to open the file with write access. Recovery . . . : Correct
the log file path name specified in the HTTP server configuration. Check the
object access permissions on the file and all sub directories in the log
file path name. The HTTP server user profile (default is QTMHHTTP) must
have write authority to the file, and must also have *X data authority to
all sub directories in the log file path name. Correct the errors and
restart the HTTP server. Technical description . . . . . . . . : Error
number (errno) 3025 was received on the file open operation. To determine
the meaning of the error number, do one of the following: - Use DSPMSGD
CPExxxx, where xxxx is the error number, to display an error message
containing more information about this error number. - Display one of the
following files that contain descriptions of error numbers: QSYSINC/SYS,
member ERRNO and QCLE/H, member ERRNO.


Paul

-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, January 29, 2019 3:44 PM
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] HTTP instance starts/fails following a recycle

What is in the logs for the HTTP Server? Job logs are rarely any use for a
web site that's cantankerous.

Usually under a directory called logs, next to the directory for the .conf
files.

As to the delay job, That depends on how long it takes to stop the web
jobs. Java?, PHP?, Nodejs?, etc. They all take their own time. Straight
HTTP goes down fast.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Tue, Jan 29, 2019 at 12:08 PM Steinmetz, Paul via WEB400 <
web400@xxxxxxxxxxxxxxxxxx> wrote:

We have an HTTP instance that we auto recycle every Monday morning at 3:30
am.
Monday morning, 1/28, the new job, 006449, ended immediately, with no
joblog.

10 ENDTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE)
20 DLYJOB DLY(60)
30 STRTCPSVR SERVER(*HTTP) HTTPSVR(BRCWEBLIVE)

1) Does the 60 second delay need to be longer?
2) Did the new job end because the old jobs did not finish ending?
3) Any other logs I could look at to troubleshoot this?
4) QTMHHTTP userprofile uses QGPL/QDFTJOBD, which is set to 4 0 *SECLVL
*YES.
So why no joblog?

Job 006314/CPACOPER/BRCWEBLIVE started on 01/28/19 at 03:30:00 in
subsystem B

Job 006449/QTMHHTTP/BRCWEBLIVE started on 01/28/19 at 03:31:01 in
subsystem Q
Job 006449/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .003 seconds
us

Job 001297/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 113.528
seconds
Job 006314/CPACOPER/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .038 seconds
us
Job 001231/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .099 seconds
us
Job 005440/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .024 seconds
us
Job 001940/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .293 seconds
us
Job 001941/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .063 seconds
us
Job 001429/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 84.495
seconds
Job 001428/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 778.694
seconds
Job 001431/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 15.184
seconds
Job 001931/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 1.093
seconds u
Job 001930/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; 3.922
seconds u
Job 001374/QTMHHTTP/BRCWEBLIVE ended on 01/28/19 at 03:31:01; .714 seconds
us

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.