I can't look at the virtual machine now it's in Podman so how do I tell if it's stuck or on a long task?

Using Windows, podman, Theory.

I got into the slots that has the task and check the date last modified of the runrivet.log file, if they are stuck the file is not updated for a while.
You can also check inside the file for the neventsm, if this is big then it expected to take a while.

Open up powershell
At the prompt, paste this (this is what gemini says to do, i dont remember how i did it
): podman exec -it $(podman ps -ql) htop
I had pythia and herwig as processes.
I used F4 to filter on these words or you can also filter on the word BOINC, this narrows the list down a lot. Then you can look at time, CPU% and memory columns. CPU will run between 99-102% and memory depending on the task could be 0 or some number.

In reply to greg_be's message of 8 May 2026:

Open up powershell
At the prompt, paste this (this is what gemini says to do, i dont remember how i did it
): podman exec -it $(podman ps -ql) htop
I had pythia and herwig as processes.
I used F4 to filter on these words or you can also filter on the word BOINC, this narrows the list down a lot. Then you can look at time, CPU% and memory columns. CPU will run between 99-102% and memory depending on the task could be 0 or some number.

Gemini told me to do that too, but "podman" is not recognized as a command in command prompt or powershell

In reply to Toby Broom's message of 8 May 2026:

I got into the slots that has the task and check the date last modified of the runrivet.log file, if they are stuck the file is not updated for a while.
You can also check inside the file for the neventsm, if this is big then it expected to take a while.

I have one without a runrivet file. This is the contents of the slot:

[folder] shared
boinc_lockfile
boinc_setup_complete
boinc_task_state.xml
docker_wrapper
Dockerfile
entrypoint.sh
init_data.xml
input
job.toml
stderr.txt

In reply to Mr P Hucker's message of 8 May 2026:

In reply to Toby Broom's message of 8 May 2026:

I got into the slots that has the task and check the date last modified of the runrivet.log file, if they are stuck the file is not updated for a while.
You can also check inside the file for the neventsm, if this is big then it expected to take a while.

I have one without a runrivet file. This is the contents of the slot:

[folder] shared
boinc_lockfile
boinc_setup_complete
boinc_task_state.xml
docker_wrapper
Dockerfile
entrypoint.sh
init_data.xml
input
job.toml
stderr.txt

The runrivet.log file should be in the shared folder. At least that's where it is with VirtualBox.

---

Found it, thanks all.

Looks like my task has strange quarks and gluons making things more complex, I'm still in the integration phase after 3 days, nearly there.....

I think on windows you would need to enter wsl 1st then you can do podman exec -it $(podman ps -ql) htop

the containers run inside the buda runner linux distro

In reply to Toby Broom's message of 8 May 2026:

I think on windows you would need to enter wsl 1st then you can do podman exec -it $(podman ps -ql) htop

the containers run inside the buda runner linux distro

Oops, I've done that before and forgot. Gemini missed an important step out!

Sorry but this server is playing up, greg_be I sent you a PM, if you haven't received it reply in here. I got an error trying to send you it.

I don't have htop inside the container so I just used top e.g.

podman exec -it ed746bb7ffd4 top -n1

 
Tasks:  17 total,   2 running,  15 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.4 us, 24.3 sy, 72.5 ni,  2.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem : 511227.9 total, 447688.1 free,  53287.8 used,  17278.2 buff/cache
MiB Swap:   8192.0 total,   8192.0 free,      0.0 used. 457940.1 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    965 boinc     30  10  635044 269404  14120 R 100.0   0.1   3196:45 Herwig

Since I have more than 1 container I used podman ps to get the ID (ed746bb7ffd4 ) that I was intrested in.