aptalca Posted April 9, 2016 Author Share Posted April 9, 2016 I did a fresh install of PlexRequests yesterday, but it doesn't appear to be working. The Docker starts, but I'm never able to connect to the Web UI (http://towerip:3000). Any thoughts? Here's the log <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 15:12:10 EDT 2016 First install detected, cloning repository Selecting the desired branch Using the master branch 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 npm-container: updating npm dependencies -- winston... Changes to your project's package version selections from updating the release: accounts-base upgraded from 1.2.2 to 1.2.5 accounts-password upgraded from 1.1.4 to 1.1.7 allow-deny added, version 1.0.3 autoupdate upgraded from 1.2.4 to 1.2.7 babel-compiler* upgraded from 5.8.24_1 to 6.6.1 babel-runtime upgraded from 0.1.4 to 0.1.7 base64 upgraded from 1.0.4 to 1.0.7 binary-heap upgraded from 1.0.4 to 1.0.7 blaze upgraded from 2.1.3 to 2.1.6 blaze-html-templates upgraded from 1.0.1 to 1.0.3 blaze-tools upgraded from 1.0.4 to 1.0.7 boilerplate-generator upgraded from 1.0.4 to 1.0.7 caching-compiler upgraded from 1.0.0 to 1.0.3 caching-html-compiler upgraded from 1.0.2 to 1.0.5 callback-hook upgraded from 1.0.4 to 1.0.7 check upgraded from 1.1.0 to 1.1.3 coffeescript upgraded from 1.0.11 to 1.0.16 ddp upgraded from 1.2.2 to 1.2.4 ddp-client upgraded from 1.2.1 to 1.2.4 ddp-common upgraded from 1.2.2 to 1.2.4 ddp-rate-limiter upgraded from 1.0.0 to 1.0.3 ddp-server upgraded from 1.2.2 to 1.2.5 deps upgraded from 1.0.9 to 1.0.11 diff-sequence upgraded from 1.0.1 to 1.0.4 ecmascript upgraded from 0.1.6 to 0.4.2 ecmascript-runtime upgraded from 0.2.6 to 0.2.9 ejson upgraded from 1.0.7 to 1.0.10 email upgraded from 1.0.8 to 1.0.11 fastclick upgraded from 1.0.7 to 1.0.10 geojson-utils upgraded from 1.0.4 to 1.0.7 hot-code-push upgraded from 1.0.0 to 1.0.3 html-tools upgraded from 1.0.5 to 1.0.8 htmljs upgraded from 1.0.5 to 1.0.8 http upgraded from 1.1.1 to 1.1.4 id-map upgraded from 1.0.4 to 1.0.6 jquery upgraded from 1.11.4 to 1.11.7 launch-screen upgraded from 1.0.4 to 1.0.10 less upgraded from 2.5.1 to 2.5.7 livedata upgraded from 1.0.15 to 1.0.17 localstorage upgraded from 1.0.5 to 1.0.8 logging upgraded from 1.0.8 to 1.0.11 meteor upgraded from 1.1.10 to 1.1.13 meteor-base upgraded from 1.0.1 to 1.0.3 minifier-css added, version 1.1.10 minifier-js added, version 1.1.10 minifiers removed from your project minimongo upgraded from 1.0.10 to 1.0.13 mobile-experience upgraded from 1.0.1 to 1.0.3 mobile-status-bar upgraded from 1.0.6 to 1.0.11 modules added, version 0.5.2 modules-runtime added, version 0.6.2 mongo upgraded from 1.1.3 to 1.1.6 mongo-id upgraded from 1.0.1 to 1.0.3 npm-mongo upgraded from 1.4.39_1 to 1.4.42 observe-sequence upgraded from 1.0.7 to 1.0.10 ordered-dict upgraded from 1.0.4 to 1.0.6 promise upgraded from 0.5.1 to 0.6.6 random upgraded from 1.0.5 to 1.0.8 rate-limit upgraded from 1.0.0 to 1.0.3 reactive-dict upgraded from 1.1.3 to 1.1.6 reactive-var upgraded from 1.0.6 to 1.0.8 reload upgraded from 1.1.4 to 1.1.7 retry upgraded from 1.0.4 to 1.0.6 routepolicy upgraded from 1.0.6 to 1.0.9 service-configuration upgraded from 1.0.5 to 1.0.8 session upgraded from 1.1.1 to 1.1.4 sha upgraded from 1.0.4 to 1.0.6 spacebars upgraded from 1.0.7 to 1.0.10 spacebars-compiler upgraded from 1.0.7 to 1.0.10 srp upgraded from 1.0.4 to 1.0.7 standard-minifier-css added, version 1.0.5 standard-minifier-js added, version 1.0.5 standard-minifiers upgraded from 1.0.2 to 1.0.5 templating upgraded from 1.1.5 to 1.1.8 templating-tools upgraded from 1.0.0 to 1.0.3 tracker upgraded from 1.0.9 to 1.0.12 ui upgraded from 1.0.8 to 1.0.10 underscore upgraded from 1.0.4 to 1.0.7 url upgraded from 1.0.5 to 1.0.8 webapp upgraded from 1.2.3 to 1.2.7 webapp-hashing upgraded from 1.0.5 to 1.0.8 * These packages have been updated to new versions that are not backwards compatible. plexrequests-meteor: updated to Meteor 1.3.1. Changes to your project's package version selections from updating package versions: 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.9.1 aldeed:collection2-core added, version 1.1.1 aldeed:schema-deny added, version 1.0.1 aldeed:schema-index added, version 1.0.1 aldeed:simple-schema upgraded from 1.3.3 to 1.5.3 aslagle:reactive-table upgraded from 0.8.18 to 0.8.28 fortawesome:fontawesome upgraded from 4.4.0 to 4.5.0 mdg:validation-error added, version 0.2.0 momentjs:moment upgraded from 2.10.6 to 2.12.0 percolate:synced-cron upgraded from 1.3.0 to 1.3.2 raix:eventemitter added, version 0.1.3 softwarerero:accounts-t9n upgraded from 1.1.6 to 1.1.7 standard-minifiers removed from your project useraccounts:bootstrap upgraded from 1.12.4 to 1.13.1 useraccounts:core upgraded from 1.12.4 to 1.13.1 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: * mdg:validation-error 0.2.0 (0.5.1 is available) * softwarerero:accounts-t9n 1.1.7 (1.3.3 is available) To update one or more of these packages, pass their names to `meteor update`. Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 15:14:04 5e4a1c6e673d syslog-ng[99]: syslog-ng starting up; version='3.5.3' [[[[[ /config/plexrequests-meteor ]]]]] => Started proxy. Unexpected mongo exit code 14. Restarting. Unexpected mongo exit code 14. Restarting. Unexpected mongo exit code 14. Restarting. Can't start Mongo server. Unspecified unrecoverable error. Exit was not clean Apr 8 15:17:01 5e4a1c6e673d /USR/SBIN/CRON[138]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 16:17:01 5e4a1c6e673d /USR/SBIN/CRON[141]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 17:17:01 5e4a1c6e673d /USR/SBIN/CRON[144]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 5e4a1c6e673d /USR/SBIN/CRON[147]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 5e4a1c6e673d /USR/SBIN/CRON[150]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 5e4a1c6e673d /USR/SBIN/CRON[153]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 5e4a1c6e673d /USR/SBIN/CRON[156]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 5e4a1c6e673d /USR/SBIN/CRON[159]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 5e4a1c6e673d /USR/SBIN/CRON[162]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 5e4a1c6e673d /USR/SBIN/CRON[165]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 5e4a1c6e673d /USR/SBIN/CRON[168]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 5e4a1c6e673d /USR/SBIN/CRON[171]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 5e4a1c6e673d /USR/SBIN/CRON[174]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 5e4a1c6e673d /USR/SBIN/CRON[177]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 5e4a1c6e673d /USR/SBIN/CRON[180]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 5e4a1c6e673d /USR/SBIN/CRON[183]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 5e4a1c6e673d /USR/SBIN/CRON[186]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Apr 9 07:17:01 5e4a1c6e673d /USR/SBIN/CRON[273]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work Quote Link to comment
nerv Posted April 10, 2016 Share Posted April 10, 2016 Reposting my reply, as I think it got missed since it was last on the previous page. Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts: <--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Quote Link to comment
aptalca Posted April 10, 2016 Author Share Posted April 10, 2016 Reposting my reply, as I think it got missed since it was last on the previous page. Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts: <--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Can you post a screenshot of your container settings? Quote Link to comment
jrdnlc Posted April 11, 2016 Share Posted April 11, 2016 Anyone know what might be causing this issue? Quote Link to comment
ijuarez Posted April 11, 2016 Share Posted April 11, 2016 Anyone know what might be causing this issue? Looks like you mac is trying to make a local cache or something. Quote Link to comment
nerv Posted April 11, 2016 Share Posted April 11, 2016 Attached. Thanks! Reposting my reply, as I think it got missed since it was last on the previous page. Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts: <--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Can you post a screenshot of your container settings? Quote Link to comment
aptalca Posted April 11, 2016 Author Share Posted April 11, 2016 Attached. Thanks! Reposting my reply, as I think it got missed since it was last on the previous page. Looks like you updated the log to be more verbose? It started for me again, but I came back in the morning and it wasn't running, and it won't start again. Here's the log from my last two restarts: <--------------------------------------> Starting container on Fri Apr 8 08:24:12 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 08:24:17 0e4ab8704a53 syslog-ng[48]: syslog-ng starting up; version='3.5.3' <--------------------------------------> <--------------------------------------> Starting container on Fri Apr 8 16:39:19 PDT 2016 Updating repository Selecting the desired branch Using the master branch 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 The latest version of Meteor, 1.3.1, is already installed on this computer. Run 'meteor update' inside of a particular project directory to update that project to Meteor 1.3.1 Starting PlexRequests. The web gui will be up once the message 'App running at: http://localhost' is displayed Apr 8 16:39:23 0e4ab8704a53 syslog-ng[46]: syslog-ng starting up; version='3.5.3' Apr 8 17:17:01 0e4ab8704a53 /USR/SBIN/CRON[70]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 18:17:01 0e4ab8704a53 /USR/SBIN/CRON[73]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 19:17:01 0e4ab8704a53 /USR/SBIN/CRON[76]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 20:17:01 0e4ab8704a53 /USR/SBIN/CRON[79]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 21:17:01 0e4ab8704a53 /USR/SBIN/CRON[82]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 22:17:01 0e4ab8704a53 /USR/SBIN/CRON[85]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 8 23:17:01 0e4ab8704a53 /USR/SBIN/CRON[88]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 00:17:01 0e4ab8704a53 /USR/SBIN/CRON[91]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 01:17:01 0e4ab8704a53 /USR/SBIN/CRON[94]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 02:17:01 0e4ab8704a53 /USR/SBIN/CRON[97]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 03:17:01 0e4ab8704a53 /USR/SBIN/CRON[100]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 04:17:01 0e4ab8704a53 /USR/SBIN/CRON[103]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 05:17:01 0e4ab8704a53 /USR/SBIN/CRON[106]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:17:01 0e4ab8704a53 /USR/SBIN/CRON[109]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 9 06:25:01 0e4ab8704a53 /USR/SBIN/CRON[112]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Can you post a screenshot of your container settings? The issue is not obvious to me. Is this a new install? I would recommend deleting the local folder and reinstalling it from scratch. Quote Link to comment
nerv Posted April 12, 2016 Share Posted April 12, 2016 I upgraded to Unraid 6.0 less than a month ago, and have been running into this issue with PlexRequests since then sadly (I hadn't used it before). I've tried fresh docker images and haven't had any luck sadly. Quote Link to comment
trurl Posted April 12, 2016 Share Posted April 12, 2016 I upgraded to Unraid 6.0 less than a month ago, and have been running into this issue with PlexRequests since then sadly (I hadn't used it before). I've tried fresh docker images and haven't had any luck sadly. Are you really using 6.0? I don't think anything but 6.1+ has been available for download for quite some time. Quote Link to comment
nerv Posted April 12, 2016 Share Posted April 12, 2016 I upgraded to Unraid 6.0 less than a month ago, and have been running into this issue with PlexRequests since then sadly (I hadn't used it before). I've tried fresh docker images and haven't had any luck sadly. Are you really using 6.0? I don't think anything but 6.1+ has been available for download for quite some time. Sorry, the real version is 6.1.9. Mostly meant that I made the upgrade from 5.x . Quote Link to comment
aptalca Posted April 12, 2016 Author Share Posted April 12, 2016 Could your docker image file be full by any chance? Also try the following in unraid terminal docker logs PlexRequests That might show more info on any potential errors Quote Link to comment
hunter69 Posted April 12, 2016 Share Posted April 12, 2016 I am attempting to install Nginx-letsencrypt. I cannot get the container to install, I click create and nothing happens. I set the config path to /mnt/cache/nginx/config. http port is 81, https is 443. Nothing happens. I have installed the following containers successfully: owncloud and apache. Is anyone else having this problem? Any ideas what I could do to get around this issue? I really appreciate you taking your time to help. Bill Quote Link to comment
nerv Posted April 12, 2016 Share Posted April 12, 2016 Could your docker image file be full by any chance? Also try the following in unraid terminal docker logs PlexRequests That might show more info on any potential errors Here's the Unraid logs from restarting it. How do you check if the docker image is full? I highly doubt it is, since it's 10GB and I saw this same issue when it was the only docker app installed, but I can check. Apr 12 08:52:44 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'restart' 'PlexRequests' Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: veth27e6fc1: renamed from eth0 Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth27e6fc1. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for vethca05738. Apr 12 08:52:44 Media kernel: device vethca05738 left promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: device vethfcc4630 entered promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: nf_conntrack: falling back to vmalloc. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth04d6a32. Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered disabled state Apr 12 08:52:44 Media kernel: eth0: renamed from veth04d6a32 Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:58 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f PlexRequests Apr 12 08:52:59 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Quote Link to comment
aptalca Posted April 12, 2016 Author Share Posted April 12, 2016 I am attempting to install Nginx-letsencrypt. I cannot get the container to install, I click create and nothing happens. I set the config path to /mnt/cache/nginx/config. http port is 81, https is 443. Nothing happens. I have installed the following containers successfully: owncloud and apache. Is anyone else having this problem? Any ideas what I could do to get around this issue? I really appreciate you taking your time to help. Bill Click on advanced view Quote Link to comment
aptalca Posted April 12, 2016 Author Share Posted April 12, 2016 Could your docker image file be full by any chance? Also try the following in unraid terminal docker logs PlexRequests That might show more info on any potential errors Here's the Unraid logs from restarting it. How do you check if the docker image is full? I highly doubt it is, since it's 10GB and I saw this same issue when it was the only docker app installed, but I can check. Apr 12 08:52:44 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'restart' 'PlexRequests' Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: veth27e6fc1: renamed from eth0 Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth27e6fc1. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for vethca05738. Apr 12 08:52:44 Media kernel: device vethca05738 left promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: device vethfcc4630 entered promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: nf_conntrack: falling back to vmalloc. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth04d6a32. Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered disabled state Apr 12 08:52:44 Media kernel: eth0: renamed from veth04d6a32 Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:58 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f PlexRequests Apr 12 08:52:59 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state I actually needed the logs for the container (by typing the command I posted in terminal), but. . . those messages in the unraid log don't seem right. Perhaps jonp or limetech can elaborate as there may be an issue with your network settings Quote Link to comment
rix Posted April 13, 2016 Share Posted April 13, 2016 Thanks for the major nginx update. Quote Link to comment
dAigo Posted April 13, 2016 Share Posted April 13, 2016 Indeed, release notes sounds great. I'll report back when renewal comes up Quote Link to comment
bisk Posted April 14, 2016 Share Posted April 14, 2016 You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work If I change my Dockers to use /mnt/cache/ how do back them up? I've got my Dockers running from /mnt/user/AppData so that everything is protected in the Array. It's one of the questions I've had about Dockers and unRAID, but I haven't been able to find a definitive answer. Quote Link to comment
aptalca Posted April 14, 2016 Author Share Posted April 14, 2016 You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work If I change my Dockers to use /mnt/cache/ how do back them up? I've got my Dockers running from /mnt/user/AppData so that everything is protected in the Array. It's one of the questions I've had about Dockers and unRAID, but I haven't been able to find a definitive answer. Look into cache pooling. That way you can have multiple disks as part of a single cache share and every piece of data exists on two separate disks (more of a mirroring approach rather than a parity protected system, but unlike traditional raid mirroring, this system uses bttrfs's builtin feature and it is very flexible in terms of showing disks of different sizes) Or you can periodically back up the cache drive contents on a user share via a simple copy operation or rsync. The reasons most people use cache shares for dockers are: 1. There is a bug that affects some containers and breaks them when they are on a user share (may be related to use of symlinks) 2. Writes to the protected array are much slower due to the parity calculation. Whereas if you use an ssd as a cache drive it can be much much faster so you get better performance in most dockers 3. Having the containers on a user share may put too much stress on the parity drive in the long run Quote Link to comment
lpe672 Posted April 19, 2016 Share Posted April 19, 2016 I'm installing the Zoneminder-1.29 and after I set everything up, I get a broken image in the monitor view. And this err in the logs: ERR [getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-607652s.sock ) failed: No such file or directory - checkStreamForErrors()] This is a clean install. I followed the directions on this topic and got no where: https://forums.zoneminder.com/viewtopic.php?t=24499 EDIT: I fixed it. In the Setting/Paths page, change PATH_ZMS from /cgi-bin/nph-zms to /zm/cgi-bin/nph-zms Quote Link to comment
aptalca Posted April 19, 2016 Author Share Posted April 19, 2016 I'm installing the Zoneminder-1.29 and after I set everything up, I get a broken image in the monitor view. And this err in the logs: ERR [getStreamCmdResponse stream error: socket_sendto( /var/run/zm/zms-607652s.sock ) failed: No such file or directory - checkStreamForErrors()] This is a clean install. I followed the directions on this topic and got no where: https://forums.zoneminder.com/viewtopic.php?t=24499 EDIT: I fixed it. In the Setting/Paths page, change PATH_ZMS from /cgi-bin/nph-zms to /zm/cgi-bin/nph-zms That forum post refers to the older version. I probably should update it to reflect that. The correct directions for ver 1.29 are on the docker hub page as well as the github page Quote Link to comment
mgworek Posted April 21, 2016 Share Posted April 21, 2016 Thank you so much for the Home-Automation-Bridge. I didn't know about it until 2 days ago. I can now have Alexa turn on my media center!! Quote Link to comment
aptalca Posted April 21, 2016 Author Share Posted April 21, 2016 Thank you so much for the Home-Automation-Bridge. I didn't know about it until 2 days ago. I can now have Alexa turn on my media center!! Yeah the echo ended up becoming one of my best purchases. I integrated that thing with my lights, media center and everything. My friend's kids especially love chatting with Alexa lol Quote Link to comment
hat22 Posted April 21, 2016 Share Posted April 21, 2016 Hi, I've installed aptalca's dolphin docker and really like the look of it. However, I can't get it to do anything other than browse directories. It's probably really obvious to most of you here but I just can't figure out how to make it do things like moving files and deleting. I think it's something to do with permissions and that by default it's set up as "nobody". I've looked through all the settings and can't find a way to change anything. I've searched google and not been able to find anything. I've even searched the forums. This makes me think it's so obvious and I'm just not getting it. I'd really appreciate it if someone could please help me understand what is going on and how to fix it in layman's terms. Thanks, Graham Quote Link to comment
aptalca Posted April 21, 2016 Author Share Posted April 21, 2016 Hi, I've installed aptalca's dolphin docker and really like the look of it. However, I can't get it to do anything other than browse directories. It's probably really obvious to most of you here but I just can't figure out how to make it do things like moving files and deleting. I think it's something to do with permissions and that by default it's set up as "nobody". I've looked through all the settings and can't find a way to change anything. I've searched google and not been able to find anything. I've even searched the forums. This makes me think it's so obvious and I'm just not getting it. I'd really appreciate it if someone could please help me understand what is going on and how to fix it in layman's terms. Thanks, Graham By default, it runs as user nobody and group users, which should have write access to your user shares in unraid. Some config folders of certain docker containers may not provide write access for the user nobody or the group users. If that's the issue, you can set the environment variables USER_ID and GROUP_ID to 0 when you install/edit the container in unraid gui so it will run as root. It's explained in the container description 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.