dotenv-flow: "BOTIUM_SPEECH_PROVIDER_TTS" is already defined in process.env and will not be overwritten
dotenv-flow: "BOTIUM_SPEECH_PROVIDER_STT" is already defined in process.env and will not be overwritten
/app/node_modules/mkdirp/lib/mkdirp-native.js:35
throw er
^
Error: EACCES: permission denied, mkdir '/app/resources/.cache/stt'
at Object.mkdirSync (fs.js:1014:3)
at mkdirpNativeSync (/app/node_modules/mkdirp/lib/mkdirp-native.js:29:10)
at Function.mkdirpSync [as sync] (/app/node_modules/mkdirp/index.js:21:7)
at Object. (/app/src/routes.js:31:26)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18) {
errno: -13,
syscall: 'mkdir',
code: 'EACCES',
path: '/app/resources/.cache/stt'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! botium-speech-processing-frontend@1.0.0 start-dist: node -r dotenv-flow/config ./src/server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the botium-speech-processing-frontend@1.0.0 start-dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/node/.npm/_logs/2024-02-06T16_35_40_834Z-debug.log
and nginx 502 Bad Gateway
so i guess if you can fix the issus frontend always restart so everything will be better.
Describe the bug CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0bd4cc8c1b2d botium/botium-speech-kaldi-en:latest "/usr/bin/supervisor…" 22 minutes ago Up 21 minutes 56180/tcp botiumspeechprocessing_stt-en_1 c1b3c5309212 botium/botium-speech-watcher:latest "/usr/bin/supervisor…" 22 minutes ago Up 21 minutes botiumspeechprocessing_watcher_1 eea24e613233 botium/botium-speech-kaldi-de:latest "/usr/bin/supervisor…" 22 minutes ago Up 21 minutes 56180/tcp botiumspeechprocessing_stt-de_1 794598aa6dd7 nginx "/docker-entrypoint.…" 22 minutes ago Up 21 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp botiumspeechprocessing_nginx_1 cd8a36723aa8 botium/botium-speech-dictate:latest "docker-entrypoint.s…" 22 minutes ago Up 21 minutes 56100/tcp botiumspeechprocessing_dictate_1 06df15d556b7 botium/botium-speech-frontend:latest "/bin/sh -c 'npm run…" 22 minutes ago Restarting (1) 32 seconds ago botiumspeechprocessing_frontend_1 1b5e2047d9f6 botium/botium-speech-marytts:latest "/bin/sh -c ./marytts" 22 minutes ago Up 21 minutes 59125/tcp botiumspeechprocessing_tts_1
docker logs botiumspeechprocessing_frontend_1
dotenv-flow: "BOTIUM_SPEECH_PROVIDER_TTS" is already defined in
process.envand will not be overwritten dotenv-flow: "BOTIUM_SPEECH_PROVIDER_STT" is already defined inprocess.envand will not be overwritten /app/node_modules/mkdirp/lib/mkdirp-native.js:35 throw er ^Error: EACCES: permission denied, mkdir '/app/resources/.cache/stt' at Object.mkdirSync (fs.js:1014:3) at mkdirpNativeSync (/app/node_modules/mkdirp/lib/mkdirp-native.js:29:10) at Function.mkdirpSync [as sync] (/app/node_modules/mkdirp/index.js:21:7) at Object. (/app/src/routes.js:31:26)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18) {
errno: -13,
syscall: 'mkdir',
code: 'EACCES',
path: '/app/resources/.cache/stt'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! botium-speech-processing-frontend@1.0.0 start-dist:
node -r dotenv-flow/config ./src/server.jsnpm ERR! Exit status 1 npm ERR! npm ERR! Failed at the botium-speech-processing-frontend@1.0.0 start-dist script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/node/.npm/_logs/2024-02-06T16_35_40_834Z-debug.log
and nginx 502 Bad Gateway so i guess if you can fix the issus frontend always restart so everything will be better.