blacky89 Posted November 16, 2016 Share Posted November 16, 2016 Did you enable cnl to listen for outside connections? Man you do really know everything! Thank you so much! I did not uncheck that box in the advanced settings. Never looked deeper into the settings as it worked with my mac. No idea why it worked, as localhostonly is still checked there. Now that my windows machine is set up, I need to find a way to permanentely map 9666 to the unraidip from mac OS. But at least that I should be able to figure out myself. Thank you again sir ! Quote Link to comment
JoeMB Posted November 19, 2016 Share Posted November 19, 2016 I'm getting this error even after just doing a fresh install of Nginx-letsencrpt Upgrading certbot-auto 0.8.1 to 0.9.3... Couldn't download https://raw.githubusercontent.com/certbot/certbot/v0.9.3/letsencrypt-auto-source/letsencrypt-auto. <urlopen error [Errno 1] _ssl.c:510: error:140773E8:SSL routines:SSL23_GET_SERVER_HELLO:reason(1000)> /etc/my_init.d/firstrun.sh: line 138: cd: /config/keys: No such file or directory Error opening input file cert.pem cert.pem: No such file or directory * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 110 Nov 19 03:58:30 47089d200a78 syslog-ng[119]: syslog-ng starting up; version='3.5.3' Quote Link to comment
SigmaInigma Posted November 19, 2016 Share Posted November 19, 2016 I'm new to unRaid. Just set up my server last night. I installed the Plex Media Server through the built-in templates and it did everything for me and installed without an issue. I am not trying to install a file manager. I've tried using midnight commander but it's a little difficult for me to understand. I can't figure out how to move files. I want a GUI File manager where I can just drag and drop. I found a docker container called dolphin that I think will suit my needs. I installed the community applications plugin so I have a docker container store now. I found Dolphin but when I try to install it, it asks for things like network type, host ports, etc. I'm not sure what to set here. Plex didn't ask me for any of this. Could anyone give me some guidance? Quote Link to comment
Squid Posted November 19, 2016 Share Posted November 19, 2016 I'm new to unRaid. Just set up my server last night. I installed the Plex Media Server through the built-in templates and it did everything for me and installed without an issue. I am not trying to install a file manager. I've tried using midnight commander but it's a little difficult for me to understand. I can't figure out how to move files. I want a GUI File manager where I can just drag and drop. I found a docker container called dolphin that I think will suit my needs. I installed the community applications plugin so I have a docker container store now. I found Dolphin but when I try to install it, it asks for things like network type, host ports, etc. I'm not sure what to set here. Plex didn't ask me for any of this. Could anyone give me some guidance? General rule, with adding any app is that the only things you ever need to change are the host / container volume paths, and port(s) if there is a conflict. Specifically on Dolphin, everything in the template that appears is correct. The only thing you may need to change is the Host Port for it (entry is blank on the template). Set it to something like 8080. After the app is installed, wait a minute or two then go to the webUI, and you'll be in business (Navigate to ROOT, then /mnt). Quote Link to comment
SigmaInigma Posted November 19, 2016 Share Posted November 19, 2016 General rule, with adding any app is that the only things you ever need to change are the host / container volume paths, and port(s) if there is a conflict. Specifically on Dolphin, everything in the template that appears is correct. The only thing you may need to change is the Host Port for it (entry is blank on the template). Set it to something like 8080. After the app is installed, wait a minute or two then go to the webUI, and you'll be in business (Navigate to ROOT, then /mnt). Cool, got it installed and the Web UI is working. So what port numbers would I use for future applications I install? I can't reuse 8080 right? Does the port number not matter? Quote Link to comment
trurl Posted November 19, 2016 Share Posted November 19, 2016 The docker (application) port should not be changed because that is the port the application uses. You can map that to any unused host port. If you aren't sure what is unused, you can usually just pick something with 4 or 5 digits (to avoid stepping on any system ports) that your other dockers or plugins aren't using. Quote Link to comment
aptalca Posted November 19, 2016 Author Share Posted November 19, 2016 I'm getting this error even after just doing a fresh install of Nginx-letsencrpt Upgrading certbot-auto 0.8.1 to 0.9.3... Couldn't download https://raw.githubusercontent.com/certbot/certbot/v0.9.3/letsencrypt-auto-source/letsencrypt-auto. <urlopen error [Errno 1] _ssl.c:510: error:140773E8:SSL routines:SSL23_GET_SERVER_HELLO:reason(1000)> /etc/my_init.d/firstrun.sh: line 138: cd: /config/keys: No such file or directory Error opening input file cert.pem cert.pem: No such file or directory * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 110 Nov 19 03:58:30 47089d200a78 syslog-ng[119]: syslog-ng starting up; version='3.5.3' That's the official letsencrypt client script trying to update itself. Not something under my control. It may have been a temporary connection issue to github I'll look into it but likely not something on my end Quote Link to comment
Marv Posted November 21, 2016 Share Posted November 21, 2016 Hi, I just started using the JDownloader container and it seems to be working fine. Just one question: As I don't want JDownloader to download files to my cache drive I'm using the following mappings /config >> /mnt/user/appdata/jdownloader2 /config/Downloads >> /mnt/user/Downloads I didn't face any problems with this yet but I want to make sure that I can actually use two mappings for the config folder. Or is there a better way for moving the Downloads folder to my array? Quote Link to comment
aptalca Posted November 21, 2016 Author Share Posted November 21, 2016 Hi, I just started using the JDownloader container and it seems to be working fine. Just one question: As I don't want JDownloader to download files to my cache drive I'm using the following mappings /config >> /mnt/user/appdata/jdownloader2 /config/Downloads >> /mnt/user/Downloads I didn't face any problems with this yet but I want to make sure that I can actually use two mappings for the config folder. Or is there a better way for moving the Downloads folder to my array? Don't map the same folder twice. I have no idea how unraid or docker handles it. Just change the second mapping to /Downloads instead of /config/Downloads and you can select that as the download location in jd2 settings Quote Link to comment
Marv Posted November 21, 2016 Share Posted November 21, 2016 Ok thank you. Luckily everything worked out like this. Quote Link to comment
ken-ji Posted November 22, 2016 Share Posted November 22, 2016 Hi, I just started using the JDownloader container and it seems to be working fine. Just one question: As I don't want JDownloader to download files to my cache drive I'm using the following mappings /config >> /mnt/user/appdata/jdownloader2 /config/Downloads >> /mnt/user/Downloads I didn't face any problems with this yet but I want to make sure that I can actually use two mappings for the config folder. Or is there a better way for moving the Downloads folder to my array? Don't map the same folder twice. I have no idea how unraid or docker handles it. Just change the second mapping to /Downloads instead of /config/Downloads and you can select that as the download location in jd2 settings This works just fine. One point is that there will now be any empty Downloads dir under /mnt/usr/appdata/jdownloader2 Quote Link to comment
captain134 Posted November 22, 2016 Share Posted November 22, 2016 Hi Thanks for all your hard work with these dockers. I am having trouble with the PlexRequests docker that previously worked great. I have deleted the docker and image and tried re-installing but I get the same following error: Starting container on Tue Nov 22 13:29:36 MST 2016 Updating repository HEAD is now at bd6572d Version bump Already up-to-date. Selecting the desired branch Using the master branch Already on 'master' Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.14 accounts-password upgraded from 1.1.4 to 1.3.3 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.13.0 babel-runtime* upgraded from 0.1.4 to 1.0.1 base64 upgraded from 1.0.4 to 1.0.10 binary-heap upgraded from 1.0.4 to 1.0.10 blaze upgraded from 2.1.3 to 2.1.8 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.11 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.10 check upgraded from 1.1.0 to 1.2.4 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.6 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.7 ecmascript upgraded from 0.1.6 to 0.6.1 ecmascript-runtime upgraded from 0.2.6 to 0.3.15 ejson upgraded from 1.0.7 to 1.0.13 email upgraded from 1.0.8 to 1.1.18 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.10 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.10 id-map upgraded from 1.0.4 to 1.0.9 jquery upgraded from 1.11.4 to 1.11.10 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.12 logging upgraded from 1.0.8 to 1.1.16 meteor upgraded from 1.1.10 to 1.6.0 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.18 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.7 modules-runtime added, version 0.7.7 mongo upgraded from 1.1.3 to 1.1.14 mongo-id upgraded from 1.0.1 to 1.0.6 npm-bcrypt upgraded from 0.7.8_2 to 0.9.2 npm-mongo* upgraded from 1.4.39_1 to 2.2.11_2 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.9 promise upgraded from 0.5.1 to 0.8.8 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.6 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.11 reload upgraded from 1.1.4 to 1.1.11 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.12 service-configuration upgraded from 1.0.5 to 1.0.11 session upgraded from 1.1.1 to 1.1.7 sha upgraded from 1.0.4 to 1.0.9 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.10 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.1 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.10 url upgraded from 1.0.5 to 1.0.11 webapp upgraded from 1.2.3 to 1.3.12 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.2.3. Changes to your project's package version selections from updating package : alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.1 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.38 autoupdate upgraded from 1.2.8 to 1.2.11 blaze upgraded from 2.1.8 to 2.1.9 blaze-html-templates upgraded from 1.0.1 to 1.0.5 blaze-tools upgraded from 1.0.9 to 1.0.10 caching-compiler upgraded from 1.0.4 to 1.1.9 caching-html-compiler upgraded from 1.0.6 to 1.0.7 coffeescript upgraded from 1.0.11 to 1.0.17 dburles:collection-helpers upgraded from 1.0.4 to 1.1.0 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.8 ddp-server upgraded from 1.2.6 to 1.2.10 fastclick upgraded from 1.0.11 to 1.0.13 fortawesome:fontawesome upgraded from 4.4.0 to 4.7.0 fourseven:scss upgraded from 3.4.1 to 3.10.1 html-tools upgraded from 1.0.10 to 1.0.11 htmljs upgraded from 1.0.10 to 1.0.11 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.15 minifier-js upgraded from 1.1.13 to 1.2.15 minimongo upgraded from 1.0.18 to 1.0.19 mobile-status-bar upgraded from 1.0.12 to 1.0.13 momentjs:moment upgraded from 2.10.6 to 2.17.0 observe-sequence upgraded from 1.0.12 to 1.0.14 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.9 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.6 spacebars upgraded from 1.0.12 to 1.0.13 spacebars-compiler upgraded from 1.0.12 to 1.0.13 standard-minifier-css upgraded from 1.0.8 to 1.3.2 standard-minifier-js upgraded from 1.0.8 to 1.2.1 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.2.15 templating-compiler added, version 1.2.15 templating-runtime added, version 1.2.15 templating-tools upgraded from 1.0.4 to 1.0.5 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 ui upgraded from 1.0.11 to 1.0.12 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.12 is available) * blaze 2.1.9 (2.2.0 is available) * coffeescript 1.0.17 (1.11.1_4 is available) * ddp-client 1.2.9 (1.3.2 is available) * ddp-server 1.2.10 (1.3.12 is available) * launch-screen 1.0.12 (1.1.0 is available) * less 2.5.7 (2.7.8 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/ => Started MongoDB. [34mW20161122-13:30:27.524(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:27.550(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. I am wondering if anyone else has this issue. Also any help would be appreciated. Thanks in advance. Quote Link to comment
aptalca Posted November 23, 2016 Author Share Posted November 23, 2016 Hi Thanks for all your hard work with these dockers. I am having trouble with the PlexRequests docker that previously worked great. I have deleted the docker and image and tried re-installing but I get the same following error: Starting container on Tue Nov 22 13:29:36 MST 2016 Updating repository HEAD is now at bd6572d Version bump Already up-to-date. Selecting the desired branch Using the master branch Already on 'master' Your branch is up-to-date with 'origin/master'. Fixing permissions Updating meteor. . . may take a while if meteor servers are being slow. The web gui will not go up until update is completed and there will be another message about PlexRquests starting Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.14 accounts-password upgraded from 1.1.4 to 1.3.3 allow-deny added, version 1.0.5 autoupdate upgraded from 1.2.4 to 1.2.8 babel-compiler* upgraded from 5.8.24_1 to 6.13.0 babel-runtime* upgraded from 0.1.4 to 1.0.1 base64 upgraded from 1.0.4 to 1.0.10 binary-heap upgraded from 1.0.4 to 1.0.10 blaze upgraded from 2.1.3 to 2.1.8 blaze-tools upgraded from 1.0.4 to 1.0.9 boilerplate-generator upgraded from 1.0.4 to 1.0.11 caching-compiler upgraded from 1.0.0 to 1.0.4 caching-html-compiler upgraded from 1.0.2 to 1.0.6 callback-hook upgraded from 1.0.4 to 1.0.10 check upgraded from 1.1.0 to 1.2.4 ddp upgraded from 1.2.2 to 1.2.5 ddp-client upgraded from 1.2.1 to 1.2.5 ddp-common upgraded from 1.2.2 to 1.2.5 ddp-rate-limiter upgraded from 1.0.0 to 1.0.6 ddp-server upgraded from 1.2.2 to 1.2.6 deps upgraded from 1.0.9 to 1.0.12 diff-sequence upgraded from 1.0.1 to 1.0.7 ecmascript upgraded from 0.1.6 to 0.6.1 ecmascript-runtime upgraded from 0.2.6 to 0.3.15 ejson upgraded from 1.0.7 to 1.0.13 email upgraded from 1.0.8 to 1.1.18 fastclick upgraded from 1.0.7 to 1.0.11 geojson-utils upgraded from 1.0.4 to 1.0.10 hot-code-push upgraded from 1.0.0 to 1.0.4 html-tools upgraded from 1.0.5 to 1.0.10 htmljs upgraded from 1.0.5 to 1.0.10 http upgraded from 1.1.1 to 1.2.10 id-map upgraded from 1.0.4 to 1.0.9 jquery upgraded from 1.11.4 to 1.11.10 launch-screen upgraded from 1.0.4 to 1.0.11 livedata upgraded from 1.0.15 to 1.0.18 localstorage upgraded from 1.0.5 to 1.0.12 logging upgraded from 1.0.8 to 1.1.16 meteor upgraded from 1.1.10 to 1.6.0 meteor-base upgraded from 1.0.1 to 1.0.4 minifier-css added, version 1.1.13 minifier-js added, version 1.1.13 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.18 mobile-experience upgraded from 1.0.1 to 1.0.4 mobile-status-bar upgraded from 1.0.6 to 1.0.12 modules added, version 0.7.7 modules-runtime added, version 0.7.7 mongo upgraded from 1.1.3 to 1.1.14 mongo-id upgraded from 1.0.1 to 1.0.6 npm-bcrypt upgraded from 0.7.8_2 to 0.9.2 npm-mongo* upgraded from 1.4.39_1 to 2.2.11_2 observe-sequence upgraded from 1.0.7 to 1.0.12 ordered-dict upgraded from 1.0.4 to 1.0.9 promise upgraded from 0.5.1 to 0.8.8 random upgraded from 1.0.5 to 1.0.10 rate-limit upgraded from 1.0.0 to 1.0.6 reactive-dict upgraded from 1.1.3 to 1.1.8 reactive-var upgraded from 1.0.6 to 1.0.11 reload upgraded from 1.1.4 to 1.1.11 retry upgraded from 1.0.4 to 1.0.7 routepolicy upgraded from 1.0.6 to 1.0.12 service-configuration upgraded from 1.0.5 to 1.0.11 session upgraded from 1.1.1 to 1.1.7 sha upgraded from 1.0.4 to 1.0.9 spacebars upgraded from 1.0.7 to 1.0.12 spacebars-compiler upgraded from 1.0.7 to 1.0.12 srp upgraded from 1.0.4 to 1.0.10 standard-minifier-css added, version 1.0.8 standard-minifier-js added, version 1.0.8 standard-minifiers upgraded from 1.0.2 to 1.0.6 templating upgraded from 1.1.5 to 1.1.9 templating-tools upgraded from 1.0.0 to 1.0.4 tracker upgraded from 1.0.9 to 1.1.1 ui upgraded from 1.0.8 to 1.0.11 underscore upgraded from 1.0.4 to 1.0.10 url upgraded from 1.0.5 to 1.0.11 webapp upgraded from 1.2.3 to 1.3.12 webapp-hashing upgraded from 1.0.5 to 1.0.9 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.4.2.3. Changes to your project's package version selections from updating package : alanning:roles upgraded from 1.2.14 to 1.2.15 aldeed:autoform upgraded from 5.7.1 to 5.8.1 aldeed:collection2 upgraded from 2.5.0 to 2.10.0 aldeed:collection2-core added, version 1.2.0 aldeed:schema-deny added, version 1.1.0 aldeed:schema-index added, version 1.1.1 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.38 autoupdate upgraded from 1.2.8 to 1.2.11 blaze upgraded from 2.1.8 to 2.1.9 blaze-html-templates upgraded from 1.0.1 to 1.0.5 blaze-tools upgraded from 1.0.9 to 1.0.10 caching-compiler upgraded from 1.0.4 to 1.1.9 caching-html-compiler upgraded from 1.0.6 to 1.0.7 coffeescript upgraded from 1.0.11 to 1.0.17 dburles:collection-helpers upgraded from 1.0.4 to 1.1.0 ddp-client upgraded from 1.2.5 to 1.2.9 ddp-common upgraded from 1.2.5 to 1.2.8 ddp-server upgraded from 1.2.6 to 1.2.10 fastclick upgraded from 1.0.11 to 1.0.13 fortawesome:fontawesome upgraded from 4.4.0 to 4.7.0 fourseven:scss upgraded from 3.4.1 to 3.10.1 html-tools upgraded from 1.0.10 to 1.0.11 htmljs upgraded from 1.0.10 to 1.0.11 iron:router upgraded from 1.0.12 to 1.0.13 launch-screen upgraded from 1.0.11 to 1.0.12 less upgraded from 2.5.1 to 2.5.7 mdg:validation-error added, version 0.2.0 minifier-css upgraded from 1.1.13 to 1.2.15 minifier-js upgraded from 1.1.13 to 1.2.15 minimongo upgraded from 1.0.18 to 1.0.19 mobile-status-bar upgraded from 1.0.12 to 1.0.13 momentjs:moment upgraded from 2.10.6 to 2.17.0 observe-sequence upgraded from 1.0.12 to 1.0.14 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 retry upgraded from 1.0.7 to 1.0.9 shell-server added, version 0.2.1 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.3.6 spacebars upgraded from 1.0.12 to 1.0.13 spacebars-compiler upgraded from 1.0.12 to 1.0.13 standard-minifier-css upgraded from 1.0.8 to 1.3.2 standard-minifier-js upgraded from 1.0.8 to 1.2.1 standard-minifiers removed from your project templating upgraded from 1.1.9 to 1.2.15 templating-compiler added, version 1.2.15 templating-runtime added, version 1.2.15 templating-tools upgraded from 1.0.4 to 1.0.5 themeteorchef:bert upgraded from 2.1.0 to 2.1.1 ui upgraded from 1.0.11 to 1.0.12 useraccounts:bootstrap upgraded from 1.12.4 to 1.14.2 useraccounts:core upgraded from 1.12.4 to 1.14.2 The following top-level dependencies were not updated to the very latest version available: * ongoworks:security 1.3.0 (2.0.1 is available) * twbs:bootstrap 4.0.0-alpha (4.0.0-alpha2 is available) Newer versions of the following indirect dependencies are available: * autoupdate 1.2.11 (1.3.12 is available) * blaze 2.1.9 (2.2.0 is available) * coffeescript 1.0.17 (1.11.1_4 is available) * ddp-client 1.2.9 (1.3.2 is available) * ddp-server 1.2.10 (1.3.12 is available) * launch-screen 1.0.12 (1.1.0 is available) * less 2.5.7 (2.7.8 is available) * mdg:validation-error 0.2.0 (0.5.1 is available) To update one or more of these packages, pass their names to `meteor update`, or just run `meteor update --all-packages`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 115 Nov 22 13:30:11 c11fa061e596 syslog-ng[122]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/ => Started MongoDB. [34mW20161122-13:30:27.524(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:27.550(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:27.551(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:27.552(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:27.553(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.180(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.181(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.182(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.183(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 [34mW20161122-13:30:28.778(-7)? (STDERR) [39m[35m/config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:348[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m}).run();[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m ^[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mError: The babel-runtime npm package could not be found in your node_modules [39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35mdirectory. Please run the following command to install it:[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m meteor npm install --save babel-runtime[39m [34mW20161122-13:30:28.779(-7)? (STDERR) [39m[35m[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at meteorInstall.node_modules.meteor.babel-runtime.babel-runtime.js (packages/babel-runtime.js:37:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at fileEvaluate (packages/modules-runtime.js:181:9)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at require (packages/modules-runtime.js:106:16)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:139:15[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at packages/babel-runtime.js:150:3[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:295:34[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Array.forEach (native)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at Function._.each._.forEach (/home/.meteor/packages/meteor-tool/.1.4.2_3.17tso1e++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/underscore/underscore.js:79:11)[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:128:5[39m [34mW20161122-13:30:28.780(-7)? (STDERR) [39m[35m at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:344:5[39m => Exited with code: 1 => Your application is crashing. Waiting for file change. I am wondering if anyone else has this issue. Also any help would be appreciated. Thanks in advance. I encountered that error on a new install as well, but haven't figured out a fix yet. I am also now part of the linuxserver team and they have a plex requests container that works well. You might want to switch to that as I will most likely deprecate this container in favor of the linuxserver one soon. That one has a different config folder structure so I would recommend setting it up from scratch. Quote Link to comment
Vaseer Posted November 23, 2016 Share Posted November 23, 2016 Hi aptalca. I was using your PlexRequests docker and got similar error and when I saw your previous post, I switched over to linuxserver's PlexRequests. Linuxserver's PlexRequests is working fine, but I haven't figured out how can I import database from your to linuxserver's PlexRequests docker. I have made backup of your PlexRequests so I have database saved. Can you give me some advice, how can I import database or it's content? Thanks Quote Link to comment
aptalca Posted November 23, 2016 Author Share Posted November 23, 2016 Hi aptalca. I was using your PlexRequests docker and got similar error and when I saw your previous post, I switched over to linuxserver's PlexRequests. Linuxserver's PlexRequests is working fine, but I haven't figured out how can I import database from your to linuxserver's PlexRequests docker. I have made backup of your PlexRequests so I have database saved. Can you give me some advice, how can I import database or it's content? Thanks Not sure, but I'll check with the team Quote Link to comment
Vaseer Posted November 26, 2016 Share Posted November 26, 2016 Hi aptalca. I was using your PlexRequests docker and got similar error and when I saw your previous post, I switched over to linuxserver's PlexRequests. Linuxserver's PlexRequests is working fine, but I haven't figured out how can I import database from your to linuxserver's PlexRequests docker. I have made backup of your PlexRequests so I have database saved. Can you give me some advice, how can I import database or it's content? Thanks Not sure, but I'll check with the team Any news? Quote Link to comment
CHBMB Posted November 27, 2016 Share Posted November 27, 2016 Hi aptalca. I was using your PlexRequests docker and got similar error and when I saw your previous post, I switched over to linuxserver's PlexRequests. Linuxserver's PlexRequests is working fine, but I haven't figured out how can I import database from your to linuxserver's PlexRequests docker. I have made backup of your PlexRequests so I have database saved. Can you give me some advice, how can I import database or it's content? Thanks Not sure, but I'll check with the team Any news? You could try copying the files from: mnt/user/appdata/PlexRequests-aptalca/plexrequests-meteor/.meteor/local/db to /mnt/user/appdata/plexrequests/db If that doesn't work, you're probably out of luck. Quote Link to comment
Vaseer Posted November 28, 2016 Share Posted November 28, 2016 Hi aptalca. I was using your PlexRequests docker and got similar error and when I saw your previous post, I switched over to linuxserver's PlexRequests. Linuxserver's PlexRequests is working fine, but I haven't figured out how can I import database from your to linuxserver's PlexRequests docker. I have made backup of your PlexRequests so I have database saved. Can you give me some advice, how can I import database or it's content? Thanks Not sure, but I'll check with the team Any news? You could try copying the files from: mnt/user/appdata/PlexRequests-aptalca/plexrequests-meteor/.meteor/local/db to /mnt/user/appdata/plexrequests/db If that doesn't work, you're probably out of luck. Thanks for suggestion. I tried but it didn't work. If you have or get any more suggestions/information, please let me know. Quote Link to comment
dave Posted December 1, 2016 Share Posted December 1, 2016 Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant Quote Link to comment
aptalca Posted December 1, 2016 Author Share Posted December 1, 2016 Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant I believe it works, but you have to run it on port 80, and to do that, you have to move the unraid gui to a different port (instructions for that are on the forum that you should be able find easily) Quote Link to comment
dave Posted December 1, 2016 Share Posted December 1, 2016 Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant I believe it works, but you have to run it on port 80, and to do that, you have to move the unraid gui to a different port (instructions for that are on the forum that you should be able find easily) Yeah, I was reading on the Vera forum that Google Home requires it to be on port 80 to connect. Thanks for the tip - I plan to try it this weekend! Quote Link to comment
ijuarez Posted December 1, 2016 Share Posted December 1, 2016 Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant I believe it works, but you have to run it on port 80, and to do that, you have to move the unraid gui to a different port (instructions for that are on the forum that you should be able find easily) You would think that at this point and time in technology companies would stop using port 80 since most homes would already have something running on port 80, baffles me. Quote Link to comment
aptalca Posted December 1, 2016 Author Share Posted December 1, 2016 Has anyone tried the HA bridge container with Google Home yet? https://github.com/bwssytems/ha-bridge/blob/master/README.md#google-assistant I believe it works, but you have to run it on port 80, and to do that, you have to move the unraid gui to a different port (instructions for that are on the forum that you should be able find easily) You would think that at this point and time in technology companies would stop using port 80 since most homes would already have something running on port 80, baffles me. The reason is that this bridge emulates a hue bridge. And the hue bridge (physical device) listens on port 80. From Google's perspective, there is nothing wrong with hardcoding the hue communication port because it is always 80. It is a problem for other software that pretend to be a hue bridge Quote Link to comment
JoeMB Posted December 9, 2016 Share Posted December 9, 2016 I'm getting this error even after just doing a fresh install of Nginx-letsencrpt Upgrading certbot-auto 0.8.1 to 0.9.3... Couldn't download https://raw.githubusercontent.com/certbot/certbot/v0.9.3/letsencrypt-auto-source/letsencrypt-auto. <urlopen error [Errno 1] _ssl.c:510: error:140773E8:SSL routines:SSL23_GET_SERVER_HELLO:reason(1000)> /etc/my_init.d/firstrun.sh: line 138: cd: /config/keys: No such file or directory Error opening input file cert.pem cert.pem: No such file or directory * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 110 Nov 19 03:58:30 47089d200a78 syslog-ng[119]: syslog-ng starting up; version='3.5.3' That's the official letsencrypt client script trying to update itself. Not something under my control. It may have been a temporary connection issue to github I'll look into it but likely not something on my end Ok for some reason that container time is wrong by 8 hours so maybe that would cause an issue? Quote Link to comment
aptalca Posted December 10, 2016 Author Share Posted December 10, 2016 I'm getting this error even after just doing a fresh install of Nginx-letsencrpt Upgrading certbot-auto 0.8.1 to 0.9.3... Couldn't download https://raw.githubusercontent.com/certbot/certbot/v0.9.3/letsencrypt-auto-source/letsencrypt-auto. <urlopen error [Errno 1] _ssl.c:510: error:140773E8:SSL routines:SSL23_GET_SERVER_HELLO:reason(1000)> /etc/my_init.d/firstrun.sh: line 138: cd: /config/keys: No such file or directory Error opening input file cert.pem cert.pem: No such file or directory * Starting nginx nginx ...fail! * Starting authentication failure monitor fail2ban ERROR No file(s) found for glob /config/log/nginx/error.log ERROR Failed during configuration: Have not found any log file for nginx-http-auth jail ...fail! *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 110 Nov 19 03:58:30 47089d200a78 syslog-ng[119]: syslog-ng starting up; version='3.5.3' That's the official letsencrypt client script trying to update itself. Not something under my control. It may have been a temporary connection issue to github I'll look into it but likely not something on my end Ok for some reason that container time is wrong by 8 hours so maybe that would cause an issue? Is your timezone set correctly in unraid? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.