errno 107 overdrive #2333
-
|
Hello everyone. Has this been happening to anyone else? For info I'm a colab pro user, I've been reinstalling sd a few times and while Errno 107 errors while using the webGUI were nothing new so far, this thing with failing to launch it in the first place has been occurring relentlessly for the past few days, didn't happen before. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
|
the only solution is to move to a different host, like runpod or paperspace, I have the notebooks there |
Beta Was this translation helpful? Give feedback.
-
|
google is definitely putting obstacles for SD |
Beta Was this translation helpful? Give feedback.
-
|
So I went and tried Paperspace for a while, worked great after a little stumble setting it up but somehow my costs went through the roof. Side note, might interest some people (just for the info, not as an encouragement to use) to know that as a colab pro user, I could always keep using the colab even as my units got all used up to 0. So at the moment I have this new colab, and paperspace successfully running. Will see which one tanks first, and the goal is to upgrade gear in a month or so to run everything locally. Will keep info coming if new things turn up. |
Beta Was this translation helpful? Give feedback.
-
|
why isn't the colab working ? |
Beta Was this translation helpful? Give feedback.
-
|
Very good question. In the process of running it, I get two errors: Traceback (most recent call last): Then, if I try to run it again I get a cascade of script errors related to errno 107, which ultimately make it impossible to stop the runtime manually unless I go and disconnect & delete. At the moment I can still use np the colab to train models but not to run them hence for now I go to the other one for that. |
Beta Was this translation helpful? Give feedback.
-
|
This time, after a good old clean reinstall, everything is back to normal again. Edit: spoke too soon. Crashed and now goes back to the good old error cascade: ERROR:root:Internal Python error in the inspect module. ERROR:root:Internal Python error in the inspect module. ERROR:root:Internal Python error in the inspect module. Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Beta Was this translation helpful? Give feedback.
the only solution is to move to a different host, like runpod or paperspace, I have the notebooks there