You can translate the question and the replies:

VDP Service went down

The VDP service on the VDP server has failed. We learned from the log that the problem occurred because it was unable to connect to Solution Manager. It entered grace period, which will conclude in five days.However, prior to that, VDP services were unavailable.We also verified that Solution Manager was operational and that the SM load balancer for licence registration was operational at the time. VDP log as follows 902618460 [main] ERROR 2023-05-22T12:25:19.098 com.denodo.solutionmanager.Info [] - Error sending license ACK (1/3). Retrying in 5000 ms. Unknown host: ****************: Name or service not known 902812872 [main] ERROR 2023-05-22T12:28:33.510 com.denodo.solutionmanager.Info [] - Error sending license ACK (2/3). Retrying in 5000 ms. Unknown host: *******************: Name or service not known 902607215 [DNI I/O-Client(50)] ERROR 2023-05-22T12:25:07.853 com.denodo.internal.o.a.r.netty.DenodoKeepAliveSenderHandler [] - Timeout checking channel [c6eeed31-/0.0.0.0:9999] state. Keep alive check sent 2023-05-22T16:09:33.241Z but no response received. Closing channel 902814318 [ODBC(76)-172.28.65.195] ERROR 2023-05-22T12:28:34.956 com.denodo.vdb.vdbinterface.client.util.iterator.VDBResultSetIterator [] - Exception ... com.denodo.internal.o.a.r.client.ClosedException: null at com.denodo.internal.o.a.r.pool.FixedConnectionPool.get(FixedConnectionPool.java:58) ~[denodo-asyncrmi.jar:8.0.7] at com.denodo.internal.o.a.r.client.UnicastRef.send(UnicastRef.java:210) ~[denodo-asyncrmi.jar:8.0.7] at com.denodo.internal.o.a.r.client.UnicastRef.invoke(UnicastRef.java:132) ~[denodo-asyncrmi.jar:8.0.7] at com.denodo.internal.o.a.r.client.RMIInvocationHandler.invokeRemote(RMIInvocationHandler.java:160) ~[denodo-asyncrmi.jar:8.0.7] at com.denodo.internal.o.a.r.client.RMIInvocationHandler.invoke(RMIInvocationHandler.java:137) ~[denodo-asyncrmi.jar:8.0.7] at com.sun.proxy.$Proxy39.notifyEndRequest(Unknown Source) ~[?:?] at com.denodo.vdb.vdbinterface.client.AbstractVDBProxy.getNextResult(Unknown Source) ~[denodo-vdp-client.jar:8.0.7] at com.denodo.vdb.vdbinterface.client.AbstractVDBProxy.getNextResult(Unknown Source) ~[denodo-vdp-client.jar:8.0.7] at com.denodo.vdb.vdbinterface.client.util.iterator.VDBResultSetIterator.hasNext(Unknown Source) ~[denodo-vdp-client.jar:8.0.7] at com.denodo.vdb.jdbcdriver.VDBJDBCAsyncResultSet.next(VDBJDBCAsyncResultSet.java:1807) ~[denodo-vdp-jdbcdriver.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.ODBCBackend.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.QueryAdapter.d3(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.ODBCFrontend.h3(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.ODBCFrontend.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.ODBCFrontend.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] at com.denodo.vdb.vdbinterface.server.odbc.ODBCListener$ODBCConnection.run(Unknown Source) ~[denodo-vdp-server.jar:8.0.7] 902814319 [ODBC(76)-172.28.65.195] ERROR 2023-05-22T12:28:34.957 com.denodo.vdb.vdbinterface.client.util.iterator.VDBResultSetIterator [] - Unable to connect to the server 902814319 [ODBC(76)-172.28.65.195] ERROR 2023-05-22T12:28:34.957 com.denodo.vdb.vdbinterface.server.odbc.ODBCBackend [] - Error: unexpected exception; nested exception is: com.denodo.internal.o.a.r.netty.KeepAliveException: Channel time out exception. Channel not available at least since 2023-05-22T16:09:33.241Z 902819909 [main] ERROR 2023-05-22T12:28:40.547 com.denodo.solutionmanager.Info [] - Error sending license ACK (3/3). Unknown host: ***************************** 902819910 [main] ERROR 2023-05-22T12:28:40.548 com.denodo.solutionmanager.Info [] - Error sending license ACK. Server starts to use a grace period of 7200 minutes. Grace period finishes at Sat May 27 12:28:40 EDT 2023 902996937 [DNI(3246)] ERROR 2023-05-22T12:31:37.575 com.denodo.internal.o.a.r.netty.RMIServerHandler [] - EXCEPTION CAUGHT on channel [id: 0xbb80d59b, L:0.0.0.0/0.0.0.0:9999 ! R:/10.120.64.59:52754]: Connection reset by peer java.io.IOException: Connection reset by peer
user
23-05-2023 04:55:46 -0400
code

2 Answers

Hi ! I have some issue on my VDP server went to "grace period" so I openend I ticket to support and they reply me with this command http://"your_solution_manager-ip":10091/externalShutdown?nodeIp=&hostDomainName="VDP_server_IP"&port=9999&product=VDP It will shutdown your VDP server so It will not be on grace period anymore, I hope it will help you for this part.
user
23-05-2023 08:44:24 -0400
Hi, In general the below error usually occurs when the server is running and tries to retrieve the license, but there is no response, then it will enter the grace period.If a Denodo server stops working unexpectedly, you have to manually notify the License Manager that the license that this Denodo server was using, is no longer in use. Otherwise, the license will be considered in use until the grace period expires (5 days since the last time this Denodo server renewed its license). > 902819910 [main] ERROR 2023-05-22T12:28:40.548 com.denodo.solutionmanager.Info [] - Error sending license ACK. Server starts to use a grace period of 7200 minutes. Grace period finishes at Sat May 27 12:28:40 EDT 2023 Hence to freeup license usage, I would perform the following: 1.Send a request to the following endpoint by replacing the appropriate values for <Port> and <Host> of License Manager and VDP servers: `http://<LICENSE_MANAGER_HOST>:<LICENSE_MANAGER_PORT>/externalShutdown?nodeIp=&hostDomainName=<VDP_SERVER_HOST>&product=VDP&port=<VDP_SERVER_PORT>` 2.Restart the Virtual DataPort server. For more information you could refer to the Free license Usage section of [**REST** **API**](https://community.denodo.com/docs/html/browse/latest/en/solution_manager/administration/appendix/rest_api/rest_api#free-license-usage) User Manual. If you still need help and if you are a user with valid support access then you can raise a support case in Denodo Support Site so that our support team can help you. Hope this helps.
Denodo Team
24-05-2023 01:28:05 -0400
code
You must sign in to add an answer. If you do not have an account, you can register here