2012-06-19 03:22:26 rvd: Unable to create transport on UDP port XXX. Previously created transport specified network as '192.168.XXX.15;192.168.180.255;192.168.XXX.125' which caused the send address for the port to be bound to 192.168.XXX.125, while current transport specifies network as ';;192.168.XXX.51;;' which requests the send address to be bound to 192.168.XXX.51. You cannot associate the same service parameter with two different network parameters.
./tibrvsend: Failed to initialize transport: Arguments conflict
In the above case just change the service port number and accordingly on the listener side. The above error is normal. Here the subnet is different So so the UDP port being reserved by some time . after sometime it will be released automatically.
If you do not want to wait upto release just use another service port . careful if the same port may be used by any other service. So better have a grep to /etc/services with the used port. In the most worst case just restart the RVD.
Example :
./tibrvsend -network ";;192.168.188.51" -service XXXX -daemon tcp:7500 Test.message "Hello World"
Next use
./tibrvsend -network ";;192.168.199.156" -service YYYY -daemon tcp:7500 Test.message "Hello World"
./tibrvsend: Failed to initialize transport: Arguments conflict
In the above case just change the service port number and accordingly on the listener side. The above error is normal. Here the subnet is different So so the UDP port being reserved by some time . after sometime it will be released automatically.
If you do not want to wait upto release just use another service port . careful if the same port may be used by any other service. So better have a grep to /etc/services with the used port. In the most worst case just restart the RVD.
Example :
./tibrvsend -network ";;192.168.188.51" -service XXXX -daemon tcp:7500 Test.message "Hello World"
Next use
./tibrvsend -network ";;192.168.199.156" -service YYYY -daemon tcp:7500 Test.message "Hello World"
No comments:
Post a Comment