The caret sign ^ means to match the most recent minor version. Removing it is fine if it works for you.
I don't understand your second question. Can you provide details?
I'm having an issue updating my HTML5 fling from 3.42 to the latest. I've tried 4.0, 4.1, and 4.2. the log shows all sorts of Java errors during the install, unable to stop the service, and then says that the service already running. The upgrade never happens.
My vCenter is VCSA Version 6.5.0.23000 Build 10964411. The HTML5 fling appliance was installed as 3.38 OVA and upgraded a few times up to 3.42.
I'd like to use the Fling as newer features become available on that versus the 6.5 VCSA baked version.
Okay, I ran the update manually and rebooted the appliance. It came up as 4.2.0 but it will not connect to my vCenter.
When I run the command manually to configure and start the service -
/etc/init.d/configui configure --start yes --user root --vc <IP_Address_Of_vCenter> --ntp <your_NTP_server> i see this:
ssh failed to log into <vcenter/PSC>
vSphere Client stopped!
configuring NTP
Adding 10.10.5.254 to /etc/ntp.conf
Requesting NTP daemon restart
Connecting to SSO server, you will be prompted for user's credentials
ssh failed to log into vcenternh01.measuredprogress.org
Waiting for vSphere Client to start: 0 seconds
Waiting for vSphere Client to start: 3 seconds
Waiting for vSphere Client to start: 6 seconds
Waiting for vSphere Client to start: 9 seconds
and so on.
I've deployed a brand new OVA - and it still won't SSH into my VC with embedded PSC.
Rebooted it and manually ran the commands as stated above again and it worked. Stopping and starting the service now responds normally without Java errors on the latest OVA.
Hi,
i have noticed that on the vSphere Client Fling ver. 4.2 the licenses assigned at the host vae alway the "never expire" as expireation date, while in the vmWare vSphere web client with flash, i have the date of the expiration. Can someone help me?
Thank!
I followed the steps in plugin-seed-doc.pdf and there are some issues.
I did following steps to make it execute like normal:
1. I remove "^" sign of "rxjs" and "rxjs-compat" in package.json.
2. There are 2 question marks after the executing generate-plugin.sh in "vSphereClientSdkTypes.ts".
Is there any side effect for development ?