captain134
-
Posts
53 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by captain134
-
-
12 hours ago, ijuarez said:
I posted about this and never got an answer even included a screenshot so I gave up.
Haven’t tried a TDarr yet cause I think it’s too much work but I will have to move on.
Sent from my iPhone using TapatalkYour question was answered 6 posts below your original post.
-
5 hours ago, JPDom1 said:
I have updated to the latest version and just 2 things to report.
1. I do my conversions folder by folder at the moment (/Mnt/usr/series/Show to convert) and then "edit" the container to the next show when it is done (/Mnt/usr/series/Show to convert). Each time the container starts up it goes back to the default settings it is not persistent.
2. When changing something in the settings and then clicking "Submit" my browser goes to http://192.168.0.4:8899/settings/?step=general with the page below. I then manually need to remove the "/?step=general" to get back to the settings GUI
Apart from that my poor Threadripper has been crying for a week while my disk free disk space keeps going up 🙂
I am experiencing the same thing with settings.
-
19 minutes ago, captain134 said:
I have run into an issue. Any help would be greatly appreciated. I had to give Plex docker its own IP for another project which works great but has broken Plexpy. I added the new IP of plex in the plexpy settings and if I click verify I get a check mark but plexpy can't actually communicate with plex and I get the "There was an error communicating with your Plex Server."
I have figured it out. Had to enable SSL. Thanks
-
I have run into an issue. Any help would be greatly appreciated. I had to give Plex docker its own IP for another project which works great but has broken Plexpy. I added the new IP of plex in the plexpy settings and if I click verify I get a check mark but plexpy can't actually communicate with plex and I get the "There was an error communicating with your Plex Server."
-
-
21 hours ago, spants said:
Yep diginc docker update is broken :-( https://github.com/diginc/docker-pi-hole/issues/208
Change the repository to diginc/pi-hole:debian_v3.1.4 for a temporary fix until the request above is fixed.
Thank you!
-
5 hours ago, bmdegraaf said:
I am getting the following error message:
[✗] DNS resolution is currently unavailable
As a result, the block lists will not update... Can someone point me in the right direction?I just installed for the first time and can confirm the same.
-
-
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.
-
Thanks for the update.
RC4 still has this issue: https://lime-technology.com/forum/index.php?topic=52857.0 . This does not happen in 6.2.
-
So I ended up giving up on my hd 7770 and just ordered a Radeon RX 460. From what I have read, it apears to be as close to Out-of-Box supported as it gets (Seems to have an issue where the screen stays black until the login screen, but I can live with that).
Tip: As an aside, for anyone annoyed with the laggy mouse performance while installing OSX, I discovered that the Libvirt Hotplug USB plugin allows me to attach a mouse and keyboard to the VM during installation, and mouse lag in VNC was completely gone...
That's good I hope you have better luck with that GPU.
What a good idea to attach a mouse before installation! I have never thought of doing that I just fought my way through the vnc mouse installation trying to convince myself its kinda fun!
Has anyone tried passing bluetooth and using a bluetooth mouse and keyboard? My Server is in another room within bluetooth range. Was thinking of doing HDMI over CAT6 to desk but i don't have a way to get keyboard and mouse over there.
I have passed through both my internal bluetooth and a bluetooth dongle and they work as expected in Sierra with a Apple Magic Trackpad.
-
Thanks for the update.
Still having this https://lime-technology.com/forum/index.php?topic=52857.0 issue. Which I believe started with the 6.3.0 RCx releases.
-
This issue is still happening in 6.3.0 RC2
-
I am having this issue:
https://lime-technology.com/forum/index.php?topic=52857.0
However I am not sure that it is a 6.3.0 issue specifically.
-
Thank you very much for this release. Updated without issue and I've found SMB transfers to VM have improved greatly. Keep up the good work.
-
The 6.2 beta versions of unraid solves the Hyper V with nvidia gpu issue. You can now enable it. FYI
[Support] Josh5 - Unmanic - Library Optimiser
in Docker Containers
Posted
This is incorrect. You can use a gpu with multiple dockers(I use it with plex and unmanic) fine. You shouldn't share it if it is passed through to a VM though.