pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLondiste won't start with dual IP addresses
6+ messages / 2 participants
[nested] [flat]
* Londiste won't start with dual IP addresses
@ 2011-08-18 23:44 Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
0 siblings, 1 reply; 6+ messages in thread
From: Craig James @ 2011-08-18 23:44 UTC (permalink / raw)
To: pgsql-admin
We had to temporarily assign two IP addresses to our servers. After doing so and rebooting, Londiste will start, but it just sits there doing nothing. The logfile has zero bytes, and it doesn't seem to connect to either the master or the slave database.
We reconfigured Postgres to listen on both addresses, but the /etc/hosts tables still point to the original addresses (that is, the second IP address shouldn't matter). But I can connect to Postgres on either IP address on all servers.
All other Postgres applications work. I can use psql, and our Perl DBI and PHP applications all work with no problems.
When I invoke "londiste.py --verbose ...", the log file says:
2011-08018 16:35:47,250 22074 DEBUG Attaching
And that's all. Nothing more ever happens.
Help? Thanks!
Craig
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Londiste won't start with dual IP addresses
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
@ 2011-08-19 08:40 ` Marko Kreen <markokr@gmail.com>
2011-08-19 16:17 ` Re: Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 17:55 ` Re: Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
0 siblings, 2 replies; 6+ messages in thread
From: Marko Kreen @ 2011-08-19 08:40 UTC (permalink / raw)
To: Craig James <craig_james@emolecules.com>; +Cc: pgsql-admin
On Fri, Aug 19, 2011 at 2:44 AM, Craig James <craig_james@emolecules.com> wrote:
> We had to temporarily assign two IP addresses to our servers. After doing
> so and rebooting, Londiste will start, but it just sits there doing nothing.
> The logfile has zero bytes, and it doesn't seem to connect to either the
> master or the slave database.
>
> We reconfigured Postgres to listen on both addresses, but the /etc/hosts
> tables still point to the original addresses (that is, the second IP address
> shouldn't matter). But I can connect to Postgres on either IP address on
> all servers.
>
> All other Postgres applications work. I can use psql, and our Perl DBI and
> PHP applications all work with no problems.
>
> When I invoke "londiste.py --verbose ...", the log file says:
>
> 2011-08018 16:35:47,250 22074 DEBUG Attaching
>
> And that's all. Nothing more ever happens.
>
> Help? Thanks!
Does the exact connect string you use in londiste config work
with psql? Like so:
$ psql -d 'connstr'
--
marko
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Londiste won't start with dual IP addresses
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
@ 2011-08-19 16:17 ` Craig James <craig_james@emolecules.com>
2011-08-19 17:53 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
1 sibling, 1 reply; 6+ messages in thread
From: Craig James @ 2011-08-19 16:17 UTC (permalink / raw)
To: Marko Kreen <markokr@gmail.com>; +Cc: pgsql-admin
On 8/19/11 1:40 AM, Marko Kreen wrote:
> On Fri, Aug 19, 2011 at 2:44 AM, Craig James<craig_james@emolecules.com> wrote:
>> We had to temporarily assign two IP addresses to our servers. After doing
>> so and rebooting, Londiste will start, but it just sits there doing nothing.
>> The logfile has zero bytes, and it doesn't seem to connect to either the
>> master or the slave database.
>>
>> We reconfigured Postgres to listen on both addresses, but the /etc/hosts
>> tables still point to the original addresses (that is, the second IP address
>> shouldn't matter). But I can connect to Postgres on either IP address on
>> all servers.
>>
>> All other Postgres applications work. I can use psql, and our Perl DBI and
>> PHP applications all work with no problems.
>>
>> When I invoke "londiste.py --verbose ...", the log file says:
>>
>> 2011-08018 16:35:47,250 22074 DEBUG Attaching
>>
>> And that's all. Nothing more ever happens.
>>
>> Help? Thanks!
> Does the exact connect string you use in londiste config work
> with psql? Like so:
>
> $ psql -d 'connstr'
Yes.
psql -d 'dbname=archive host=iridium user=postgres'
connects with no problem.
Thanks,
Craig
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Londiste won't start with dual IP addresses
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
2011-08-19 16:17 ` Re: Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
@ 2011-08-19 17:53 ` Marko Kreen <markokr@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Marko Kreen @ 2011-08-19 17:53 UTC (permalink / raw)
To: Craig James <craig_james@emolecules.com>; +Cc: pgsql-admin
On Fri, Aug 19, 2011 at 7:17 PM, Craig James <craig_james@emolecules.com> wrote:
> On 8/19/11 1:40 AM, Marko Kreen wrote:
>> On Fri, Aug 19, 2011 at 2:44 AM, Craig James<craig_james@emolecules.com>
>> wrote:
>>>
>>> We had to temporarily assign two IP addresses to our servers. After
>>> doing
>>> so and rebooting, Londiste will start, but it just sits there doing
>>> nothing.
>>> The logfile has zero bytes, and it doesn't seem to connect to either the
>>> master or the slave database.
>>>
>>> We reconfigured Postgres to listen on both addresses, but the /etc/hosts
>>> tables still point to the original addresses (that is, the second IP
>>> address
>>> shouldn't matter). But I can connect to Postgres on either IP address on
>>> all servers.
>>>
>>> All other Postgres applications work. I can use psql, and our Perl DBI
>>> and
>>> PHP applications all work with no problems.
>>>
>>> When I invoke "londiste.py --verbose ...", the log file says:
>>>
>>> 2011-08018 16:35:47,250 22074 DEBUG Attaching
>>>
>>> And that's all. Nothing more ever happens.
>>>
>>> Help? Thanks!
>>
>> Does the exact connect string you use in londiste config work
>> with psql? Like so:
>>
>> $ psql -d 'connstr'
>
> Yes.
>
> psql -d 'dbname=archive host=iridium user=postgres'
>
> connects with no problem.
Hm. Londiste does not do anything fancy with connections.
Perhaps you have some other problem.
Does 'londiste conf.ini provider tables' work?
Does 'londiste conf.ini subscriber tables' work?
Do you have pgqadm running on provider db?
--
marko
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Londiste won't start with dual IP addresses
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
@ 2011-08-19 17:55 ` Craig James <craig_james@emolecules.com>
2011-08-19 18:00 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
1 sibling, 1 reply; 6+ messages in thread
From: Craig James @ 2011-08-19 17:55 UTC (permalink / raw)
To: Marko Kreen <markokr@gmail.com>; +Cc: pgsql-admin
On 8/19/11 1:40 AM, Marko Kreen wrote:
> On Fri, Aug 19, 2011 at 2:44 AM, Craig James<craig_james@emolecules.com> wrote:
>> We had to temporarily assign two IP addresses to our servers. After doing
>> so and rebooting, Londiste will start, but it just sits there doing nothing.
>> The logfile has zero bytes, and it doesn't seem to connect to either the
>> master or the slave database.
>>
>> We reconfigured Postgres to listen on both addresses, but the /etc/hosts
>> tables still point to the original addresses (that is, the second IP address
>> shouldn't matter). But I can connect to Postgres on either IP address on
>> all servers.
>>
>> All other Postgres applications work. I can use psql, and our Perl DBI and
>> PHP applications all work with no problems.
>>
>> When I invoke "londiste.py --verbose ...", the log file says:
>>
>> 2011-08018 16:35:47,250 22074 DEBUG Attaching
>>
>> And that's all. Nothing more ever happens.
>>
>> Help? Thanks!
> Does the exact connect string you use in londiste config work
> with psql? Like so:
>
> $ psql -d 'connstr'
As I mentioned earlier, yes it does work.
I also discovered by looking at all the postgres processes that it's making the first connection (to the master), but it doesn't seem to even try to make the second connection.
Could there be something else it's waiting for? The dual-network issue may be completely irrelevant. I know that while the IT guy was reconfiguring the network, he had to do a forced-reboot at least once without shutting down Postgres. Is it possible that the Londiste tables are in some invalid state, and the daemon is waiting for something that's never going to happen?
Thanks,
Craig
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Londiste won't start with dual IP addresses
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Re: Londiste won't start with dual IP addresses Marko Kreen <markokr@gmail.com>
2011-08-19 17:55 ` Re: Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
@ 2011-08-19 18:00 ` Marko Kreen <markokr@gmail.com>
0 siblings, 0 replies; 6+ messages in thread
From: Marko Kreen @ 2011-08-19 18:00 UTC (permalink / raw)
To: Craig James <craig_james@emolecules.com>; +Cc: pgsql-admin
On Fri, Aug 19, 2011 at 8:55 PM, Craig James <craig_james@emolecules.com> wrote:
> On 8/19/11 1:40 AM, Marko Kreen wrote:
>>
>> On Fri, Aug 19, 2011 at 2:44 AM, Craig James<craig_james@emolecules.com>
>> wrote:
>>>
>>> We had to temporarily assign two IP addresses to our servers. After
>>> doing
>>> so and rebooting, Londiste will start, but it just sits there doing
>>> nothing.
>>> The logfile has zero bytes, and it doesn't seem to connect to either the
>>> master or the slave database.
>>>
>>> We reconfigured Postgres to listen on both addresses, but the /etc/hosts
>>> tables still point to the original addresses (that is, the second IP
>>> address
>>> shouldn't matter). But I can connect to Postgres on either IP address on
>>> all servers.
>>>
>>> All other Postgres applications work. I can use psql, and our Perl DBI
>>> and
>>> PHP applications all work with no problems.
>>>
>>> When I invoke "londiste.py --verbose ...", the log file says:
>>>
>>> 2011-08018 16:35:47,250 22074 DEBUG Attaching
>>>
>>> And that's all. Nothing more ever happens.
>>>
>>> Help? Thanks!
>>
>> Does the exact connect string you use in londiste config work
>> with psql? Like so:
>>
>> $ psql -d 'connstr'
>
> As I mentioned earlier, yes it does work.
>
> I also discovered by looking at all the postgres processes that it's making
> the first connection (to the master), but it doesn't seem to even try to
> make the second connection.
>
> Could there be something else it's waiting for? The dual-network issue may
> be completely irrelevant. I know that while the IT guy was reconfiguring
> the network, he had to do a forced-reboot at least once without shutting
> down Postgres. Is it possible that the Londiste tables are in some invalid
> state, and the daemon is waiting for something that's never going to happen?
Look at the logs, what queries does it do?
--
marko
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2011-08-19 18:00 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-08-18 23:44 Londiste won't start with dual IP addresses Craig James <craig_james@emolecules.com>
2011-08-19 08:40 ` Marko Kreen <markokr@gmail.com>
2011-08-19 16:17 ` Craig James <craig_james@emolecules.com>
2011-08-19 17:53 ` Marko Kreen <markokr@gmail.com>
2011-08-19 17:55 ` Craig James <craig_james@emolecules.com>
2011-08-19 18:00 ` Marko Kreen <markokr@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox