|
On 24/05/2006, at 2:16 AM, James H H Lampert wrote:
Moreover, a tied-up server port wouldn't explain why I can't so much as inspect the configuration.
You can't inspect the configuration using WRKHTTPCFG because the *ADMIN server on your release is now using Apache. WRKHTTPCFG works only on the Classic server configuration files. You need to use the *ADMIN web interface (catch-22) or locate the configuration file in the IFS and use DSPF/EDTF (or some PC-based equivalent). On my system that is in:
midrange.com
/QIBM/ProdData/HTTPA/admin/conf/admin-ibm.conf
The -vv option you've previously been told about should have created a
spooled file. What does it say? Check for Apache log files too.
The Apache *ADMIN instance requires Java so make sure that's installed and that both Apache and Java are current on PTFs.
Also make sure TCP is properly configure and that you host and domain names are correct.
SIGKILL is simply the end job signal. Either the Apache server sent itself SIGKILL or someone else did.
Ah, I see later appends from you indicating you've solved the problem. I'm sending this anyway because it explains why WRKHTTPCFG doesn't work.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.
