Installation according to readme fails on armv6 (node-gyp) about stretto HOT 25 CLOSED

Okay a few things so we can get to the bottom of this...

Can you give me the full install log? From when you run npm install until when it gives you the prompt back again? I can't gather much information from that one line.

Also the fact you are running an ARM processor could be causing the issue, perhaps google the error along with "armv6" or something and see what comes up?

from stretto.

Another idea is to run sudo npm install -g node-gyp and then do an npm install and see if it works.

from stretto.

Ok. Tried to install node-gyp globally and it does install, after which nothing changes, however.

From log:

50209 info linkStuff [email protected]
50210 verbose linkBins [email protected]
50211 verbose linkMans [email protected]
50212 verbose rebuildBundles [email protected]
50213 info install [email protected]
50214 info postinstall [email protected]
50215 verbose unlock done using /root/.npm/_locks/nan-55cf406a9e9165b0.lock for /root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/node_modules/nan
50216 verbose about to build /root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
50217 info build /root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
50218 verbose linkStuff [ false,
50218 verbose linkStuff false,
50218 verbose linkStuff false,
50218 verbose linkStuff '/root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules' ]
50219 info linkStuff [email protected]
50220 verbose linkBins [email protected]
50221 verbose link bins [ { wscat: './bin/wscat' },
50221 verbose link bins '/root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules/.bin',
50221 verbose link bins false ]
50222 verbose linkMans [email protected]
50223 verbose rebuildBundles [email protected]
50224 verbose rebuildBundles [ 'commander', 'nan', 'options', 'tinycolor' ]
50225 verbose gentlyRm vacuuming /root/node-music-player/node_modules/express.io/node_modules/socket.io/node_modules/socket.io-client/node_modules/.bin/wscat
50226 info install [email protected]
50227 verbose unsafe-perm in lifecycle false
50228 verbose stack Error: spawn ENOMEM
50228 verbose stack at exports.errnoException (util.js:746:11)
50228 verbose stack at ChildProcess.spawn (child_process.js:1155:11)
50228 verbose stack at exports.spawn (child_process.js:988:9)
50228 verbose stack at spawn (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:7:13)
50228 verbose stack at runCmd (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:207:14)
50228 verbose stack at /usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:175:7
50228 verbose stack at process._tickCallback (node.js:355:11)
50229 verbose cwd /root/node-music-player
50230 error Linux 3.12.28+
50231 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
50232 error node v0.12.0
50233 error npm v2.5.1
50234 error code ENOMEM
50235 error errno ENOMEM
50236 error syscall spawn
50237 error spawn ENOMEM
50238 error If you need help, you may report this error at:
50238 error http://github.com/npm/npm/issues
50239 verbose exit [ 1, true ]

from stretto.

Judging by the error:

50228 verbose stack Error: spawn ENOMEM

I would recommend you follow the suggestions from this

Is the device a device with low memory? It could be running out of memory... Do you have swap configured correctly?

from stretto.

aah... yes. that could very well be it. thanks for your help. i going to look into this and report back

from stretto.

No worries. let me know how you go and we can close this issue if it's simply a low memory issue 👍

from stretto.

I forgot that the embedded linux system that I was using came with a OS that has no swap. Enableing swap surpased this issue, but no changes, that is the page looks exactly the same when loaded in a browser.

from stretto.

Where did your log go?

Anyway it was in the github notification email... It looks like you tried to run npm install from /root. When the music player is actually clones to /root/node-music-player/. Every time you hit an error and reply can you plese give me a full log, and properly code embed it with github markdown?

from stretto.

Sorry I posted a log that I realized was not the correct one, and the deleted it. I once tried to reinstall when I was in the incorrect folder by accident. It didn't go very far...

from stretto.

but there is no other log file. I wonder if it only makes a log when something fails?

from stretto.

Yeah not a lot file, I'm just talking the output when you run npm install. There is only a npm-debug.log file output if it fails. So yeah just show me the output of running npm install. If that goes through successfully you can run node app.js and it should run just fine.

from stretto.

I don't have an output write now, but I can describe it - or maybe reproduce it for you later. A clean install outputs the lines in post 1 of this thread:

[email protected] install /root/node-music-player/node_modules/express.io/node_module/socket.io             
/node_modules/socket.io-client/node_modules/ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

and then a a tree stucture of the modules. Running the app with the command you give above starts the program and it states that it is listening at 2000.

connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0 
Express server listening on port 2000

Accessing the page with a browser works, but the page is unusable. Lookig at the source in the browser looks, it looks ok, but the way it is displayed is not correct. Tried on mobile, MacBook, Old laptop running Debian testing.

from stretto.

Did you run grunt after npm install?

from stretto.

yes

from stretto.

Can you give some screenshots?

from stretto.

Looks like no javascript:

from stretto.

That's what it looks like when grunt hasn't run, make sure you have grunt globally installed with sudo npm install -g grunt, then run grunt and then restart/start the server with node app.js

from stretto.

You know what? I thought that grunt was installed with grunt-cli and because running grunt caused the machine to do "stuff" and not give an error, I was sure that it was installed. However, it was not, and now that it is the page looks quite different. I'm sorry that I wasted your time like this, and thanks for helping nevertheless.

from stretto.

No worries. Glad I could help. Be sure to let me know how your experience with node-music-player goes! 👍

from stretto.

Yes, the thing is, I don't know where to do that. You don't seem to have a support forum or something like that .

from stretto.

just adding on to the issue or creating another issue for it. Or on gitter

from stretto.

Thanks, I installed this on PiMusicBox (http://www.woutervanwijk.nl/pimusicbox/)(https://github.com/woutervanwijk/Pi-MusicBox). This is a mopidy (https://www.mopidy.com/) server on raspbian (a third party debian port) running on Raspberry pi. This is also why the swap is off by default (the RPi uses an sd-card as a drive and it is not good in the long run to write on it, as it has a limited amount of read/write operations that can be performed on it). Something like your sofware should come by default with pimusicbox imo. It does share music by default with Samba, but for some situations that is not enough.

I don't have the technical competence to understand as much but it might be that there could have been some easier way to install node music player on this operating system, since it apparently uses some kind of application off node. Here I am using an older version of Raspbery pi that comes with a single core 800 mhz processor and the only problem with that is perhaps that scanning the library is a bit slow i you have lots of music. But with newer versions of RPi with more RAM and the quad-core ARM Cortex-A7 maybe would not have any problem? Unless this is I/O-limited (probably is to some extent). Other than that it workd really well!

from stretto.

I guess pi-musicbox is their own thing and the different online services are just ones they integrate with (BTW their ui looks really nice). And yeah I just guess node music player might be a bit too heavyweight for a pi, I've tried it on one of my first gen ones before and yeah its real slow.

But yeah I'm glad you managed to get it working! :)

from stretto.

I tried it to see how it would work and what the UI is like. I am going to install it again on the newer version of PI, and if you want I can report to you if it is any quicker/better.

from stretto.

Yeah sounds good. Cheers! :)

from stretto.