pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bhella Paramjeet-PFCW67 <PBhella@Motorola.com>
To: pgsql-admin@postgresql.org
Cc: Subbiah Stalin-XCGF84 <SSubbiah@Motorola.com>
Subject: Postgres database is not logging any messages after the reboot
Date: Wed, 10 Oct 2007 13:43:29 -0400
Message-ID: <1645d4840003b59c@previdencia.gov.br> (raw)

Hi 

The server that hosts our production postgres databases had to be
rebooted last night as the file systems got remounted as read only.
After the reboot we re-started the databases but now nothing is getting
logged into the pglogs. Can you please assist us in figuring out the
problem and help resolve it. Below listed are the error messages in the
/var/log/messages file due to which we had to reboot the server. This is
a linux x86-64 server. Your prompt response will be highly appreciated.

 Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1):
ext3_free_blocks_sb: bit already cleared for b
lock 3931168
Oct 10 06:45:02 sandbox kernel: Aborting journal on device sdb1.
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1):
ext3_free_blocks_sb: bit already cleared for b
lock 3931169
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1):
ext3_free_blocks_sb: bit already cleared for b
lock 3931170
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1):
ext3_free_blocks_sb: bit already cleared for b
lock 3931171
Oct 10 06:45:02 sandbox kernel: ext3_abort called.
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1):
ext3_journal_start_sb: Detected aborted journa
l
Oct 10 06:45:02 sandbox kernel: Remounting filesystem read-only
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_free_blocks_sb: Journal has aborted
Oct 10 06:45:02 sandbox last message repeated 70 times
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has aborte
d
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_truncate: Journal has aborted
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has aborte
d
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_orphan_del: Journal has aborted
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has aborte
d
Oct 10 06:45:02 sandbox kernel: EXT3-fs error (device sdb1) in
ext3_delete_inode: Journal has aborted
Oct 10 06:45:02 sandbox kernel: __journal_remove_journal_head: freeing
b_committed_data

Thanks
Paramjeet Bhella
 

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

                http://www.postgresql.org/about/donate



view thread (7+ messages)  latest in thread

Message-ID: <1645d4840003b59c@previdencia.gov.br>
Permalink:  ../1645d4840003b59c@previdencia.gov.br/
Also on:    postgresql.org/message-id/1645d4840003b59c@previdencia.gov.br

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: PBhella@Motorola.com, SSubbiah@Motorola.com
  Subject: Re: Postgres database is not logging any messages after the reboot
  In-Reply-To: <1645d4840003b59c@previdencia.gov.br>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox