IEM Virtual (2.3.1-1) on VMWare Workstation Pro Crashes

0
Dear Community,   We have deployed IEM Virtual on VMWare Workstation for demonstration purposes. After some usage, when the application is restarted, we can no longer access Edge Management. Only the Service and Maintenance sections are available using a recovery key.   We have reinstalled IEM Virtual several times, but unfortunately, we encounter the same issue each time.   Based on my initial findings, certain services remain stuck in the "starting" state, particularly the database service (Postgres), which fails to start.   Below are some logs for reference:   - log\pods\iem_auth-service-..\wait-for-postgres 2024-09-25T06:43:42.367305914Z stdout F postgres.iem.svc.cluster.local:5432 - no response2024-09-25T06:43:42.368165504Z stdout F waiting for database - log\pods\iem_postgres.. 2024-09-25T06:39:09.119211342Z stderr F postgresql 06:39:09.11 INFO  ==> ** PostgreSQL setup finished! **2024-09-25T06:39:09.119271691Z stdout F 2024-09-25T06:39:09.144302135Z stderr F postgresql 06:39:09.14 INFO  ==> ** Starting PostgreSQL **2024-09-25T06:39:09.171082815Z stderr F 2024-09-25 06:39:09.170 GMT [1] LOG:  pgaudit extension initialized2024-09-25T06:39:09.188727338Z stderr F 2024-09-25 06:39:09.187 GMT [1] LOG:  starting PostgreSQL 14.12 on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit2024-09-25T06:39:09.18881653Z stderr F 2024-09-25 06:39:09.188 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 54322024-09-25T06:39:09.188837712Z stderr F 2024-09-25 06:39:09.188 GMT [1] LOG:  listening on IPv6 address "::", port 54322024-09-25T06:39:09.18983853Z stderr F 2024-09-25 06:39:09.189 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"2024-09-25T06:39:09.195986786Z stderr F 2024-09-25 06:39:09.195 GMT [89] LOG:  database system was interrupted; last known up at 2024-09-14 08:06:39 GMT2024-09-25T06:39:09.287898669Z stderr F 2024-09-25 06:39:09.287 GMT [89] LOG:  unexpected pageaddr 0/81C4000 in log segment 000000010000000000000012, offset 18513922024-09-25T06:39:09.287926615Z stderr F 2024-09-25 06:39:09.287 GMT [89] LOG:  invalid primary checkpoint record2024-09-25T06:39:09.287933138Z stderr F 2024-09-25 06:39:09.287 GMT [89] PANIC:  could not locate a valid checkpoint record2024-09-25T06:39:09.289014546Z stderr F 2024-09-25 06:39:09.288 GMT [1] LOG:  startup process (PID 89) was terminated by signal 6: Aborted2024-09-25T06:39:09.289028871Z stderr F 2024-09-25 06:39:09.288 GMT [1] LOG:  aborting startup due to startup process failure2024-09-25T06:39:09.293152421Z stderr F 2024-09-25 06:39:09.292 GMT [1] LOG:  database system is shut down     Regards, Fatih
asked
3 answers
0

Hi Fatih,

 

can you please a support request and also provide the IEMV logs downloaded from the maintenance and service user interface please?

 

This would probably require some further analysis.

 

https://support.industry.siemens.com/cs/my/src and select product:

 

"Virtual (Virtual Appliance)" under product family "Industrial Edge Management"

 

Thank you,

Ondrej

answered
0

Hi Fatih,  which type of setup is your IEMV, IP-based or DNS-based? Static IP or DHCP? Is there any additional error/message displayed in the console view of the VM?  Did you change any configuration when importing the .OVA file?

 

Also did you identify if the IEM breaks always after a specific running time or always after a restart?  Do you perform the restart from the Service and Maintenance UI or directly from the VMWare?

answered
0

Hello Cosmin,

 

Thanks for your prompt response. 

Please find my response:

- IP-Based with static IP (I'm was not able to run with DNS-based deployment)

- I did not change any configuration during import

- IEM does not breaks after the first restart but, there is not any specific number of restart or duration before breaks. Actually, it happens when host machine closed i.e. due to power cut etc.

- Receiving authorization error when trying to access edge management.'Unauthorized', url: 'https://192.168.1.52:4443/api/iemaab-api/v1/auth'

 

Note: IED Virtual and IEM Ready VM continue to work without any problem under same conditions.

 

Thanks,

Fatih

answered