Author Topic: tRAID Broker Service Crashes  (Read 3803 times)

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
tRAID Broker Service Crashes
« on: March 10, 2016, 06:32:40 pm »
I am a long time user of tRAID and have been running the latest release since shortly after it became available. Overall it works great. It performs well and does what I need. I use is for a storage pool consisting of 5 DRUs and 1 PPU. My database has low activity and is used primarily for housing movies, tv show and related metadata. Every few days the Broker Service crashes. The time between crashes varies, but is always several days. I have run a lot of trace logging, but that never shows anything of value. I can't relate the crashes to any particular type of activity. In every case restarting the Broker Service and the storage pool circumvents the problem. There is never any associated system crash. It is running in Windows 10 Pro at current maintenance. Most recently I set up ProcDump to dump  in the event of an unhandled exception. After 8 days of running, the Broker Service crashed and a dump was produced. The ProcDump log shows exception c0000005.ACCESS_VIOLATION. The event log entry for the crash shows:

Log Name:      Application
Source:        Application Error
Date:          3/10/2016 4:34:22 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Data-Server-1
Description:
Faulting application name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Faulting module name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Exception code: 0xc0000005
Fault offset: 0x00059b84
Faulting process id: 0x9dc
Faulting application start time: 0x01d175580957122b
Faulting application path: C:\Users\Steve\Application Data\Downloads\tRAID Host Package\NZFS-TRAID-HOST-1.0_final_2015-11-09\common\NZFSB.exe
Faulting module path: C:\Users\Steve\Application Data\Downloads\tRAID Host Package\NZFS-TRAID-HOST-1.0_final_2015-11-09\common\NZFSB.exe
Report Id: fa789744-2f99-4d18-ab77-6f9f2ed455de
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-03-10T21:34:22.000000000Z" />
    <EventRecordID>8175</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Data-Server-1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NZFSB.exe</Data>
    <Data>1.0.0.1</Data>
    <Data>56407513</Data>
    <Data>NZFSB.exe</Data>
    <Data>1.0.0.1</Data>
    <Data>56407513</Data>
    <Data>c0000005</Data>
    <Data>00059b84</Data>
    <Data>9dc</Data>
    <Data>01d175580957122b</Data>
    <Data>C:\Users\Steve\Application Data\Downloads\tRAID Host Package\NZFS-TRAID-HOST-1.0_final_2015-11-09\common\NZFSB.exe</Data>
    <Data>C:\Users\Steve\Application Data\Downloads\tRAID Host Package\NZFS-TRAID-HOST-1.0_final_2015-11-09\common\NZFSB.exe</Data>
    <Data>fa789744-2f99-4d18-ab77-6f9f2ed455de</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

I have read some forum entries that sound similar but with no apparent resolution.

I run a weekly verify sync scan of the database and that happened to run during the early morning of the day of the crash. It ran without exception, and there has not been any correlation between the timing of those scans and the crashes.

I am certainly not expert at analyzing ProcDumps. So first of all, if this sounds like an error of which you are already aware, I don't want to waste your or my time. If you want further information from me, please tell me exactly what you want. I can post a link to the dump file obviously, but is there some particular analysis you want me to run on it first? Are there caching options that are known to cause such problems?

It would be nice if there were one single place we could go to get all the information we need to post bug reports that are useful to you. If that exists, please point me to it, and I apologize for missing it. I have spent a lot of time reading forum posts but admit that I cannot begin to cover them all.

One other thing I noticed when running ProcDump to trap the error. It report numerous

Exception: E06D7363.?AVECBFSError@@

messages. I saw this referenced in another post but did not see an answer. Obviously they must be handled exceptions, but what are they and why are there so many? Just curious.

Thanks for your help.

Offline jamohamo

  • Jr. Member
  • **
  • Posts: 63
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #1 on: April 10, 2016, 06:30:36 am »
Steve, I just fixed mine. See my thread "Storage Pool crashes after 5 to 10 minutes **SOLVED** ". I hope that helps.

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #2 on: May 12, 2016, 09:33:05 am »
Thanks for your response and sorry it took me so long to see it. I'm not used to getting any responses here. I can't tell that I have your problem, but I have decided to try running without my landing disk for awhile. My storage pool used to run for months without a failure, so the frequent crashes I have now obviously reflect some adverse change. I want to see if not using the landing disk has any effect.

