|
Peter, I ran into some similar problems trying to convert a Classic server to pbA. I eventually gave up trying to get the covnersion to work and created the new config by hand. You can use the converted statements as a guide though until you are comfortable with pbA. I think the real problem here is that you are trying to use a DB2 type file for logging purposes... /QSYS.LIB/QUSRSYS.LIB/LPHERRLOG.FILE/HTTPDLOG.MBR Instead, try something like this... ErrorLog logs/basic_error_log Now your errors will be logged in your web server's xxx/logs directory in a file called basic_error_log. The next upgrade for pbA is supposed to include the ability to log by date but for now you will have to deal with one big file. HTH, Joel R. Cochran Director of Internet Services VamaNet.com (800)480-8810 mailto:webmaster@vamanet.com > -----Original Message----- > From: Peter Dow [mailto:maillist@dowsoftware.com] > Sent: Friday, August 23, 2002 1:47 PM > To: WEB400@midrange.com > Subject: [WEB400] HTTP Server pba HTP8420 error when starting > > > I just installed V5R1 with the latest CUM, converted an > original server > instance to an Apache instance, and tried to start it. > > On the 1st attempt it gets msgid HTP8420 with errno 3406, > which is CPE3406, > which says > > Message . . . . : Operation would have caused the process > to be suspended. > Recovery . . . : A resource is temporarily unavailable. > Try the operation > again later. > > At this point, the log file was created, and the member > added, so I tried > again. > > > On the 2nd attempt, it also gets msgid HTP8420 but this time > with errno 0: > > HTP8420 Diagnostic 10 08/23/02 10:35:18 QZSRAPR > QHTTPSVR *STMT QZSRCORE QHTTPSVR *STMT > From module . . . . . . . . : QZSRSNDM > From procedure . . . . . . : sendMessageToJobLog > Statement . . . . . . . . . : 11 > To module . . . . . . . . . : ZSRVMSG > To procedure . . . . . . . : send_log_open_failure_msg > Statement . . . . . . . . . : 18 > Message . . . . : Error occurred opening log file > /QSYS.LIB/QUSRSYS.LIB/LPHERRLOG.FILE/HTTPDLOG.MBR. > Cause . . . . . : The log file could not be opened > during HTTP server > start > up. As a result, the HTTP server did not start. The log > file name was > specified on the ErrorLog directive in the HTTP > Configuration file. The > error number received was: 0. Recovery . . . : If the > error number is > a > value other than 0, determine the meaning of error number > and perform > the > appropriate recovery for that error. If the log file name > is in error, > correct the name specified on the ErrorLog directive in > the HTTP server > configuration. Correct the errors and restart the HTTP > server. Technical > description . . . . . . . . : Error number (errno) 0 > was received when > trying to open the file. 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. > > What's going on here? Am I missing a PTF? > > tia, > Peter Dow > Dow Software Services, Inc. > 909 793-9050 voice > 909 522-3214 cellular > 909 793-4480 fax > > > > _______________________________________________ > This is the Web Enabling the AS400 / iSeries (WEB400) mailing list > To post a message email: WEB400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/web400 > or email: WEB400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/web400. >
As an Amazon Associate we earn from qualifying purchases.
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.