Jump to content

jedimstr

Members
  • Content Count

    107
  • Joined

  • Last visited

Community Reputation

4 Neutral

About jedimstr

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Personal Text
    IAmYourFathersBrothers NephewsCousinsFormerRoomate

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Congrats on moving forward with this new container and giving everyone what they wanted whether they wanted to stay on older versions or leap ahead to current released versions. I've already moved on to other container providers, but happy to see you guys take critique and release a better product that should please everyone.
  2. I'm sorry for causing such a hubub. I really didn't mean for this to get out of hand.
  3. Look, I'm sorry if I came off in a bad way and really don't want to badger. But the criteria mentioned in the past on why things aren't updating "not until it shows up on their download page" occurred and things still weren't updated. So if that's no longer the case, then you guys should stop saying it. Nice and easy, just don't say it. Keep a 5 year old version, fine. Don't say you'll update when their software page is updated. That's no longer a valid excuse. You should also maybe think about rewording this then: "Our build pipeline is a publicly accessible Jenkinsserver. This pipeline is triggered on a weekly basis, ensuring all of our users are kept up-to-date with latest application features and security fixes from upstream."
  4. I'm sorry if I've been ticking you off. That's definitely NOT my intention. But I want to make clear that previous criteria claimed for keeping this particular repo up to date have been met days before the weekly update cycle, but that weekly cycle didn't pick up this update on the unstable tag. So lets keep this to the technical reasons why this was, not on a personal level. If there's some other reason fine. I'm just calling out that something broke here. Also the reasoning of why to choose LinuxServer.io's repos versus others, is because they have been reliable in pretty much every other repo.
  5. Fair enough, I wasn't proposing to do things at the drop of a hat. I was proposing that if the source of the images were posted as has been deemed as the previous requirement for updating the unstable tag, then the pipeline should have picked up that version on the weekly update, but didn't, then something is wrong. It's not a personal attack against you, so don't take it as such. My response to yours was because your response went against what even LinuxServer.io's site says. As for the importance of this release... 5.10.12 is actually very important from a security perspective due to an open known exploits in the wild. Lots of us really do need this version to mitigate possible attacks/scans that are occuring: https://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-Network-Controller-5-10-12-Stable-has-been-released/ba-p/2665341
  6. Also... if you want to claim that, then don't have this on your website's main motto: "We make and maintain container images for the community." Because if you claim that, then yes, Linuxserver.io DOES purely exist to keep every repository software updated. That's the point.. If not why use Linuxserver.io in the first place. I love you guys for keeping one place where to have reliable repo sources, but to claim that it's not why you're here is disingenuous at best.
  7. Understood and much appreciated on the family/lives front. Wish I had time to contribute as well. That said, previous excuse of "it has to be on the download page" rarely applies anymore, so its probably best not to use it and just say "we'll get to it when we get to it". And yes, it is stuck on 5.9.x on unstable at the moment so don't know why you wouldn't think that. If you create a new container and point it to the unstable tag, you don't get 5.10.x so yes, stuck meaning it's still on previous version release is valid. Side request (and probably can't be tackled for awhile so I guess more of a wishlist item): since naming conventions count to some of us for tags, and fully understanding previous issues leading to your team keeping the latest "stable" releases from Ubiquiti as "unstable" tags because of their software f' ups. Can we have something like this instead? Long Term Release: /latest Latest UBNT deemed stable release: /ubntstablerelease Latest UBNT beta release: /beta That way default is always longterm and more likely to be stable. This also avoids calling something "unstable" when that particular beta or "stable" release may actually be really stable.
  8. Have you read some of them? Previous criteria was that latest releases are available in UBNT's download page before they appear in Unstable tag. UBNT has had 5.10.12 available on it's download page for a few days now: https://www.ui.com/download/unifi The Unstable tag had an update 2 days ago (more than a day after 5.10.12 was available from the download page) yet its still stuck on 5.9.x. So...
  9. Well now that 5.10.12 is on the download page: https://www.ui.com/download/unifi/ I was expecting the latest "unstable" tag to get it, especially since I saw there was an update last night. But no, the Unstable tag does not have the fully released version yet. Can you guys push one out instead of waiting another week since it WAS on the download page before the latest Unstable tag was updated last night?
  10. Extremely appreciated! Can't wait until 6.7 hits stable release.
  11. I'm seeing the following error for the speedtest-for-influxdb-and-grafana container in the log after the latest update and then the container stops: Traceback (most recent call last): File "/src/InfluxdbSpeedtest.py", line 9, in <module> from influxspeedtest.common import log ImportError: No module named 'influxspeedtest'
  12. Definitely a bummer... thanks anyway. If you encounter something in the future that you may want to try, I can test. If it helps any, here's the github repo for the Absolute Series Scanner and HAMA agent with plugin and scanner install instructions: https://github.com/ZeroQI/Hama.bundle Thanks!
  13. Barely generates anything when it errors out... This is what that log has: :/mnt/cache/appdata/NowShowingv2/logs# tail nowshowing.log I, [2018-03-28T20:51:36.777404 #1208] INFO -- : Announcement Email Sent. I, [2018-03-28T20:54:53.374364 #1213] INFO -- : Starting up NowShowing I, [2018-03-28T20:58:53.251809 #1226] INFO -- : Starting up NowShowing I, [2018-03-28T21:01:42.762540 #1239] INFO -- : Starting up NowShowing I, [2018-03-28T21:42:04.322653 #1188] INFO -- : Starting up NowShowing And the container log has this after a fresh restart and test report run: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 10-apply-perms: applying... [fix-attrs.d] 10-apply-perms: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-set-uidgid: executing... usermod: no changes ----------------------------------------- NowShowing ----------------------------------------- Brought to you by: Ninthwalker/GroxyPod/Limen75 ----------------------------------------- User xyz set to: 99 Group xyz set to: 100 ----------------------------------------- [cont-init.d] 10-set-uidgid: exited 0. [cont-init.d] 20-setup: executing... Advanced config file detected. Keeping existing files rm: can't remove '/etc/fail2ban/jail.d/*': No such file or directory Server ready Please go to http://hostServerIP:hostPort/admin to configure settings [cont-init.d] 20-setup: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2018-03-28 21:40:41: (log.c.217) server started /usr/local/sbin/combinedreport: end of file reached (EOFError)
  14. Looks like I'm getting the same old error I used to get with the last versions of the old PlexReports and original Now Showing even with my HAMA based Anime Library excluded: /usr/local/sbin/combinedreport: end of file reached (EOFError) This shows in the log everytime I run a test. SMTP setup works with the announcement email. I'll note (just as I did sometime last year) that I used to be able to run PlexReports without issue since it ignored my HAMA agent based Anime Library, and at some point (probably same time PlexReports started having issues with empty/blank Libraries) PlexReports stopped working. Now Showing V1 and now V2 doesn't seem to fix this situation. I added my Anime Library to the Plex Settings/Libraries To Skip, but it still hits this EOFError. I even added all my personal family video libraries and other home video libraries that shouldn't be an issue to the Libraries To Skip list, only leaving Movies, TV Shows, and my music libraries (which this should be skipping anyway since they're not videos). Still no go.