Parallel Unoserver with different ports hangs/gets stuck about unoserver HOT 5 OPEN

This is the correct place, and that should work in theory, although I have never tried joblib. I hope to get time to look at the unoserver backlog soon.

The output above looks correct. What happens when you try to start a conversion with unoconvert?

from unoserver.

Hi @regebro

I made some progress but came across another roadblock. So, I realized I have to have the unoservers started in a separate process, so I have my unoservers in a separate file and ran it prior.

In my pdf conversion file, I try to connect via this command:
command = "unoconvert --convert-to pdf --interface {} --port {} \"{}\" \"{}\"".format("127.0.0.1", str(port), input_path, output_path)

os.system(command)

This is my error output:
unoserver.converter.NoConnectException: Connector : couldn't connect to socket (Connection refused)

This is all done on separate cores.

Any advice?
Thanks!
Edit: I've tried ports "0" and "1" for a multicore testing for both the servers and the pdf conversion client

from unoserver.

That should work.

from unoserver.

Welp, it doesn't work though:/
But thanks for giving a look over to see if I'm missing anything too obvious/making sure I'm on the right track, I'll continue to debug this

from unoserver.

If this is still an issue, you're probaly hitting what I did - each conversion server instance now uses two tcp ports. Add --uno-port $((port+100)) or something.
(See issue #29...)

from unoserver.