Jump to content

jfoxwoosh

Members
  • Posts

    58
  • Joined

  • Last visited

Everything posted by jfoxwoosh

  1. It happened again. After server reboot, ozwdaemon cannot start back up again. I have attached the logs here. Going through it, it seems like some old zwave device is stuck in the stick and causing problems. Can someone please help verify this? Perhaps I need to factory reset the stick? logs.zip
  2. After rebooting, the shares are back to normal. Thank you! Now the "fix common problems" are reporting "/var/log is getting full (currently 100 % used)." What can I do to mitigate this? tower-diagnostics-20210104-1234.zip
  3. @JorgeB Okay, that makes sense. It was the last thing I did. I was trying spaceinvader1's script on dumping the VBIOS of my primary GPU. I will try disabling it.
  4. After a server reboot, all user share just disappeared. I have attached the diagnostic file. Please help. tower-diagnostics-20210104-1145.zip
  5. @FoxxMD, thank you for the assistance. It is working now. Upon inspecting the log, it seems like the problem was not being able to connect to MQTT due to incorrect username/password. I re-entered the username/password in the MQTT/ozwdaemon dockers several times but that did not fix the problem. I ended up having to delete everything inside "passwords.mqtt" file and start fresh.
  6. @FoxxMD, thank you for the reply. I have double checked the IP address, and it is correct. How do I check if the MQTT server is reachable or not? I don't see ozw folder in my appdata share. The docker's configuration is shown in the attached picture. I don't find any filed to map the Config folder like other dockers I had. Is this something I need to add manually? Or am I looking at the wrong place?
  7. Hi, I restarted my server yesterday and ozwdaemon has since refused to start up. It is giving me the following error log (attached). I couldn't find anything when try to google the status code 254. So far I have tried restart the MQTT/ozwdaemon docker and re-enter the username/password, but nothing worked.
  8. running 6.8.3, and official plex container exhibits this problem
×
×
  • Create New...