On Tue, Jan 11, 2011 at 2:00 PM, Bill Moran
wrote:
> In response to Victor Hugo dos Santos :
Hello Bill,
[...]
> Here's my recommendation:
> 0) Make sure you're getting reliable backups of the database. Try
> restoring one to another system.
yes.. worked the last week
> 1) make sure you'r
On Tue, Jan 11, 2011 at 1:39 PM, Kern Sibbald wrote:
> On Tuesday 11 January 2011 14:29:45 Victor Hugo dos Santos wrote:
Hello Kern,
[...]
>> That is a bacula bug ??
>
> Very unlikely. It looks like the Postgres database has been corrupted. You
> will need to research the problem and solutio
Hi,
even not bacula related my two cents:
- which os and version do you run postgresql on
- which version of postgresql do you use (psql startup output will show you
this - and an additional message if client and server have different versions)
- which filesystem do you use
- you can try dump
In response to Victor Hugo dos Santos :
>
> > The other error is indicative of a filesystem problem. I can't think
> > of any normal circumstance that would cause that error, and thus it
> > concerns me.
>
> mmm.. the RAID controller, badblocks and fsck don't show any errors in
> the filesystem
In response to Victor Hugo dos Santos :
> this the complete postgresql error logs:
>
> first
> ===
> 2011-01-10 06:11:25 CLST ERROR: could not open relation with OID 2247622656
> 2011-01-10 06:11:25 CLST STATEMENT: INSERT INTO Filename (Name)
> SELECT a.Name FROM (SELECT DISTINCT Name F
On Tuesday 11 January 2011 14:29:45 Victor Hugo dos Santos wrote:
> Hi guys !!
>
> Two weeks ago, my system began working abnormal..
> first, the database have a "corruption" in table public.file
> http://www.mail-archive.com/[email protected]/msg36393.html
>
> I sent this error to the pgs
On Tue, Jan 11, 2011 at 1:16 PM, Bill Moran
wrote:
> In response to Victor Hugo dos Santos :
>
>> this the complete postgresql error logs:
>>
>> first
>> ===
>> 2011-01-10 06:11:25 CLST ERROR: could not open relation with OID 2247622656
>> 2011-01-10 06:11:25 CLST STATEMENT: INSERT INTO
I would run the bacula dbcheck program to fix this.
John
--
Protect Your Site and Customers from Malware Attacks
Learn about various malware tactics and how to avoid them. Understand
malware threats, the impact they can
On Tue, Jan 11, 2011 at 1:01 PM, Victor Hugo dos Santos
wrote:
[...]
> in postgresql logs only show this error:
>
> =
> 2011-01-11 00:24:20 CLST ERROR: could not open relation with OID 2247622656
> 2011-01-11 00:24:20 CLST STATEMENT: INSERT INTO Filename (Name)
> SELECT a.Name FROM
On Tue, Jan 11, 2011 at 11:20 AM, Bob Hetzel wrote:
> Sounds like your filesystem where the databases are held has filled up. When
> checking for this, make sure that it isn't a temporary situation--to
> determine that you'll have to check the drive space at the time of the
> error, in addition to
Hi guys !!
Two weeks ago, my system began working abnormal..
first, the database have a "corruption" in table public.file
http://www.mail-archive.com/[email protected]/msg36393.html
I sent this error to the pgsql-admin, because I thought that the
problem was only in the database.
In thi
11 matches
Mail list logo
