• Content Count

  • Joined

  • Last visited

Everything posted by tronyx

  1. There was only the catalina.out file. I deleted it, restarted the container and got the same result. The permissions did look correct. I looked into the catalina.out file and I am seeing the following error, which seems like the culprit: INFO: Starting Servlet Engine: Apache Tomcat/8.0.32 (Ubuntu) Sep 25, 2018 7:08:21 PM org.apache.catalina.valves.AccessLogValve open SEVERE: Failed to open access log file [/var/lib/tomcat8/logs/localhost_access_log.2018-09-25.txt] /var/lib/tomcat8/logs/localhost_access_log.2018-09-25.txt (Permission denied)
  2. Just updated to your latest image and now Tomcat is failing to start. No other changes on my end, and even previous images using their respective tags are no longer working. Seeing the following in the Docker logs for the container: *** Running /etc/my_init.d/ Using existing properties file. Using existing MySQL extension. No permissions changes needed. *** Running /etc/rc.local... * Starting Tomcat servlet engine tomcat8! guacd[37]: INFO: Guacamole proxy daemon (guacd) version 0.9.14 started Starting guacd: SUCCESS *** Booting runit daemon... *** Runi
  3. Having an issue with Flood seeming to become unresponsive after about a day. Sometimes restarting the container corrects it, but other times I need to blow away the container and recreate it. I have DEBUG set to true, but there is nothing in the container logs. Is this an already known issue? The port seems to still be responsive, but the webUI times out.
  4. Alright, swapped USB ports, brought it online, mucked around in settings and whatnot for about 20 minutes to get it to read and write to the flash drive and it's been stable so I started the array. Array came online and did NOT require a parity check so that might be a better sign that things are ok. I'll take it slow with starting up other services on the network for now.
  5. That's what I was thinking, but wanted to post here first since I've already rebooted a few times. Will try another port and see what happens. This system only has USB 2.0.
  6. Ok, oddly enough it just recovered without me doing anything. Attaching new diagnostics, but I think the most relevant thing is the following from the syslog: Jun 24 15:34:41 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt! Jun 24 15:34:41 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout Jun 24 15:37:11 Morgoth kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt! Jun 24 15:37:11 Morgoth kernel: i801_smbus 0000:00:1f.3: Transaction timeout Jun 24 15:37:11 Morgoth kernel: w83795 0-002f: Failed to read from register 0x02f, err -110 Jun 24 15:
  7. It just happened again. This time with the array stopped and literally nothing happening. I made no changes and didn't perform any actions.
  8. Woke up this morning to find my shares unavailable, the GUI had reverted to the light theme, and my flash drive showing under both Flash and Unassigned Devices. Did a clean reboot through the GUI, it wanted to start a parity check, and then the system locked up at about 2%. No errors on the screen. Only option was to force reboot. Same thing happened; obviously an unclean shutdown was detected so a parity check was triggered, and the system locked up at about 2% again. Shutdown the box, swap the flash drive for a brand new one after testing it, and the same thing happens again, right around th
  9. Thanks, that's what I was thinking it was indicating. Appreciate your time and response.
  10. FCP plugin informed me that the System experienced one or more call traces and to post for help. Diagnostics attached. I found the following, but am unsure as to what it could indicate and whether or not it's ignorable (Had to use pastebin as posting it as code flagged it as spam due to the content of the error): Any/all help is greatly appreciated.
  11. Reported the issue on your GutHub (, but wanted to post here as well as it seems you're very responsive here. NowShowing encounters a 404 looking for Marvel's The Punisher and just continuously retries: Seems that NowShowing doesn't handle 404 errors from theTVDB very well: D, [2017-11-18T15:21:38.394907 #70] DEBUG -- : Response from thetvdb for query series/329367/all/en.xml: Code: 404. E, [2017-11-18T15:21:38.395176 #70] ERROR -- : Could not connect to Will retry in 30 seconds D, [2017-11-18T15:22:08.395416 #70] DEBUG