Web UI Plugins Page Not Loading, Dockers not updating (vmdk)


Recommended Posts

16 hours ago, uldise said:

i suggest you upgrade your ESXi to version say 6.5. don't go with 6.7, as they removed support for old CPUs, if you have an older system.

and with 6.5 you can't use old legacy vsphere client for management anymore, only from your browser. 

My only noticeable issues are the web UI Plugins tab/Page Not Loading/listing plugins and the repetitive USB reset/refreshes in syslog. However, I'm preparing to upgrade my esxi host from 5.5 to 6.5u2 today. 

Link to comment
2 minutes ago, guruleenyc said:

However, the Plugin screen on the web UI still does not load. It hangs indefinitely. All other UI screens work fine.

I will attach a new diagnostic file shortly...

That page goes to the internet to check for updates. Maybe something not working like DNS.

Link to comment
7 minutes ago, trurl said:

That page goes to the internet to check for updates. Maybe something not working like DNS.

Here is what is showing in my log:

 

Nov  9 14:16:32 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Nov  9 14:18:25 Tower nginx: 2018/11/09 14:18:25 [error] 5020#5020: *7451 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.186, server: , request: "GET /plugins/dynamix.plugin.manager/include/ShowPlugins.php?check=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "172.16.1.5", referrer: "http://172.16.1.5/Plugins"
Nov  9 14:46:49 Tower kernel: docker0: port 3(vethcc2c99d) entered disabled state
Nov  9 14:46:49 Tower kernel: vethda8698c: renamed from eth0
Nov  9 14:46:49 Tower avahi-daemon[4966]: Interface vethcc2c99d.IPv6 no longer relevant for mDNS.
Nov  9 14:46:49 Tower avahi-daemon[4966]: Leaving mDNS multicast group on interface vethcc2c99d.IPv6 with address fe80::d06f:18ff:fefb:b4c2.
Nov  9 14:46:49 Tower kernel: docker0: port 3(vethcc2c99d) entered disabled state
Nov  9 14:46:49 Tower kernel: device vethcc2c99d left promiscuous mode
Nov  9 14:46:49 Tower kernel: docker0: port 3(vethcc2c99d) entered disabled state
Nov  9 14:46:49 Tower avahi-daemon[4966]: Withdrawing address record for fe80::d06f:18ff:fefb:b4c2 on vethcc2c99d.
Nov  9 14:47:03 Tower kernel: docker0: port 3(vethcb01bb1) entered blocking state
Nov  9 14:47:03 Tower kernel: docker0: port 3(vethcb01bb1) entered disabled state
Nov  9 14:47:03 Tower kernel: device vethcb01bb1 entered promiscuous mode
Nov  9 14:47:03 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethcb01bb1: link is not ready
Nov  9 14:47:03 Tower kernel: docker0: port 3(vethcb01bb1) entered blocking state
Nov  9 14:47:03 Tower kernel: docker0: port 3(vethcb01bb1) entered forwarding state
Nov  9 14:47:03 Tower kernel: docker0: port 3(vethcb01bb1) entered disabled state
Nov  9 14:47:05 Tower kernel: eth0: renamed from vethc7aca2a
Nov  9 14:47:05 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethcb01bb1: link becomes ready
Nov  9 14:47:05 Tower kernel: docker0: port 3(vethcb01bb1) entered blocking state
Nov  9 14:47:05 Tower kernel: docker0: port 3(vethcb01bb1) entered forwarding state
Nov  9 14:47:07 Tower avahi-daemon[4966]: Joining mDNS multicast group on interface vethcb01bb1.IPv6 with address fe80::9475:63ff:feed:9a12.
Nov  9 14:47:07 Tower avahi-daemon[4966]: New relevant interface vethcb01bb1.IPv6 for mDNS.
Nov  9 14:47:07 Tower avahi-daemon[4966]: Registering new address record for fe80::9475:63ff:feed:9a12 on vethcb01bb1.*.

EDIT: I just turned off all vswitch security options to see if this makes a difference.

Edited by guruleenyc
Link to comment

