DietPi install - interface (and potentially software) not available

[petruut]

Hi there - great job with this again.

Installed it into a Prox VM of DietPi and downloaded the software via the diet pi-software menu (fresh install).

I can ping the DietPi just fine on its local address, but the :1099 gives me nothing.

How can I troubleshoot this from root@DietPi?

[wiedehopf]

bash /opt/adsb/log-sanitizer.sh | curl -F'expires=24' -F'file=@-'  https://0x0.st

This will upload some diagnostic information, you can share the link here.

[petruut]

Some more information from the DietPi-Services:

[petruut]

[wiedehopf]

Nvm ... not sure why python-requests didn't install.

apt install -y python3-requests

Then it should probably start working?

[petruut]

done @wiedehopf

[wiedehopf]

Yeah that wasn't quite needed after all, check my last post again, changed it.

[petruut]

thanks for that - did it and now we're at: https://0x0.st/XBMQ.txt

the webpage is still not running (gave it a reboot for good measure, but still nothing on 1099)

[wiedehopf]

Running on port 80, not sure why.

[wiedehopf]

Let's see why it thinks it's not an app install but an image:

 ls /opt/adsb/*.feeder.image

Really this is not an issue if the VM is dedicated for this anyhow.

[petruut]

everything seems to be working on :80!! you're fantastic.

The RAM use of the VM is quite high, at 1.8-1.9G - running just this + 2x feeders on the fresh dietPi. is this normal, or is it likely to result from some of the app vs image you mentioned earlier?

this is what I'm getting when I run what you suggested:

[wiedehopf]

You'd have to check for example with htop what is using the memory.

You can probably limit the VM to 1.5G memory without issue.

linux will use free memory for file caching, doesn't necessarily mean that it actually needs that much memory.