Accessing non-container logs about globalping-hwprobe HOT 4 CLOSED

I assume you started the container upgrade using the USB key, as mentioned in the instructions.
You should be able to recover the probe following the instruction howto to factory reset it,
If it still doesn't start the container, then it's possible that sdcard is faulty.

Regarding the questions about the dev logs, there is a way to access those logs, but you will need a hardware probe with a serial console cable mod.
To access the internal logs of the system is just a matter of following:
cat /dev/vcsX where X is the number of subsystem logs you want to see.

Regarding the collection of logs in a file, I strongly advise against this, this is not a PC, and having a filesystem being actively written is a very bad idea.

from globalping-hwprobe.

I see, I suppose the requirement for a special dev setup is acceptable but I was mostly thinking if we can't store those logs in RAM to some extent, the same way as the docker logs work.

from globalping-hwprobe.

They are in the RAM, just not in files.
There are multiple log streams (watchdog, system monitor, etc....) , during development is very useful to have real-time status, instead of the plain old "tail -f... " approach

PS: I know the system is very locked up, apologies, I know it's a pain to dev... but that was one of the requirements of @jimaek ... to make the users happy with security....

from globalping-hwprobe.

Well, then, I guess my question is just - would it be hard to pipe whatever we have to the SSH output in addition to the current container logs? If yes, let's close this for now but if not, might be useful.

from globalping-hwprobe.