Indexing stops after only 4000 songs (Node 2)

Answered
Andreas Schüldt

I've been using the Logitech Squeezebox streaming solution for over ten years and it has worked very well indexing my 55.000 files (mix of FLAC and MP3 with immaculate metadata) and 550 GB of data in one folder. The problem was that the Spotify streaming integration was basically a hack and hard to use seamlessly with the multi-room setup so i spent 500 euro on a Node 2.

The problem is that the Node 2 / BluOS cannot index my music and I've been sending logfiles to support for a while - in short the indexing is aborted with memory issues and broken pipe messages and the support team tells me its because corrupted files and folders and that these should be removed. However I suspsect the system is not dimensioned / programmed cleverly enough because if i move the so called corrupted folders and files inte a very small folder with only a few hundred files it does work (Everything else the same)

Is it only me or is this a known issue?

(I run windows Environment with very fast Wifi and fiber network)

 

0

Comments

10 comments

Date Votes
  • Official comment
    Jade L.
    Sr. Support Crew Member

    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,

  • 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
  • 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
  • Tony W.
    Product Support Manager

    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
  • 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
  • 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...

    1
  • elky

    Trying again after giving up indexing my music collection two years ago...  looks like nothing has changed and nothing has been fixed.  :( 

     

    This device is not fit for purpose.

    0
  • Alain DW
    Lossless

    I must disagree, I have a relatively modest collection of +10 000 tracks, flac and mp3, and re-indexing on my nas takes under a minute (over wifi no less). Rebuilding completely maybe 5, I never timed this.

    All files have been individually tagged using mp3tag and/or quod libet.

    Album art is limited to 600x600 max and I noticed that larger art seems to slow down the process.

    So I would suggest you meticulously scrutinize your files.

    0
  • elky

    Bluesound offers no useful way to identify which file(s) of those 10,000+ files is causing the whole index process to fail.

    As OP also said, other music systems don't have the same issues, so there's really no way to figure out what the problem is and therefore how to successfully load the rest of your music collection.

    0
  • Tony W.
    Product Support Manager

    Hi Elky

    Reindex your collection. If it fails again, in the Bluesound App, please select Help, Send Support Request and our Support Crew will be happy to assist.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post