Re: HA replication of /www directory -- MIDRANGE-L

Only do that if there are no other ip's you would rather not have the
www exposed to...

Best regards,

On Sun, Oct 9, 2011 at 11:46 AM, John Jones <chianime@xxxxxxxxx> wrote:

Listen, according to the docs, defaults to port 80 and all TCP addresses.

With that in mind, maybe you can try just
Listen 80
or omit the Listen lines all together.

On Sun, Oct 9, 2011 at 7:04 AM, <rob@xxxxxxxxx> wrote:

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
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John Jones <chianime@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/07/2011 04:25 PM
Subject: Re: HA replication of /www directory
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Use multiple Listen directives:
http://httpd.apache.org/docs/2.2/mod/mpm_common.html#listen

On Fri, Oct 7, 2011 at 2:00 PM, <rob@xxxxxxxxx> wrote:

How do you tell it both addresses?

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From: John Jones <chianime@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/07/2011 02:58 PM
Subject: Re: HA replication of /www directory
Sent by: midrange-l-bounces@xxxxxxxxxxxx

Why not just listen on both IP addresses on both systems? It shouldn't
matter since only one or the other interface would be up the machine.

I would think you'd want the replication in case any changes are made to
the
web site. Here, we dynamically add & remove objects all the time (we
serve
reports via web interface) but due to locking issues we can't leave the
MIMIX data group active. So we just turn the data group on at night &

let

it catch up when few or no users are online.

On Fri, Oct 7, 2011 at 1:15 PM, <rob@xxxxxxxxx> wrote:

Currently I noticed that we are replicating our /www and all
subdirectories except the log directories. I am guessing we excluded

the

log directories quite some time ago due to locks. The problem is that

the

/WWW/servername/conf/httpd.conf directory may have a line like
listen xxx.xxx.xxx.xxx:80
on one system and
listen yyy.yyy.yyy.yyy:80
on the backup system and replicating it clobbers the change.

Can y'all see any reason to replicate the /www directory? I thought

of

backup reasons as we only back up from the backup machine (other than

the

once every other month save of the primary). I guess if backups are

that

critical we can set up our HA software to replicate to another

directory

like /backup/www.

Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
John Jones, CISSP
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
John Jones, CISSP
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
John Jones, CISSP
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.