-
Posts
28,691 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by Squid
-
-
1 hour ago, dlandon said:
You can set up the syslog server to log to itself and logs will go to the syslog share. You have to set it up on the syslog server itself. i.e. if the syslog server is 192.168.1.10, you can set the syslog server on 192.168.1.10 to log to itself by setting 192.168.1.10 in the syslog setup.
Nobody thinks of it like that, and it's never actually logged anything in my system setting the syslog server to the IP or 127.0.0.1. For remote systems it works no problems
-
45 minutes ago, theangelofspace15 said:
Now I have it setup with a share called `logs` Let see if if happens again
That won't work. It's a common misconception of the syslog server. The share option is for where to send logs that are incoming (eg from another server). You want the mirror to flash
-
You system / network is unable to download the icons after the first installation. (After it downloads once, they are cached) Alternatively, your docker image is very corrupt.
For the dashboard, does this happen if you close the browser down? Are you automatically clearing cookies when closing the browser?
-
Did you remake the flash drive? That happens if the template isn't within /config/plugins/dockerMan/templates-user on the flash drive (eg: you inadvertently deleted it), is corrupt etc
- 1
-
Nothing to do with docker folder, and a reboot might fix but may only be temporary. Did you delete the xml files from /config/plugins/dockerMan/templates-user
That's the only time that message would pop up if the installed container references a template that does not exist or if you pulled out the flash drive and re-inserted, the flash dropped offline or if the drive has corruption on it.
-
2 hours ago, Kilrah said:
Doesn't this mean that a slow USB drive may now have more impact if things will have to be read from it regularly instead of RAM though?
If so then it would be better to have a choice, for many setups 1GB of RAM is negligible.
The operation of the OS hasn't changed in that respect. Flash drive speed only impacts boots.
-
Changed Status to Closed
- 1
-
Not a bug. The templates for the containers that you added are no longer on the flash drive or corrupted. They are stored in /config/plugins/dockerMan/templates-user
For docker being full, Container Size on the Docker tab should offer some insights as to what is going on
-
21 hours ago, CallOneTech said:
AD issue
There is a new plugin to also tweak the AD settings to try and come up with the solution(s)
- 2
-
1 hour ago, JonathanM said:
It already includes the latest version that is licensed for 3rd party redistribution.
Newer versions must be directly downloaded from the original website.
Actually, the GitHub repo linked (https://github.com/memtest86plus/memtest86plus) is GPL2.0 and could be included ( @limetech)
Would solve at least one major issue with the current version where it won't work with UEFI booting...
- 1
- 2
-
3 hours ago, frodr said:
Appdata backup plugin is not supported in 6.12rc2, and asked to upgrade according to fix common problems. No plugin to update though. I deleted the plugin and looked for it in the Apps store. Nowhere to be found.
It's marked as being incompatible with 6.12 (although I have no trouble with it). There is a manual install link in the support thread for the plugin for a replacement beta version)
You can install the deprecated one in 6.12 by enabling show incompatible and deprecated apps in CA's settings
- 1
-
4 minutes ago, ChatNoir said:
One thing you want to do if you're upgrading on a running machine via the manual method is move all of the bz* files from the root of the flash to the previous folder and then extract the zip contents onto the root of the flash.
Simply overwriting (which has been the suggestion in the forums for years) existing bz* files may cause issues / boot failures under certain circumstances
-
54 minutes ago, goodolwheatie said:
Probably not. I'm sure it's an oversight
-
1 hour ago, rogueosb said:
I'm getting a "No swap limit support" warning in docker, which prevents me from using the memory options for containers. See the "docker info" output below:
Thanks. You do get a warning, but the memory constraints you put in do work
- 1
-
14 minutes ago, winglam said:
I encountered 1 issue. mover doesn't seem to work. clicked move bottom & grey out, but nothing is being moved.
You'd have to enable mover logging in Settings - Schedules, Mover Schedule, try it again and then create a new thread with your diagnostics
- 1
-
-
1 hour ago, Bizquick said:
I hate having to waste a Disc to add to the top array that I wont use.
Nothing says you can't simply use a flash drive you have kicking around for the array
-
macvlan
Are you assigning dedicated IP addresses to one or more containers? Switching the network driver (settings - Docker with the service stopped) from macvlan to instead be ipvlan will probably fix you up
-
Collapsing is gone, and now you remove items instead to set it up how you like
-
12 minutes ago, isvein said:
Just me, or does Docker uses forever to check for updates?
Seems fine to me
-
Changed Status to Retest
-
Since the "Help" display hasn't been in CA for maybe 2 years now, I'd suggest to update CA to the latest version and try again.
CA definitely works on 6.12
-
NOTE
Any plugin which has been hacking its way into the dashboard has now been marked as being incompatible.
These plugins: GPU Stats, Corsair Power Supply, Disk Location and Plex Streams now actually crash the dashboard and it is highly recommended to uninstall them. They will not be available again via Apps until such time as the respective authors update their plugins to be compatible and notify me of this.
Also ensure that all other plugins are up to date. Notably, NUT and IPMI (versions from dmacias) will also crash the dashboard, but replacements for these are available within CA (from SimonF)
- 9
- 1
-
11 minutes ago, SimonF said:
it is awaiting merge of the PR by the owner
Thanks. I had thought that this had already been handled. Since the current release crashes the dashboard now, it is also being marked as incompatible.
Once the PR is merged and released and I'm notified of this then the incompatibility will be lifted.
- 1
Unraid OS version 6.12.0-rc6 available
-
-
-
-
-
in Prereleases
Posted
Really depends upon how you are set up if there will be an issue. It's the passing of /mnt or /mnt/user to a container where there is a problem and then accessing the exclusive share from it. (EG: on the Krusader app, /media gets mapped to /mnt/user. You can access everything from it except for the exclusive shares)
99.9% of the time this shouldn't be done, as it's a quick and dirty shortcut, and you are effectively giving the container access to your entire server (eg: Does Plex really need access to your banking information?)
In other words, most people will already have their appdata share being "exclusive" and its not an issue because it winds up getting passed through as /config -> /mnt/user/appdata)
But, as has been stated already it's being looked at.