Nov  9 13:49:22 Tower nginx: 2018/11/09 13:49:22 [error] 5020#5020: *2939 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.101, server: , request: "GET /plugins/dynamix.plugin.manager/include/ShowPlugins.php?check=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "172.16.1.5", referrer: "http://172.16.1.5/Plugins"
Nov  9 13:53:57 Tower root: Fix Common Problems: Other Warning: Could not perform unknown plugins installed checks
Nov  9 13:53:58 Tower root: Fix Common Problems: Warning: Docker application plexpy has moderator comments listed
Nov  9 13:53:58 Tower root: Fix Common Problems: Other Warning: CPU possibly will not throttle down frequency at idle
Nov  9 13:54:00 Tower root: Fix Common Problems: Other Warning: Could not perform docker application port tests
Nov  9 14:16:32 Tower emhttpd: req (2): csrf_token=****************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog
Nov  9 14:16:32 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
Nov  9 14:18:25 Tower nginx: 2018/11/09 14:18:25 [error] 5020#5020: *7451 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.186, server: , request: "GET /plugins/dynamix.plugin.manager/include/ShowPlugins.php?check=0 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "172.16.1.5", referrer: "http://172.16.1.5/Plugins"
 

Link to comment

When I run the Fix Problems plugin from settings screen, it also appears to hang and I see this in the logs:

 

Nov  9 15:09:14 Tower nginx: 2018/11/09 15:09:14 [error] 5020#5020: *12912 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.186, server: , request: "POST /plugins/fix.common.problems/include/fixExec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "172.16.1.5", referrer: "http://172.16.1.5/Settings/FixProblems"
 

My Community Apps, Nerd Pack, and all other screens appear to be fine.

Link to comment
On 11/11/2018 at 12:42 PM, Squid said:

Have you tried Settings - Notification Settings, and then disabling Plugin Update Checks.

 

Plugin page should load at that point.  And what would happen after that if you check for updates within the page

That did the trick! :-)  My plugins page now loads and lists all plugins after I disabled plugin update checks under Notifications.

So I then went to Plugins > and now I see all my plugins listed. I click update for the Unassigned Devices plugins and it updated successfully. If that's the case, then why is the plugin update notification hanging things?

 

However, if I go to Plugins and click check for updates, it hangs.

Edited by guruleenyc
Link to comment

No idea.  Probable work around is to install CA Auto Update applications.  It will check in the background for updates.  If you don't want it to actually update anything and want to do it manually, just check off everything to not auto update.  It will still show the updates being available on the plugins page.

Link to comment
10 hours ago, Squid said:

No idea.  Probable work around is to install CA Auto Update applications.  It will check in the background for updates.  If you don't want it to actually update anything and want to do it manually, just check off everything to not auto update.  It will still show the updates being available on the plugins page.

I will see if CA Auto Update plugin, which is already installed, succeeds at updating my plugins since the 'Check for updates' button /function hangs.... 

Link to comment

My plugins and and dockers are still not updating. I have removed pfsense from the picture and connected unraid directly to ISP router with no firewall rules. When I attempt to update a docker in example below, it appears to update, but then after refreshing the dockers page it still shows update ready.

2018-11-16_10-45-35.png.96ad6922b5be0c97dbbe362aef4131f3.png

 

Attached are my unraid diagnostic files for review.

 

Thank you in advance,

tower-diagnostics-20181116-1045.zip

Link to comment
  • 2 weeks later...

UPDATE: I uninstalled openVMTools_auto.plg-10.2.5 on my unRAID 6.5.2 and my Docker updating seems back to normal. But my plugin update check appears to hang indefinitely. 

 

The only issue I am seeing that may be related is the Fix Problems plugin reports this:

Quote

Unable to communicate with GitHub.comReset your modem / router or try again later, or set your  to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Router's IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins

But at the CLI I can ping by DNS and resolve DNS addresses. Moreover, Docker updates succeed. 

 

Any ideas?

Link to comment
  • 4 weeks later...
  • 4 months later...
On 1/2/2019 at 10:25 AM, guruleenyc said:

Bump; anyone have similar problems with openVMTools_auto.plg-10.2.5? I'm not totally convinced its the openvmtools....

Update: I decommissioned my unraid VMDK and went bare metal. Pleased with added performance and Unraid's VM capabilities. This thread can be closed.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.