I wrote an upstart script for starting slony on ubuntu 10.04+. If there's any interest in including it in the slony distro, you can find it here: https://github.com/pgexperts/upstart-scripts/blob/master/etc/init/slony.conf -- -- Jeff Frost <jeff@...> CTO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 FAX: 415-762-5122 http://www.pgexperts.com/
Not sure what I'm missing but I get this error when I try to run the slony
config. I'm running this at postgres. I ran the config earlier this week
and we had to stop slony. Try to run it today but fails
$ ./slony-conf.sh
<stdin>:21: PGRES_FATAL_ERROR load '$libdir/slony1_funcs'; - ERROR:
could not access file "$libdir/slony1_funcs": No such file or directory
<stdin>:21: Error: the extension for the Slony-I C functions cannot be
loaded in database 'dbname=canvas_db host=harv user=postgres'
It all looks correct but can't find slony1_funcs when running conf
$ find /opt/postgres -name slony1_funcs.so
/opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so
$ pg_config --libdir
/opt/postgres/9.0.3-pgdg/lib
$ pg_config --pkglibdir
/opt/postgres/9.0.3-pgdg/lib
$ ll /opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so
-rwxr-xr-x 1 postgres postgres 39K Apr 9 14:28
/opt/postgres/9.0.3-pgdg/lib/slony1_funcs.so
0___ Wolfgang Schwurack
c/ /'_ SA/DBA - UEN
(*) \(*) 801-587-9444
wolf@...
(Continue reading)On 12-05-07 03:26 PM, Jan Wieck wrote: > On 5/7/2012 2:58 PM, Steve Singer wrote: > If it works on Win32, I don't see how it can make things worse. It isn't > watertight "when using NFS", but then again, that isn't such a reliable > solution for log shipping to begin with. > Your patch does in fact compile on Win32. I don't see any problems with applying this patch. > > Jan >
On 12-05-07 07:33 PM, Richard Yen wrote: > On Mon, May 7, 2012 at 12:22 PM, Steve Singer <ssinger@... > <mailto:ssinger@...>> wrote: > > > The archive sequence numbers are supposed to be assigned on the node > the slon is for (node 3 is this case). So two remote_worker threads > inside of slon 3 SHOULDN'T ever get the same archive counter number > (we should be serializing on an update of the archive_counter > table), thus they shouldn't be writing to the same file. One > theory is that some of the "shouldnt's" are actually happening (for > reasons we haven't determined) > > > I notice in my logs that I see very frequent occurrences of these (maybe > once per minute): > > 16:28]myhost:/home/richyen# head /var/log/local0 > Apr 29 20:13:31 myhost.example.com <http://myhost.example.com> > postgres[21243]: [4876-1] 2012-04-29 20:13:31.873 PDT [user=###,db=### > localhost(57453) PID:21243 XID:1971641858]ERROR: could not serialize > access due to concurrent update > Apr 29 20:13:31 myhost.example.com > <http://myhost.example.com> postgres[21243]: [4876-2] 2012-04-29 > 20:13:31.873 PDT [user=###,db=### localhost(57453) PID:21243 > XID:1971641858]STATEMENT: update "_slony".sl_archive_counter set > ac_num = ac_num + 1, ac_timestamp = CURRENT_TIMESTAMP; select > ac_num, ac_timestamp from "_slony".sl_archive_counter; > Apr 29 20:13:31 myhost.example.com > <http://myhost.example.com> postgres[21243]: [4877-1] 2012-04-29(Continue reading)
On 12-05-07 12:51 PM, Jan Wieck wrote: > On 5/7/2012 10:16 AM, Steve Singer wrote: >> On 12-05-07 10:09 AM, Steve Singer wrote: >>> On 12-05-05 10:14 AM, Jan Wieck wrote: >>>> On 5/2/2012 5:39 PM, Steve Singer wrote: > > Me too and I agree that O_EXCL certainly isn't the best way to do it. > However, the presented patch does not change any existing functionality > (except for the exclusiveness in creating the temp file). > > While there remains a possible race condition when using NFS, the log > file I examined would very unlikely slip through it. Remember, the first > process must have written more than 32K before the second process calls > open(2). > > What I intended with this simple patch was to give Richard a chance to > identify the processes involved in creating this problem. Up to this > moment we don't even know exactly how this happens. Sorry, I was thinking you were proposing this patch for commit on the 2.0, 2.1, 2.2 branches not just for Richard. I wouldn't be opposed to a patch that doesn't make things worse on nfs/cifs systems (if it compiles on win32). I think we both agree that the real problem is what is causing two files to be opened at the same time, and we don't yet have a handle why that is the case. > >(Continue reading)
Hey all!
I successfully setup my first slony replication - however quite a few
conceptual questions raised on the way:
I have the following setup (taken from slon_tools.conf):
add_node(node => 1,
host => 'master.foo',
dbname => 'foo',
port => 5432,
user => 'slony',
password => 'XXX');
add_node(node => 11,
host => 'slave1.foo',
dbname => 'foo',
port => 6254,
user => 'slony',
password => 'XXX');
add_node(node => 12,
host => 'slave2.foo',
dbname => 'foo',
port => 2254,
user => 'slony',
password => 'XXX');
This config got deployed on every node, every pg_hba.conf-file contained
a line which allowed all other servers to connect as user slony.
(Continue reading)
I am getting this error..i dont know where to change..can anyone say..
<stdin>:8: loading of file /usr/local/pgsql/share//slony1_funcs.sql: PGRES_FATAL_ERROR ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1
ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1
_______________________________________________ Slony1-general mailing list Slony1-general@... http://lists.slony.info/mailman/listinfo/slony1-general
When i specify
_______________________________________________ Slony1-general mailing list Slony1-general@... http://lists.slony.info/mailman/listinfo/slony1-general
Hi,
_______________________________________________ Slony1-general mailing list Slony1-general@... http://lists.slony.info/mailman/listinfo/slony1-general
From: Lakshmi Priya <gangulynj <at> gmail.com>
To: Glyn Astill <glynastill-/E1597aS9LT10XsdtD+oqA@public.gmane.org>
Sent: Wednesday, 11 April 2012, 10:44
Subject: Re: [Slony1-general] Error in slony
How to run the Update functions..On Wed, Apr 11, 2012 at 1:56 PM, Glyn Astill <glynastill-/E1597aS9LT10XsdtD+oqA@public.gmane.org> wrote:It means that the version of the functions in your schema does not match the compiled version of slony. I'm guessing you need to run "update functions"From: Lakshmi Priya <gangulynj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: slony1-general-8kkgcvHRObyz5F2/bZa4Fw@public.gmane.org
Sent: Wednesday, 11 April 2012, 8:24
Subject: [Slony1-general] Error in slony
_______________________________________________Can any one say what this error meant..??
<stdin>:8: loading of file /usr/local/pgsql/share//slony1_funcs.sql: PGRES_FATAL_ERROR ERROR: Slonik version: 2.0.6 != Slony-I version in PG build 2.1.1.
Slony1-general mailing list
Slony1-general-8kkgcvHRObyz5F2/bZa4Fw@public.gmane.org
http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________ Slony1-general mailing list Slony1-general@... http://lists.slony.info/mailman/listinfo/slony1-general
_______________________________________________ Slony1-general mailing list Slony1-general@... http://lists.slony.info/mailman/listinfo/slony1-general
RSS Feed15 | |
|---|---|
29 | |
46 | |
58 | |
29 | |
41 | |
63 | |
28 | |
53 | |
50 | |
43 | |
43 | |
48 | |
64 | |
25 | |
51 | |
61 | |
60 | |
153 | |
61 | |
66 | |
94 | |
72 | |
130 | |
156 | |
138 | |
80 | |
75 | |
60 | |
78 | |
63 | |
77 | |
136 | |
177 | |
203 | |
74 | |
69 | |
101 | |
61 | |
49 | |
92 | |
65 | |
70 | |
103 | |
180 | |
173 | |
140 | |
221 | |
140 | |
123 | |
115 | |
289 | |
150 | |
190 | |
146 | |
145 | |
205 | |
189 | |
177 | |
221 | |
130 | |
141 | |
222 | |
191 | |
156 | |
167 | |
219 | |
198 | |
218 | |
103 | |
152 | |
148 | |
132 | |
144 | |
214 | |
166 | |
168 | |
167 | |
153 | |
189 | |
240 | |
182 | |
215 | |
203 | |
191 | |
111 | |
71 | |
2 |
