Jump to content

dlandon

Community Developer
  • Posts

    10,397
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. I saw a lot of preclear activity in the log. That may have affected the format.
  2. I am re-evaluating my development efforts with Unraid and need to cut back on some plugins that are not providing core functionality in Unraid. This plugin will be deprecated starting with Unraid 6.9. This plugin does not provide enough of an enhancement to the Unraid OS and I don't have the time to continue development efforts. If it's deemed to be a necessary part of Unraid, LT should include the functionality.
  3. I am re-evaluating my development efforts with Unraid and need to cut back on some plugins that are not providing core functionality in Unraid. This plugin will be deprecated starting with Unraid 6.9. This plugin does not provide enough of an enhancement to the Unraid OS and I don't have the time to continue development efforts. If it's deemed to be a necessary part of Unraid, LT should include the functionality.
  4. I am re-evaluating my development efforts with Unraid and need to cut back on some plugins that are not providing core functionality in Unraid. This plugin will be deprecated starting with Unraid 6.9. This plugin does not provide enough of an enhancement to the Unraid OS and I don't have the time to continue development efforts.
  5. My music is all .wma and plays fine on my Transporter. How are you playing the music?
  6. That functionality is built into Unraid. You'll have to report that bug to Unraid.
  7. Follow the exact instructions on the first post to get started.
  8. Unfortunately, ownCloud can't be updated automatically. You can see an update coming by the notice in the ownCloud UI. I will update the docker php version to the highest supported by the latest ownCloud version after several months of the release.
  9. No, because ZM is exposed the Internet, it is imperative that security updates be applied when available. Normally very quick.
  10. There are some timers to set so Unraid has the time it needs to shutdown. The defaults are a bit too short. If you don't set them correctly, you will get a forced unclean shutdown that will add to your frustration.
  11. There are really no old configs. Do this at a command prompt. This copies the flash config files to a /tmp file system that UD uses to update it's information. The flash copy is kept current whenever a change is made, but the /tmp copy may have gotten messed up. /usr/local/emhttp/plugins/unassigned.devices/scripts/copy_config.sh
  12. That doesn't show that the share is mounted. Unmount the share and see if the log messages stop.
  13. I get it! We are trying to track it down. You don't need to keep saying the logs keep flooding. Look at the /flash/config/plugins/unassigned.devices/samba_mount.cfg file on your flash drive and see if there is a 'WD External' reference anywhere there. If so post the contents of that file for me. The passwords are encrypted, but you can remove the user and passwords if you' like. It's possible there is an errant entry in the .cfg file.
  14. If you are mounting this share with UD, you'll have to remove it and re-create it.
  15. Where is it renamed to WDEX? UD mount point? UD will still have to mount it by its name on the router.
  16. Your log is impossible to read because of the massive amount of these messages: Nov 1 05:17:41 R7UNRAID kernel: IPv6: ADDRCONF(NETDEV_UP): veth1e6b4ff: link is not ready Nov 1 05:17:41 R7UNRAID kernel: docker0: port 12(veth1e6b4ff) entered blocking state Nov 1 05:17:41 R7UNRAID kernel: docker0: port 12(veth1e6b4ff) entered forwarding state Nov 1 05:17:41 R7UNRAID kernel: docker0: port 12(veth1e6b4ff) entered disabled state Nov 1 05:17:42 R7UNRAID kernel: CIFS VFS: BAD_NETWORK_NAME: \\192.168.1.1\WD External Nov 1 05:17:42 R7UNRAID kernel: eth0: renamed from veth0cbfcee Nov 1 05:17:42 R7UNRAID kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1e6b4ff: link becomes ready Nov 1 05:17:42 R7UNRAID kernel: docker0: port 12(veth1e6b4ff) entered blocking state Nov 1 05:17:42 R7UNRAID kernel: docker0: port 12(veth1e6b4ff) entered forwarding state This one should be investigated: Nov 1 05:17:42 R7UNRAID kernel: TCP: request_sock_TCP: Possible SYN flooding on port 51328. Sending cookies. Check SNMP counters. Your remote share server is 192.168.1.1. That's normally a router address. Is your WD External attached to your router?
  17. Set the contents of the opencv_ok file to 'yes' and opencv.sh will be run whenever it is necessary and you don't need to be concerned about if it needs to be re-compiled.
  18. If the container command: /usr/bin/nvidia-smi does not show the nvidia gpu, then you need to find out why and get it resolved. Do you have the Unraid nvidia plugin installed properly for your gpu?
  19. It's very clear in the opencv.sh script notes when it is run. Just read it. I can't support the ES configuration here, it's too complicated with too many options. A person needs to go the the ES documentation for support.
×
×
  • Create New...