Re: [firebird-support] HUGE Log File

Hi, Usually such huge log is related with a database corruption. Can you please send here small excerpt from the most recent records of firebird.log (10-15 lines)? Regards, Alexey Kovyazin IBSurgeon

Re: [firebird-support] HUGE Log File

On 14 Sep 2015 15:14:38 -0700, "chubmast...@mac.com [firebird-support]" wrote: > Im no IT guy so bear with me. I have a 2009 iMac running os x 10.8 It > has a 640 gb hard drive. Firebird.log is taking up 424 gb. I have a > digital X-ray program that uses

Re: [firebird-support] HUGE Log File

I do at times have to force quit the application which is related to if the clients are idle for an extended period of time. This happens less often since I have set them not to go to sleep during working hours and quit the applications at the end of the day. About a month ago there was a

Re: [firebird-support] HUGE Log File

Actually maybe a month ago there was a corruption and I had to restore from a day from a time machine backup. I am not in the office today to look at the file however for two days it recorded error 22 full disk many times which was the problem caused by the corruption it seems

Re: [firebird-support] HUGE Log File

And thank you

Re: [firebird-support] HUGE Log File

At 10:14 a.m. 15/09/2015, chubmast...@mac.com [firebird-support] wrote: >Im no IT guy so bear with me. I have a 2009 iMac running os x 10.8It has >a 640 gb hard drive. Firebird.log is taking up 424 gb. I have a digital >X-ray program that uses firebird as it's framework. They deny they

Re: [firebird-support] HUGE Log File

At 11:58 a.m. 15/09/2015, chubmast...@mac.com [firebird-support] wrote: >Actually its a 424 gb log file that increased by 300 gb since sept 10, 2015 Yes, sorry, I noticed that after I posted. ;-) It won't do any harm to open your new log file in a day or two, and see just what is happening

Re: [firebird-support] HUGE Log File

Any way I trashed the file without emptying , restarted and everything seems to work. I'll empty it when convinced no more problems. I wonder if there is any chance my mac only thought it thought the file was that large.