> Hi, My pg_xlog dir has been growing rapidly the last 4 days, and my disk
> is now almost full (1000Gb) even though the database is only 50Gb. I have a
> streaming replication server running, and in the log of the slave it says:
>
> cp: cannot stat `/var/lib/postgresql/9.2/wals/0000000200000E1B000000A9':
> No such file or directory
> cp: cannot stat `/var/lib/postgresql/9.2/wals/0000000200000E1B000000A9':
> No such file or directory
> 2013-06-10 11:21:45 GMT FATAL:  could not connect to the primary server:
> could not connect to server: No route to host
>                 Is the server running on host "192.168.0.4" and accepting
>                 TCP/IP connections on port 5432?
>
> All the time.
>
> I have tried to restart the server, but that didn't help. I checked the
> master, and the file /var/lib/postgresql/9.2/wals/0000000200000E1B000000A9
> does not exist! I'm pretty lost here, can someone help me solve this and
> get my master server cleaned up. What is causing this, and what do I need
> to do?
>
>
IIRC, this kind of situation we may expect, when the archive command was
failed at master side. Could you verify, how many files
"000000xxxxxxx.ready" reside under the master's pg_xlog/archive_status
directory. And also, verify the master server's recent pg_log file, for
finding the root cause of the master server down issue.


Dinesh

-- 
*Dinesh Kumar*
Software Engineer

Ph: +918087463317
Skype ID: dinesh.kumar432
www.enterprisedb.co
<http://www.enterprisedb.com/>m<http://www.enterprisedb.com/>
*
Follow us on Twitter*
@EnterpriseDB

Visit EnterpriseDB for tutorials, webinars,
whitepapers<http://www.enterprisedb.com/resources-community> and
more <http://www.enterprisedb.com/resources-community>

Reply via email to