I Broke My VM Asterisk 13.20.0.rc2 on Google Cloud

A note about sizing an Asterisk VM on GCP is very important with all of the packages I installed, Jansoon, Mariadb, creating a database, installing asterisk odbc connector, selecting specific repositories, configuring conf files, tuning for performance plus monitoring, storage of log files, and iptables from a 10 gig I only have 118 MB of space left and the server will not allow me to log in via telnet, gui or ssh in. This is good to know and I am working with tech support to try and save the instance. Will update. This is for 13.20.0.rc2 on Centos X86_64 and I have redo the ubuntu 16.04 installation because I am not able to install asterisk 1.6. Searching for solutions:

/usr/src/asterisk- multiple definition of `ast_str_append’
hashtest2.o:/usr/src/asterisk- first defined here
collect2: error: ld returned 1 exit status
/usr/src/asterisk- recipe for target ‘hashtest2’ failed
make[1]: *** [hashtest2] Error 1
Makefile:422: recipe for target ‘utils’ failed
make: *** [utils] Error 2

There is no guarantee that Asterisk 1.6 will build on modern distributions. Compilers and such change, and each time that happens we have to make changes to Asterisk to ensure it continues to build and work. These changes are generally done before releases occur so most people never notice. Older versions don’t receive these changes.

@jcolp painfully I am learning this would you recommend 13 or 15 LTS?

13 is the current LTS. 15 is standard. Support timeframes are on the wiki[1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

1 Like

@jcolp 13 it is thanks. Will update any issues?

If you have any problems then create a new thread and someone may help.

Will do @jcolp there are differences installing Asterisk 13.20.0.rc2 on Centos and Ubuntu. Major differences will post my findings afterward. The broken Centos 7 Server might have to be redone depending on the communication with Google Cloud Support. This is a good thing have to review my notes for exponential growth of files over a period of time.

@jcolp this is the reply I received from Google Support about installing 13.20.0.rc2, pjproject, mariaDB to store call information in a database from one call to test.

“You had VoIP traffic at that time, that Asterisk stored the recordings on uncompressed WAV files and that filled up most of the space.”

As a workaround, my suggestion is to backup the current disk, spin up another instance, attach the disk to that VM and try to free up space from there.

My question for me to research is how to size Asterisk with Database for exponential growth for at least five years?

Next is there a way to compress wav files?


Asterisk stores it in the format provided, there are other formats and they may have different compression. Otherwise you have to do post processing to a format that would work for you.

@jcolp there is much to consider. Thanks