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