I seem to be seeing the same thing. I am using the -f option for persistence, but initial port mappings are ignored and VM's are assigned ports in the order they are powered on. It is possible I am missing something basic - any tips or suggestions appreciated.
Debug output below:
root@vSPC:~# /root/vSPC.py/vSPC.py -d --server -f /root/vSPC.py/ConnectionList.d at --vm-expire-time 31536000
INFO:root:Starting vSPC on proxy port 13370, admin port 13371, allocating ports starting at 50000
DEBUG:root:sending WILL 0
DEBUG:root:sending WILL 3
DEBUG:root:sending WILL 1
DEBUG:root:sending DO 0
DEBUG:root:sending DO 3
DEBUG:root:sending DO 232
DEBUG:root:client wants to 37, sending DONT
DEBUG:root:still waiting for [(251, 0), (251, 3), (251, 1), (253, 0), (253, 3), (253, 232)]
DEBUG:root:client says we should 0
DEBUG:root:client says we should 3
DEBUG:root:client says we should 1
DEBUG:root:client will 0
DEBUG:root:client will 3
DEBUG:root:client will 232
DEBUG:root:still waiting for [(232, 0), (232, 80), (232, 82)]
DEBUG:root:client knows VM commands: [0, 1, 2, 3, 40, 41, 43, 44, 45, 46, 48, 70, 71, 73, 80, 81, 84, 85, 86, 87, 82, 83]
DEBUG:root:client wants to proxy server to vSPC.py
DEBUG:root:still waiting for [(232, 80), (232, 82)]
DEBUG:root:50135d0008cd9717-ae75e41246923123:'cam-vpro30' listening on port 50000
DEBUG:root:client wants to 44, sending DONT
DEBUG:root:sending WILL 0
DEBUG:root:sending WILL 3
DEBUG:root:sending WILL 1
DEBUG:root:sending DO 0
DEBUG:root:sending DO 3
DEBUG:root:sending DO 232
DEBUG:root:client wants to 37, sending DONT
DEBUG:root:still waiting for [(251, 0), (251, 3), (251, 1), (253, 0), (253, 3), (253, 232)]
DEBUG:root:client says we should 0
DEBUG:root:still waiting for [(251, 3), (251, 1), (253, 0), (253, 3), (253, 232) ]
DEBUG:root:client says we should 3
DEBUG:root:client says we should 1
DEBUG:root:client will 0
DEBUG:root:client will 3
DEBUG:root:client will 232
DEBUG:root:client knows VM commands: [0, 1, 2, 3, 40, 41, 43, 44, 45, 46, 48, 70, 71, 73, 80, 81, 84, 85, 86, 87, 82, 83]
DEBUG:root:client wants to proxy server to vSPC.py
DEBUG:root:still waiting for [(232, 80), (232, 82)]
DEBUG:root:still waiting for [(232, 82)]
DEBUG:root:5013b08bae4808fd-bb28b51e53a26365:'cam-vpro37' listening on port 50001
DEBUG:root:client wants to 44, sending DONT
thanks
Last edit: Zach Loafman 2012-05-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would love to use this tool, but the port mappings need to stay consistent to work in our environment. Will persistent port mappings be added in the future?
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't quite know why sourceforge keeps eating my replies. Sigh.
We have been using persistent port mappings for a while, so I'm not exactly sure what's happening in your configuration/setup. I will try to look at it soon, but $LIFE has been in the way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I seem to be seeing the same thing. I am using the -f option for persistence, but initial port mappings are ignored and VM's are assigned ports in the order they are powered on. It is possible I am missing something basic - any tips or suggestions appreciated.
Debug output below:
root@vSPC:~# /root/vSPC.py/vSPC.py -d --server -f /root/vSPC.py/ConnectionList.d at --vm-expire-time 31536000
INFO:root:Starting vSPC on proxy port 13370, admin port 13371, allocating ports starting at 50000
DEBUG:root:sending WILL 0
DEBUG:root:sending WILL 3
DEBUG:root:sending WILL 1
DEBUG:root:sending DO 0
DEBUG:root:sending DO 3
DEBUG:root:sending DO 232
DEBUG:root:client wants to 37, sending DONT
DEBUG:root:still waiting for [(251, 0), (251, 3), (251, 1), (253, 0), (253, 3), (253, 232)]
DEBUG:root:client says we should 0
DEBUG:root:client says we should 3
DEBUG:root:client says we should 1
DEBUG:root:client will 0
DEBUG:root:client will 3
DEBUG:root:client will 232
DEBUG:root:still waiting for [(232, 0), (232, 80), (232, 82)]
DEBUG:root:client knows VM commands: [0, 1, 2, 3, 40, 41, 43, 44, 45, 46, 48, 70, 71, 73, 80, 81, 84, 85, 86, 87, 82, 83]
DEBUG:root:client wants to proxy server to vSPC.py
DEBUG:root:still waiting for [(232, 80), (232, 82)]
DEBUG:root:50135d0008cd9717-ae75e41246923123:'cam-vpro30' listening on port 50000
DEBUG:root:client wants to 44, sending DONT
DEBUG:root:sending WILL 0
DEBUG:root:sending WILL 3
DEBUG:root:sending WILL 1
DEBUG:root:sending DO 0
DEBUG:root:sending DO 3
DEBUG:root:sending DO 232
DEBUG:root:client wants to 37, sending DONT
DEBUG:root:still waiting for [(251, 0), (251, 3), (251, 1), (253, 0), (253, 3), (253, 232)]
DEBUG:root:client says we should 0
DEBUG:root:still waiting for [(251, 3), (251, 1), (253, 0), (253, 3), (253, 232) ]
DEBUG:root:client says we should 3
DEBUG:root:client says we should 1
DEBUG:root:client will 0
DEBUG:root:client will 3
DEBUG:root:client will 232
DEBUG:root:client knows VM commands: [0, 1, 2, 3, 40, 41, 43, 44, 45, 46, 48, 70, 71, 73, 80, 81, 84, 85, 86, 87, 82, 83]
DEBUG:root:client wants to proxy server to vSPC.py
DEBUG:root:still waiting for [(232, 80), (232, 82)]
DEBUG:root:still waiting for [(232, 82)]
DEBUG:root:5013b08bae4808fd-bb28b51e53a26365:'cam-vpro37' listening on port 50001
DEBUG:root:client wants to 44, sending DONT
thanks
Last edit: Zach Loafman 2012-05-09
I would love to use this tool, but the port mappings need to stay consistent to work in our environment. Will persistent port mappings be added in the future?
thanks
I don't quite know why sourceforge keeps eating my replies. Sigh.
We have been using persistent port mappings for a while, so I'm not exactly sure what's happening in your configuration/setup. I will try to look at it soon, but $LIFE has been in the way.
I am seeing the exact same behavior. Was there ever a solution for this?