Thread: read only error..hard reboot not work as well

read only error..hard reboot not work as well

From
Raman kumar
Date:
FYI & A

FATAL:  lock file "postmaster.pid" already exists
HINT:  Is another postmaster (PID 18779) running in data directory "/var/lib/pgs
ql/data"?
FATAL:  pre-existing shared memory block (key 5432001, ID 3276801) is still in u
se
HINT:  If you're sure there are no old server processes still running, remove th
e shared memory block or just delete the file "postmaster.pid".
FATAL:  pre-existing shared memory block (key 5432001, ID 3276801) is still in u
se
HINT:  If you're sure there are no old server processes still running, remove th
e shared memory block or just delete the file "postmaster.pid".
FATAL:  pre-existing shared memory block (key 5432001, ID 3276801) is still in u
se
HINT:  If you're sure there are no old server processes still running, remove th
e shared memory block or just delete the file "postmaster.pid".
FATAL:  pre-existing shared memory block (key 5432001, ID 3276801) is still in u


could not write to log file: Read-only file system
could not write to log file: Read-only file system
could not write to log file: Read-only file system
could not write to log file: Read-only file system
could not write to log file: Read-only file system
could not write to log file: Read-only file system


--
Thanks & Regards,
Raman Kumar

http://raman-kumar.blogspot.com   (Linux)

http://raman-kumar1.blogspot.com  (Sun )

Re: read only error..hard reboot not work as well

From
"Kevin Grittner"
Date:
Raman kumar <raman36127@gmail.com> wrote:

> could not write to log file: Read-only file system

I'm not at all sure what you're trying to tell us or what you want
from us.  You have a file system which is mounted as read-only, that
much is clear ... but not much else.  That is going to break lots of
things on your computer, PostgreSQL included.  Why is the file
system mounted read-only?

http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

-Kevin

Re: read only error..hard reboot not work as well

From
"Mark Johnson"
Date:

 

It seems postgres is suffering from a file system condition, so your solution lies there and not with postgres.  There are many reasons why a file system can become read-only.  For example, if you are using virtual machines and run in to a low I/O bandwidth condition, the vm software can put the file systems into a read-only state to prevent data corruption.  Some clusterware and storage hardware vendors also do this on purpose to prevent corruption.  Without knowing more about your system there are too many possbiel causes to list them here.  My suggestion is to search the Internet for a possible cause/solution.  If, for example, you are using vmware on Linux then you might want to Google for "vmware linux read only filesystem".

-Mark