You can translate the question and the replies:

cannoct login through default admin credentials

HI, when we tried to login through default credentials,lunux os it gave us an error as ** CONNECTION ERROR : CONNECTION REFUSED : CONNECT "** checked log sand we found the error as **INTERNAL ERROR : SUPPORT 4 PROCESSORS BUT 6 HAS BEEN FOUND ** then again restricted the processor by ** taskset -c 0-3 ./vqlserver_startup.sh &** now when we tried to connect to vdp by ADMIN credentials error displayed was **AUtHENTICATION ERROR : THE USER NAME AND PASSWORD IS INCORRECT ** We have never changed the admin credentials, guide us how to solve this issue, we dont even have other ADMIN user created apart from default admin user **logs :** 14962 [main] FATAL 2018-06-04T13:13:01.286 com.denodo.util.launcher.ShutdownHandler [] - Unexpected error. Connection refused (Connection refused) java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_151] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_151] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_151] at java.net.Socket.connect(Socket.java:538) ~[?:1.8.0_151] at java.net.Socket.<init>(Socket.java:434) ~[?:1.8.0_151] at java.net.Socket.<init>(Socket.java:211) ~[?:1.8.0_151] at com.denodo.util.shutdown.ShutdownHandler.shutdown(ShutdownHandler.java:228) [denodo-commons-util.jar:6.0.7] at com.denodo.util.shutdown.ShutdownHandler.shutdown(ShutdownHandler.java:253) [denodo-commons-util.jar:6.0.7] at com.denodo.vdb.vdbinterface.server.Shutdown.main(Unknown Source) [denodo-vdp-server.jar:6.0.7] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_151] at com.denodo.util.launcher.Launcher.invokeMain(Launcher.java:143) [denodo-commons-launcher-util.jar:6.0.0] at com.denodo.util.launcher.Launcher.main(Launcher.java:236) [denodo-commons-launcher-util.jar:6.0.0] 859 [main] INFO 2018-06-04T13:13:23.669 server.start [] - Starting Denodo Platform 6.0 20170925 - Operating system: Linux (amd64) - Java(TM) SE Runtime Environment (build 1.8.0_151-b12) - Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode) 2822 [main] FATAL 2018-06-04T13:13:25.632 com.denodo.vdb.util.InternalError [] - Internal Error: Supported 4 processors but 6 have been found. 2822 [main] FATAL 2018-06-04T13:13:25.632 com.denodo.vdb.util.InternalError [] - Internal Error 2822 [main] ERROR 2018-06-04T13:13:25.632 com.denodo.vdb.vdbinterface.server.VDBManagerImpl [] - Supported 4 processors but 6 have been found. 14762 [main] FATAL 2018-06-04T13:17:02.646 com.denodo.util.launcher.ShutdownHandler [] - Unexpected error. Connection refused (Connection refused) java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_151] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_151] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_151] at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_151] at java.net.Socket.connect(Socket.java:538) ~[?:1.8.0_151] at java.net.Socket.<init>(Socket.java:434) ~[?:1.8.0_151] at java.net.Socket.<init>(Socket.java:211) ~[?:1.8.0_151] at com.denodo.util.shutdown.ShutdownHandler.shutdown(ShutdownHandler.java:228) [denodo-commons-util.jar:6.0.7] at com.denodo.util.shutdown.ShutdownHandler.shutdown(ShutdownHandler.java:253) [denodo-commons-util.jar:6.0.7] at com.denodo.vdb.vdbinterface.server.Shutdown.main(Unknown Source) [denodo-vdp-server.jar:6.0.7] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_151] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_151] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_151] at com.denodo.util.launcher.Launcher.invokeMain(Launcher.java:143) [denodo-commons-launcher-util.jar:6.0.0] at com.denodo.util.launcher.Launcher.main(Launcher.java:236) [denodo-commons-launcher-util.jar:6.0.0] 786 [main] INFO 2018-06-04T13:17:53.687 server.start [] - Starting Denodo Platform 6.0 20170925 - Operating system: Linux (amd64) - Java(TM) SE Runtime Environment (build 1.8.0_151-b12) - Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode) 3509 [Thread-3] INFO 2018-06-04T13:17:56.410 com.denodo.tomcat.manager.TomcatManager [] - Tomcat script launched with value 0 5571 [Thread-3] WARN 2018-06-04T13:17:58.472 com.denodo.tomcat.manager.TomcatManager [] - Invalid path '' 6927 [Thread-3] INFO 2018-06-04T13:17:59.828 com.denodo.tomcat.manager.TomcatManager [] - 'denodo-restfulws' has been deployed. 7024 [Thread-3] INFO 2018-06-04T13:17:59.925 com.denodo.tomcat.manager.TomcatManager [] - 'export' has been deployed.
user
05-06-2018 02:38:44 -0400

1 Answer

Hi I have checked the logs that you have supplied and it appears that the VDP Server is running correctly after the taskset changes, so I think that it is likely that you have a mistake in your connection parameters. If the situation is that you have multiple Denodo VDP Servers running, please ensure that you are connecting to the correct VDP Server, and ensure that the authentication details are correct for that server. Also, you can check that you are using the default administrator username/password, which is “admin”/“admin”. If you use “Admin” or “ADMIN” for either it will not work. You can also try and access the Denodo Self Service Information Tool to check if maybe the issue is isolated to the VDP Admin tool. I hope this helps!
Denodo Team
06-06-2018 12:30:09 -0400
You must sign in to add an answer. If you do not have an account, you can register here