Menu
▾
▴
Re: [Postgres-xc-general] failed to find proc in ProcArray
|
From: Koichi S. <koi...@gm...> - 2014-02-14 02:49:19
|
I don't see anything strange in the configuration file. I found regression test sets up gtm port explicitly (value is the default, 6666, though). Could you try to configure your cluster with pgxc_ctl, which is far simpler and you have much less chance to encounter errors? This utility comes with built-in command sequences needed to configure and operate your cluster. Or, could you re-run the same with different log_min_message level? Regards; --- Koichi Suzuki 2014-02-14 11:16 GMT+09:00 Rishi Ramraj <the...@gm...>: > Missed the coordinator.conf file. Find attached. > > > On Thu, Feb 13, 2014 at 9:15 PM, Rishi Ramraj <the...@gm...> > wrote: >> >> Find all of the files attached. I have the GTM, coordinator and datanode >> services all hosted on the same Linux Mint machine for testing. They >> communicate using the loopback interface. >> >> To initialize the cluster, I ran the following: >> >> /var/lib/postgres-xc/gtm $ initgtm -Z >> /var/lib/postgres-xc/data $ initdb -D . --nodename data >> /var/lib/postgres-xc/coord $ initdb -D . --nodename coord >> >> To start the cluster, I use upstart: >> >> /usr/local/pgsql/bin/gtm -D /var/lib/postgres-xc/gtm >> /usr/local/pgsql/bin/postgres --datanode -D /var/lib/postgres-xc/data >> /usr/local/pgsql/bin/postgres --coordinator -D /var/lib/postgres-xc/coord >> >> I will increase the log level and try to reproduce the errors. >> >> >> On Thu, Feb 13, 2014 at 8:39 PM, 鈴木 幸市 <ko...@in...> wrote: >>> >>> Hello; >>> >>> You need to set log_statement GUC to appropriate value. Default is >>> “none”. “all” prints all statements accepted. Also, it will be a good >>> idea to include session ID in the log_line_prefix GUC. Your >>> postgresql.conf has some information how to set this. I tested >>> REL1_1_STABLE with four coordinators, four datanodes and four gtm_proxy and >>> did not have any additional log for any coordinators/datanodes. It will >>> be helpful what statements you issued. >>> >>> Here’s what I got in REL1_1_STABLE (I configured the cluster using >>> pgxc_ctl). >>> >>> Coordinator: >>> LOG: database system was shut down at 2014-02-14 10:2sd >>> LOG: autovacuum launcher started >>> >>> Datanode: >>> LOG: database system was shut down at 2014-02-14 10:21:08 JST >>> LOG: database system is ready to accept connections >>> LOG: autovacuum launcher started >>> >>> I’d like to have your configuration, each postgresql.conf file and what >>> you’ve done to initialize, start and run your application. >>> >>> Best; >>> --- >>> Koichi Suzuki >>> >>> 2014/02/14 0:38、Rishi Ramraj <the...@gm...> のメール： >>> >>> I just tried with REL1_1_STABLE. Here are my logs from the coordinator: >>> >>> LOG: database system was shut down at 2014-02-13 10:14:16 EST >>> LOG: database system is ready to accept connections >>> LOG: autovacuum launcher started >>> ERROR: syntax error at or near "asdf" at character 1 >>> STATEMENT: asdf; >>> LOG: failed to find proc 0x7f7d4a79ea60 in ProcArray >>> STATEMENT: create database test; >>> LOG: failed to find proc 0x7f7d4a79bc60 in ProcArray >>> ERROR: cannot drop the currently open database >>> STATEMENT: drop database test; >>> LOG: failed to find proc 0x7f7d4a79ea60 in ProcArray >>> STATEMENT: drop database test; >>> ERROR: syntax error at or near "blah" at character 1 >>> STATEMENT: blah blah blah; >>> LOG: failed to find proc 0x7f7d4a79bc60 in ProcArray >>> LOG: failed to find proc 0x7f7d4a79bc60 in ProcArray >>> LOG: failed to find proc 0x7f7d4a79bc60 in ProcArray >>> >>> The logs from the datanode: >>> >>> LOG: database system was shut down at 2014-02-13 10:19:33 EST >>> LOG: database system is ready to accept connections >>> LOG: autovacuum launcher started >>> LOG: failed to find proc 0x7f06bee5ea60 in ProcArray >>> STATEMENT: COMMIT PREPARED 'T10014' >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5ea60 in ProcArray >>> STATEMENT: COMMIT PREPARED 'T10023' >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> LOG: failed to find proc 0x7f06bee5bc60 in ProcArray >>> >>> The datanode seems to continuously produce logs but the coordinator does >>> not. I issued CREATE NODE commands to both services but they don't seem to >>> show up in the log. >>> >>> >>> On Thu, Feb 13, 2014 at 9:49 AM, Rishi Ramraj >>> <the...@gm...> wrote: >>>> >>>> I haven't been issuing commits or aborts every 30 seconds. So far, I've >>>> only issued five commands to the cluster using psql, but I have over 100 >>>> logs. I will try 1.1 today and let you know. >>>> >>>> Do you use a specific branching methodology, like gitflow? Do you have a >>>> bug tracking system? If you need any help with release engineering, let me >>>> know; I don't mind volunteering some time. >>>> >>>> >>>> On Thu, Feb 13, 2014 at 1:41 AM, 鈴木 幸市 <ko...@in...> wrote: >>>>> >>>>> GTM message is just a report. When GTM starts, it tries to read if >>>>> there is any slave connected in previous run and it didn’t find one. >>>>> >>>>> The first message looks not harmful but could be some potential issues. >>>>> Please let me look into it. The chance to have this message is at the >>>>> initialization of each datanode/coordinator, COMMIT, ABORT, COMMIT PREPARED >>>>> or ABORT PREPARED. >>>>> >>>>> Do you have a chance to issue them every 30 seconds? >>>>> >>>>> If possible, could you try release 1.1 and see if you have the same >>>>> issue (first message)? I think release 1.1 is better because master is >>>>> anyway development branch. >>>>> >>>>> Best; >>>>> --- >>>>> Koichi Suzuki >>>>> >>>>> 2014/02/13 14:51、Rishi Ramraj <the...@gm...> のメール： >>>>> >>>>> > Hello All, >>>>> > >>>>> > I just installed postgres-xc from the git master branch on a test >>>>> > machine. All processes are running on the same box. On both the coordinator >>>>> > and data processes, I'm getting the following logs about every 30 seconds: >>>>> > >>>>> > LOG: failed to find proc 0x7fd9ee703f80 in ProcArray >>>>> > >>>>> > On the GTM process, I'm getting the following logs at about the same >>>>> > frequency: >>>>> > >>>>> > LOG: Any GTM standby node not found in registered node(s). >>>>> > LOCATION: gtm_standby_connect_to_standby_int, gtm_standby.c:381 >>>>> > >>>>> > The cluster seems to be working properly. I was able to create a new >>>>> > database and a table within that database without any problem. I restarted >>>>> > all services and the data was persisted, but the logs persist. Any idea >>>>> > what's causing these logs? >>>>> > >>>>> > Thanks, >>>>> > - Rishi >>>>> > >>>>> > ------------------------------------------------------------------------------ >>>>> > Android apps run on BlackBerry 10 >>>>> > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. >>>>> > Now with support for Jelly Bean, Bluetooth, Mapview and more. >>>>> > Get your Android app in front of a whole new audience. Start now. >>>>> > >>>>> > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk_______________________________________________ >>>>> > Postgres-xc-general mailing list >>>>> > Pos...@li... >>>>> > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general >>>>> >>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> - Rishi >>> >>> >>> >>> >>> -- >>> Cheers, >>> - Rishi >>> >>> >> >> >> >> -- >> Cheers, >> - Rishi > > > > > -- > Cheers, > - Rishi > > ------------------------------------------------------------------------------ > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > |
