Hi At.Mitani,
No debug message found in any log files.
Now i extract the tar file for 1.7rc4, how can i apply the patch ?
Regards,
Mike Ho
Cityline
Tel : 31036823
----- Original Message -----
From: "mike" <mike.ho@xxxxxxxxxxxxxxx>
To: <pgcluster-general@xxxxxxxxxxxxx>
Sent: Saturday, March 03, 2007 9:32 AM
Subject: Re: [Pgcluster-general] Problem in Pgcluster
> Hi At.Mitani,
>
> Where can i view the debug message?
>
> Now i set Use_Replication_Log to 'No'
>
>
> Mike
>
>
> ----- Original Message -----
> From: <a.mitani@xxxxxxxxxxxxxx>
> To: <pgcluster-general@xxxxxxxxxxxxx>
> Sent: Friday, March 02, 2007 8:24 PM
> Subject: Re: [Pgcluster-general] Problem in Pgcluster
>
>
> > Hi Mike,
> >
> > One more, please set "no" to "<Use_Replication_Log>" in your
> > pgreplicate.conf.
> >
> > And please show us your debug message of pglb and pgreplication as well,
> > if you can.
> >
> > Regards,
> > ---------------------
> > At.Mitani
> >
> >
> > > Thank for your reply. Both server can listen to all to all ip in
> > > pg_hba.conf
> > > (All trust)
> > >
> > > listen_addresses = '*' in postgres config. file.
> > >
> > > Mike
> > >
> > > ----- Original Message -----
> > > From: <a.mitani@xxxxxxxxxxxxxx>
> > > To: <pgcluster-general@xxxxxxxxxxxxx>
> > > Sent: Friday, March 02, 2007 7:18 PM
> > > Subject: Re: [Pgcluster-general] Problem in Pgcluster
> > >
> > >
> > >> Hi,
> > >>
> > >> At first, please discribe one data on one line in all configuration
> > >> files.
> > >> Next, please check "listen_addresses" in "postgresql.conf" and
> > >> "pg_hba.conf" on each Cluster DB.
> > >>
> > >> Regards,
> > >> ----------------
> > >> At.Mitani
> > >>
> > >>
> > >> > Dear all, I'm trying to use pgcluster 1.7.0-rc4 (with postgresql
> > > 8.2.3)My
> > >> > setup: - two postgresql servers, 128.128.3.1 and .2
> > >> > Load balancer an replication ride on 128.128.3.1 serverThe
> > >> > pgreplicate.conf file looks like this:
> > >> >
> > >> > ## pgreplicate.conf begin
> > >> > <Cluster_Server_Info> <Host_Name> 128.128.3.2 </Host_Name>
> > > <Port>
> > >> > 5432 </Port> <Recovery_Port> 7001
> > >> > </Recovery_Port></Cluster_Server_Info><Cluster_Server_Info>
> > > <Host_Name>
> > >> > 128.128.3.1 </Host_Name> <Port> 5432
> > >> </Port>
> > >> > <Recovery_Port> 7001
> > >> > </Recovery_Port></Cluster_Server_Info><LoadBalance_Server_Info>
> > >> > <Host_Name> 128.128.3.1 </Host_Name> <Recovery_Port>
> > > 6001
> > >> > </Recovery_Port></LoadBalance_Server_Info><Host_Name>
> > >> > 128.128.3.1 </Host_Name><Replication_Port> 8001
> > >> > </Replication_Port><Recovery_Port> 8101
> > >> > </Recovery_Port><RLOG_Port> 8301
> > >> > </RLOG_Port><Response_Mode> normal
> > >> > </Response_Mode><Use_Replication_Log> yes
> > >> > </Use_Replication_Log><Replication_Timeout> 1min
> > >> > </Replication_Timeout><LifeCheck_Timeout> 3s
> > >> > </LifeCheck_Timeout><LifeCheck_Interval> 15s
> > >> > </LifeCheck_Interval>
> > >> > ## === pgreplicate.conf end
> > >> > The cluster.conf file for the two servers is identical:
> > >> > ## === cluster.conf file
> > >> > <Replicate_Server_Info>
> > >> > <Host_Name> 128.128.3.1 </Host_Name>
> > >> > <Port> 8001 </Port>
> > >> > <Recovery_Port> 8101 </Recovery_Port>
> > >> > </Replicate_Server_Info>
> > >> > <Host_Name> 128.128.3.1 </Host_Name>
> > >> > <Recovery_Port> 7001 </Recovery_Port>
> > >> > <Rsync_Path> /usr/bin/rsync </Rsync_Path>
> > >> > <Rsync_Option> ssh -1 </Rsync_Option>
> > >> > <Rsync_Compress> yes </Rsync_Compress>
> > >> > <Pg_Dump_Path> /usr/local/pgsql/bin/pg_dump
> > >> > </Pg_Dump_Path>
> > >> > <When_Stand_Alone> read_only </When_Stand_Alone>
> > >> > <Replication_Timeout> 1min </Replication_Timeout>
> > >> > <LifeCheck_Timeout> 3s </LifeCheck_Timeout>
> > >> > <LifeCheck_Interval> 11s </LifeCheck_Interval>
> > >> >
> > >> > ## === end of cluster.conf file
> > >> >
> > >> > And load balancer config:
> > >> > <Cluster_Server_Info>
> > >> > <Host_Name> 128.128.3.1 </Host_Name>
> > >> > <Port> 5432 </Port>
> > >> > <Max_Connect> 32 </Max_Connect>
> > >> > </Cluster_Server_Info>
> > >> > <Cluster_Server_Info>
> > >> > <Host_Name> 128.128.3.2 </Host_Name>
> > >> > <Port> 5432 </Port>
> > >> > <Max_Connect> 32 </Max_Connect>
> > >> > </Cluster_Server_Info>
> > >> >
> > >> > <Host_Name> 128.128.3.1 </Host_Name>
> > >> > <Backend_Socket_Dir> /tmp </Backend_Socket_Dir>
> > >> > <Receive_Port> 5431 </Receive_Port>
> > >> > <Recovery_Port> 6001 </Recovery_Port>
> > >> > <Max_Cluster_Num> 128 </Max_Cluster_Num>
> > >> > <Use_Connection_Pooling> no </Use_Connection_Pooling>
> > >> > <LifeCheck_Timeout> 3s
> > >> > </LifeCheck_Timeout>
> > >> > <LifeCheck_Interval> 15s
</LifeCheck_Interval>
> > >> >
> > >> >
> > >> > Load balanacer list 5431 port and sync. the structure and data to
> > >> > 128.128.3.1 & .2 database
> > >> >
> > >> > I want to test on the situation when 1 of cluster server down.
> > >> > However, after i shutdown postgres in 3.1 server, the whole
postgres
> > >> was
> > >> > unable to access
> > >> > with error 'Sorry, backend connection is full'
> > >> >
> > >> > Alternatively, if i shutdown postgres in 3.2, load balancer can
still
> > >> > listen the request and propagate result to database in 3.1
> > >> > server; But when the 3.2 postgres resume, the latest change cannot
be
> > >> > replicated to 3.2 database.
> > >> >
> > >> > Any clue?
> > >> >
> > >> > Mike
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > _______________________________________________
> > >> > Pgcluster-general mailing list
> > >> > Pgcluster-general@xxxxxxxxxxxxx
> > >> > http://pgfoundry.org/mailman/listinfo/pgcluster-general
> > >> >
> > >>
> > >> _______________________________________________
> > >> Pgcluster-general mailing list
> > >> Pgcluster-general@xxxxxxxxxxxxx
> > >> http://pgfoundry.org/mailman/listinfo/pgcluster-general
> > >>
> > >
> > >
> > > _______________________________________________
> > > Pgcluster-general mailing list
> > > Pgcluster-general@xxxxxxxxxxxxx
> > > http://pgfoundry.org/mailman/listinfo/pgcluster-general
> > >
> >
> > _______________________________________________
> > Pgcluster-general mailing list
> > Pgcluster-general@xxxxxxxxxxxxx
> > http://pgfoundry.org/mailman/listinfo/pgcluster-general
> >
>
|
