[Getting false OS update notice]

3 minutes ago, dlandon said:

Next.

 

Ok, that's wrong. Need to investigate. Thanks.

[Getting false OS update notice]

Just now, dlandon said:

6.5.0 in the latest situation of false positive.

 

And what about this file /tmp/plugins/unRAIDServer.plg ?

 

Does it say category = stable or next ?

[Getting false OS update notice]

Ah, if I understand correctly. You are on a stable release and still receive a notification about the RC release?

 

[Getting false OS update notice]

2 minutes ago, dlandon said:

Changed Status to Open

 

Huh? Did it happen again to you?

 

What version is reported in /usr/local/emhttp/plugins/unRAIDServer/unRAIDServer.plg ?

[Getting false OS update notice]

30 minutes ago, dlandon said:

I'm considering this a one time fluke.

 

I am not sure what caused it (that part of the code didn't change), still on the 4 times a day check without notifications.

[Getting false OS update notice]

For testing purposes I let the check for updates run 4 times a day, until now no false positives...

[Docker page loading indicator spinning]

Thanks for the update.

 

I have installed "untelegraf" as well, but it is running fine no hang ups since installing yesterday.

 

There are reports on the Docker forum about more people not able to stop containers. It could well be a bug in docker. To be continued.

 

[spaces in Server Name cause problems]

When a name is automatically changed corrected, perhaps add a syslog entry saying something like "Invalid host name XXX corrected to YYY" ?

[Docker page loading indicator spinning]

There are some reports of people with similar issue and not being able to stop a container. Apparently a recurring issue since the introduction of 'containerd' and still present in version 17.12.1-ce. Some people downgraded to version 12.09 as a workaround.

 

Here is a link

[Docker page loading indicator spinning]

Is there anything interesting in /var/log/docker.log (might be a big file)?

 

You can also get the logs of a container

docker logs untelegraf

 

[Docker page loading indicator spinning]

Try to stop the containers, the command below attempts to stop all running containers.

docker stop $(docker ps --format='{{.Names}}')

Let me know if some containers can't be stopped and which one(s).

 

Our posts crossed

[Docker page loading indicator spinning]

May I ask everybody who had the Docker tab hanging to execute the below command (just copy + paste) and see if this succeeds.

docker inspect --format='{{.State.Running}}#{{range $p,$c := .HostConfig.PortBindings}}{{$p}}:{{(index $c 0).HostPort}}|{{end}}#{{range $p,$c := .Config.ExposedPorts}}{{$p}}|{{end}}#{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}#{{range $c := .HostConfig.Binds}}{{$c}}|{{end}}' $(docker ps -a --format='{{.Names}}')

Thanks

[Same Call Trace as in 6.5.0 diagnostics attached]

11 minutes ago, andreidelait said:

I've used firefox and chrome yesterday. It crashed while using the Samsung TV.

However as I mentioned there are users experiencing this without even having plex installed.

 

It is also my believe that the issue is not related to a specific application, but a general communication issue (lots of applications use TCP to communicate).

 

[Same Call Trace as in 6.5.0 diagnostics attached]

19 minutes ago, Bobat said:

The client was a Roku box hooked up to my TV, so no browser involved.

 

It was a short in the dark, didn't know what client you were using.

[Same Call Trace as in 6.5.0 diagnostics attached]

6 hours ago, Bobat said:

One local stream, so not particularly heavy traffic.

 

Which browser are you using the view Plex streams?

 

Microsoft browers are known to use RST (reset) quite often when something goes wrong in the communication, e.g. missing packet. Perhaps viewing with a different browser gives better results?

[Docker page loading indicator spinning]

Clear your browser cache, see if that makes a difference.

 

[Same Call Trace as in 6.5.0 diagnostics attached]

Reading that link about the patch...

 

The linux guys introduced at some point a patch to purge the TCP write queue when a TCP session is reset (RST), but forgot to reset the send part, which can result in a NULL pointer dereference.

 

Sending a TCP RST command is quite common to restart a TCP session, can happen when for instance both parties get out of sync due to heavy and/or missing traffic and decide to start over again. Perhaps people experiencing the call traces see this happening when heavy downloading/uploading is taking place?

 

[mover started/finished lines not getting logged]

How to squeeze bugs fast...