[[6.9.2] GUI Docker page layout error in advanced view when container repository name is very long]

I made another update to fix this.

Thanks

 

[OpenSSL needs update (CVE-2021-3711 and CVE-2021-3712)]

rc2 will have version 1.1.1l

[Unraid OS version 6.10.0-rc1 available]

55 minutes ago, danioj said:

Rinse and repeat every two hours. Has anyone else noticed this?

How are your disks connected: SATA ports on the motherboard or a disk controller (which type)?

 

[[unRAID 6.10.0-rc1] - Seemingly random crashes]

Disable host access to custom networks and retest.

 

Btw ipvlan should have worked in your situation...

[not offering me the update from 6.9.2]

If the system has no internet connection, it is unable to retrieve information and won't show a new version.

Did you check your connection is working?

 

[Unraid OS version 6.10.0-rc1 available]

19 hours ago, DuzAwe said:

Had a random reboot this morning

Looks like a RAM issue, try to rum a memory test.

 

[[6.9.2] webUI docker IP/hostname not following actual access]

Docker networks are attached to the management interface (br0/eth0). This is expected behavior.

Not a bug.

 

[[6.9.2] Network connection speed reported as 1000 Mbps when it is really 10000 Mbps]

The GUI just reports what linux (the driver) is reporting.

I use 10G interfaces on different systems, have never seen this. When 10G is stays 10G.

 

 

[6.9.0/6.9.1 - Kernel Panic due to netfilter (nf_nat_setup_info) - Docker Static IP (macvlan)]

Why don’t you try Unraid version 6.10.0-rc1 ?

[[6.9.2] Non english file names in docker config path]

I made a correction, should be available in next version.

 

[Unraid OS version 6.10.0-rc1 available]

1 hour ago, Leoyzen said:

I don't care about IO wait at all....

On contrary, you should care about iowait.

Too high iowait makes your system slow and unresponsive even if you have a powerful CPU.

 

[[6.x.x] rsyslog filters do not affect local syslog]

6 hours ago, mgutt said:

So with Unraid 6.10 it should work by adding this to the Go file?

 

Yes, that will work.

Alternatively you can append the line to the existing file 01-blocklist.conf (which contains are messages to suppress)

 

 

[UnRaid 6.10.0-rc1 - Array won't stop, and will not reboot.]

Diagnostics of 6.9.2 won't help.

We need diagnostics of the new version and when the issue occurs.

 

The most common reason the array won't stop is a process or terminal session keeping files/folders opened.

Make sure you have nothing running or any open terminal sessions which may interfere.

 

[Unraid OS version 6.10.0-rc1 available]

2 hours ago, JorgeB said:

Just upgraded a test server and don't see one of my pools in the main GUI page

This is a bug.

I can reproduce the issue and working on a fix.

 

Made a fix, should come in rc2

[Unraid OS version 6.10.0-rc1 available]

15 minutes ago, kaiguy said:

The crash you refer to is when enabling the host access to custom networks option, yes?

There are mixed reports. Host access seems to be one of the possible causes, but not the only cause.

Some people -including myself - never experience crashes, this makes it hard to troubleshoot.

 

18 minutes ago, kaiguy said:

is there any benefit (or drawback) from switching to ipvlan?

macvlan and ipvlan achieve the same purpose: a dedicated network with isolation

According to the Docker documentation ipvlan is a more lightweight implementation, which may benefit performance.

There are some minimum linux version and docker version requirements to use ipvlan, but obviously these are met in Unraid.

 

21 minutes ago, kaiguy said:

Any help to the cause just in general testing in normal usage?

It will help me (us) tremendously if people test and confirm that switching from macvlan mode to ipvlan mode solved their crashing issue.

 

[Unraid OS version 6.10.0-rc1 available]

I like to highlight other improvements available in 6.10, which are maybe not so obvious to spot from the release notes and some of these improvements are internal and not really visible.

 

- Event driven model to obtain server information and update the GUI in real-time

• The advantage of this model is its scalability. Multiple browsers can be opened simultaneously to the GUI without much impact
• In addition stale browser sessions won't create any CSRF errors anymore
• People who keep their browser open 24/7 will find the GUI stays responsive at all times

- Docker labels

• Docker labels are added to allow people using Docker compose to make use of icons and GUI access
• Look at a Docker 'run' command output to see exactly what labels are used

- Docker custom networks

• A new setting for custom networks is available. Originally custom networks are created using the macvlan mode, and this mode is kept when upgrading to version 6.10
• The new ipvlan mode is introduced to battle the crashes some people experience when using macvlan mode. If that is your case, change to ipvlan mode and test. Changing of mode does not require to reconfigure anything on Docker level, internally everything is being taken care off.

- Docker bridge network (docker0)

• docker0 now supports IPv6. This is implemented by assigning docker0 a private IPv6 subnet (fd17::/64), similar to what is done for IPv4 and use network translation to communicate with the outside world
• Containers connected to the bridge network now have both IPv4 and IPv6 connectivity (of course the system must have IPv6 configured in the network configuration)
• In addition several enhancements are made in the IPv6 implementation to better deal with the use (or no-use) of IPv6

- Plugins page

• The plugins page now loads information in two steps. First the list of plugins is created and next the more time consuming plugin status field is retrieved in the background. The result is a faster loading plugins page, especially when you have a lot of plugins installed

- Dashboard graphs

• The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)
• The CPU graph may be hidden as well in case it is not desired
• Both graphs have a configurable time-line, which is by default 30 seconds and can be changed independently for each graph to see a longer or shorter history.
• Graphs are updated in real-time and are useful to observe the behavior of the server under different circumstances

 

 

