Re: [Vserver] postgres 8.1
On Mon, Oct 09, 2006 at 10:10:38AM -0500, [EMAIL PROTECTED] wrote: > On Mon, 9 Oct 2006 16:01:49 +0200 > Guenther Fuchs <[EMAIL PROTECTED]> wrote: > >Hi there, > > > >on Monday, October 9, 2006 at 3:29:55 PM there was > >posted: > > > >vhn> LOG: could not resolve "localhost": Name or > >service not > >vhn> known > > > >put "localhost 127.0.0.1" (or better: your guest main > >IP) into the > >file /etc/hosts in your guest - this should solve your > >problem. > > > I have adeded "localhost pup.ip.x.x" to /etc/host. it now > resolves localhost but autovacuum still does not start. I > have multiple vserver guest, I have all traffic that is > not explicitedly allowed blocked on the loopback well, hope you allow guest to guest traffic and guest to host traffic (if you want that) as this will happen via the loopback device ... at least guest to the same guest ip should be allowed, otherwise all kind of things will start failing ... > interface. I am using fwbuilder to manage the firewall. I > am not sure which ports to allow for udp socket for stat > collector. I don't know fwbuilder and I do not know stat collector either, but I'm sure google will help you there ... best, Herbert > ___ > Vserver mailing list > Vserver@list.linux-vserver.org > http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] postgres 8.1
On Mon, 09 Oct 2006 10:10:38 -0500 <[EMAIL PROTECTED]> wrote: On Mon, 9 Oct 2006 16:01:49 +0200 Guenther Fuchs <[EMAIL PROTECTED]> wrote: Hi there, on Monday, October 9, 2006 at 3:29:55 PM there was posted: vhn> LOG: could not resolve "localhost": Name or service not vhn> known put "localhost 127.0.0.1" (or better: your guest main IP) into the file /etc/hosts in your guest - this should solve your problem. I have adeded "localhost pup.ip.x.x" to /etc/host. it now resolves localhost but autovacuum still does not start. I have multiple vserver guest, I have all traffic that is not explicitedly allowed blocked on the loopback interface. I am using fwbuilder to manage the firewall. I am not sure which ports to allow for udp socket for stat collector. This is the log now! LOG: could not send test message on socket for statistics collector: Operation not permitted LOG: disabling statistics collector for lack of working socket LOG: database system was shut down at 2006-10-09 10:13:59 CDT LOG: checkpoint record is at 0/10AA648 LOG: redo record is at 0/10AA648; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 66579; next OID: 20444 LOG: next MultiXactId: 1; next MultiXactOffset: 0 WARNING: autovacuum not started because of misconfiguration HINT: Enable options "stats_start_collector" and "stats_row_level". LOG: database system is ready LOG: transaction ID wrap limit is 2147484146, limited by database "postgres" LOG: incomplete startup packet ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] postgres 8.1
On Mon, 9 Oct 2006 16:01:49 +0200 Guenther Fuchs <[EMAIL PROTECTED]> wrote: Hi there, on Monday, October 9, 2006 at 3:29:55 PM there was posted: vhn> LOG: could not resolve "localhost": Name or service not vhn> known put "localhost 127.0.0.1" (or better: your guest main IP) into the file /etc/hosts in your guest - this should solve your problem. I have adeded "localhost pup.ip.x.x" to /etc/host. it now resolves localhost but autovacuum still does not start. I have multiple vserver guest, I have all traffic that is not explicitedly allowed blocked on the loopback interface. I am using fwbuilder to manage the firewall. I am not sure which ports to allow for udp socket for stat collector. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] postgres 8.1
Hi there, on Monday, October 9, 2006 at 3:29:55 PM there was posted: vhn> LOG: could not resolve "localhost": Name or service not vhn> known put "localhost 127.0.0.1" (or better: your guest main IP) into the file /etc/hosts in your guest - this should solve your problem. -- regards 'n greez, Guenther Fuchs (aka "muh" and "powerfox") ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
