You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting error on restart server and not able to get live access, Using Mac OS, Please refer below logs
node-stream % npm run start
[email protected] start /Users/a10660927/Desktop/rupak/node-stream
supervisor -w server ./server/app.js
Running node-supervisor with
program './server/app.js'
--watch 'server'
--extensions 'node,js'
--exec 'node'
Starting child process with 'node ./server/app.js'
Watching directory '/Users/a10660927/Desktop/rupak/node-stream/server' for changes.
Press rs for restarting the process.
7/26/2022 23:50:14 32528 [INFO] Node Media Server v2.4.4
App listening on 3333!
7/26/2022 23:50:14 32528 [INFO] Node Media Rtmp Server started on port: 1935
7/26/2022 23:50:14 32528 [INFO] Node Media Http Server started on port: 8888
7/26/2022 23:50:14 32528 [INFO] Node Media WebSocket Server started on port: 8888
(node:32528) UnhandledPromiseRejectionWarning: Error: spawn /usr/local/bin/ffmpeg EACCES
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
at onErrorNT (internal/child_process.js:472:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use node --trace-warnings ... to show where the warning was created)
(node:32528) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:32528) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
7/26/2022 23:57:13 32528 [INFO] [rtmp disconnect] id=TH93H1SK
7/26/2022 23:57:13 32528 [INFO] [rtmp disconnect] id=HZYBV3AB
7/26/2022 23:57:44 32528 [INFO] [rtmp disconnect] id=M58CLYT7
7/26/2022 23:57:44 32528 [INFO] [rtmp disconnect] id=48SK84KD
7/26/2022 23:58:19 32528 [INFO] [rtmp disconnect] id=0VAY3VVP
7/26/2022 23:58:19 32528 [INFO] [rtmp disconnect] id=8QJUITVY
7/26/2022 23:59:19 32528 [INFO] [rtmp disconnect] id=WBJ4ONHD
7/26/2022 23:59:19 32528 [INFO] [rtmp disconnect] id=Q1I8AW9F
7/27/2022 24:00:49 32528 [INFO] [rtmp disconnect] id=IL83IFZM
7/27/2022 24:00:49 32528 [INFO] [rtmp disconnect] id=E0G7NNQ9
^CReceived SIGINT, killing child process...
Parent process exiting, terminating child...
The text was updated successfully, but these errors were encountered:
Getting error on restart server and not able to get live access, Using Mac OS, Please refer below logs
node-stream % npm run start
Running node-supervisor with
program './server/app.js'
--watch 'server'
--extensions 'node,js'
--exec 'node'
Starting child process with 'node ./server/app.js'
Watching directory '/Users/a10660927/Desktop/rupak/node-stream/server' for changes.
Press rs for restarting the process.
7/26/2022 23:50:14 32528 [INFO] Node Media Server v2.4.4
App listening on 3333!
7/26/2022 23:50:14 32528 [INFO] Node Media Rtmp Server started on port: 1935
7/26/2022 23:50:14 32528 [INFO] Node Media Http Server started on port: 8888
7/26/2022 23:50:14 32528 [INFO] Node Media WebSocket Server started on port: 8888
(node:32528) UnhandledPromiseRejectionWarning: Error: spawn /usr/local/bin/ffmpeg EACCES
at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
at onErrorNT (internal/child_process.js:472:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use
node --trace-warnings ...
to show where the warning was created)(node:32528) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag
--unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)(node:32528) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
7/26/2022 23:57:13 32528 [INFO] [rtmp disconnect] id=TH93H1SK
7/26/2022 23:57:13 32528 [INFO] [rtmp disconnect] id=HZYBV3AB
7/26/2022 23:57:44 32528 [INFO] [rtmp disconnect] id=M58CLYT7
7/26/2022 23:57:44 32528 [INFO] [rtmp disconnect] id=48SK84KD
7/26/2022 23:58:19 32528 [INFO] [rtmp disconnect] id=0VAY3VVP
7/26/2022 23:58:19 32528 [INFO] [rtmp disconnect] id=8QJUITVY
7/26/2022 23:59:19 32528 [INFO] [rtmp disconnect] id=WBJ4ONHD
7/26/2022 23:59:19 32528 [INFO] [rtmp disconnect] id=Q1I8AW9F
7/27/2022 24:00:49 32528 [INFO] [rtmp disconnect] id=IL83IFZM
7/27/2022 24:00:49 32528 [INFO] [rtmp disconnect] id=E0G7NNQ9
^CReceived SIGINT, killing child process...
Parent process exiting, terminating child...
The text was updated successfully, but these errors were encountered: