Failed to scan library with Volumio v2.502

Help and Support Help
1

Hi,

I am having trouble scanning a music flac library but its stops at a certain point. I am guessing it has something to do with an illegal object, which it cannot read/process.

I am kind of new, tried to pinpoint the problem myself, but am stuck because I don’t understand where it goes wrong.

It says, it cannot read property ‘0’ or something, but it doesn’t tell me which folder or anything and “events.js:126:13” is kind of cryptic for me…

logs.volumio.org/volumio/6yA0wEB.html

Can someone point me in the right direction? Thanks!

Remco

2

Error message is:

error:  message=Cannot read property '0' of undefined, stack=TypeError: Cannot read property '0' of undefined

but that’s rather vague, and you’ll need to wait for someone more familiar with the scanning code to interpret that.

When it stops scanning, do you have any tracks in your library? Do you see track numbers incrementing during the scan?

3 
Nov 20 10:30:05 volumio-rpi2 volumio[808]: error:  message=Cannot read property '0' of undefined, stack=TypeError: Cannot read property '0' of undefined
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at /volumio/app/plugins/music_service/upnp_browser/index.js:83:67
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at /volumio/app/plugins/music_service/upnp_browser/index.js:626:21
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Parser. (/volumio/node_modules/xml2js/lib/parser.js:303:18)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at emitOne (events.js:116:13)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Parser.emit (events.js:211:7)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at SAXParser.onclosetag (/volumio/node_modules/xml2js/lib/parser.js:261:26)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at emit (/volumio/node_modules/sax/lib/sax.js:624:35)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at emitNode (/volumio/node_modules/sax/lib/sax.js:629:5)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at closeTag (/volumio/node_modules/sax/lib/sax.js:889:7)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at SAXParser.write (/volumio/node_modules/sax/lib/sax.js:1436:13)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Parser.exports.Parser.Parser.parseString (/volumio/node_modules/xml2js/lib/parser.js:322:31)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Parser.parseString (/volumio/node_modules/xml2js/lib/parser.js:5:59)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at /volumio/app/plugins/music_service/upnp_browser/index.js:625:24
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Request.handleRequestResponse [as _callback] (/volumio/node_modules/unirest/index.js:463:26)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at Request.self.callback (/volumio/node_modules/unirest/node_modules/request/request.js:187:22)
Nov 20 10:30:05 volumio-rpi2 volumio[808]: at emitTwo (events.js:126:13)

This error in the logs aren’t from the library scanning, but from the upnp browser
specifically:

var services = data.root.device[0].serviceList[0].service;
4

Thanks for your reply! It did scan other folders before it started to hang.

I have now built my library by adding one folder one at a time and executed an update of the library after that. I found out there was a certain folder which caused the scanning to hang. I was hoping that the error log could tell me with which folder it had problems with scanning.

Anyway, I left out the folder which caused the hanging of the scanning process and is the library is ok.

Thanks for the help.

Remco

5

Any chance you could post logs of while trying to scan that particular folder now that you have identified it? :slight_smile: