When I build mediasoup environment, come into dir "server". I use the command node server.js which results in the following error:
mediasoup:ERROR:Worker worker process failed [pid:undefined]: spawn /root/mediasoup-demo/server/node_modules/mediasoup/worker/out/Release/mediasoup-worker ENOENT
screenshot of the error
make sure you have all the requirements for the installation process https://mediasoup.org/documentation/v3/mediasoup/installation/
Related
Has anyone seen this error that has just started happening on my linux box? npm run serve and npm run build both run fine on my Windows machine as usual, but, as of yesterday, I get the following error on the linux box.
The code is the same (pulled from the git repo) and npm install is run before npm run serve or npm run build
Any ideas how I can track this down?...
root#agilesimulations:/usr/apps/socket-test# npm run serve
> socket-test#0.1.0 serve
> vue-cli-service serve --port 8098
INFO Starting development server...
98% after emitting CopyPlugin
ERROR Failed to compile with 1 error 3:38:16 PM
error in ./src/main.js
Syntax Error: Error: Cannot find module '#eslint/eslintrc'
# multi (webpack)-dev-server/client?http://localhost:8098&sockPath=/sockjs-node (webpack)/hot/dev-server.js ./src/main.js
I am currently working on HyperLedger composer v1.1 on Ubuntu Virtual Machine (16.04 LTS) hosted in remote server and using VMWare Vsphere client to connect to that host machine. My PC (Windows 7) and the hosting server are in the same LAN.
In fact, I am following the tutorial (https://hyperledger.github.io/composer/latest/tutorials/developer-tutorial).
I managed to install the chaincode onto the network but when I tried to start the business network using the command :
composer network start --networkName tutorial-network --networkVersion 0.0.1 --networkAdmin admin --networkAdminEnrollSecret adminpw --card PeerAdmin#hlfv1 --file networkadmin.card
I got this error :
✖ Starting business network definition. This may take a minute...
Error: Error trying to start business network. Error: No valid responses from any peers.
Response from attempted peer comms was an error: Error: 2 UNKNOWN: error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/composer-runtime-hlfv1 failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443 ...."
Then, when I saw the suggestion of #PaulO'Mahony at "hyperledger-composer v1.1:unable to instantiate chaincode"
I tried to locate the npmrc file but it was not there then I did as #oligofren suggested at Node .npmrc file.
After that, I have executed this command :
composer network install --c PeerAdmin#hlfv1 --a tutorial-network#0.0.1.bna -o npmrcFile=/home/user1/.npmrc"
where ".npmrc" file is generated after I have logged in (using npm login).
Finally, when try to execute the above command "composer network start...." the same error is still exist !!!
Note that : I have executed "./stopFabric.sh", "./teardownFabric.sh" and then "./startFabric.sh" before I did each solution!
I am having difficulty with npm run serve for a tutorial I'm doing through Udacity. For some reason, the npm task manager keeps breaking when trying to run the BABEL and Browserify tasks and will not complete serving on any port. Would love to get this resolved.
I am getting the following error when I run the grunt command after generating the app using Yeoman generator:
Loading "grunt-karma.js" tasks...ERROR
>> TypeError: Cannot read property 'prototype' of undefined
>> Local Npm module "grunt-node-inspector" not found. Is it installed?
Running "env:dev" (env) task
Running "sass:dist" (sass) task
Running "less:dist" (less) task
Running "jshint:all" (jshint) task
>> 86 files lint free.
Running "csslint:all" (csslint) task
>> 2 files lint free.
Running "mkdir:upload" task
Running "copy:localConfig" (copy) task
Copied 1 file
Running "concurrent:default" (concurrent) task
Loading "grunt-karma.js" tasks...ERROR
>> TypeError: Cannot read property 'prototype' of undefined
Loading "grunt-karma.js" tasks...ERROR
>> TypeError: Cannot read property 'prototype' of undefined
>> Local Npm module "grunt-node-inspector" not found. Is it installed?
>> Local Npm module "grunt-node-inspector" not found. Is it installed?
Running "nodemon:dev" (nodemon) task
Running "watch" task
Waiting...
[nodemon] 1.11.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: server.js config/**/*.js
modules/*/server/**/*.js
[nodemon] starting `node --debug server.js`
(node:16253) [DEP0062] DeprecationWarning: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead.
[nodemon] app crashed - waiting for file changes before starting...
I found a similar question(Yeoman grunt could not connect to MongoDB) but I was not able to find the solution to my problem there.
Is that an old version of MEAN.js? I believe grunt was replaced by gulp and also an issue regarding node-inspector was fixed by this pull request.
You should check which version you're using and make the necessary changes.
I am trying to integrate our build server with our angular build. Locally the build work perfectly but when I try and run the build on the build server I am getting the following error:
RunGulp:
Running gulp task dev
gulp
[08:35:38] Using gulpfile C:\Builds\10639\TCC.NET\1.Development CI\src\TCC.W
eb.Client\gulpfile.js
[08:35:38] Starting 'default'...
[08:35:38] Starting 'build'...
[08:35:38] Starting 'js'...
stream.js:74
throw er; // Unhandled stream error in pipe.
^
EXEC : error: EPERM: operation not permitted, open 'C:\Builds\10639\TCC.NET\1.
Development CI\src\TCC.Web.Client\public\app.module.js' [C:\Builds\10639\TCC.N
ET\1.Development CI\src\TCC.Web.Client\TCC.Web.Client.csproj]
at Error(native)
C:\Builds\10639\TCC.NET\1.Development CI\src\TCC.Web.Client\TCC.Web.Client.wpp
.targets(14, 5): error MSB3073: The command "gulp" exited with code 1. [C:\Build
s\10639\TCC.NET\1.Development CI\src\TCC.Web.Client\TCC.Web.Client.csproj]
I've looked at some various posts on the error and they mostly revolve around permissions issues but the public folder and the app.module.js files have the correct permissions.
I am not at all familiar with gulp so looking for some other ideas on things to check.
My issue turned out to be the readonly flag on the files being built.
Found a solution here