cluster already running / removed stale pid file, error you may get while start up the postmaster.
postmaster daemons create pid files when start up, remove them when the process exits. some time pid file exist even after postmaster daemons exit because the process crashed before it could remove the pid file or the system crashes and processes do not get a chance to remove their pidfiles even if they want to.
--> in this case just find out & remove postmaster pid file ( you could find out pid file in data directory of postgresql installed path)
or
--> find out the the running process id (PID) using port no & kill PID
lsof | grep 5432 --(lsof | grep PortNo) and kill the pid
kill -9 PID
or
--> find out the the running process id (PID) using process name & kill PID
ps -ef | grep postmaster --(lsof | grep PortNo) and kill the pid
kill -9 PID
Once stop the running postmaster using pid, start the postgres database server.
All about data processing & analytics. Open source database,No-SQL and Hadoop. Discussed issues/solution which I've got during my experience..
Thursday, September 23, 2010
Subscribe to:
Post Comments (Atom)
Labels
- #agriculture (1)
- #ai (5)
- #pdf (1)
- Big Data (30)
- blogging (3)
- data analytics (5)
- data science (7)
- Deep Learning (4)
- Hadoop (28)
- Hadoop Eco System (27)
- hdfsCommands (4)
- Hive (5)
- IssueSolution (4)
- jobs (3)
- links (1)
- Machine Learning (4)
- mahout (2)
- MapReduce (1)
- MongoDB (6)
- MySQL (4)
- PlpgSQL (8)
- postgres (6)
- PostgreSQL (53)
- R (20)
- RHadoop (2)
- search keywords (1)
- social (2)
- spark (3)
- twitter (6)
- usecase (2)
- visualization (7)
- weka (1)
No comments:
Post a Comment