Tagged: 8.5 thinos wms 1.4 mqtt
July 29, 2018 at 2:58 am #47276
I’ve got a few ThinOS 8.5 boxes up and running now for testing, and I’m finding that when I set the URL for our WMS server in the CCM fields (https://wdm.actualdomain.com) it connects to the WMS server, then tries to switch to a newly downloaded server name for the WMS and MQTT servers (ie – from wdm.actualdomain.com to livwsapp208.ad-domain.local), which then causes the ThinOS 8.5 clients to not be able to connect to the WMS server.
The WMS server worked fine with clients up to 8.4, where it would use a valid FQDN with an Internet domain (.com) and a real certificate. With this new “feature” on 8.5, the client is connecting to the valid URL, then it switches to the actual active directory based name of the server that WMS is running on, which doesn’t match the certificates in use, and also isn’t a name that is available to a lot of the DNS servers that our clients are using.
Has anyone else seen this in action? And is there a place that I can configure WMS (currently on 1.1, moving to 1.2 in a few minutes) to pass back the URL that I want it to use instead of the hostname of the virtual machine? Or perhaps there is a place that I can override that setting?
Also, since you no longer are able to enter a MQTT server, and it’s getting the machine name instead of the desired URL, I’d need to figure out how to fix that too.
Thanks.July 30, 2018 at 3:11 pm #47287
We had this problem before.
Check you ccm.ini file and see what it says.
mqtt.server.url=tcp://wms.actualdomain.com:1883July 30, 2018 at 5:52 pm #47298
Hi Johhen –
That sounds like exactly what I’m seeing, but my next dumb questions is where is the ccm.ini file located? I can’t find it on my server…
andrasJuly 31, 2018 at 1:28 pm #47310
C:\Program Files\DELL\WMS\ccm.iniAugust 14, 2018 at 4:57 pm #47424jtaukeParticipant
- Total Post: 3
I’m having this exact same problem. Once our 5060 clients were updated to 8.5, they began trying to change the WMS/MQTT server name to the internal AD name of the WMS server.
However, I can’t seem to find ccm.ini at the path indicated above.August 24, 2018 at 1:40 am #47525
I was never able to find the ccm.ini file anywhere on the server either, but what seemed to work for me was to add a line in my ThinOS advanced config that contained the names of the servers. The log on the devices still show they are trying to switch, but actually can’t as what they are switching to doesn’t exist.
The line (all in a single line) that I put in Advanced Config was this:
CCMEnable=yes AdvancedConfig=yes CCMServer=wdm.domain.com MQTTServer=wdm.domain.com:1883
Switching out the wdm.domain.com for your URL obviously.
Seems to be working for me now.
But if anyone can find the ccm.ini file…I’d like to try that still too.August 26, 2018 at 1:54 am #47553
Update – I went back to testing this morning, and found that it wasn’t working with the config that I posted previously. I did a bit more research and playing, and came up with this one:
CCMEnable=yes CCMServer=https://wdm.domain.com MQTTServer=wdm.domain.com
Switching out the wdm.domain.com for your URL obviously.
With that configuration in my 8.5 advanced settings, I still see the errors about switching names of the server in the system information on the client, however the configuration is downloaded correctly from the WMS and it is also connecting correctly to the server for MQTT (I’m able to send messages and restart the clients). I’ve tested this from factory reset a few times and all is working correctly.
Hope this helps.December 3, 2018 at 11:47 pm #48319
Anyone ever find this ccm.ini file? I am having this exact issue and am swimming through logs trying to figure out why its erroring out.December 4, 2018 at 10:15 am #48321
I think ccm.ini was included in an older version of WMS, but it is still in the directory root of my installation after Upgrades: C:\Program Files\DELL\WMS\ccm.ini
Not sure if it is supported, but maybe you could try to create the file manually with these lines?
Before URL change it looked like this:
Please note that the original ccm.ini file also contain some other settings for jpa.connection pwd, mongodb pwd, tenant e-mail, tenant pwd, local.repo path.December 4, 2018 at 11:18 pm #48332
.If I use a CNAME instead of the AD name, it changes the server back to the AD name for MQTT. It then also states that it needs to reboot because of a server change. If I reboot it at that point, it gets stuck into a boot loop. I then have to factory reset it and it will come up. If I reboot, it goes into a bootloop. This ccm.ini file is non existent and the idea of adding information to the advanced config doesnt seem to work either.December 6, 2018 at 11:57 pm #48344
I never did find any ccm.ini file.
What I did discover is that I had to change the DNS service record to the AD name otherwise all of the clients will get into a bootloop. They configure, see that the server changed to the AD name instead of the CNAME. Change the Visual Settings and then reboot, factory reset themselves because of the server name change and go through the never ending loop.
Is this a confirmed BUG that is listed somewhere? We really do need to use a CNAME. Thank you!January 18, 2019 at 2:19 pm #48877OranionParticipant
- Total Post: 42
- Frequent Flyer
Hi Guys, you to keep you updated.
I faced similar issue after changing my Windows Server Hostname from ServerA to ServerB. We use DHCP Options to send WMS & MQTT to our Clients and even after changing these settings to the new Servername, it kept resetting it to the old “ServerA”. Even if the client was reset to factory defaults.
I then found out that I needed to change the following file to get the thing running. Should also solve your issues, i guess..
=> replace servername of all valuesMarch 4, 2019 at 8:06 pm #49286
I am looking within the bootstrap file and I dont see anywhere where it shows the local server name? am I missing something?August 9, 2019 at 7:18 pm #50556
Did anyone ever figure this out?September 26, 2019 at 7:38 pm #50832the0duke0Participant
- Total Post: 5
We are also using a CNAME on the WMS server, and MQTT was configuring itself to the server’s host name instead of the CNAME. After looking for all the config files listed above I found that you can edit this in the admin portal, at least in WMS 1.4.
Go to Portal Administration -> System -> Setup
and scroll all the way to the bottom.
- You must be logged in to reply to this topic.