vicidial.org

Hello everyone,

I've got a Vicibox Redux v.3.1.15 server with Vicidial 2.12b0.5 SVN 2530 and asterisk 1.4 on which i was also running Limesurvey.

Due to the newest version requiring MySQL 5.5.3 i had to do an upgrade of MySQL.

I created a VPS clone of the server to test with.
I first went into Yast and used this repository:
http://download.opensuse.org/distributi ... /repo/oss/
I then upgraded mysql-community-server from v5.1.57-0.3.1 to v5.5.16-3.3.1
I got an error about unknown option '--skip-locking' which i solved by disabling that in my.cnf
I then used this repo http://download.opensuse.org/distributi ... /repo/oss/
And upgraded to mysql-community-server v5.5.30-1.1.1

I checked apache error log, mysql error log, messages but i don't see anything gamebreaking. The web interface and asterisk are still running.

So far as i can see all is running fine. But how can i be sure no problems will come of this?

MySQL doesn't change enough from version to version to cause any issues. As long as it's there and running it should be fine. Similar to NTP and networking, it must merely be present and functional.

BUT: Beware the my.cnf entries. Vicidial requires some unusual settings pertaining to capacity (specifically the number of open connections is freakin' huge by comparison to normal/default). So be sure to check settings against the Vicidial my.cnf.

We do NOT recommend running MySQL 5.5 or higher. We instead recommend switching to a comparable MariaDB version, like most Linux distros have done in the last 2 years. Unfortunately, MySQL 5.5 removed a lot of legacy code that helped it to run better, That code is still in MariaDB, which is a drop-in replacement for MySQL.

I stand corrected. So does LimeSurvey require MySQL or will it run on MariaDB 5.5?

Gentlemen, thank you for the feedback.

I just installed MariaDB this way:

First I uninstalled mysql community server with yast and then rebooted.
Then I proceded to install mariadb-client and libmariadb-client16.
Then I installed mariadb server.
I made a backup of my.cnf and created a new my.cnf from one of the newer vicibox servers that came with mariadb.
After rebooting I noticed mariadb would not start automatically. To fix that I had to use yast and then go to System>System Services (Runlevel) and enable mysql.

Then i installed Limesurvey and it worked fine. Now i will do the same steps on the production server and hope no problems will arise. The difference there is that i have to do a limesurvey upgrade whereas on the test server i did a clean install.

Update: The upgrade succeeded on the operational server but only Mariadb and asterisk won't start during boot.

I can start them by doing the

Code: Select all

rcmysql start

and

Code: Select all

/usr/sbin/asterisk -vvvgc

commands.

Then i wanted to change the startup config by using Yast > System > System Services (runlevel) but when i did that Yast got stuck on loading the next screen at 28% and when i rebooted the server my inittab, boot and rc files were corrupted. Luckily i had backups of those from another server and the server is up again.

But now i have the same problem of asterisk and mariadb not starting on boot.

How do i fix this?