Gave that a try.
Listen 10.17.6.33:80
Listen 10.10.1.195:80
Never seems to come fully up. Here's the detail:
- Changed DNS to point mainserver(10.17.6.33) to address of
backupserver(10.10.1.195)
- ping mainserver to verify
Try to go to
http://mainserver/mgr and it never comes up
On backupserver I look at netstat and there's only one listener on port
80.
Connection type . . . . . . : *TCP
Local address . . . . . . . : 10.10.1.195
Local port . . . . . . . . . : 80
Remote address . . . . . . . : *
Remote port . . . . . . . . : *
Display Jobs Using Connection
Current
Name User Number Type User
KRONOS QTMHHTTP 664115 *BCH QTMHHTTP
Normally, when we have an http server running there are multiples of that
job in the qhttpsvr subsystem.
Looking at the above joblog I see:
CALL PGM(QHTTPSVR/QZHBMAIN) PARM('-S' 'KRONOS' '-uiMin' '10' '-uiMax'
'4
'-cEAMap' '*CCSID' '-cAEMap' '*CCSID' '-uiCCSID' '819' '-apache' '-d'
'
ww/kronos' '-f' 'conf/httpd.conf')
HTTP Server waiting for address 10.17.6.33 port 80 to become available.
HTTP Server waiting for address 10.17.6.33 port 80 to become available.
HTTP Server waiting for address 10.17.6.33 port 80 to become available.
HTTP Server waiting for address 10.17.6.33 port 80 to become available.
...
HTTP Server waiting for address 10.17.6.33 port 80 to become available.
HTTP server failed to bind to port 80 .
HTTP Server Instance KRONOS failed.
Job ended abnormally.
Object QUS00000BD in QTEMP type *USRSPC deleted.
Job 664115/QTMHHTTP/KRONOS ended on 10/09/11 at 07:35:44; .087 seconds
used; end code 30 .
So listening on two addresses with the hope of replicating data between
the two doesn't work.
So, leaving replication off, I changed the configuration to only have one
listen line.
On backupserver it listens on
Listen 10.10.1.195:80
On mainserver it listens on
Listen 10.17.6.33:80
I did an
endTCPSVR SERVER(*HTTP) HTTPSVR(KRONOS)
strTCPSVR SERVER(*HTTP) HTTPSVR(KRONOS)
However, when 10.17.6.33 is down, and the dns points mainserver to
10.10.1.195, I cannot connect using
http://mainserver/mgr
This isn't some weird thing where the name in the url (mainserver) has to
match cfgtcp-12, is it? I know of some items that are picky in that way.
Remote Remote Local
Address Port Port Idle Time State
...
* * 80 000:10:49 Listen
...
Connection identification:
Remote host name . . . . . . . . . . . . . . :
Remote internet address . . . . . . . . . . : *
Remote port . . . . . . . . . . . . . . . . : *
Local host name . . . . . . . . . . . . . . . : mainserver.dekko-1
Local internet address . . . . . . . . . . : 10.10.1.195
Local port . . . . . . . . . . . . . . . . : 80
Associated user profile . . . . . . . . . . . : QTMHHTTP
Current
Name User Number Type User
KRONOS QTMHHTTP 664157 *BCH QTMHHTTP
KRONOS QTMHHTTP 664159 *BCH QTMHHTTP
KRONOS QTMHHTTP 664168 *BCH QTMHHTTP
No untoward messages in their joblogs.
Rob Berendt
midrange.com
