this output will show you if you have any memeory avaiable (do this while openfire is running, try repeating it a few times to see fi memory is changing (balooning or something).
Also check to see if you have a swap file setup, as this will help prevent the kernel from forcfully killing your stuff when it’s starving for memory.
the same command of free -m will have a line at the bottom labeled “Swap:”, see if it has numbers in it or if it’s just zero (0). If it’s zero, you dont have swap setup.
Some VPS platforms do not allow swap at all, such as OpenVZ. To my knowledge, many others do such as Xen (XenServer), KVM, etc. However, the OpenVZ VPS’ tend to be the cheapest options (because they are poor in performance and have limitations such as no swap space).
If your system has less than 2GB’s or memory, i’d say set at least 2GB’s of swap. there’s plenty of discussion on the web for proper swap space size, but start with 2GB’s and see what happens.
hmm, ya, 128MB of RAM will probably not work, and 1Gb of ram might be cutting it pretty close, especially after the system has started all it’s services and programs, etc. before you even try to run openfire.
I had their 2GB plan for a while, but outgrew it once I tried to run anything more than a basic website. So I’m now at the 4GB plan. It’s a very very good price for a VPS that is running on an SSD drive (very very fast!).
Have you tried openfire on one of your 1GB VPS' with the 2GB of swap? I think it should work (maybe not comfortably, but should still run).
hmm, maybe try setting openfire up on a local computer that has more than 1GB of ram and see if it works. either you are still running into ram/memory issues (depening on what else you have running at the same time) or somet other issue such as file permissoins, or something. my bet is it’s still resources you’re running out of, mainly ram.
you can try this at the terminal:
watch free -m
this will every 2 seconds show you the memory usage. you can try starting openfire, then running the above command, and see if memory usage spikes then crashes when openfire is killed by the system.