Moved to a new VPS hosting. (server with 650 mb ram)
I fresh installed the latest java JDK
I fresh installed wowza 2
root@cpanel [/usr/local/WowzaMediaServer/bin]# ./startup.sh
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I searched the wowza forums, and found threads suggesting to edit
/usr/local/WowzaMediaServer/bin/setenv.sh
I did that. I think originally it was
JAVA_OPTS="-Xmx768M"
I tried instead:
JAVA_OPTS="-Xmx384M"
and also:
JAVA_OPTS="-Xmx128M"
But I still get memory errors and Wowza won`t run.
Take a look at this line in the log startup lines:
Hardware Physical Memory: 275MB/1024MB
The VMS has 1024MB of RAM, but only 275MB is free. I think there is even less by the time java heap is allocated then Wowza continues to startup. This is just not a good server for Wowza.
Right, sorry. So you already down to 128. Well, you have to keep going lower till it works. Even at 128 it is not a very useful streaming server anyway. Take a look at the Wowza partners page for other hosting options:
After having installed JDK and Wowza again, without errors and trying to run it as a standalone for the first time, instead of a prompt for Serial I get the usual error.
The wowzamediaserver_error.log was empty and these are the contents of the wowzamediaserver_access.log right after the error:
Following your suggestion, Richard, I gave up my previous attempt to move to this new host, and stayed with my previous one. 2 months gone by and Im trying again, on a new server and having the exact same problem with yet another host. The first time it was Mochahost, now its vpsLatch. The strange thing is that both hosts offer packages with 1024 RAM and the current host on which Wowza is running without problem has only 768 RAM !
I installed wowza without errors on the new host but when trying to start it I got:
Then I edited the bin/setenv.sh to:
JAVA_OPTS="-Xmx128M"
Then I tried running it again and this time I get:
(The Log error I get is only because I tried editing the Log4j.properties file in order to get a log of the problem and did a bad job, I need to fix that)
But this time it says 285mb out of 1024 (whereas in the previous host, it said 275MB out of 1024MB)
Does this host , too lack RAM or am I having here some other kind of a problem?
Not sure about what production level actually means. My current host is running Wowza and serving flv files without problem with only 768MB RAM.
Are saying, JasonH, that I should be thankfull its running in the current host as it its not supposed to and that if I want to move to a new one I`d better make sure it has no less than 4 GB RAM, please?
I changed the heap size to 100, than 64 than 32 than 16 - same error no matter what.
Richard, I must admit I`m very confused.
How can it be that on Hostgator`s “VPS3” package of 768MB RAM everything is running without any error, with the original heapsize setting of 768M, and two new different servers who claim more RAM have the exact same error occurs no matter how ridiculously low I go with the heap size?
I admit my knowledge and understanding of the java environemnt is nil. Still, I simply dont understand how no amount of memory is low enough especially, as Im not working it hard, just attempting to run without any load while on the working server it can carry the load of multiple clients requests. I cannot help but wonder if there is not a missing factor or setting here.
I tried reproducing the same conditions as on the working server - such as installing JRE instead of JDK and then installing the same older JRE version (build 1.6.0_18-b07) but to no avail.
Thanks for the list of Wowza-partners but as far as I could understand they are rather streaming services and not low-cost VPS services on which I can install Wowza by myself, or if they are, prices are much higher than what I`m aiming at currently, while developping my environement
I invested a lot of time and effort in adapting scripts and modules for Wowza to my needs, and maybe I`m on the step of giving it all up which to me is really sad.
Maybe it Helps Idk i got the same error as u got , i just modified the Heap Size File on Wowza to 512 M then it started and i got the Java Error That u got Above then i Changed to 128 M and it simply worked no lags or something i am streaming with 4500 Kbps everything is alright , i bought a server with 10 Gbps Nic so now it goes very good