[Unraid OS version 6.10.0-rc1 available]

10 minutes ago, Frank1940 said:

This reminded me of something.

Thought it was addressed, but apparently it felt through the cracks.

Something for rc2 ...

[[6.9.2] Adding VMs to br0 slows performance using AQC107 10Gbe ethernet]

Each VM takes resources away, especially CPU resources, which impacts single stream performance.

You need to test with multiple streams to see the true limitation of your network.

 

I am using the AQC107 chipset too (Asus NIC) and have 5 VMs running:

 

Test 1: PC to server (4 streams)

C:\Tools\iperf>iperf3 -c 10.0.101.11 -i0 -P4
Connecting to host 10.0.101.11, port 5201
..
..
[SUM]   0.00-10.00  sec  11.0 GBytes  9.49 Gbits/sec                  sender
[SUM]   0.00-10.00  sec  11.0 GBytes  9.49 Gbits/sec                  receiver

 

Test 2: Server to PC (4 streams)

C:\Tools\iperf>iperf3 -c 10.0.101.11 -i0 -P4 -R
Connecting to host 10.0.101.11, port 5201
Reverse mode, remote host 10.0.101.11 is sending
..
..
[SUM]   0.00-10.00  sec  10.9 GBytes  9.38 Gbits/sec    0             sender
[SUM]   0.00-10.00  sec  10.9 GBytes  9.37 Gbits/sec                  receiver

 

 

[[6.10.0-rc1] wsdd-mcast-v6 recurring error in log]

8 hours ago, bonienl said:

You likely have docker veth interfaces with ipv6 in use, causing this message.

 

Under Settings -> SMB -> WSD options, add

-4 -i br0

 

This limits wsd to ipv4 only and let it listen to interface br0 only (assuming you have br0)

 

[Unraid OS version 6.10.0-rc1 available]

1 hour ago, nuhll said:

any fix to the anoying 

You likely have docker veth interfaces with ipv6 in use, causing this message.

 

Under WSD options, add

-4 -i br0

 

This limits wsd to ipv4 only and let it listen to interface br0 only (assuming you have br0)

[[6.9.2] Non english file names in docker config path]

Your Docker service failing to start is a different issue.

We need diagnostics to see what happened.

 

In Unraid 6.10.0-rc1 Russian names are properly displayed in the dropdown menu.

 

[Unraid OS version 6.10.0-rc1 available]

Limetech has highly automated the process to replace or upgrade registration keys. This is an attempt to help users quicker and get their system up-and-running faster in case disaster strikes, but this brings 'other' challenges; you don't want rogue users to abuse the system.

 

Pretty sure emails can still be used to communicate with Limetech and address issues in the more traditional way.

 

[Unraid OS version 6.10.0-rc1 available]

2 minutes ago, sjaak said:

i prefer the old way, unraid works fully offline

This is still true (assuming you have a registered version, not trial).

You can happily keep using Unraid without the UPC functionality, but you will loose convenience when something goes wrong and your registration key or configuration gets lost.

 

[Unraid OS version 6.10.0-rc1 available]

59 minutes ago, peter76 said:

because the paths

/mnt/user/...... don't exist any more.

 

You have not (never) enabled user shares, see Settings -> Global Share Settings -> Enable user shares.

 

Unraid 6.10 has these disabled by default, as part of the hardened security measures.

 

[Unraid OS version 6.10.0-rc1 available]

2 minutes ago, trurl said:

Looks like you can't really remove it from the plugins page after upgrade because it no longer appears on the plugins page.

 

The plugin is automatically uninstalled after the upgrade.