Indexing stops after only 4000 songs (Node 2)

Answered

Comments

6 comments

  • Official comment
    Avatar
    Jade L.

    Hi Andreas,

    If you haven't already, please read over the support article I have linked below. This should help you understand what could be causing your index to fail and provide you with some steps to help resolve that issue.

    https://support1.bluesound.com/hc/en-us/articles/204103486-Why-did-indexing-cause-my-Bluesound-Player-to-restart

    Regards,

    Comment actions Permalink
  • Avatar
    Pasi

    I am new owner of node2i and have exatly same issue.

    Indexing fails with broken pipe everytime after about 4000 files and usually before that.

    That link what they keep posting idexing with http request and more logging does not do any better.

    Fails everytime and there is nothing wrong with my files or metadata tags. All my other apps and servers are fully satisfied with my files and library.

    I have fine tuned my Samba server to set keep alives but doesnt help. And also SMB2 or SMB3 forced  no help. I can see Node2 mount with SMB3_00 so it should be fine, but no.

    I just hope that there was nfs mount option, it works much better with Linux based systems!

    0
    Comment actions Permalink
  • Avatar
    Andreas Schüldt

    Hi Pasi, I'm sad to hear that this issue is not sorted even in the improved version and all firmware updates since then. How hard can it be for the code to skip one file if it's corrupt or have the wrong metadata? I suspect it is still a hardware issue and that the reason bluesound ignores us is because there's no fix.

    My temporary solution is that I have created a new folder with 4000 songs I listen to more often - but it's not a satisfying solution.

    0
    Comment actions Permalink
  • HI Pasi

    If your index crashes and stops, it is hitting a corrupted file. The above posted KB Article is designed to help you locate that corrupted file. Remove that file and the index will complete.

    If problem persists, please send our Support Crew the log by selecting Help, Send Support Request in the App.

    -1
    Comment actions Permalink
  • Avatar
    Pasi

    I have played around with this:
    https://support1.bluesound.com/hc/en-us/articles/204103486

    removed all folders where it was showing in log file broken pipe. And it always happens when indexing gets around 3500 files, never over 4000.

    Jul 12 12:37:32 (none) user.info ./ms.pl: main::__ANON__ ./ms.pl (1376) Scanning file /var/mnt/10.10.10.60-musat/AC DC/Rock Or Bust/11 - Emission Control.mp3
    Jul 12 12:37:34 (none) user.info dspout: [warning] stream recovery: Broken pipe (count=26)
    Jul 12 12:37:34 (none) user.err ./ms.pl: main::__ANON__ ./ms.pl (1397) reindex failed

    I ended up moving about 1600 files to other folder. Then I mounted that share and removed original share and did rebuild index. All was indexed without issues. So there is nothing wrong with files.

    Then I moved everything back to original share and mounted that and removed temporary and again indexing is failing after 3500 files!

    And support request sent from app, but no answer other than automatic message.

    1
    Comment actions Permalink
  • Avatar
    Andreas Schüldt

    Bad programming on underdimensioned hardware is the true reason! Both Squeezebox and Google Music still index the same 55.000 files folder without any problems...

    0
    Comment actions Permalink

Please sign in to leave a comment.