Update IEM to 1.5.4-8-amd64 seems to hang

0
After updating to 1.5.4-8 the ui seems to hang  
asked
5 answers
0

I have the same problem, maybe we can try to restart the VM?

answered
0

I can add some more color to this it appears as if the backend is running (I can see the status in ie hub as active "green") the application on the IEDs are running. 

 

I had a conversation with our solutions partner and he indicated that this was a problem where the backend and the front end get disconnected. 

 

At this point I will have to delete and rebuild the VM (Or Attempt the Factory Reset) option under the BIOS start menu..

 

 

 

Demo_System_Overview_for_Mendix.png

answered
0

I received no error from the update process on the IEM (I used the tab in management).  I cant get to that screen or I would take a picture.  I there a mechanism to recover any logs or other information from the IEM?

 

I also grabbed the last screen at the end of IEM boot (2nd Screen Shot) I see many messages around a problem was detected and the boot script was inserting the "Y" to fix them...  

 

IEM_Issue_After_Update.png

 

IEM_Issue_After_Update_Final_Message_After_Boot.png

 

 

 

 

answered
0

Continued this is what I see using iectl...

 

with this config

 

{
 "iehub": {
  "name": "jbh_iehub",
  "values": {
   "password": "************",
   "url": "***************",
   "user": "jherring@heitek.com"
  },
  "configtype": "iehub"
 },
 "iem": {
  "name": "iem_04",
  "values": {
   "password": "************",
   "url": "10.241.96.20",
   "user": "jherring@heitek.com"
  },
  "configtype": "iem"
 },
 "iem-os": {
  "name": "jbh_iem_os",
  "values": {
   "password": "************",
   "url": "https://172.16.18.128:9443",
   "user": "jherring@heitek.com"
  },
  "configtype": "iem-os"
 }
}

C:\IECTL>iectl iem catalog list
Error: Post "/p.service/api/v4/login/direct": unsupported protocol scheme ""
Usage:
  iectl iem catalog list [flags]

 

answered
0

Dear John. We are still investigating what is the problem with new IEM version 1.5.4. Since we had couple of similar reports, we removed this version from HUB.  We are threating it with highest priority. As soon as I get more info about fix or workaround, I will inform you in this post. 

answered