/hydrus/ - Hydrus Network

What happened when you clicked the menu to auto setup the repos? Did some popup windows appear in the bottom right? Or did you get an error, or did nothing happen?

If you go services->manage services->remote->file/tag repositories, do you have any entries?

If you go search->new x search do you have any file repositories listed?

Public Tag repository is synchronised, but read-only art file repository isn't.

When I go to search->new x search I got "new read-only art file repository search" but when I choose it, it look like in the photo…

>>1453

Once your client downloads and process some updates from my file repository, the files should appear in your searches.

How is your client set up to process repository updates? You should find those options under file->options->maintenance and processing. If you haven't changed them, your client should attempt to synchronise your repositories whenever the client has been idle for a while.

Under services->review services, where it says your file repo is not synchronised, does it say anything about recent errors? Do you have something like 'downloaded 1,126/1,126' and so on, or do you have something about 'not initialised yet'? If you have some downloaded, how many are processed?

>>1485

This is interesting, thank you. I think your tag service is probably just paused at 630, and will continue quietly when you aren't looking.

With the file sync, I think what is happening is that the bit of code that syncs attempts to completely sync each service in turn, and for you that happens to always mean the tag service first. The daemon has probably been putting in five or twenty minute bursts of processing when the client is idle, but since the tag service won't be completely done until about ten or so total hours of quiet 100% CPU processing is done, it has never even attempted to start the file service.

Long-time users like me don't notice this sort of problem because we only need a few minutes a day to keep up with the tag repo.

I have made the sync daemon randomise its sync order to stop bottlenecks like this choking other new services. Please let me know if your file repo has made any progress after a few days of running v183!

Also please check your tag service in a couple of days and let me know if that 630 hasn't moved on at all.