Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: compsos on March 23, 2013, 07:12:25 AM

Title: Upgrading to Ver4 from 3.2
Post by: compsos on March 23, 2013, 07:12:25 AM

Hi
ver sail sail-3.2.0-16.noarch.rpm upgrading to sail-4.0.0-53.noarch.rpm
       smesailenv smesailenv-3.2.0-17.noarch.rpm upgrading to smesailenv-4.0.0-11.noarch.rpm
Is there some sort of upgrade routine that needs to done on the sark.db v3.2 database for 4 to be able to load? 
Asterisk reports no peers and the webpage is blank. Suspect the db does not load. Reloaded using the default DB and tried to regress but only got half the data. Still no extensions or trunks. Did not find any logs indicating the problem. Both the sark access and error logs were good.
Have gone back to sail-3.1.1-22.noarch.rpm and smesailenv-1.0.0-30.noarch.rpm and that is OK on the original DB

Have I missed an instruction somewhere?

Title: Re: Upgrading to Ver4 from 3.2
Post by: apmuthu on March 24, 2013, 07:21:41 AM

Hope you have the backup of sark.db v3.2.0, taken prior to upgrading/downgrading.

Just open it in sqlite3 and take a SQL dump.

Now remove all SAIL and SMESAILENV rpms and install the latest sme4 with:

Code: [Select]

yum remove smesailenv sail
wget http://www.sailpbx.com/sail/sail-4.0-testing/rpms/sail-4.0.0-54.noarch.rpm
wget http://www.sailpbx.com/sail/sail-4.0-testing/rpms/smesailenv-4.0.0-11.noarch.rpm
yum localinstall smesailenv-4.0.0-11.noarch.rpm sail-4.0.0-54.noarch.rpm
signal-event post-upgrade; signal-event-reboot

Now take the sqlite3 dump of the latest /opt/sark/db/sark.db and compare with the old backup and populate as requited and transfer back to the current install and stop and start the pbx.

If you cannot do the last part just send me the two sark.db files and I'll see what can be done.

Title: Re: Upgrading to Ver4 from 3.2
Post by: Teviot on June 20, 2013, 08:49:41 PM

Quote from: apmuthu on March 24, 2013, 07:21:41 AM

yum remove smesailenv sail
wget http://www.sailpbx.com/sail/sail-4.0-testing/rpms/sail-4.0.0-54.noarch.rpm
wget http://www.sailpbx.com/sail/sail-4.0-testing/rpms/smesailenv-4.0.0-11.noarch.rpm
yum localinstall smesailenv-4.0.0-11.noarch.rpm sail-4.0.0-54.noarch.rpm
signal-event post-upgrade; signal-event-reboot

Now take the sqlite3 dump of the latest /opt/sark/db/sark.db and compare with the old backup and populate as requited and transfer back to the current install and stop and start the pbx.

If you cannot do the last part just send me the two sark.db files and I'll see what can be done.

Would this be the same procedure for v3.1.1-27 to v4 ????