Jump to content

Squid

Community Developer
  • Posts

    28,770
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Make sure this is checked off in Settings - Docker (advanced view) with the service stopped
  2. Or just disable the built-in nic in the BIOS, unless your switches support failover, bonding etc.
  3. Supposed to be ok to reinstall now
  4. Then something was bombing your server with initialization at the time and has now levelled itself out.
  5. No, but you then have to manage everything yourself instead of the OS You do the stubbing via system devices Either there or in Settings - CPU pinning. Doesn't matter as CPU Pinning writes the entries to syslinux. no
  6. First place to start is https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173 But I would also update to 6.9.1 as the later kernels have better Ryzen support And also run a memory test for a minimum of a single pass (ideally a couple of them)
  7. Somethings up. It took FCP 30 seconds to basically return the first issue (during which time it also wound up downloading some files) Mar 10 20:05:00 Tower root: Fix Common Problems Version 2021.03.07 Mar 10 20:05:27 Tower nginx: 2021/03/10 20:05:27 [error] 9524#9524: *2394 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.16.0.2, 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.0.1", referrer: "http://172.16.0.1/Plugins" Mar 10 20:05:31 Tower root: Fix Common Problems: Warning: Share appdata set to not use the cache, but files / folders exist on the cache drive ** Ignored Ma Then in the middle of it there's another 2 minute pause Mar 10 20:05:54 Tower root: Fix Common Problems: Warning: Deprecated plugin dark.theme.plg ** Ignored Mar 10 20:07:03 Tower nginx: 2021/03/10 20:07:03 [error] 9524#9524: *2509 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.16.0.2, 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.0.1", referrer: "http://172.16.0.1/Plugins" Mar 10 20:07:52 Tower root: Fix Common Problems: Warning: Docker application marcvidalmartinez has moderator comments listed And then it finally finished Mar 10 20:11:08 Tower root: Fix Common Problems: Other Warning: Background notifications not enabled 6 minutes to run something that should only require maybe 20 seconds. In the middle of all of this you checked for plugin updates (20:05:03) and it timed out at 20:07:03 How is the speed on plugin checks if you go to Notification Settings - Disable Check for plugin updates, then Plugins and Press Check for Updates? You've got it in Network settings 3 times. Once is enough, and the others should point to alternatives in case the one fails.
  8. Post your diagnostics to see if there's something obvious there.
  9. Post your diagnostics. But, odds on you've got internet connectivity issues
  10. Clear your browser cache @dlandon
  11. Is the keyboard still connected? Edit the VM and uncheck that.
  12. Have you considered that the battery is no good?
  13. Works for me. Where are you doing this?
  14. Reseat the cabling to all drives. You probably slightly disturbed them.
  15. Post a new set of diagnostics
  16. Is /UNASSIGNED mapped to /mnt/disks with Read/Write:SLAVE in Krusader's template?
  17. Best guess is that the flash drive dropped completely offline. A reboot will be necessary to fix. Another option is massive corruption on the flash drive
  18. Thanks for the fix Trouble though with what you've done is that many users may not be aware of the issue (ie: the plugin may have auto updated), and if at some point when they do check out the webUI they'll have the issues on a version of the plugin which is already fixed. Why not bump the version of the plugin so that every version to avoid any issues?
  19. When its on it's own specific IP address (br0), all port mappings are ignored by docker itself
×
×
  • Create New...