Avaliable Memory in ignition.conf

Ignition
1

I run my Ignition server on a VM and recently cloned it to do some testing. I was in the process applying Windows updates, upgrading Java and upgrading Ignition from 7.1.6 to 7.1.7. On the original server I had edited ignition.conf to allow Java to access 2048 MB of ram. After the edit, it still showed a max of 1,022 mb available on the gateway. Now, on my cloned machine, it shows 2.0 gb available. Nothing was changed in ignition.conf, and I noticed it even before all the upgrades on the cloned machine. Any though on why this might be? I am including a capture of the status pages from both servers.

Thanks!

systemStatus.jpg773×287 51.1 KB

2

48 days of uptime tells me you haven’t restarted the first server (the one with only 1GB still).

Changing the config file doesn’t take effect until you restart the service. Maybe upgrade to 7.1.7 while you’re at it and you should see it change.

3

I don’t know why I didn’t try that first… Bonehead move on my part. Will perform a restart over the weekend and post results.

Thanks!