pallid whale
Required Information
What version of Tracearr are you running? v1.4.24
Are you running in Docker, LXC, Unraid, TrueNAS, or another environment? created from Proxmox Helper scripts. appears to be an LXC
Provide your full docker compose file. - dont think there is one
Include any relevant logs ( via https://pastebin.com/ ) or screenshots.
blazing briarBOT
Required Information
What version of Tracearr are you running? v1.4.24
Are you r...
pallid whale
After upgrading to the latest Tracearr, i am now getting the 502 bad gateway error. to install i used the proxmox helper script. to upgrade you just type 'upgrade' at the cmd prompt. Not sure if Docker is installed but when using 'systemctl status docker' says no service file found so pretty sure its not there
pallid whale
issue seems to have resolved itself. I can now browse the site.
pallid whale
seems to be an intermittent issue. its back again
twilit minnow
still waiting on the logs..
twilit minnow
how much memory did you give it? what is this running on?
pallid whale
tried to update it adn it complained about memory so i increased it to 12GB and gave it a hdd size of 30GB
twilit minnow
ok lets see what durzo says when he gets on. he created that install script so hes way more knowledgable there
pallid whale
i was able to get a backup off of it. spun up a new instance and uploaded the backup
everythign is working fine there
the issue presented when trying to run the update function. thats when all the hinkyness started
tall sigil
Did the update command finish successfully or did it error? What happens if you run it again?
pallid whale
it ran successfully once i added the extra ram. when i run it again it just says no updates
tall sigil
So you're saying it failed update before? Is it working ok now? There is a way to force a re update if it's not
pallid whale
it failed due to not enough memory. i shut it down, added more ram, then restarted it and ran the update. the update ran fine. after that i was getting timeouts, 502 errors, and a services page in tracearr that said it would refresh once it reconnected to redis/db
it was intermittent but i was able to get in and download a backup. spun up a new LXC container using the helper script and then uploaded the back up and everything is working fine on the new one
tall sigil
alright. it probably was not needed, you could have just run a force update to recompile the current version, but hey if it works it works
one thing to note is, when the lxc starts it analyses how much ram you allocated to the lxc and dedicates a portion of that to postgres. if you start with say 6GB and then reduce it down to 2GB its going to crash again. you should stop the lxc, change ram, then start it again cleanly.
and update should be given atleast 4GB
the build process is intense, after build you can reduce it. and its on my list to move away from building from source and install a precompiled version, but thats in the future
pallid whale
i noticed with the new lxc spun up, it started with 8GB of ram rather than the 4GB