Обсуждение: Slony RPM issue
Hi Devrim, I ran into another RPM issue, this time with Slony. I grabbed the RPM from http://developer.postgresql.org/~devrim/slony/1.1.0/rpms/PG8.0.3/ Trying to run slon_start, I got errors such as: $ slon_start --config /etc/slon_tools.conf 2 Invoke slon for node 2 - @@@/slon -s 1000 -d2 -g 80 replication 'host=dev2 dbname=booktown user=postgres port=5432' 2>&1 > /var/log/slony/slony1/node2/booktown-2005-10-05_16:23:53.log & sh: line 1: @@@/slon: No such file or directory Slon failed to start for cluster replication, node node2 This turned out to be because /usr/lib/pgsql/slon-tools.pm contained several un-expanded @@PGBINDIR@@ prefixes - once I replaced them with /usr/bin it all ran just fine. Please let me know if I can assist in fixing these issues. Also, thanks to David and Gavin for their help on IRC - it made a big difference to my day! Regards, Philip. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan ----------------- Utiba Pty Ltd This message has been scanned for viruses and dangerous content by Utiba mail server and is believed to be clean.
Hi, On Wed, 5 Oct 2005, Philip Yarra wrote: > Hi Devrim, I ran into another RPM issue, this time with Slony. :-) > I grabbed the RPM from > http://developer.postgresql.org/~devrim/slony/1.1.0/rpms/PG8.0.3/ > > Trying to run slon_start, I got errors such as: > $ slon_start --config /etc/slon_tools.conf 2 > Invoke slon for node 2 - @@@/slon -s 1000 -d2 -g 80 replication 'host=dev2 > dbname=booktown user=postgres port=5432' 2>&1 >> /var/log/slony/slony1/node2/booktown-2005-10-05_16:23:53.log & > sh: line 1: @@@/slon: No such file or directory > Slon failed to start for cluster replication, node node2 > > This turned out to be because /usr/lib/pgsql/slon-tools.pm contained several > un-expanded @@PGBINDIR@@ prefixes - once I replaced them with /usr/bin it all > ran just fine. Hrrm. It seems that I've installed wrong file in the spec :( However slon-tools file is not updated by the Makefile, so I'll try to fix that, too. Thanks for the report. It will fixed in CVS and all the RPM sets later today. Always feel free to send me a patch if you want, I can apply your patch, too. BTW, could you please report the possible Slony problems to slony1-general@gborg.postgresql.org later? Regards, -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org
On Wed, Oct 05, 2005 at 05:32:40PM +0300, Devrim GUNDUZ wrote: > > Hi, > > On Wed, 5 Oct 2005, Philip Yarra wrote: > > >Hi Devrim, I ran into another RPM issue, this time with Slony. > > :-) > > >I grabbed the RPM from > >http://developer.postgresql.org/~devrim/slony/1.1.0/rpms/PG8.0.3/ > > > >Trying to run slon_start, I got errors such as: > >$ slon_start --config /etc/slon_tools.conf 2 > >Invoke slon for node 2 - @@@/slon -s 1000 -d2 -g 80 replication 'host=dev2 > >dbname=booktown user=postgres port=5432' 2>&1 > >>/var/log/slony/slony1/node2/booktown-2005-10-05_16:23:53.log & > >sh: line 1: @@@/slon: No such file or directory > >Slon failed to start for cluster replication, node node2 > > > >This turned out to be because /usr/lib/pgsql/slon-tools.pm contained > >several > >un-expanded @@PGBINDIR@@ prefixes - once I replaced them with /usr/bin it > >all > >ran just fine. This is also a problem for 64bit machines which like to install things in lib64. The @@PGBINDIR@@ is also unset in these cases. Generally a short sed (or perl if you like) script will fix these up. But it is really pretty obscure trail for people to find the exact problem. --elein > > Hrrm. > > It seems that I've installed wrong file in the spec :( However slon-tools > file is not updated by the Makefile, so I'll try to fix that, too. > > Thanks for the report. It will fixed in CVS and all the RPM sets later > today. Always feel free to send me a patch if you want, I can apply your > patch, too. > > BTW, could you please report the possible Slony problems to > slony1-general@gborg.postgresql.org later? > > Regards, > -- > Devrim GUNDUZ > Kivi Bili?im Teknolojileri - http://www.kivi.com.tr > devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr > > http://www.gunduz.org > _______________________________________________ > Slony1-general mailing list > Slony1-general@gborg.postgresql.org > http://gborg.postgresql.org/mailman/listinfo/slony1-general
Hi Devrim, On Thu, 6 Oct 2005 12:32 am, Devrim GUNDUZ wrote: > Thanks for the report. It will fixed in CVS and all the RPM sets later > today. Always feel free to send me a patch if you want, I can apply your > patch, too. OK, you got my previous email about why pgsql-libs was dependent on compat-libs RPM? I don't even know where to start with fixing RPM issues, but I guess I can learn if you would like help? > BTW, could you please report the possible Slony problems to > slony1-general@gborg.postgresql.org later? Sure will. Ermmm, there isn't something you want to tell me is there? :-) I'd rather hear about gotchas now rather than finding them myself at the eleventh hour. Regards, Philip. -- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan ----------------- Utiba Pty Ltd This message has been scanned for viruses and dangerous content by Utiba mail server and is believed to be clean.
Hi, On Thu, 6 Oct 2005, Philip Yarra wrote: > On Thu, 6 Oct 2005 12:32 am, Devrim GUNDUZ wrote: >> Thanks for the report. It will fixed in CVS and all the RPM sets later >> today. Always feel free to send me a patch if you want, I can apply your >> patch, too. > > OK, you got my previous email about why pgsql-libs was dependent on > compat-libs RPM? See: http://people.planetpostgresql.org/devrim/index.php?/archives/15-New-PostgreSQL-point-releases.html "New" 8.0.4 RPMs will solve that problem. Cheers, -- Devrim GUNDUZ Kivi Bilişim Teknolojileri - http://www.kivi.com.tr devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org
Hello all, I want to set a system level flag for my own purposes. What changes in initdb.c or any other files are expected. And When I will run my postgresql , how I get that system level flag. On Thu, 6 Oct 2005, Devrim GUNDUZ wrote: > > Hi, > > On Thu, 6 Oct 2005, Philip Yarra wrote: > >> On Thu, 6 Oct 2005 12:32 am, Devrim GUNDUZ wrote: >>> Thanks for the report. It will fixed in CVS and all the RPM sets later >>> today. Always feel free to send me a patch if you want, I can apply your >>> patch, too. >> >> OK, you got my previous email about why pgsql-libs was dependent on >> compat-libs RPM? > > See: > http://people.planetpostgresql.org/devrim/index.php?/archives/15-New-PostgreSQL-point-releases.html > > "New" 8.0.4 RPMs will solve that problem. > > Cheers, > -- > Devrim GUNDUZ > Kivi Bili?im Teknolojileri - http://www.kivi.com.tr > devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr > http://www.gunduz.org > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org > -- ------------------ | Sandeep Satpal | | M.Tech Student | | Lab 212 KReSIT | ------------------
On Thu, 6 Oct 2005 05:10 am, elein wrote: > Generally a short sed (or perl if you like) script will fix > these up. But it is really pretty obscure trail for people > to find the exact problem. Yeah, it's not that it's hard to fix when you know where to look, but my aim is to produce a site installation checklist for other people to follow. The simpler it is, the better the chance of it being successful. I'd prefer a site installation to be: - install PostgreSQL RPMs - unpack our specific postgresql.conf and pg_hba.conf - set up database from scripts - install Slony RPM - unpack our specific slony config files - run minimal commands to get Slony going - profit! (or at least I don't get woken up by phone calls at 3am) That's why I'm so keen on the RPMs working out of the box, with minimal need for post-installation tweaks/fixes. Regards, Philip.