Jump to content

Squid

Community Developer
 View Profile  See their activity

  • Posts

    28,770

  • Joined

  • Last visited

  • Days Won

    314

 Content Type 

Everything posted by Squid

  1. Squid
    This test was put in by @ljm42 I'm glad that it did work correctly and found the invalid configuration.
  2. Squid
    I'm too lazy to figure out stuff in bash that I can do in 2 seconds in php
  3. Squid
    The first part is to be expected after the update. The second part is a known issue
  4. Squid
    6.9 requires a password to login via SSH. If it worked after the upgrade, then it only worked by accident. But what you want is effectively pointless (No GUI password, but password for SSH) since if you don't set a password for the GUI, you've still got access to the terminal via the icon within the GUI. Why do you need no password on the GUI and a password on SSH?
  5. Squid
    You can't.
  6. Squid
    Yeah. (I never read the OP 😄) Set everything to Yes. Stop Docker in Settings - Docker. Run mover. Wait for it to finish. Re-enable and set everything back to Prefer. Run Mover
  7. Squid
    As an aside, you most likely want appdata and domains, and system to be set to useCache: Prefer Depending upon how you do things, you may also want Downloads set the same way.
  8. Squid
    https://forums.unraid.net/topic/57181-docker-faq/#comment-566084 Then throw the resulting xml within /boot/config/plugins/community.applications/private/someNameHere/{filename}.xml It'll show up within the Private category on CA and is as close as you'll get to how it'll get handled via the appfeed if / when its added to CA
  9. Squid
    Changed Status to Retest
  10. Squid
    If under Notification Settings dynamix is set to check for plugin updates on a schedule in the background, then every time you go to the Plugins tab an update check is also performed. Since that happens, no "Check For Updates" button appears.
  11. Squid
    Huh? You just said you had access to the WebGUI. If you need access to SSH then you have to have a password. This is part of 6.9, and no easy way around it. I don't see how you're "hosed". If you insist on having no password and insist on having SSH access your solution is to go back to 6.8.3
  12. Squid
    A password is required if you want SSH access. No (easy) way around it.
  13. Squid
    Yup. It's the vmbackup plugin Delete vmbackup.plg from /config/plugins on the flash drive and reboot If you don't / can't reboot, then also rm -rf /usr/local/emhttp/plugins/vmbackup will fix it up.
  14. Squid
    It's never been. But, you won't be able to log in via SSH to the terminal if you don't
  15. Squid
    That's the general way to do it. Alternatively instead of rebuilding the drive you would do a Tools - New Config, keep all the assignments and when starting the array make sure you check off that Parity is already valid. BUT, the downside to that is that a write to the drive did indeed fail (hence why the drive is disabled), and since the write failed, Parity reflects the write, but the drive doesn't. Ergo, the contents of the drive differs (slightly) from what is currently being emulated.
  16. Squid
    So long as you have a password, you will always get asked after a reboot, etc. Remove the password via the users tab (change the password to a "space" on both entries, then remove what you just typed and hit apply)
  17. Squid
    What version of Unraid? You need to be running 6.9.0 for the network to work From the console, diagnostics And then post the resulting file here (logs folder on the flash drive)
  18. Squid
    Try disabling / uninstalling the S3 Sleep plugin.
  19. Squid
    It would look like when this happens is that your system is running out of memory, and it kills off some processes (in the case in the syslog, it killed your VM). What you've got to do is figure out what else is happening in the system when this goes on. Perhaps limit the memory allowed to any and all the other docker apps present.
  20. Squid
    Memory errors. Your system event log will probably have more info on which stick Mar 1 20:11:08 Helios kernel: EDAC MC0: 1 CE memory read error on CPU_SrcID#0_Ha#0_Chan#3_DIMM#0 (channel:3 slot:0 page:0x51a029 offset:0xd00 grain:32 syndrome:0x0 - area:DRAM err_code:0001:0093 socket:0 ha:0 channel_mask:8 rank:0)
  21. Squid
    Have you run a memtest yet? Set the Power Supply Idle Control to be "typical"?
  22. Squid
    Because the command line bypasses the entire system of mount points, since you're navigating on both to be /mnt/user/abc and /mnt/user/def so the mount point in both cases is /mnt/user Along with included / excluded, useCache settings. Because of the single mountpoint
  23. Squid
    That got changed awhile ago. But, the error code sometimes being returned is a different issue (It appears to happen if the plugin is already installed) Solution appears to be to uninstall the plugin, reboot then reinstall. The bigger problem is that 2021.02.03 doesn't actually work and causes display corruption, etc.
  24. Squid
    While it's not marked as being incompatible yet it is currently incompatible with 6.9.0 stable. I've let @JTok know the errors in the support thread that's causing this. I give people some time to fix problems before I mark stuff as being incompatible.
  25. Squid
    The problem with the GUI corruption is that a couple of the .page files are saved in Windows format, not Linux (ie: \r\n instead of \n) Couple other issues is that every .page file has to have Menu="vmbackup:x" and not Menu="Vmbackup:x"
×
×
  • Create New...