Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to start after successful installation #83

Open
Mohsyn opened this issue Jan 30, 2024 · 6 comments
Open

Fail to start after successful installation #83

Mohsyn opened this issue Jan 30, 2024 · 6 comments

Comments

@Mohsyn
Copy link

Mohsyn commented Jan 30, 2024

After a successful install when I navigate to "Model Organizer" tab it shows:

Unable to initialize database: failed to init SQLite storage: 'Namespace' object has no attribute 'mo_database_dir'

@alexandersokol
Copy link
Owner

Did you tried to restart SD UI after installation?

@OuticNZ
Copy link

OuticNZ commented Feb 13, 2024

I'm getting the same error and yes I have started. I have multiple installs of SD, using different installs - Automatic1111, SDNext, etc...

This extension is working on Automatic1111.

In SD.Next (Instance 11) I get this error.
image

I notice an error in the log.

21:18:15-847227 ERROR    API error: GET:                                        
                         http://192.168.3.11:9000/file=extensions/sd-model-organize
                         r/javascript/tinymce/tinymce.min.js {'error':          
                         'HTTPException', 'code': 404, 'detail': 'File not      
                         found:                                                 
                         extensions/sd-model-organizer/javascript/tinymce/tinymc
                         e.min.js.', 'body': '', 'errors': '404: File not found:
                         extensions/sd-model-organizer/javascript/tinymce/tinymc
                         e.min.js.'} 

In this example SD.Next has the following startup command line options:

Command line args: ['--listen', '--port=9000',         
                         '--insecure', '--medvram', '--allow-code',             
                         '--config=/app/webui/config.json',                     
                         '--ui-config=/app/webui/ui-config.json',               
                         '--log=/tmp/sdnext.log', '--models-dir=/config/models',
                         '--data-dir=/config/data', '--log=/tmp/sdnext.log']

The location as to where the extensions are stored is not under the webui directory.

I have a second SD.Next instance which is also getting the same error.
image

This one has a different start command line setup.

Command line args: ['--listen', '--port=9000',         
                         '--insecure', '--medvram', '--allow-code', '--debug']

No obvious errors in the logs. It doesn't really mention the extension much at all. No errors during install.

21:37:34-253586 DEBUG    Running extension installer:                           
                         /config/04-SD-Next/webui/extensions/sd-model-organizer/
                         install.py                                             

On the second instance the API Error doesn't occur. The extension directory is under the WebUI directory, i.e. default location.

So, is this extension compatible with SD.Next?

@OuticNZ
Copy link

OuticNZ commented Feb 13, 2024

Well, after rebooting for I don't know how many times. It's working sort of.

SD.Next - Instance 1 is still getting the API error and the page layout is broken
SD.Next - Instance 2 - is working fine.

Shrug.

@Mohsyn
Copy link
Author

Mohsyn commented Apr 12, 2024

Did you tried to restart SD UI after installation?

Yes. That did not help. Disabled the plugin atm

harukaxxxx added a commit to harukaxxxx/sd-model-organizer that referenced this issue Jul 11, 2024
import `argparse` to fix init database error in **sd.next**

alexandersokol#83
@harukaxxxx
Copy link
Contributor

harukaxxxx commented Jul 11, 2024

Did you tried to restart SD UI after installation?

Yes. That did not help. Disabled the plugin atm

In the meantime, you can fix this problem easily by adding import argparse into preload.py manually.

@harukaxxxx
Copy link
Contributor

This issue has been resolved by #97 and may be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants