[MapProxy] windows background seeding error

[Robert k]

Hello everybody,

I would like to try mapproxy background seeding on windows server 2012R
and have currently encountered the following error.

The normal seeding with the new Mapproxy version == 1.11.0 works great
under Windows. But background seeding does not work. An error is sent to
the CMD or PowerShell terminal. Python tries to send the signal (stop
subprocess) to the console. It seems the CMD or PS can not handle the
signal and the seed process is not stopped and keeps going.


error message:
19, in call_with_duration
cmd.send_signal(signal.SIGINT)
File "d:\srv\python27_32bit\lib\subprocess.py", line 767, in send_signal
raise ValueError("Unsupported signal: {}".format(sig))
ValueError: Unsupported signal: 2


Is this a known issue, and if so, is there a work around?

So far, I have found the blog that explains the signal error under
Windows,
(https://stefan.sofa-rockers.org/2013/08/15/handling-sub-process-hierarchies-python-linux-os-x/).

Best regards
Robert

[Oliver Tonnhofer]

Hi,

this is not known. Can you create a new issue on GitHub? https://github.com/mapproxy/mapproxy/issues/new
Thanks!

Regards,
Oliver
--
Oliver Tonnhofer | Omniscale GmbH & Co KG | https://omniscale.com
OpenStreetMap WMS and tile services | https://maps.omniscale.com

Post by Robert k
Hello everybody,
I would like to try mapproxy background seeding on windows server 2012R
and have currently encountered the following error.
The normal seeding with the new Mapproxy version == 1.11.0 works great
under Windows. But background seeding does not work. An error is sent to
the CMD or PowerShell terminal. Python tries to send the signal (stop
subprocess) to the console. It seems the CMD or PS can not handle the
signal and the seed process is not stopped and keeps going.
19, in call_with_duration
cmd.send_signal(signal.SIGINT)
File "d:\srv\python27_32bit\lib\subprocess.py", line 767, in send_signal
raise ValueError("Unsupported signal: {}".format(sig))
ValueError: Unsupported signal: 2
Is this a known issue, and if so, is there a work around?
So far, I have found the blog that explains the signal error under
Windows,
(https://stefan.sofa-rockers.org/2013/08/15/handling-sub-process-hierarchies-python-linux-os-x/).
Best regards
Robert
_______________________________________________
MapProxy mailing list
https://lists.osgeo.org/mailman/listinfo/mapproxy