I’m very new to Ignition SCADA and no previous experience. I have watched few basic intro videos on YT and I have installed Standard trial version 8.1.49. I am provided with .gwbk backup file made in version 8.1.35, with no additional data. I have found out the actual version by using Zip utility to look into the backup.
First thing after installation of standard Ignition version is to go to config and choose Backup/restore. I have checked box “Restore Disabled”, but when restoring process starts, I have windows “This take a moment” with “Ignition Gateway is Unknown” and it stays like that, like it is stuck.
In case I shutdown the browser, I can see that Ignition service is disabled and it stays like that.
How to troubleshoot what the problem is and if there is some quicker time to fix Gateway again without reinstalling Ignition?
The most common reason for that situation is a different port in the backup from the base install. The defaults are 8088 (http) and 8043 (https), but many prefer to switch to the standard ports, 80 and 443. The web UI can't know this ahead of time, so will continue trying on 8088 or 8043.
Use netstat to see if Ignition is listening on an unexpected port.
Thank you for you reply.
I have managed to find a reason, it is a bit bizarre. I inspected wrapper.log and found this in the log:
os::commit_memory(0x0000015d46000000, 33554432000, 0) failed; error='The paging file is too small for this operation to complete' (DOS error/errno=1455)
From some reason in the .conf file, initial memory was set to 32 Gb and max memory to 54 GB, while in fact I have about 20 GB free space on my disk.
Those aren't a disk space setting, but memory usage settings. If you tell Ignition to use more memory than you have RAM, and your OS has a paging file, it may attempt to satisfy the request with virtual memory instead of real RAM.
Don't let this happen. If the application really needs such a large RAM allocation, and its max doesn't easily fit within your own hardware's real RAM size, you will need better hardware.
Yes, for sure only 16 GB RAM available, but virtual memory could not compensate that, because also not enough disk space. Probably if I had more disks space, it would take longer time, but would finish eventually.
If your hardware cannot keep Ignition entirely within RAM, your hardware is insufficient.
Consider editing ignition.confwithin the backup (using zip utils) before restoring. So you can set the memory limits to something more appropriate for your hardware. (In a 16GB machine, I recommend no more than ~12GB if a headless server. Less if other apps will be running.)