My gateway is not running. I have tried some basic trouble shooting from forums, but it hasn't done anything. My url is "http://localhost:8088/web/waiting" I've seen people say try deleting the 'waiting' or try '/home' but it just goes back to 'waiting'. On the Tab it says Gateway Not Running in Chrome, and the screen never actually loads just says "Ignition Gateway is Starting". But on my Services app on windows, it says Ignition Gateway is running.
Can you upload your wrapper.log file(s) from the Ignition install dir?
If very large, include only the end, from the last service restart.
Or zip it 
It's crazy the amount of people that will send 50MB of individually uploaded wrapper log files to support instead of zipping it into practically nothing.
Indeed. But a faulted start is usually pretty short. Probably would fit in a preformatted text block.
1 Like
From the program files: Inductive automation -> Ignition -> logs
I've attached the end of the wrapper.txt file. Do you want wrapper.log.1-5? Sorry I'm very new to this. Thanks in advance. Also I think it could be a problem with the way my VM is set up.
wrapper.txt.txt (18.2 KB)
Nothing more? Even if you wait a while?
It seems to be stuck loading tags from a tag provider:
I [t.m.provider ] [09:03:20.140]: Tag provider initialized. Starting to load tags... provider=wxt_b1a
Did you restore a backup into this gateway? Or did you find yourself in this state after a reboot?
How is this VM provisioned? If it's severely under-provisioned and you're restoring a "full fat" production gateway backup, starting everything up could take a long time; I've seen VMs struggle for tens of minutes to start up.
I found myself here after restoring a backup. So I restored my .gwbk file and then been sat with this all day.
It has 8GB memory, 8processors, 120GB storage. Sorry if this doesn't answer your question. I've never had to use a VM before.
Do you know what the max memory is set to on the gateway backup?
If the ignition.conf file in the backup is requesting more than 8gB (really, if your VM only has 8, Ignition shouldn't receive more than 6gB), then the OS underlying the VM will probably have to start paging - which kills performance on bare metal, and is absolutely going to kill a VM. I'd sort of expect the startup to fail immediately if that were the case, but 
stranger things have happened.
I do not know. Can answer that later if need be. I have someone with more experience with VMs looking at mine now. I'll let you know if that resolves the issue as well.
You can look in the gateway backup, in its ignition.conf. (Gateway backups are just zip files.)
Tell that to one of our customers' IT 
I thought 8GB for the OS would be OK, they were hitting 98% memory so I increased to 12GB (by reducing allocation to ignition) and that still wasn't enough. So they increased the memory allocated to the vm to give 22GB just for the OS. Turns out all the garbage they have on there for monitoring uses up a significant portion of ram. They said up to 20% @pturmel you can probably guess what OS 
3 Likes
wrapper.java.maxmemory=4096
Update! Have had my VM configured differently and is running much better.
Gateway is now up and running. Seems to me it was was issues due to ram/processing power on the VM. Still a bit slow, but don't think that is avoidable. Thank you everyone for your responses.
Thanks for reporting back. Please mark one of the posts above as "Solution" so that it shows up on the main index as solved.