Community Developer
  • Content count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About ninthwalker

  • Rank
    Advanced Member


  • Gender
  1. To clarify, your plex account email gets it when you do a manual -t but not when the cron job runs it? what does the below cmd look like? Does it list the 2 cron's? "docker exec nowshowing crontab -l"
  2. Good. Glad that was easy.
  3. Good idea, thanks for the suggestion.
  4. So I have actually come across that myself before. It's usually if I have a Plex Library with nothing in it. I haven't figured out a way yet for it to not error out on that bug. Can you check if you have a Library created with nothing in it? If so are you able to remove the Library and does the report run then? If you don't have an empty Library then I'm not sure what the issue is and I'll have to get more debugging from you and look into it.
  5. Thanks Jimmy, glad it's working well for you.
  6. Depends on how much content has been added during the polling period. If you have added 12 movies and 20 TV shows in the past week it may take a few minutes. It has to scan your plex libraries then get the metadata from themoviedb or tvdb and they have rate limits on their API's.
  7. After you fill in the basic template info and install the docker navigate to your appdata config directory. In there will be an advanced.yaml settings file that you can modify to change the time and report type and logo's, etc. look at the example file or go to the github page for help on the settings.
  8. It looks like that is probably the cron job from plexReport trying to run but you don't have the plexReport docker installed anymore. If you followed the instructions you probably have a 'plexreport_schedule.cron file on your flash drive in config/plugins somewhere that got loaded at startup. Find the file, delete it and then at the console type 'update_cron' . you can check that it's been removed, by running the below command. You can also manually edit the below file if 'update_cron' didn't work. 'cat /etc/cron.d/root'
  9. So a few things here. I think you may have mistyped something into the original docker template variables when you were first trying and then upon your successful install entered everything correctly. The reason I say this is that all the fields you added to the advanced.yaml are not really being seen by the program. It's not programmatically possible as it is looking for a different file for those settings. Same with the "home_page" you added. That variable doesn't exist anywhere. The idea with the template variables is that if someone doesn't want to modify any files, the docker will 'just work' with only the template variables. If they want additional control then that's where they can modify the advanced.yaml file. You can verify that your variables from the template are correctly being written by running this command below from unRAID console It is this file that is read for the plex/email connections. The file should look exactly like the code below (but your own variables) and not be modified as it will be overwritten from the docker template variable upon a restart. docker exec nowshowing cat /opt/config.yaml This should display something similar to: --- plex: server: api_key: evR45JG90USwqMChR2 mail: address: port: '587' username: password: TopSecretP@ssw0rd!
  10. NowShowing, the successor to plexReport has been released. We suggest everyone to install the new NowShowing docker as plexReport will no longer be maintained. NowShowing provides a lot more features and customization including a web page! See this post for support:
  11. App name: NowShowing Docker Hub: Github: Wiki: (A lot of good info) The NowShowing docker provides a summary of new media that has recently been added to Plex. You can select to have it generate an email and/or create a web page for your users to visit. NowShowing is the successor of the popular plexReport docker. The original brainchild of bstascavage ( Further developed by NinthWalker & enhanced by GroxyPod, NowShowing adds additional improvements and features in a friendly, easy to install docker. _________________________________________________ Installation: Preferred installation method: From the Community Applications 'APPS' section in unRAID. You can also install by adding the following template repository:
  12. We are about to release a new spinoff of this docker actually. It incorporates an advanced file for better customization, as well as additional features like a web page. Specifically for your question, there is not currently a way to do exactly what you describe. The current plexReport docker was hard coded and reports 7 days worth of media. However in this new advanced file, you can specify the period of days to report on from 1-7. If that is too much, you could select say 2 day's worth to report on, and then send that out once a week. That will sort of achieve what you are trying to do, although it won't let you pick and choose what Items to report.
  13. I cant reproduce the error on my side. Seems like a docker exec issue than the program generating the issue though. Could be related to the base docker image, or possible your unraid/docker version. What is your docker/unraid version? If the report is still sending out, I probably won't look into it much more. We are close to releasing a new docker to replace plexreport anyways so time is being spent on that right now.
  14. I haven't seen that error before, and not sure if it's plexReport or not. A quick search seems more related to a go docker instance, but possibly docker exec related as well. Some more info would help. The only time plexReport runs is when the report goes out. If you run it with the "-t" option to test then look at the log does it happen right then? Can you duplicate it happening twice? to test: "docker exec plexReport plexreport -t" if it does happen during those exact few minutes it runs, does the report still go out? Also, check if you can docker exec into it normally and if just that even triggers the error. "docker exec -it plexReport /bin/bash"
  15. A new App has been added to the Repository: App name: DashBtn Docker Hub: Github: This is a Docker for use with Amazon Dash Button's. It intercepts the button press and allows you to do various home automation tasks. ie: Turn on lights, start a movie for your kid, notifications, order a pizza, etc. Use this docker to create your own scripts using Python, Shell, & curl.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.