kazanjig

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by kazanjig

  1. I was able to get the MinecraftPE world files off my kid's iPad and I put them where I *thought* they should go in the server after clearing out the default files. No success. Any suggestions would be appreciated.
  2. EDIT: Ugh, pulled a stoopid. I was putting Shinobi on 'proxynet' instead of br1. --------------------------- Hi all. I'm having a problem with SWAG/Shinobi using an IP address in a second subnet. It _was_ working a couple days ago but then a few things blew up with UnRAID/my network and now I cannot get Shinobi to start on the correct subnet. I've deleted and reinstalled SWAG and Shinobi, no luck. I've blown up my Docker file and rebuilt, no luck. Desired: Shinobi on 'proxynet' at 192.168.2.100:8080 (I have it set correctly in the manually created shinobi.subdomain.conf) Result: Shinobi starts on 'proxynet' at 192.168.1.100:8080 (which is a problem because I also run Ubiquiti equipment) No matter what I put in the conf file for an IP address, it is ignored. Even if I put an IP address in the *.*.1.* subnet it's still ignored and Shinobi fires up using my UnRAID server's IP address. As a point of reference,I can start Shinobi on br0 and br1 using IP addresses in their respective subnets and its works just fine bypassing 'proxynet'. So, good that it appears to not be a routing issue (outside of Docker's own routing). It's as if SWAG isn't seeing the shinobi.subdomain.conf file at all. Any thoughts on what could be causing SWAG to ignore the conf file?
  3. EDIT: Ugh, pulled a stoopid. I was putting Shinobi on 'proxynet' instead of br1. ----------------------------- Hi all. I'm having a problem with SWAG/Shinobi using an IP address in a different subnet. It _was_ working a couple days ago but then a few things blew up with UnRAID/my network and now I cannot get Shinobi to start on the correct subnet. Desired: Shinobi on 'proxynet' at 192.168.2.100:8080 (I have it set correctly in the manually created shinobi.subdomain.conf) Result: Shinobi start on 'proxynet' at 192.168.1.100:8080 (which is a problem because I also run Ubiquiti equipment) Any thoughts on what could be causing SWAG to ignore the IP address/subnet in the conf file? EDIT: Shinobi will start at 192.168.2.100 if I change the network to br1 1 which is on the *.2.* subnet, so it's not a routing issue. It's as if SWAG isn't seeing the shinobi.subdomain.conf file at all. But it _is_ seeing the conf file because if I set it to an IP address/port on the *.1.* subnet it works. There's just something about the *.2.* subnet SWAG doesn't like... I deleted the SWAG and Shinobi containers, deleted the 'proxynet' network, and rebuilt it all. Same result.
  4. So, I think it's actually a cache issue. My syslog is getting flooded with "shfs: cache disk full" and I believe that's causing the whole system to hang. I'm not currently using the server -- it was unstable and would only stay up for a couple days before crashing so I'm trying to 'rebuild' it. There is a bunch of data stored on it but no shares actively being used, no Dockers or VMs running. There's a bunch of stuff on my cache from previous Docker installs that I'll likely need to regain access to. I've attached my diagnostics. Any help would be greatly appreciated. ursus-diagnostics-20210908-1046.zip
  5. For the life of me I cannot get the Unifi Controller web UI to respond. I've tried 5.7, 5.8, 5.9, LTS... I've even deleted my Docker img and started everything from scratch. I've updated to the latest Unraid 6.9.2. Nothing works and I have no idea what I'm missing. EDIT: In 5.9, the web UI responds but I get "UniFi Controller is starting up... Please wait a moment". Refreshing after several minutes reveals the same message.
  6. Haven’t been running the suspect Docker and still unstable. Here are pics of the error(s) on display when I go to reboot. Send to be a similar corruption. Also I’m still having the problem that I have to reboot twice to get network connectivity. Sent from my iPhone using Tapatalk
  7. Thanks, all. Turns out my son was saving ridiculous numbers of restore points in Minecraft that was causing the Docker image to fill. Hopefully that was the cause of all the problems, not just the recent one. Will run without MineOS for a while to see if it stays up. Appreciate the direction.
  8. Here's what was on the display at the latest crash just before Docker started failing to start. I presume this led to the Docker img getting corrupted. The array (without Docker) has been up for ~36 hours now which is unheard of as of late. Not sure what "unexpected item end" is or if it's related to the img getting full. I'll look into it -- my kids were running a couple Minecraft servers but everything I was running is pretty standard fare. EDIT: Well, gee, look at that... -rw-rw-rw- 1 nobody users 68719476736 Sep 6 17:37 docker.img Is there any way to confirm Minecraft is the culprit?
  9. Thanks for the reply. I had the docker img get corrupted about a month ago and recreated it. I can’t remember exactly but I think the instability started around that time. It seems unusual to have two corruptions so close in time. Wondering if it’s a hardware (memory) issue. If not, I may just start from scratch. I saw a couple posts on what I would need to save to maintain my array. Makes me very anxious to blow it up though.
  10. Over the past couple weeks, my array has become unstable where about daily it becomes unresponsive and an error trace is displayed on the monitor. A forced restart is needed but usually twice as the first reboot the server isn't visible on the network for some reason. Today, even though it boots, Docker refuses to start. Diagnostics and pictures of the last couple error traces attached. I also have the syslog saved to flash but it's ~65MB -- can't upload so here's a link. Wondering if it's a hardware or software issue -- I'm lost. Any help would be greatly appreciated. ursus-diagnostics-20200906-1741.zip