Offline cameronwmckay

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #3 on: June 18, 2016, 03:07:21 am »
It seems I am having exactly the same problem, and it cannot be caused by a landing disk as I do not have one.

I have seen it occur five times in the last two months.

Here is the even viewer dump which seems to be the same as steve's.  Would love to hear some feedback.

Faulting application name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Faulting module name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Exception code: 0xc0000005
Fault offset: 0x00059b84
Faulting process id: 0xcfc
Faulting application start time: 0x01d1c212e1a5c779
Faulting application path: C:\NZFS-TRAID-HOST-1.0_final_2015-11-09\NZFS-TRAID-HOST\common\NZFSB.exe
Faulting module path: C:\NZFS-TRAID-HOST-1.0_final_2015-11-09\NZFS-TRAID-HOST\common\NZFSB.exe
Report Id: 144e8dd6-3312-11e6-80be-e0cb4e2c4cd5
Faulting package full name:
Faulting package-relative application ID:


Offline cameronwmckay

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #4 on: June 22, 2016, 03:24:59 am »
So it seems I have had it again:

Faulting application name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Faulting module name: NZFSB.exe, version: 1.0.0.1, time stamp: 0x56407513
Exception code: 0xc0000005
Fault offset: 0x00059b84
Faulting process id: 0xdac
Faulting application start time: 0x01d1c71efaff5eb7
Faulting application path: C:\NZFS-TRAID-HOST-1.0_final_2015-11-09\NZFS-TRAID-HOST\common\NZFSB.exe
Faulting module path: C:\NZFS-TRAID-HOST-1.0_final_2015-11-09\NZFS-TRAID-HOST\common\NZFSB.exe
Report Id: 1f1e2259-3818-11e6-80be-e0cb4e2c4cd5
Faulting package full name:
Faulting package-relative application ID:

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #5 on: June 27, 2016, 01:16:06 pm »
Just as an update, I have tried turning off all types of caching and the landing disk. None of that had any effect. I still get the same crash every several days. I am back to running with a landing disk and most caching back on. None of that seems to change anything. I just get a Broker Service crash at the same location every week to 10 days. It's too bad because once upon a time, I could run tRAID for several months without a failure. Since Brahim seems to be away from the forum for the time being, I am living with the problem and hoping to someday see a new release that fixes this. It wouldn't be so bad if tRAID had an automation interface to allow me to restart the storage pool when the failures occur. As it is, I can restart the service and the array just fine, but I have't found a reasonable way to avoid manual intervention to restart the storage pool.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #6 on: June 28, 2016, 12:12:22 pm »
Please PM me a link to the ProcDump.

Thanks.

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #7 on: July 03, 2016, 11:33:26 am »
For the Forum, per Brahim's request, I did PM him the ProcDump on June 30. I hope it will give him what he needs to fix this.

Offline cameronwmckay

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #8 on: July 28, 2016, 05:16:11 am »
Has there been any update on this issue?

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #9 on: August 09, 2016, 05:15:00 pm »
Not that I have seen. I still get the crashes every few days.

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #10 on: August 21, 2016, 11:33:57 am »
One thing I notice is that the crashes usually happen after 7 or eight days. I run a Verify Sync every night that might be cycling through the database in about that amount of time. I'm wondering if it could be happening when the cycle is completing or restarting. I hate to turn the Verify Sync off, but it might be worth a try to see if the crashes are affected.

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #11 on: August 21, 2016, 07:19:12 pm »
Check your PM.

Offline steve-jarrell

  • Newbie
  • *
  • Posts: 33
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #12 on: September 05, 2016, 11:53:42 am »
Brahim,

I responded to your PM twice today and both times received a database error. I'm not sure if it actually went to you, so let me know if it didn't.

Thanks,
Steve

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #13 on: September 06, 2016, 08:07:40 am »
Got them.
Thanks.

Offline cameronwmckay

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: tRAID Broker Service Crashes
« Reply #14 on: September 28, 2016, 06:55:52 pm »
Any update on this one?