Subject | Re: Crashing (Was: Invalid Block Type Encountered) |
---|---|
Author | mnfirebird |
Post date | 2005-02-23T00:24:18Z |
ummm, the platform is a rackspace Athon:
[root@fedora root]# uname -a
Linux fedora 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 athlon
i386 GNU/Linux
For whatever reason, I think that I fixed things to the point where
they work OK.
The only major problem is that the system is now crashing. I told my
customer that I've never heard of firebird or interbase doing this.
Essentially, Apache runs a script which uses the embedded library as
user apache.
When I first set up the system, the semaphores were owned by apache
(since it kicked off fb_lock_mgr) and when root tried to run isql,
the isql script would hang.
So then I setuid and chmod +s on the fb_lock_mgr program.
That let multiple users access the database but then the system
started crashing, as mentioned.
When I got home today, I thought about using an inittab boot entry to
launch fb_lock_mgr so it runs as root and creates semaphores as root.
At this point, I don't know what to think about the crashes.
Does anyone think it's possible for embedded firebird to crash a
fedora linux server?
The system seems to crash in close proximity to when I run isql so I
was thinking about fb_lock_mgr.
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
[root@fedora root]# uname -a
Linux fedora 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 athlon
i386 GNU/Linux
For whatever reason, I think that I fixed things to the point where
they work OK.
The only major problem is that the system is now crashing. I told my
customer that I've never heard of firebird or interbase doing this.
Essentially, Apache runs a script which uses the embedded library as
user apache.
When I first set up the system, the semaphores were owned by apache
(since it kicked off fb_lock_mgr) and when root tried to run isql,
the isql script would hang.
So then I setuid and chmod +s on the fb_lock_mgr program.
That let multiple users access the database but then the system
started crashing, as mentioned.
When I got home today, I thought about using an inittab boot entry to
launch fb_lock_mgr so it runs as root and creates semaphores as root.
At this point, I don't know what to think about the crashes.
Does anyone think it's possible for embedded firebird to crash a
fedora linux server?
The system seems to crash in close proximity to when I run isql so I
was thinking about fb_lock_mgr.
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
> At 07:57 AM 30/01/2005 -0800, you wrote:(gds) and
>
> >I wrote a custom application that used the Firebird DSQL library
> >couldn't connect. I saw these errors in the log:type
> >
> >localhost Thu Jan 20 23:43:20 2005
> > Database: /root/fb/data/history.db
> > internal gds software consistency check (invalid block
> > encountered (147))type
> >
> >localhost Thu Jan 20 23:45:59 2005
> > Database: /root/fb/security.fdb
> > internal gds software consistency check (invalid block
> > encountered (147))application
> >
> >After running isql on the database(history.db), thenmy custom
> >could connect to the database again.the screen.
> >
> >Any ideas why? When I ran gfix -verify, nothing was reported to
> You are encountering a mismatch - typically, a lower version of theserver
> trying to connect to a database with higher on-disk structure(ODS). An
> old server will see garbage in the header of a database createdwith a
> higher ODS.calls
>
> In Firebird 1.5, Isql is OK, because it makes its own internal API
> and attaches to the server that it "knows about".InterBase or
>
> Your reference to "gds" makes me suspect that you are trying to run
> multiple versions of the database server that don't know about one
> another. It sounds like you are running Classic and you have
> Firebird 1 also listening for connections.symlink
>
> You should also use the correct client for Fb 1.5. It is OK to
> your Fb 1.5 client as libgds.so to support an older application,but your
> symlinks must point to libfembed.so (Classic only) orlibfbclient.so
> (Superserver or Classic).server
>
> You're not giving a lot away about your installation (platform,
> model). That would help...
>
> ./heLen