Matthew Orres

I think this is actually just due to an older bug in the LittleLogistics mod, as the namespaces in the stack trace seems to suggest

We found an issue when using the latest version of the Life in the Village 3 mod (using LitV3 version 1.13, the last before their 2.0 bump) and the server hard crashed each time someone placed a train. Here's the exception text for occasion 1: and we confirmed that the same happened when we added a train (but the minecart that looks like the Steam engine was OK?) (exception stack trace is identical, save for being 15 minutes later due to having to restart the container). I know maintaining a mod like this is likely similar to herding rowdy cats (especially since there is a TON of mods involved here), but not sure if anyone else had come across this. Otherwise, I think things have been rock solid. So thank you for providing the image!!

So. I think I figured out what the issue was here - I don't think there's anything explicitly wrong with Snoopy's Docker template (though it is a bit out of date, and I think I'm going to dig in to seeing how to get emoncms to run on PHP 8). The issue was... I created the MySQL user incorrectly. The user needs scoped to more than just localhost. Primary way to determine if this is your issue is if the error message you get from emoncms/PHP includes a Docker IP (starts with 172) that doesn't correspond to any of your other Docker containers (still don't 100% understand where the IP came from). Once I setup the user correctly, the emoncms web UI showed up and I was able to log in. That being said. I've also created my own emoncms app in CA, the difference from Snoopy's is that it's fully standalone and does not include MQTT. I think the version of emoncms used is newer, but it might also be a far larger Docker image (might be better if I find a production-optimized version of emoncms - their docker is used as a devbox). Anywho, search for emoncms in CA and mine will show up next to Snoopy's if you're interested. Thank you for your work on this container, Snoopy. Yours was an excellent guide to work off of (I've never used emoncms prior to this, so your work was crucial to me!)

Howdy, I just recently added a new emoncms template to CA after attempting to use the existing one, but finding it didn't work (but I didn't quite understand why - and it may have been an issue on my part) - but noticed the template hadn't been touched since 2020. Regardless, I put another spin on it in that this template _only_ provides emoncms, and does not bundle MySQL, Redis or MQTT. Based off of the official emoncms docker image (as in, I literally copied it rather than basing it off of it) it should be fairly simple to keep updated, though right now it's a manual process. In the future I may develop tooling to have it done for me automatically.

I recently installed the Emoncms docker image, and when I configured it to speak with the existing MySQL database container I have - it doesn't seem to use the container variable with the value provided. I provided a Docker network address ending in 10, but the MySQL error I get lists the Emoncms's address (which ends in 8). What am I missing here?