Subject | Re: [firebird-support] Re: SCH_validate -- not entered |
---|---|
Author | Helen Borrie |
Post date | 2007-03-06T06:25:47Z |
At 11:23 AM 6/03/2007, you wrote:
threads and restarting the topic.
Whichever one of you it is who is running Firebird SS on Fedora, you
need to check whether you are running the NPTL build (as you need to
be). SCH_validate is to do with thread scheduling and if you try to
run the pthreads version on Fedora without disabling NPTL, you are
likely to get these errors.
You might also get them if a local client has primary access to
libfbembed.so through a symbolic link. With it, that local client
can connect directly to the database as a no-network Classic client
and cause problems for other connections trying to get in remotely
via the Supersever.
are getting file I/O errors. There is only one Firebird client
interface that accesses a database as a file: that is the embedded
client on POSIX. It should not be anywhere around a Superserver
installation. And that libary should *never* be used for threaded connections.
Both of you check and double check that your applications are
connecting through the correct client library for the server that you
are running. And the guy with the Fedora box, make sure you are
properly set up for threading.
./heLen
>Hello!You two are making things very confusing by hijacking each other's
>These errors are quite rare, so i guess it is quite hard to answer
>anything.
>
>Do you have anything in php error log when/before you had
>SCH_validate error? I have to check, but in my case I could have
>something about "deadlock update conflicts with concurrent update". I
>cannot check logs right now, but I will. I get these sometimes. The
>deadlock thing is something I have to ask about our software
>developer...
>
>Do you get these SCH_validate errors often? Could you check your
>hardware? How long your server was up and running before SCH_validate?
>
>That is bad that we cannot give any test cases, but it would be nice
>that experts could say something about our cases?
>
>ps. I have read these support/devel lists like 5 years for now.
>Activity of these lists was a one big good plus choosing database
>engine :)
>-Jarkko
threads and restarting the topic.
Whichever one of you it is who is running Firebird SS on Fedora, you
need to check whether you are running the NPTL build (as you need to
be). SCH_validate is to do with thread scheduling and if you try to
run the pthreads version on Fedora without disabling NPTL, you are
likely to get these errors.
You might also get them if a local client has primary access to
libfbembed.so through a symbolic link. With it, that local client
can connect directly to the database as a no-network Classic client
and cause problems for other connections trying to get in remotely
via the Supersever.
>--- In firebird-support@yahoogroups.com, "Aldo Caruso" <acaruso@...>Those must be PHP errors and one is tempted smell rodents when you
>wrote:
> >
> > Hi bazoona,
> >
> > I've got just the same errors in the firebird.log, and I'm using
>too
> > php, but instead of the sysdba user I use an unprivileged one.
> >
> > The only difference is that after the same SCH_validate error, the
> > same INET errors, I also got the I/O database file error but
>slightly
> > different in the last line:
> >
> > Instead of
> >
> > "Illegal seek"
> >
> > I got
> >
> > "Invalid file handler"
are getting file I/O errors. There is only one Firebird client
interface that accesses a database as a file: that is the embedded
client on POSIX. It should not be anywhere around a Superserver
installation. And that libary should *never* be used for threaded connections.
Both of you check and double check that your applications are
connecting through the correct client library for the server that you
are running. And the guy with the Fedora box, make sure you are
properly set up for threading.
./heLen