Open Ray123456a opened 1 year ago
Seems it takes too long for you to apply the configuration changes. Run netopeer2 with -t 30
to increase the default 5 s timeout.
My netopeer2-server is running with -t 500
Oh, sorry, it is the client that times out, so add --rpc-timeout 500
to the edit-config
command.
Still not work
What netopeer2 version are you using? If the current release, this will most likely be a problem in your callbacks. Perhaps you do not even need such long timeouts but you need to fix a dead lock that you created.
Like I said, you should update first because the next version 2.1.69 includes some concurrency fixes already. But please update to 2.1.71, the latest release.
Hello, I'm trying to build netopeer2 with custom library and header that I've put in other directory by doing this:
but end up meet this error:
Firstly, I do not understand why you are writing into an unrelated issue, you should have created a new one.
It seems you are cross-compiling netopeer2 and so are largely on your own, there is no official guide for that. But the few words mentioning it will be helpful in this case.
Hi, here is my problem, when I configuring the xml, these node parameters can be configured sucessfully, but I didn't recived the "OK" response.