jademonkee

Members
  • Posts

    236
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Somerset, England

Recent Profile Visitors

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

jademonkee's Achievements

Explorer

Explorer (4/14)

29

Reputation

  1. It's now populated with traffic, like HTTP over TLS SSL, Facebook, GMail, Google APIs (SSL), and "Unknown". I'd still prefer current bandwidth usage, but it's better than the previously empty graphs. And I don't know if it's because I use my own DHCP rather than the one in the USG, but the "Client device types" pie chart remains populated with only one type ("Others") so isn't particularly useful. So, a mild improvement, but an improvement all the same.
  2. To be honest, it wasn't a particularly rigorous test... I turned it on, and set a Linux ISO to download over Usenet. It was about half the usual speed (~20MB/s vs ~40MB/s). By the time I'd turned it back on, that download had finished. So I grabbed a different ISO and tried that and it was fast again. I took it that, as I'd previously disabled it, this must be why. HOWEVER, sometimes different downloads connect to different (slower) Usenet servers, so it's not unusual for my downloads to occasionally be significantly slower. I shall try it again today to see if it does really impact me as much as I thought. To answer your Qs: QoS is off Threat management/IDS/IPS is off Hardware offloading is enabled (as is 'Hardware offload scheduler' whatever that is) UPDATE: I've enabled Traffic Identification and this time it didn't negatively affect my downloads. Last time must have been a coincidence. Thanks for the headsup!
  3. One thing I should probably also mention is to make sure that you don't use the (default) 'latest' tag in the docker image, but instead explicitly state a version (even if it's the latest one). That way you can check the Unifi forums (or here) to see if there's any bugs in a new version before upgrading to it, but still receive updates to the Docker image itself. As such, for the current latest version use this tag in the Docker 'Repository' value on the 'edit' page: linuxserver/unifi-controller:version-6.4.54 If you have already installed the Docker using the 'latest' tag, don't fret: just change the 'repository' value to the above, and you'll be fine. Note that if you have a 'latest' tag, you shouldn't try and downgrade to an earlier version: you're best off nuking the install and starting from scratch if you want to downgrade (just coz configs often change between versions). Info on tags here: https://hub.docker.com/r/linuxserver/unifi-controller/tags
  4. FWIW I have this same setup and am running the latest v6.4.54. Note however, that the front page on this version is pretty useless for the USG now, as I have a 500mbps internet connection, which is too fast for deep packet inspection to work without causing a bottleneck, and the front page now shows DPI info rather than current bandwidth usage. It can't currently be changed, either, so it just sits there being useless. Curiously, the Android app still shows bandwidth, so I now have to use that to see if something is eating my bandwidth. So, up until recently, 6 was fine. But if you have a fast internet connection and want useful info on the front screen, then stick with the version previous to v6.4.54, as it has bandwidth rather than DPI on the dashboard. Don't go any further back than that, though, as they start to get real flaky. As it's a new setup, I'd prob go to 6, as you're going to have to jump to that version sooner or later anyway, but the version recommended by JonathanM is perfectly fine, too. EDIT: I later found out that traffic analysis doesn't negatively effect bandwidth on my connection, so do ignore any above advice not to enable it.
  5. Out of curiosity, do you have in your logs: 211004 10:30:59 mysqld_safe Logging to '/config/databases/90d1ec1b4a9c.err'. 211004 10:30:59 mysqld_safe Starting mariadbd daemon with databases from /config/databases I have it in mine, but everything works fine (or at least seems to). Just wondering if I do the above 'downgrade, command, upgrade fix' if it will fix that problem, too. Cheers.
  6. I responded, and shall again: I have had no issues.
  7. Ok, so since upgrading (or since the weird error that reset the theme in the dashboard?) I no longer see traffic on my dashboard. Yay. I just love this company... EDIT: Unless it's just changed what's displayed there? It used to show the current bandwidth being used, but maybe it's now meant to show the results of the "traffic identification" option, which I have turned off. I've just turned it on, but it's still not showing anything. I'll give it a few minutes to populate... Any idea how to just show bandwidth being used again, like it used to? EDITEDIT: confirming that yes, the dashboard has changed to display the data gathered by the "traffic identification" option. Can also confirm that enabling the traffic management option severely reduces my throughput, so I have once again disabled it. EDITEDITEDIT: later further testing showed that enabling traffic management doesn't impact my bandwidth: my initial poor results were simply coincidence.
  8. I've had the same error in my log since the Alpine re-base. Nothing is broken on my end, though (I'm only using it for a single instance of Nextcloud with 2 users). I'm pretty sure someone in this thread told me it's nothing to worry about, but I would like to know why it's happening. 210927 12:23:15 mysqld_safe Logging to '/config/databases/e42e52e45c78.err'. 210927 12:23:16 mysqld_safe Starting mariadbd daemon with databases from /config/databases
  9. I just took the plunge. Will report back if anything strange happens. Something strange happened before I upgraded: the theme went to white (from dark) and it said that some WiFi options I had weren't compatible. I had changed nothing since I last upgraded, so don't know why. Maybe something corrupted in the db (again...)? So yeah: any problems I face may not actually be due to the upgrade, anyhow.
  10. You can see the available tags here: https://hub.docker.com/r/linuxserver/mariadb/tags?page=1&ordering=last_updated I don't know the difference between version-10.5.12-r0 and 10.5.12-r0-ls36 but maybe someone here can advise. If you swap to one of those versions, you'll stay on that version until you change the tag. (I think you may still get minor updates to the container, but not mariadb - someone will have to confirm). In saying that, it seems that "latest" would be one of those two, so it's probably no problem updating this time as the latest image is still some variant of the 10.5.12 version you're on (or even the exact same version), and - again - the problems were because of the 'rebasing' of the image, not an update to mariadb itself. So yeah. It's probably pretty safe to update - but there's also no harm in waiting for a few more people in the thread to speak of their experience.
  11. Sorry, it seems you misunderstood: Step 1 of the fix was to set the tag to a manual version, step 2 was to specify the 'latest' tag, which will always pull down the latest version. If you set the tag to the version you're currently on, it will stay on that version. Any Docker updates will just be to the related container files, not mariadb itself, so shouldn't break anything. In saying that, I have the latest update and it's fine. However, I didn't have a problem when I upgraded to the Alpine base (although it was suggested earlier in this thread that the errors happened only on larger DBs, as they took longer to shut down than was given by the "update" command. The tag swap 'fix' worked because it did a "shutdown" command before upgrading, which gave mariadb enough time to shut down gracefully before the update, so it gave the impression of it doing more than it really did).
  12. You can manually specify a version for mariadb to stay on, and it will stay on it (that's what the 'fix' earlier in this thread involved). However, the reason that things broke last update was because it moved to an Alpine base from Ubuntu. That won't happen again, so future updates should be fine (and may come with security benefits).
  13. Anyone here have any idea how to get this container to support AAC / M4A files? I added some to my library, but they don't even appear in the library after a scan, let alone allow me to play them. Any idea how to get them working? I don't know how to access the files mentioned here: https://wiki.slimdevices.com/index.php/AAC.html And don't know if FAAD2 is installed or not (nor how to install it). Thanks all!
  14. FYI Customer Support have said that my maintenance has now completed and it's now ok for me to log back in again, so I have done so. Will see if the sync finishes and report back if it does/doesn't. Here's the email as it contains some good info:
  15. I updated this morning and have this in the logs: It's not adding any extra lines (like, they're not repeating), and Swag + NextCloud are working fine (the only things that use it - and I don't even remeber if they both do, or just NC... heh)). Is that safe mode anything to worry about? Or is it all good?