chris1259

Members
  • Posts

    73
  • Joined

  • Last visited

Everything posted by chris1259

  1. "The client noticed that the server is not Elasticsearch and we do not support this unknown product" This is the same issue i had when i tested both elasticsearch dockers available in community applications for v6.6.2 and v7.10.2 at the time. Does this message have anything to do with licensing / forking the project? I installed Elasticsearch 8, as suggested by JAnguita, from the repository "docker.elastic.co/elasticsearch/elasticsearch:8.11.1", but it did not help. Additionally: On v8.11.1, running "/usr/share/elasticsearch/bin/elasticsearch-plugin install --batch ingest-attachment" no longer works and provides the message: "[ingest-attachment] is no longer a plugin but instead a module packaged with this distribution of Elasticsearch -> Please restart Elasticsearch to activate any plugins installed" I don't see occ installed, and do not know the name of the module.
  2. Thanks for the update. How did you discover the fix and where did you install the docker container from?
  3. Could this be referring to unRaid's OS and not the container? Open terminal in unRaid cp /etc/sysctl.conf /etc/sysctl.backup nano /etc/sysctl.conf paste vm.overcommit_memory = 1 save and reboot
  4. I still have the same issue. Now running v6.12.4 Nextcloud v27.0.2 elasticsearch v6.6.2
  5. Running v6.12.0-rc4.1 Tested both elasticsearch dockers available in community applications for versions 6.6.2 and 7.10.2. Up to this point everything appears to be working. When i run ./occ fulltextsearch:test at /var/www/html/, in the Nextcloud v26.0.1 container i receive the error: .Testing your current setup: Creating mocked content provider. ok Testing mocked provider: get indexable documents. (2 items) ok Loading search platform. (Elasticsearch) ok Testing search platform. fail In ProductCheckTrait.php line 32: The client noticed that the server is not Elasticsearch and we do not support this unknown product fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY] Is this a known issue? Or does this have anything to do with licensing / forking the project? I have not tried a more recent version of the elasticsearch yet. Thank you.
  6. "If the GUI cannot be accessed for any reason then using the diagnostics command from the Linux command line level will generate the same information and put the resulting zip file into the logs folder on the flash drive." Of course it's that easy 🙂 Thanks. I will give it another go and report back.
  7. If i could reach the server via SSH, is there a command i could run that would generate the diags? Thanks.
  8. I wanted to report an issue i experienced with v6.12.0-rc5. In short, 12+hrs after upgrading i lose access to the Web UI and samba shares. I did not check SSH, and I was not able to check the server locally before rolling back to v6.12.0-rc4.1, which has been stable, including all other RC's before 5. Gracefully powering down the server with a press of the power button will bring the server back, however, the issue repeats itself 12+hrs later. If anyone has any suggestions on what log i should monitor please let me know. Thank You. diagnostics-20230503-0805.zip
  9. First, thank you to @muwahhid and @rob_robot as their posts were very helpful. Running v6.12.0-rc4.1 Tested both elasticsearch dockers available in community applications for versions 6.6.2 and 7.10.2. Up to this point everything appears to be working. When i run ./occ fulltextsearch:test in the Nextcloud v26.0.1 container i receive the error: .Testing your current setup: Creating mocked content provider. ok Testing mocked provider: get indexable documents. (2 items) ok Loading search platform. (Elasticsearch) ok Testing search platform. fail In ProductCheckTrait.php line 32: The client noticed that the server is not Elasticsearch and we do not support this unknown product fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY] Is this a known issue? Or does this have anything to do with licensing / forking the project? I have not tried a more recent version of the elasticsearch yet. Thank you.
  10. This issue is not longer present since upgrading Firefox to v96.0.1 / v96.0.2 on Windows.
  11. Today i was not able to log into the WebUI after FireFox updated to v96.0 using the default username/password. Internet Explorer on Windows 10 21H2 did not work either. I had to use Microsoft Edge on Windows 10 21H2. I did not test Chrome. Firefox v95.0.1 on Xubuntu (Linux) does work. I am not asking for a fix, just sharing info.
  12. Is it documented anywhere what all of the default settings are when an unRaid server is booted for the first time? I tried searching in the unRaid Wiki, and only found a few settings. I understand that some of the "help balloons" in the server itself may state what the default settings are, but i was hoping for a complete list. I specifically would like to know the default settings for the use of a cache drive under user shares. Worst case i could boot a new copy of unRaid on another box and check manually. Example: appdata (only)? CommunityApplicationsAppdataBackup (prefer) ? isos (yes)? system (prefer)? Thanks
  13. I recently replaced 2 data drives at once when my last parity check was 7 or more days old. It worked fine. It should be noted that i have 2 parity drives.
  14. I am having a noVNC error myself since i upgraded to v6.8.0 and i posted it here.
  15. noVNC encountered an error: SyntaxError: import not found: supportsImageMetadata https://ServerName/plugins/dynamix.vm.manager/novnc/core/display.js:11:9 VNC driver: QXL Accessed WebGUI with Firefox v71.0 x64, Java 8 Update 231 x64 and Windows 10 1909 x64 (fully patched). Upgraded 3 servers from v6.7.2 to v6.8.0 without issue. One of the 3 servers displays this error when trying to VNC to any virtual machine through the WebGUI. Rebooting the server fixed it for the first connection, but then displayed the error again on additional attempts. I don't see any complaints about this in the system log, and I have not tried this from another machine yet. Is dynamix.vm.manager included in unRaid? Because the only plugins installed in December 2019 are Enhanced Log Viewer & Unassigned Devices. Off topic... Logs\libvirt.txt in the diagnostics log shows all of my VM's as "tainted". I found a thread here with a fix for it, but i already have the correct path to libvirt.img. Another thread says it's normal. No issues with the VM's. Edit: This is working fine from another machine. It might just be an issue with Java. Weird that it works fine on one server but not the other.
  16. Thank you for posting this update. I believe my PXE boot server has been broken since about Jan 2019 after an unRaid version update. "I used the following files from syslinux zip file in my tftpboot folder: chain.c32, ldlinux.c32, libutil.c32, mboot.c32, memdisk, menu.c32, pxelinux.0, vmlinuz" Does this mean here? Or in tftp\pxelinux.cfg\roms? I copied them to both locations until i can reboot the server and test. "chain.c32, ldlinux.c32, libutil.c32, mboot.c32, memdisk, menu.c32, pxelinux.0, vmlinuz" From which directory did you copy these from? I guess it depends on if you are booting with UEFI or not? syslinux-6.03\bios syslinux-6.03\efi32 syslinux-6.03\efi64 I have a mixed environment of machines and extracted the files from the bios directory to test with.
  17. Running "ls -al" at /mnt/user/Share showed that .Recycle.Bin created a symbolic link to itself. I ended up running "rm -rf .Recycle.Bin" and recreated the directory .Recycle.Bin. The duplicate directories did not return after i tested deleting a file.
  18. Renamed \\ServerName\flash\config\network.cfg to network.cfg.old, updated from v6.7.0 to v6.7.2 and rebooted. After 4 days it appears this has fixed the issue. If the issue returns i will report back. THANK YOU!
  19. I noticed that the default setting for this plugin is "Enable Recycle Bin for Deleted Files? = No", which defeats the whole purpose of having it installed. After 2 days of it set to "No", the directory replication is still there. Even after reboots. This is not a big deal and might sort itself out in future releases of the plugin or unRaid. Thanks for help everyone.
  20. Settings changed to default and server rebooted. I will wait 5 days and see what happens. Thanks.
  21. I tried that too. On both X:\.Recycle.Bin and X:\.Recycle.Bin\.Recycle.Bin. So i removed the plugin and rebooted. But the directory is still there. This does not happen on unRaid v6.7.0 I am left with the directory 41 times --> X:\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin\.Recycle.Bin I then reinstalled the plugin and rebooted again. But the issue remains. It's not a big deal, it's just a bug somewhere.
  22. I emptied the recycle bin which had about 15gb and 71K+ files in it, rebooted the server, but it's still there.
  23. My version: 2019.04.08 I am also having this issue. I have seen this in the past and a reboot usually fixes the problem. I never brought it up as it happened rarely. As far as i can tell this happened after i upgraded unRaid to v6.7.2 from v6.7.1. I also use robocopy to sync data from 1 server to another, but i have always excluded the .Recycle.Bin directory. I wanted to ask if anyone knows a fix before i uninstall and reinstall the plugin. Thanks.
  24. Thanks. I will try that after i re-run the upgrade and report back the results.