All
Larry Prikockis Switchvox memory leak -> High swap usage since upgrade to 5.8.5
Has any progress been made on a fix to this memory leak problem with 5.8.5? Having to reboot our phone system every few days after it freezes is not what I would call an acceptable workaround for an Enterprise-class product :(
Alternatively, is there a way to downgrade a Switchvox appliance to an earlier version of the software?
Alternatively, is there a way to downgrade a Switchvox appliance to an earlier version of the software?
There is a resolution slated for 5.9.1 which should be out very shortly.
If you have support, you can open a tech support ticket and we can install a script that runs a cron job every hour to keep the memory down until the formal release of the fix.
If you would like to rollback the version, you will need to have a backup made on the earlier version as backups must be restored to the same version they were taken on.
You would lose any configurations, voicemail, logs, that were done after that backup.
Here is a link to steps on restoring:
http://support.digium.com/articles/FAQ/How-to-rollback-to-a-previous-Switchvox-version?retURL=%2Fapex%2FKnowledge&popup=false
Thank you,
All Answers
There is a resolution slated for 5.9.1 which should be out very shortly.
If you have support, you can open a tech support ticket and we can install a script that runs a cron job every hour to keep the memory down until the formal release of the fix.
If you would like to rollback the version, you will need to have a backup made on the earlier version as backups must be restored to the same version they were taken on.
You would lose any configurations, voicemail, logs, that were done after that backup.
Here is a link to steps on restoring:
http://support.digium.com/articles/FAQ/How-to-rollback-to-a-previous-Switchvox-version?retURL=%2Fapex%2FKnowledge&popup=false
Thank you,
Also- re: this cron job fix-- would this involve dropping calls every hour when it runs or is it non-destructive?
thanks
Hello,
D P: The cron job install is a recent option as a patch until the permanent, true fix is released, and yes, we did only have the option to manually run the script before.
We understand the frustration this issue has caused many of our customers, but it was not identified when 5.8.5 was released, but quite a bit after, and engineering is working very hard on resolving it as quick as possible.
Larry: We have been told tentatively this month, but I cannot say that is in stone.
The cron job will not disrupt business or drop calls or anything of that nature.
Thank you.
Are we any closer to this mythical 5.9.1 release? I can't understand how a supposedly "enterprise" solution can be rolled out with such a showstopper of a fault and so many months go by with no real fix.
As a result of this, we've been directed by our senior management to start looking into alternative phone solutions. I know software has bugs, but the people who pay the bills have lost all confidence in this product :(