Server fails moments after starting.
See original GitHub issuedocker run -d -p 2700:2700 alphacep/kaldi-en:latest
When I run this docker container it fails moments after starting…docker logs produces:
docker logs d1d2f2742e8a4a52f3937aff26b2c7628829e313cede5ad60cb4424c897a53c3
LOG ([5.5.643~1-7e185]:ConfigureV2():src/model.cc:138) Decoding params beam=13 max-active=7000 lattice-beam=6
LOG ([5.5.643~1-7e185]:ConfigureV2():src/model.cc:141) Silence phones 1:2:3:4:5:6:7:8:9:10:11:12:13:14:15
LOG ([5.5.643~1-7e185]:ComputeDerivedVars():ivector-extractor.cc:183) Computing derived variables for iVector extractor
LOG ([5.5.643~1-7e185]:ComputeDerivedVars():ivector-extractor.cc:204) Done.
LOG ([5.5.643~1-7e185]:RemoveOrphanNodes():nnet-nnet.cc:948) Removed 1 orphan nodes.
LOG ([5.5.643~1-7e185]:RemoveOrphanComponents():nnet-nnet.cc:847) Removing 2 orphan components.
LOG ([5.5.643~1-7e185]:Collapse():nnet-utils.cc:1472) Added 1 components, removed 2
LOG ([5.5.643~1-7e185]:CompileLooped():nnet-compile-looped.cc:345) Spent 0.00747085 seconds in looped compilation.
LOG ([5.5.643~1-7e185]:ReadDataFiles():src/model.cc:190) Loading HCLG from /opt/vosk-model-en/model/graph/HCLG.fst
LOG ([5.5.643~1-7e185]:ReadDataFiles():src/model.cc:209) Loading words from /opt/vosk-model-en/model/graph/words.txt
LOG ([5.5.643~1-7e185]:ReadDataFiles():src/model.cc:217) Loading winfo /opt/vosk-model-en/model/graph/phones/word_boundary.int
LOG ([5.5.643~1-7e185]:ReadDataFiles():src/model.cc:225) Loading CARPA model from /opt/vosk-model-en/model/rescore/G.carpa
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Solved - Server crashes the moment after starting. | SpigotMC
Solved Server crashes the moment after starting.
Read more >Server Fail: Three Signs Your Server Is on the Brink
Another thing to note regarding fans and server temperature is that when an overheated server first starts up or reboots, the fans will...
Read more >3 signs your server is about to fail - Spiceworks
Server FAIL: 3 signs your server is on the brink · 1) Temperature troubles: CPU running hot · 2) Constant reboots or random...
Read more >Advanced troubleshooting for Windows boot problems
Learn to troubleshoot when Windows can't boot. This article includes advanced troubleshooting techniques intended for use by support agents ...
Read more >How to Fix a 500 Internal Server Error on Your WordPress Site
The 500 Internal Server Error status code occurs when the server encounters an error that prevents it from fulfilling the request.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Most likely it goes out of memory. Do you have memory limitation in your docker? It should be something like 4Gb or better 8Gb for this server to run.
Same as #77