-
Notifications
You must be signed in to change notification settings - Fork 3
Internal Server Error/500 for API GETs #2
Comments
Hello, did you remember to run database migrations before starting the server? user@local:hyve/services/server$ yarn migrate You will also need to run a sync before the API will start working: user@local:hyve/services/sync-<client or server>$ yarn sync This is also mentioned here: https://github.com/mserajnik/hyve#running-without-docker The fact that If that doesn't fix it, could you please open This should make it so it should display exceptions in the console when you hit the API and encounter an error. Please provide me with that error message then. Sorry, there's currently no configuration to set this. |
Thanks for the quick response. I did run both migration and sync beforehand and they both seemed to successfully complete but there does seem to be something wrong with the database.
|
In that case it looks like the sync didn't go through successfully. Are you trying to sync from the client or server database? Could you try running it again and take a look at the output of the sync? It should tell you how many files, tags and namespaces it synced at the end. |
Also make sure hyve server is actually connecting to the correct |
I'm trying to sync from the client database. Here's what I get when running
|
Hm, that looks correct. At least if you currently don't have any tags? hyve automatically tries to get tags from the first tag service that it finds (so if you are using multiple and have your tags on later services, this wouldn't work right now). And you are sure the path to the In this case, I'm a bit out of ideas, but would suggest you try to open the It should look like this for a working database: |
Ah! I had Again, thanks for the quick responses and your patience. |
Glad you figured it out! Sorry, it's not the easiest to get running since you basically have to duplicate some configuration across the different services. Ideally, I'd want to have one central location for configuration; I might do something about this in the future.
Yes, that's likely the case. I implemented the client sync shortly before the ability to have multiple tag repositories was introduced into hydrus and haven't touched it since then. I guess hydrus might not add those tags you get from the PTR automatically to the local I should also make this configurable, although there's the issue that it's quite a hassle for the user to figure out which service ID is the correct one. Hence the automatic choice for the client sync at the moment; the server sync requires manual configuration, but the IDs are more predictable there and running the server is more technically advanced, which is why I don't feel too bad about having the user configure it manually there. |
No worries! I'll look into tag migration to shove everything into my local tag service (after backing it all up), which would be good enough for me right now. Cheers! |
I'm setting up without Docker and think everything is set up correctly, however after starting up the server and web services the page displays:
Along with the console logging these:
I'm on MacOS 10.13.6 if that has any relevancy. If there's any other details I can provide to help please let me know. And thank you for your hard work!
The text was updated successfully, but these errors were encountered: