Found the log file. The log is mostly errors of the type:

lserver Sat Feb 23 16:40:14 2013
INET/inet_error: read errno = 104

with this type of error occurring a couple of times in a few minutes, then not repeating for 3 to 8 hours.

Otherwise, the only entries are startup and shutdown, corresponding to when we rebooted Mint:

lserver Sun Feb 24 13:47:29 2013
Shutting down the server with 35 active connection(s) to 5 database(s), 0 active service(s)

So, the maximum we should have would have been about 50 connections to 6 databases. The theory Firebird could be running out of memory would make sense if each connection was rather large.

Later this week we will consolidate into 3 databases and replace the superclassic model with the superserver model and see if the problem recurs.

--- In firebird-support@yahoogroups.com, "jackmason17@..." <jackmason17@...> wrote:
>
> There is no log in /var/log for anything resembling firebird. Where else would it be?
>
>
>
> --- In firebird-support@yahoogroups.com, "mariuz" <mariuz@> wrote:
> >
> >
> >
> > --- In firebird-support@yahoogroups.com, "jackmason17@" <jackmason17@> wrote:
> > >
> > > We converted from Windows 7 Interbase 6.02 last Monday by backing up the databases then restoring them to SuperClassic under Mint. The hardware is an Intel I3 with 8GB of memory, a hardware RAID (2 SSDs), and a system SSD. All 5 Firebird databases are on the RAID, a shared drive with Windows 7.
> >
> >
> > How is the shared driver with windows , it is a windows samba share ? i mean do the windows guests have access to write the firebird database ? this can be a major cause for corruption , also please send the logs for firebird usually is in /var/log/firebird2.5.log
> > or at least the error message from the log
> >
> > Does ssd raid is ok , check dmesg or the mdstat for raid status
> >
>