|
From: Juned K. <jkh...@gm...> - 2014-05-01 06:32:54
|
Hi koichi, Yeah my gtm.control file is exists but it contains no data. yes it used to work earlier this problem happened suddenly. still 123G space is available on server. I didn't setup anything in recovery.conf file manually. On Thu, May 1, 2014 at 11:52 AM, 鈴木 幸市 <ko...@in...> wrote: > Could you share gtm.control file which is placed at the same directory as > gtm.conf. I’m afraid this file has been removed or corrupt. Did it use > to work and then happened this problem? If so, did you met any other > issues on the operation? Do you really have enough file space at the > datanode? Xlog archive consumes much file space. This is no difference > from PostgreSQL. > > Did you setup archive_cleanup_command configuration in your > recovery.conf file to clean up old archive log? pg_archivecleanup utility > will help. > > Regards; > --- > Koichi Suzuki > > 2014/05/01 15:00、Juned Khan <jkh...@gm...> のメール: > > Anyone can please help me with this how to solve this issue ? > > > On Mon, Apr 28, 2014 at 5:01 PM, Juned Khan <jkh...@gm...> wrote: > >> in logs i found this >> DETAIL: The failed archive command was: rsync >> pg_xlog/000000010000001C0000006A postgres@db01 >> :/home/postgres/pgxc/nodes/datanode_archlog/000000010000001C0000006A >> rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: >> Broken pipe (32) >> rsync: write failed on >> "/home/postgres/pgxc/nodes/datanode_archlog/000000010000001C0000006A": No >> space left on device (28) >> rsync error: error in file IO (code 11) at receiver.c(322) >> [receiver=3.0.9] >> rsync: connection unexpectedly closed (28 bytes received so far) [sender] >> rsync error: error in rsync protocol data stream (code 12) at io.c(605) >> [sender=3.0.9] >> LOG: archive command failed with exit code 12 >> >> >> >> On Mon, Apr 28, 2014 at 4:51 PM, Juned Khan <jkh...@gm...> wrote: >> >>> Hi all, >>> >>> I setup pgxc, but today when i tried fire one manual query i got below >>> message. i am not able to show table descriptions as well. >>> >>> database=# \d >>> ERROR: could not access status of transaction 0 >>> DETAIL: Could not write to file "pg_clog/000B" at offset 40960: No >>> space left on device. >>> >>> sometimes its showing table description in below format. >>> >>> database=# \dt >>> <table border="1"> >>> <caption>List of relations</caption> >>> <tr> >>> <th align="center">Schema</th> >>> <th align="center">Name</th> >>> <th align="center">Type</th> >>> <th align="center">Owner</th> >>> </tr> >>> >>> >>> -- >>> Thanks, >>> Juned Khan >>> >>> <http://www.inextrix.com/> >>> >> >> >> >> -- >> Thanks, >> Juned Khan >> >> <http://www.inextrix.com/> >> > > > > -- > Thanks, > Juned Khan > iNextrix Technologies Pvt Ltd. > www.inextrix.com > ------------------------------------------------------------------------------ > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE > Instantly run your Selenium tests across 300+ browser/OS combos. Get > unparalleled scalability from the best Selenium testing platform available. > Simple to use. Nothing to install. Get started now for free." > > http://p.sf.net/sfu/SauceLabs_______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general > > > -- Thanks, Juned Khan <http://www.inextrix.com/> |