stable diffusion - how do I view the active log?

When you launch stable diffusion in local, you have a DOS window with a log that gives infos on all actions taken. But on runpod, the terminal shows the sequence of initialization, and then it stops recording after the 1st model is loaded. Why is that, how can I see the current state? I currently need it to try understanding how to open files on my network storage, but it's an useful tool in general that I know I'll need a lot later.
No description
No description
Solution:
Read the README for instructions on how to see the logs. You can't really use launch.py because the pod already starts it and looks like you also didn't activate the venv first, if you want to do that you basically have to set the DISABLE_AUTOLAUNCH environment variable, again see the README.
Jump to solution
5 Replies
ashleyk
ashleyk5mo ago
Forge shows me logs, must be something to do with the way you installed it.
mardicarus
mardicarus5mo ago
There's a problem indeed. I ditched forge and created a new volume with your template "ultimate". I launched A1111 with the "connect" menu. It runs, but the log is nowhere to be seen. So I close the window, open a terminal and use "launch.py" in the sd folder. There, it spends several minutes downloading and configuring stuff. And when I launch SD via the "connect" menu, the log shows nothing. And I'm very confused. I suppose it's a different instance, then where can I see the terminal for the one that's launched via the "connect" button, so I can get logs, if I need to restart it etc?
No description
mardicarus
mardicarus5mo ago
and there it installs a lot of stuff again when I re-deploy a pod
No description
mardicarus
mardicarus5mo ago
Also using webui.py didnt work
Solution
ashleyk
ashleyk5mo ago
Read the README for instructions on how to see the logs. You can't really use launch.py because the pod already starts it and looks like you also didn't activate the venv first, if you want to do that you basically have to set the DISABLE_AUTOLAUNCH environment variable, again see the README.