VenomIreland Posted November 5, 2015 Share Posted November 5, 2015 I'm having some problems using the PlexReqeusts docker, I set it up with the correct port mapping and config location, but despite it being listed as running, I cannot connect to the web interface. What could I be doing wrong? What path are you using for the config folder? If you post a log, I'll take a look I'm using the path /mnt/user/appdata/plexrequests/ for the config. Where can I find the log files? Quote Link to comment
CHBMB Posted November 5, 2015 Share Posted November 5, 2015 I'm having some problems using the PlexReqeusts docker, I set it up with the correct port mapping and config location, but despite it being listed as running, I cannot connect to the web interface. What could I be doing wrong? What path are you using for the config folder? If you post a log, I'll take a look I'm using the path /mnt/user/appdata/plexrequests/ for the config. Where can I find the log files? Quote Link to comment
VenomIreland Posted November 6, 2015 Share Posted November 6, 2015 ... Ahh, thanks! Had it in advanced view so I missed that. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/firstrun.sh... First install detected, cloning repository Cloning into 'plexrequests-meteor'... Using the master branch Already on 'master' Your branch is up-to-date with 'origin/master'. nobody, this is your first time using Meteor! Installing a Meteor distribution in your home directory. This project is already at Meteor 1.2.1, the latest release. Your top-level dependencies are at their latest compatible versions. The following top-level dependencies were not updated to the very latest version available: * iron:core 1.0.8 (1.0.11 is available) * iron:router 1.0.10 (1.0.12 is available) Newer versions of the following indirect dependencies are available: * iron:controller 1.0.8 (1.0.12 is available) * iron:dynamic-template 1.0.8 (1.0.12 is available) * iron:layout 1.0.8 (1.0.12 is available) * iron:location 1.0.9 (1.0.11 is available) * iron:middleware-stack 1.0.10 (1.0.11 is available) * iron:url 1.0.9 (1.0.11 is available) To update one or more of these packages, pass their names to `meteor update`. Nov 6 00:09:42 c32e4f03d98e syslog-ng[62]: 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 Quote Link to comment
aptalca Posted November 6, 2015 Author Share Posted November 6, 2015 I'm having some problems using the PlexReqeusts docker, I set it up with the correct port mapping and config location, but despite it being listed as running, I cannot connect to the web interface. What could I be doing wrong? What path are you using for the config folder? If you post a log, I'll take a look I'm using the path /mnt/user/appdata/plexrequests/ for the config. Where can I find the log files? I was suspecting that. Many people reported having issues with docker containers with the config folder on a user share. If the appdata share is a cache only share, change the path to /mnt/cache/appdata/plexrequests/ and it should work Quote Link to comment
VenomIreland Posted November 6, 2015 Share Posted November 6, 2015 Damn, I don't have a cache drive currently, anything else I could try? Quote Link to comment
aptalca Posted November 6, 2015 Author Share Posted November 6, 2015 Damn, I don't have a cache drive currently, anything else I could try? Hmm. Try this: make the share exist only on disk1 and use the path /mnt/disk1/appdata/plexrequests Not sure if that will work but it's worth a try Quote Link to comment
Peanutman85 Posted November 7, 2015 Share Posted November 7, 2015 I just noticed a problem with PlexRequests. I updated it last night, so not sure if that's what caused the problem. I am getting the following when I try to access the WebUI: Your app is crashing. Here's the latest log: /home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:278 throw(ex); ^ MongoError: E11000 duplicate key error index: meteor.movies.$c2_imdb dup key: { : "tt2096673" } at Object.Future.wait (/home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:398:15) at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:790:1) at packages/aldeed_collection2/packages/aldeed_collection2.js:77:1 at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:249:5 - - - - - at Object.toError (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/utils.js:114:11) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/db.js:1354:26 at Server.Base._callHandler (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/base.js:453:41) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:488:18 at [object Object].MongoReply.parseBody (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:446:20) at [object Object].emit (events.js:95:17) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:207:13) at [object Object].emit (events.js:98:17) at Socket.<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection.js:440:22) Exited with code: 8 Your application is crashing. Waiting for file change. Any ideas? Quote Link to comment
aptalca Posted November 7, 2015 Author Share Posted November 7, 2015 I just noticed a problem with PlexRequests. I updated it last night, so not sure if that's what caused the problem. I am getting the following when I try to access the WebUI: Your app is crashing. Here's the latest log: /home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:278 throw(ex); ^ MongoError: E11000 duplicate key error index: meteor.movies.$c2_imdb dup key: { : "tt2096673" } at Object.Future.wait (/home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:398:15) at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:790:1) at packages/aldeed_collection2/packages/aldeed_collection2.js:77:1 at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:249:5 - - - - - at Object.toError (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/utils.js:114:11) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/db.js:1354:26 at Server.Base._callHandler (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/base.js:453:41) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:488:18 at [object Object].MongoReply.parseBody (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:446:20) at [object Object].emit (events.js:95:17) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:207:13) at [object Object].emit (events.js:98:17) at Socket.<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection.js:440:22) Exited with code: 8 Your application is crashing. Waiting for file change. Any ideas? That's a plex requests issue. I believe someone reported it on their forums recently and it was said that the new version does not allow duplicate entries. If you update and your database contains duplicates, it causes issues. You might want to ask there. Quote Link to comment
flamegrilled Posted November 7, 2015 Share Posted November 7, 2015 apt-get install usbutils.I did all that after your first reply.I see the host(unraid) does not have the /dev/v4l directory so I cannot see the usb camera either. From the ZM app : Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 020: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It is mapping the usb devices after the usb update. Is v4l missing in this install(zm container)? See if this works: http://askubuntu.com/questions/276572/how-do-i-install-video4linux2-in-ubuntu-12-10-and-do-i-need-to I have tried that and many after that and /dev/video0 still nowhere to be seen.It always complains about missing lib* files.which I could never find. Without logs or details on what you tried, it's hard for me to tell what the issue is. I'll try to dig up an old usb camera from storage this weekend and see if I can get it to work sean-N250P:~$ /dev/v v4l/ vfio/ sean-N250P:~$ /dev/v4l/ bash: /dev/v4l/: Is a directory sean-N250P:~$ cd /dev/v4l/ sean-N250P:/dev/v4l$ dir by-id by-path sean@sean-N250P:/dev/v4l$ cd by-path/ sean-N250P:/dev/v4l/by-path$ ls pci-0000:00:1d.3-usb-0:1:1.0-video-index0 pci-0000:00:1d.7-usb-0:8:1.0-video-index0 sean-N250P:/dev/v4l/by-path$ cd .. sean-N250P:/dev/v4l$ cd by-id sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ uname -a Linux sean-N250P 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:22:32 UTC 2015 i686 i686 i686 GNU/Linux sean-N250P:/dev/v4l/by-id$ cat /etc/issue Ubuntu 15.04 \n \l sean-N250P:/dev/v4l/by-id$ Hey Aptalca, I have gone through many apt-get installs on the container with different versions of v4l and other drivers,but failure to load /dev/video0 etc was the case.I have pasted the outcome from my Ubuntu notebook and you can see the camera coming up everytime.I have run this too function makedev () {N) for dev in 0 1 2 3; do echo "/dev/$1$dev: char 81 $[ $2 + $dev ]" rm -f /dev/$1$dev mknod /dev/$1$dev c 81 $[ $2 + $dev ] chmod 666 /dev/$1$dev done # symlink for default device rm -f /dev/$1 ln -s /dev/${1}0 /dev/$1 } # see http://roadrunner.swansea.uk.linux.org/v4lapi.shtml echo "*** new device names ***" makedev video 0 makedev radio 64 makedev vtx 192 makedev vbi 224 # "*** old device names (for compatibility only) ***" #makedev bttv 0 #makedev bttv-fm 64 MAKEDEV It loads this lrwxrwxrwx 1 root root 11 Nov 6 21:47 video -> /dev/video0 crw-rw-rw- 1 root root 81, 0 Nov 6 21:47 video0 crw-rw-rw- 1 root root 81, 1 Nov 6 21:47 video1 crw-rw-rw- 1 root root 81, 2 Nov 6 21:47 video2 crw-rw-rw- 1 root root 81, 3 Nov 6 21:47 video3 lrwxrwxrwx 1 root root 9 Nov 6 21:47 vtx -> /dev/vtx0 crw-rw-rw- 1 root root 81, 192 Nov 6 21:47 vtx0 crw-rw-rw- 1 root root 81, 193 Nov 6 21:47 vtx1 crw-rw-rw- 1 root root 81, 194 Nov 6 21:47 vtx2 crw-rw-rw- 1 root root 81, 195 Nov 6 21:47 vtx3 but I assume v4l has to combine the /dev/video* to the root@661e7b6e967e:/dev# lsusb Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@661e7b6e967e:/dev# and in this case /dev/bus/usb/003 Quote Link to comment
jrdnlc Posted November 7, 2015 Share Posted November 7, 2015 Do you plan on adding Boxcar support to plex requests? Quote Link to comment
VenomIreland Posted November 7, 2015 Share Posted November 7, 2015 I was suspecting that. Many people reported having issues with docker containers with the config folder on a user share. If the appdata share is a cache only share, change the path to /mnt/cache/appdata/plexrequests/ and it should work That worked! I am now having a separate issue with adding to Sonarr though, I'm getting an error trying to approve TV Shows as follows: [34mI20151107-09:47:17.306(0)? [39mSonarr Series Post -> Match error: Expected string, got undefined Quote Link to comment
aptalca Posted November 7, 2015 Author Share Posted November 7, 2015 Do you plan on adding Boxcar support to plex requests? Unfortunately, I'm not the developer of plex requests. I only created a docker container for it. You can ask them in their thread on the Plex forum Quote Link to comment
aptalca Posted November 7, 2015 Author Share Posted November 7, 2015 I was suspecting that. Many people reported having issues with docker containers with the config folder on a user share. If the appdata share is a cache only share, change the path to /mnt/cache/appdata/plexrequests/ and it should work That worked! I am now having a separate issue with adding to Sonarr though, I'm getting an error trying to approve TV Shows as follows: [34mI20151107-09:47:17.306(0)? [39mSonarr Series Post -> Match error: Expected string, got undefined That's a plex requests issue. You should ask them on the plex forum or create an issue on their github repo Quote Link to comment
aptalca Posted November 8, 2015 Author Share Posted November 8, 2015 apt-get install usbutils.I did all that after your first reply.I see the host(unraid) does not have the /dev/v4l directory so I cannot see the usb camera either. From the ZM app : Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 020: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It is mapping the usb devices after the usb update. Is v4l missing in this install(zm container)? See if this works: http://askubuntu.com/questions/276572/how-do-i-install-video4linux2-in-ubuntu-12-10-and-do-i-need-to I have tried that and many after that and /dev/video0 still nowhere to be seen.It always complains about missing lib* files.which I could never find. Without logs or details on what you tried, it's hard for me to tell what the issue is. I'll try to dig up an old usb camera from storage this weekend and see if I can get it to work sean-N250P:~$ /dev/v v4l/ vfio/ sean-N250P:~$ /dev/v4l/ bash: /dev/v4l/: Is a directory sean-N250P:~$ cd /dev/v4l/ sean-N250P:/dev/v4l$ dir by-id by-path sean@sean-N250P:/dev/v4l$ cd by-path/ sean-N250P:/dev/v4l/by-path$ ls pci-0000:00:1d.3-usb-0:1:1.0-video-index0 pci-0000:00:1d.7-usb-0:8:1.0-video-index0 sean-N250P:/dev/v4l/by-path$ cd .. sean-N250P:/dev/v4l$ cd by-id sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ uname -a Linux sean-N250P 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:22:32 UTC 2015 i686 i686 i686 GNU/Linux sean-N250P:/dev/v4l/by-id$ cat /etc/issue Ubuntu 15.04 \n \l sean-N250P:/dev/v4l/by-id$ Hey Aptalca, I have gone through many apt-get installs on the container with different versions of v4l and other drivers,but failure to load /dev/video0 etc was the case.I have pasted the outcome from my Ubuntu notebook and you can see the camera coming up everytime.I have run this too function makedev () {N) for dev in 0 1 2 3; do echo "/dev/$1$dev: char 81 $[ $2 + $dev ]" rm -f /dev/$1$dev mknod /dev/$1$dev c 81 $[ $2 + $dev ] chmod 666 /dev/$1$dev done # symlink for default device rm -f /dev/$1 ln -s /dev/${1}0 /dev/$1 } # see http://roadrunner.swansea.uk.linux.org/v4lapi.shtml echo "*** new device names ***" makedev video 0 makedev radio 64 makedev vtx 192 makedev vbi 224 # "*** old device names (for compatibility only) ***" #makedev bttv 0 #makedev bttv-fm 64 MAKEDEV It loads this lrwxrwxrwx 1 root root 11 Nov 6 21:47 video -> /dev/video0 crw-rw-rw- 1 root root 81, 0 Nov 6 21:47 video0 crw-rw-rw- 1 root root 81, 1 Nov 6 21:47 video1 crw-rw-rw- 1 root root 81, 2 Nov 6 21:47 video2 crw-rw-rw- 1 root root 81, 3 Nov 6 21:47 video3 lrwxrwxrwx 1 root root 9 Nov 6 21:47 vtx -> /dev/vtx0 crw-rw-rw- 1 root root 81, 192 Nov 6 21:47 vtx0 crw-rw-rw- 1 root root 81, 193 Nov 6 21:47 vtx1 crw-rw-rw- 1 root root 81, 194 Nov 6 21:47 vtx2 crw-rw-rw- 1 root root 81, 195 Nov 6 21:47 vtx3 but I assume v4l has to combine the /dev/video* to the root@661e7b6e967e:/dev# lsusb Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@661e7b6e967e:/dev# and in this case /dev/bus/usb/003 I dug up an old usb cam and can confirm that lsusb lists the device as being on the usb bus, however dmesg shows no drivers loaded for the device. AFAIK, docker can pass through any device that has a driver loaded for it. My guess is that unraid does not contain the proper drivers for usb cameras and therefore no dev/video0 created for it. I don't think there is any way around it other than compiling a custom kernel for unraid, which is probably not worth the trouble. Or, if you have vt-d support, you can create a VM and passthrough that usb bus and have the VM load the drivers for the camera. I think you would be better off with an IP cam Quote Link to comment
mike Posted November 9, 2015 Share Posted November 9, 2015 Damn, I don't have a cache drive currently, anything else I could try? Hmm. Try this: make the share exist only on disk1 and use the path /mnt/disk1/appdata/plexrequests Not sure if that will work but it's worth a try I had this same problem and making the appdata share only use disk5 worked for me. Quote Link to comment
aptalca Posted November 9, 2015 Author Share Posted November 9, 2015 Damn, I don't have a cache drive currently, anything else I could try? Hmm. Try this: make the share exist only on disk1 and use the path /mnt/disk1/appdata/plexrequests Not sure if that will work but it's worth a try I had this same problem and making the appdata share only use disk5 worked for me. Great! Thanks for confirming Quote Link to comment
flamegrilled Posted November 9, 2015 Share Posted November 9, 2015 apt-get install usbutils.I did all that after your first reply.I see the host(unraid) does not have the /dev/v4l directory so I cannot see the usb camera either. From the ZM app : Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 020: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It is mapping the usb devices after the usb update. Is v4l missing in this install(zm container)? See if this works: http://askubuntu.com/questions/276572/how-do-i-install-video4linux2-in-ubuntu-12-10-and-do-i-need-to I have tried that and many after that and /dev/video0 still nowhere to be seen.It always complains about missing lib* files.which I could never find. Without logs or details on what you tried, it's hard for me to tell what the issue is. I'll try to dig up an old usb camera from storage this weekend and see if I can get it to work sean-N250P:~$ /dev/v v4l/ vfio/ sean-N250P:~$ /dev/v4l/ bash: /dev/v4l/: Is a directory sean-N250P:~$ cd /dev/v4l/ sean-N250P:/dev/v4l$ dir by-id by-path sean@sean-N250P:/dev/v4l$ cd by-path/ sean-N250P:/dev/v4l/by-path$ ls pci-0000:00:1d.3-usb-0:1:1.0-video-index0 pci-0000:00:1d.7-usb-0:8:1.0-video-index0 sean-N250P:/dev/v4l/by-path$ cd .. sean-N250P:/dev/v4l$ cd by-id sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ ls usb-0c45_USB_camera-video-index0 usb-Image_Processor_WebCam_SCB-0355N-video-index0 sean-N250P:/dev/v4l/by-id$ uname -a Linux sean-N250P 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:22:32 UTC 2015 i686 i686 i686 GNU/Linux sean-N250P:/dev/v4l/by-id$ cat /etc/issue Ubuntu 15.04 \n \l sean-N250P:/dev/v4l/by-id$ Hey Aptalca, I have gone through many apt-get installs on the container with different versions of v4l and other drivers,but failure to load /dev/video0 etc was the case.I have pasted the outcome from my Ubuntu notebook and you can see the camera coming up everytime.I have run this too function makedev () {N) for dev in 0 1 2 3; do echo "/dev/$1$dev: char 81 $[ $2 + $dev ]" rm -f /dev/$1$dev mknod /dev/$1$dev c 81 $[ $2 + $dev ] chmod 666 /dev/$1$dev done # symlink for default device rm -f /dev/$1 ln -s /dev/${1}0 /dev/$1 } # see http://roadrunner.swansea.uk.linux.org/v4lapi.shtml echo "*** new device names ***" makedev video 0 makedev radio 64 makedev vtx 192 makedev vbi 224 # "*** old device names (for compatibility only) ***" #makedev bttv 0 #makedev bttv-fm 64 MAKEDEV It loads this lrwxrwxrwx 1 root root 11 Nov 6 21:47 video -> /dev/video0 crw-rw-rw- 1 root root 81, 0 Nov 6 21:47 video0 crw-rw-rw- 1 root root 81, 1 Nov 6 21:47 video1 crw-rw-rw- 1 root root 81, 2 Nov 6 21:47 video2 crw-rw-rw- 1 root root 81, 3 Nov 6 21:47 video3 lrwxrwxrwx 1 root root 9 Nov 6 21:47 vtx -> /dev/vtx0 crw-rw-rw- 1 root root 81, 192 Nov 6 21:47 vtx0 crw-rw-rw- 1 root root 81, 193 Nov 6 21:47 vtx1 crw-rw-rw- 1 root root 81, 194 Nov 6 21:47 vtx2 crw-rw-rw- 1 root root 81, 195 Nov 6 21:47 vtx3 but I assume v4l has to combine the /dev/video* to the root@661e7b6e967e:/dev# lsusb Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 8564:4000 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:602c Microdia Clas Ohlson TWC-30XOP Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@661e7b6e967e:/dev# and in this case /dev/bus/usb/003 I dug up an old usb cam and can confirm that lsusb lists the device as being on the usb bus, however dmesg shows no drivers loaded for the device. AFAIK, docker can pass through any device that has a driver loaded for it. My guess is that unraid does not contain the proper drivers for usb cameras and therefore no dev/video0 created for it. I don't think there is any way around it other than compiling a custom kernel for unraid, which is probably not worth the trouble. Or, if you have vt-d support, you can create a VM and passthrough that usb bus and have the VM load the drivers for the camera. I think you would be better off with an IP cam Aptalca Thanks for all the effort you have put in the Zoneminder project so far .It is appreciated. You are right.It looks that way.I will go for VM for usb and use my 6 IP camera'sin the container.USBIP not an option either I suppose?What resources(cpu+ram) will I need for ZM?What about splitting ZM resources in another container to reduce the need for more resources in a VM?I meant putting less in the ZM container,say a mariadb container for the data?If I were looking to use a box with a quad core and 8gb's of ram for 6 IP camera's? Quote Link to comment
Vaseer Posted November 15, 2015 Share Posted November 15, 2015 Today I upgraded PlexRequests and now I have problem accessing WebUI. I get error, that App has crashed: Your app is crashing. Here's the latest log: /home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:278 throw(ex); ^ MongoError: E11000 duplicate key error index: meteor.movies.$c2_imdb dup key: { : "tt2140379" } at Object.Future.wait (/home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:398:15) at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:790:1) at packages/aldeed_collection2/packages/aldeed_collection2.js:77:1 at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:249:5 - - - - - at Object.toError (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/utils.js:114:11) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/db.js:1354:26 at Server.Base._callHandler (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/base.js:453:41) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:488:18 at [object Object].MongoReply.parseBody (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:446:20) at [object Object].emit (events.js:95:17) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:207:13) at [object Object].emit (events.js:98:17) at Socket.<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection.js:440:22) Exited with code: 8 Your application is crashing. Waiting for file change. I have tried with docker restart and reinstall (Edit > Save [With same configuration. This counts as reinstall?]). Update/reinstall is done without an error. I didn't try removing and new installation, because I don't know what happens with movie/series database. Where is database saved? How can I make database backup? Quote Link to comment
aptalca Posted November 15, 2015 Author Share Posted November 15, 2015 Today I upgraded PlexRequests and now I have problem accessing WebUI. I get error, that App has crashed: Your app is crashing. Here's the latest log: /home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:278 throw(ex); ^ MongoError: E11000 duplicate key error index: meteor.movies.$c2_imdb dup key: { : "tt2140379" } at Object.Future.wait (/home/.meteor/packages/meteor-tool/.1.1.10.ki0ccv++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/server-lib/node_modules/fibers/future.js:398:15) at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:790:1) at packages/aldeed_collection2/packages/aldeed_collection2.js:77:1 at /config/plexrequests-meteor/.meteor/local/build/programs/server/boot.js:249:5 - - - - - at Object.toError (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/utils.js:114:11) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/db.js:1354:26 at Server.Base._callHandler (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/base.js:453:41) at /home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:488:18 at [object Object].MongoReply.parseBody (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/responses/mongo_reply.js:68:5) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/server.js:446:20) at [object Object].emit (events.js:95:17) at [object Object].<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:207:13) at [object Object].emit (events.js:98:17) at Socket.<anonymous> (/home/.meteor/packages/npm-mongo/.1.4.39_1.1klkbg5++os+web.browser+web.cordova/npm/node_modules/mongodb/lib/mongodb/connection/connection.js:440:22) Exited with code: 8 Your application is crashing. Waiting for file change. I have tried with docker restart and reinstall (Edit > Save [With same configuration. This counts as reinstall?]). Update/reinstall is done without an error. I didn't try removing and new installation, because I don't know what happens with movie/series database. Where is database saved? How can I make database backup? This issue was brought up in the plexrequests thread on the plex forum. Plexrequests is crashing because you have duplicate items in your database. The new version does not allow adding a duplicate and it errors out when there are duplicates in the database. I believe they recommended the deletion of the duplicate item in the database. You should be able search that thread for the exact methods. Quote Link to comment
Vaseer Posted November 15, 2015 Share Posted November 15, 2015 I remember that I had some duplicated items on the movie list, but I removed them (in previous version). Obviously I missed some. Is possible to install previous version to check for duplicated entry and delete them? Quote Link to comment
PhAzE Posted November 16, 2015 Share Posted November 16, 2015 Great job on RDP-Calibre. How can I set a username and password for the Calibre webserver? It's active, but when I log into the RDP session and go to settings in the app, it says the web server is not on (yet it is, and it's working) and none of the settings in the RDP session change the webserver that is active. Quote Link to comment
aptalca Posted November 16, 2015 Author Share Posted November 16, 2015 Great job on RDP-Calibre. How can I set a username and password for the Calibre webserver? It's active, but when I log into the RDP session and go to settings in the app, it says the web server is not on (yet it is, and it's working) and none of the settings in the RDP session change the webserver that is active. I'll look into it. The container is launching the webserver as a separate task from command line. I thought the built in server settings worked, but in reality I never tried to change any settings. Quote Link to comment
aptalca Posted November 20, 2015 Author Share Posted November 20, 2015 Great job on RDP-Calibre. How can I set a username and password for the Calibre webserver? It's active, but when I log into the RDP session and go to settings in the app, it says the web server is not on (yet it is, and it's working) and none of the settings in the RDP session change the webserver that is active. I remember now why I decided to launch the webserver separately through command line. If I let users use the built-in webserver, the settings and the port forwarding (host-to-container) would be too complicated to set up. By doing it separately, I was able to set it all up for the user and it just worked. If you would like to utilize the built-in webserver where you can change all the settings and add a password, you can follow the directions below. Keep in mind that the changes will persist through start and stops of the container but not if you reinstall or update it: in unraid terminal, type the following to access the container: docker exec -it RDP-Calibre bash Modify the startup script to permanently stop the existing webserver: nano /etc/my_init.d/firstrun.sh Delete the last line and hit ctrl-x to save and exit Restart the container and open the webgui Under Preferences/Sharing over the net, enter the port number "8081" (this is the internal port number within the container) and set other options, and start the webserver Now, you should be able to access the built-in server through the "second" port number you selected when you installed the container (alternatively, you can hit the link for that in the unraid gui under the docker tab as shown in the attached screenshot) Quote Link to comment
CHBMB Posted November 21, 2015 Share Posted November 21, 2015 Thanks Aptalca for this awesome PlexRequests docker. For anyone wanting to reverse-proxy PlexRequests with Apache First of all edit your xml like so: Then add this to your conf file in Apache (I'm using the linuxserver.io version.) <Location /requests> ProxyPass http://UNRAIDIP:3000/requests ProxyPassReverse http://UNRAIDIP:3000/requests </Location> I believe, judging by the github repo that this will work with the master branch as well, but I haven't tested it myself. Hope that helps anyone looking to do the same. Quote Link to comment
aptalca Posted November 23, 2015 Author Share Posted November 23, 2015 Thanks Aptalca for this awesome PlexRequests docker. For anyone wanting to reverse-proxy PlexRequests with Apache First of all edit your xml like so: Then add this to your conf file in Apache (I'm using the linuxserver.io version.) <Location /requests> ProxyPass http://UNRAIDIP:3000/requests ProxyPassReverse http://UNRAIDIP:3000/requests </Location> I believe, judging by the github repo that this will work with the master branch as well, but I haven't tested it myself. Hope that helps anyone looking to do the same. Thanks so much for the directions. I never tried reverse proxy but have been curious 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.