Subject Re: [firebird-support] Huge Log file size crashing server
Author Helen Borrie
At 12:43 PM 29/01/2006, you wrote:
>Dear friends,
>
>We have following setup
>
>One Win 2003 server acting as PDC
>Another Win 2000 server
>A Linux (FC4 samba) Firebird Server.

Samba? See below.


>OFC Backbone 10/100baseT Lan with about
>35 to 40 win 9x/xp nodes. Some are using
>SQL server based application on 2k3 server
>and some are using Firebird based application
>on Linux server.
>
>The Firebird server has been recently added to
>port a application which was earlier in paradox.

Was it, in between times, in InterBase 5?

>For Firebird application D-5/IBO is used.
>
>We are facing a peculiar problem of very huge
>Firebird log file getting almost 6/7 GB
>which occupies whole partition and server
>crashes or application gets blocked.

You can delete firebird.log any time there are no connections to any
databases. Do you have this as a regular part of your housekeeping?


>following line repeats thousand/million ... times
>to make the log file to such size
>
>rsp.com (Server) Sat Jan 28 10:24:57 2006
> INET/inet_error: read errno = 9

The "usual" causes of this error are:

1) you have remote users trying to access the server through a
non-licensed client. Are you trying to use an IB 5 version of gds32.dll?
2) you have local or remote clients trying to access a Classic server
using an InterBase client (this won't work...but if it were an IB6
client library, you would get an exception in the application...so I
still have my money on IB 5 clients)
3) You mentioned Samba. Samba should not be in the picture at
all. Tell us how you are using Firebird with Samba.


>Can somebody tell me what could be reason for this

What's "this"? If you have limited diskspace available on the
server, you need to be watching the size of the log file.

>and how shall i overcome that.

The log file shouldn't be getting so large, anyway. Allowing, say, a
generous 300 bytes for each incident logged, a 6 Gb log file would
represent something in the order of 20 million incidents. Are they
contiguous and covering a short period of time? Are you sure this
isn't a DoS attack from the internet or even from the internal network?

>Is there any way to limit size of log file

Assuming you do backups on a regular basis in a cron job, include
deleting (or renaming and moving) the log file in the job.

But be suspicious about a log file that grows fast.

>or reduce level of log in Firebird or time being eliminate log file
>altogether ?

Not a desirable solution.

1) Find out what's causing this volume of incidents and fix that.
2) Make provision to have enough diskspace.
3) Don't involve Samba with either Firebird servers or Firebird clients.