MDS SmartDashboard component failed to connect to server x.x.x.x

[czinu]

Hello,

I have freshly installed 1 x R80.40 Management Server  + 1 x R80.40 MDS as OpenServers. I am using initial 15 days license as of now.

After creating domain on MDS and login into it I cannot do anything with the following failure message on SmartConsole.

SmartDashboard component failed to connect to server x.x.x.x. Please contact technical support.

Any ideas?

Thanks in advance.

[Tal_Paz-Fridman]

Hi,

Does it happen consistently, each time?

Could you please try to restart the services on the relevant machine (mdsstop + mdsstart) and see if it still happens?

[czinu]

I did two or three fresh installations, added jumbo fixes in the meantime and it had the same issue all the time. It still does not work after restart of services.

For the record I am adding outputs of the mdsstart, mdssart, mdsstat api, status commands.

[Tal_Paz-Fridman]

Thank you for the details.

Could you also try using one of the the MDSs where it happened with a new installation of SmartConsole, preferably on a different Windows machine?

If a different machine is not available, try using a Portable SmartConsole.

Thanks

[the_rock]

Something is messed up here : (. So if mdsstat shows all up, makes no sense why you keep getting that error in dashboard. So, just to make sure I got this right, you do log into dashboard, but then once you see that error cant click on anything, right? If you did fresh install 4 times, dont waste time doing it again, thats not the issue then. Can you run cpwd_admin list command on mds level and send the output? Im afraid this may need some debugs, depending on whats causing it.

[czinu]

Yes thats right, after login to specific domain via SmartConsole when I click anything I get the same error all over again.

I am trying to arrange new windows server to check it with new installation of SmartConsole as suggested by  Tal_Paz-Fridman

In the mean time output of cpwd_admin list.

CP-DEMO-MDS8040-NEW> cpwd_admin list
APP PID STAT #START START_TIME MON COMMAND
CPD 17201 E 1 [09:17:15] 23/11/2021 Y cpd
CPM 17517 E 1 [09:17:18] 23/11/2021 N /opt/CPsuite-R80.40/fw1/scripts/cpm.sh -s
SOLR 17597 E 1 [09:17:20] 23/11/2021 N java_solr /opt/CPrt-R80.40/conf/jetty.xml
RFL 17638 E 1 [09:17:20] 23/11/2021 N LogCore
SMARTVIEW 17687 E 1 [09:17:21] 23/11/2021 N SmartView
INDEXER 18131 E 1 [09:17:25] 23/11/2021 N /opt/CPrt-R80.40/log_indexer/log_indexer
SMARTLOG_SERVER 18482 E 1 [09:17:28] 23/11/2021 N /opt/CPSmartLog-R80.40/smartlog_server
CPD.CP-DEMO-MS8040-NEW 19511 E 1 [09:17:46] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPshrd-R80.40/bin/cpd'
CPVIEWD.CP-DEMO-MS8040-NEW 19529 E 1 [09:17:46] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPshrd-R80.40/bin/cpviewd'
FWD.CP-DEMO-MS8040-NEW 19606 E 1 [09:17:47] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPsuite-R80.40/fw1/bin/fwd -n'
FWM.CP-DEMO-MS8040-NEW 19621 E 1 [09:17:47] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPsuite-R80.40/fw1/bin/fwm'
INDEXER.CP-DEMO-MS8040-NEW 21405 E 1 [09:18:02] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPrt-R80.40/log_indexer/log_indexer'
SMARTLOG_SERVER.CP-DEMO-MS8040-NEW 22212 E 1 [09:18:15] 23/11/2021 N cma_with_wd CP-DEMO-MS8040-NEW '/opt/CPmds-R80.40/customers/CP-DEMO-MS8040-NEW/CPSmartLog-R80.40/smartlog_server'
DASERVICE 22770 E 1 [09:18:22] 23/11/2021 N DAService_script
FWD 22773 E 1 [09:18:22] 23/11/2021 N fwd -n
FWM 22776 E 1 [09:18:22] 23/11/2021 N fwm mds
CPVIEWD 22778 E 1 [09:18:23] 23/11/2021 N cpviewd
CPVIEWS 22782 E 1 [09:18:23] 23/11/2021 N cpview_services
REPMAN 22792 E 1 [09:18:23] 23/11/2021 N java_repository_manager

[the_rock]

Ok, that looks real good, everything is established, nothing in terminated state, which is exactly what you want to see. Now, here is question, as silly as it may seem...have you ensured you are using LATEST smart console build? If so, please try another PC and let us know the results. Im probably not nearly Provider-1 expert as @Tal_Paz-Fridman is, but I worked with it in the past, though before R80 version, but I know the core of all the commands and how it works had not changed much.

[czinu]

still no luck. I have tried it on windows 10 (previously win7) and build 425 of both portable and non portable SmarConsole. Now I am trying to install R81 MDS and see if there is any difference.

[the_rock]

To add to what @Tal_Paz-Fridman said, you can also run mdsstat and check if all shows ok status. Its is a bit odd it would happen on brand new config.