Koozali.org: home of the SME Server

upgrading from an old version

Offline jibe

  • ****
  • 128
  • +0/-0
upgrading from an old version
« on: December 19, 2009, 11:20:42 AM »
Hi,

As I had this problem of callback, I'm still using -688 version. This is now difficult to upgrade my SME with Zaptel giving me headaches each time with kernel changes, and I now badly need callback.

I should like to upgrade SAIL and use DAHDI while being sure that callback will work. What should I do (this is a production server) ? Can I just uninstall and reinstall Asterisk and Sail, keeping all my phone config ?

Thanks.

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: upgrading from an old version
« Reply #1 on: December 22, 2009, 02:29:16 AM »
Quote
Can I just uninstall and reinstall Asterisk and Sail, keeping all my phone config ?

Not from that far back...  The latest SVN number is -r1107, which means you are about 400 iterations behind.  That's a little difficult to manage in one go.  Here's what you can try... 

NB - BACK EVERYTHING UP BEFORE YOU START!

Take a copy of the sail database, you'll find it at /home/e-smith/db/selintra.  Also, just to be on the safe side, take copies of any greetings you've recorded (assuming you wish to keep them).  A USB pen drive is ideal for this.
 
Now, do a completely fresh sail install; preferably on a different physical machine to minimise downtime and so that you can continue to run the old system in the event of problems.

Download the little merge routine which you will find at http://sarkpbx.com/sail/utilities/aelmerge.pl

Now point the merge routine at the old DB file you saved at the beginning.  It might look something like this...

Code: [Select]
perl aelmerge.pl /media/mypendrive/selintra
the routine will merge your old DB into the new one. 

With a bit of luck you should be good to go.  However, I cannot stress enough that you MUST set everything up initially such that you can regress to the old system in the event of something going bang.

Kind Regards

S   

 

Offline apmuthu

  • *
  • 244
  • +0/-0
Re: upgrading from an old version
« Reply #2 on: December 22, 2009, 06:57:43 PM »
Where is the SAIL SVN located for public read access?

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #3 on: February 10, 2010, 03:04:15 PM »
Hi,

I had more urgent things to do and I'm trying this only now...

I have a problem with aelmerge.pl : I tried several ways to get it, but each time I obtain a file containing html code !!! Could you verify please ?

Thanks.

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: upgrading from an old version
« Reply #4 on: February 10, 2010, 05:47:30 PM »
yes there is a problem with the module.

I'll see if we can fix it

Kind Regards

S

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #5 on: February 10, 2010, 09:58:07 PM »
Ok, thanks. I'll just wait about it.

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: upgrading from an old version
« Reply #6 on: February 11, 2010, 12:47:48 AM »

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #7 on: February 11, 2010, 02:37:00 PM »
Hi,

Ok, thanks  :-)

I'll try asap and let you know.

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #8 on: February 11, 2010, 06:22:23 PM »
The merge worked well, but I have still a problem... Here is what I did :

- Save all (automatically done by Affa)
- Save the selintra database
- remove old version of Sail and Asterisk (yum remove of all rpms)
- post-upgrade and reboot
- Reinstall new version of Sail and Asterisk
- console-save, post-upgrade and reboot
- Save the new database
- Merge the old database with aelmerge.pl
At this time, I was able to see all my trunks, extensions, routes etc. But all trunks and all extensions were marked as unconnected. A commit in the General Settings panel, and all my trunks were connected. But nothing to do to connect the extensions. I tried :
- Commit on the extensions panel,
- Edit and commit an extension,
- console-save, post-upgrade and reboot

Even if I create a new extension, it cannot get connected...

I was unable to go further : this is a production server, I had to go back to the old version so that it can work. I'll have to try again during the close hours...

Any suggestion ?

Offline SARK devs

  • *****
  • 2,806
  • +1/-0
    • http://sarkpbx.com
Re: upgrading from an old version
« Reply #9 on: February 11, 2010, 10:22:49 PM »
If you do sip show peers and the extensions are there in asterisk then it is either firewall or some other network issue.  I guess you need to redo it when you have more time on the switch.  Alternatively try a test server install first.

I'm assuming you haven't changed subnets or anything of that nature.

Kind Regards

S

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #10 on: February 12, 2010, 11:45:08 AM »
Hi,

I guess you need to redo it when you have more time on the switch.
Yes, sure !

Waiting for that, I took the log of Asterisk. I begin to analyse it, and here is the beginning :
Code: [Select]
[Feb 11 15:13:01] NOTICE[7835] cdr.c: CDR simple logging enabled.
[Feb 11 15:13:01] NOTICE[7835] loader.c: 161 modules will be loaded.
[Feb 11 15:13:02] NOTICE[7835] res_odbc.c: Adding ENV var: INFORMIXSERVER=my_special_database
[Feb 11 15:13:02] NOTICE[7835] res_odbc.c: Adding ENV var: INFORMIXDIR=/opt/informix
[Feb 11 15:13:02] NOTICE[7835] res_odbc.c: res_odbc loaded.
[Feb 11 15:13:02] WARNING[7835] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Feb 11 15:13:02] WARNING[7835] res_musiconhold.c: Cannot open dir /var/lib/asterisk/moh or dir does not exist
[Feb 11 15:13:02] WARNING[7835] res_musiconhold.c: No music on hold classes configured, disabling music on hold.
[Feb 11 15:13:02] NOTICE[7835] chan_ooh323.c: ---------------------------------------------------------------------------------
---  ******* IMPORTANT NOTE ***********
---
---  This module is currently unsupported.  Use it at your own risk.
---
---------------------------------------------------------------------------------
[Feb 11 15:13:02] NOTICE[7835] chan_ooh323.c: Unable to load config ooh323.conf, OOH323 disabled
[Feb 11 15:13:02] NOTICE[7835] config.c: Registered Config Engine odbc
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: Starting AEL load process.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: calculated config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: parsed config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: checked config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: compiled config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: merged config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] NOTICE[7835] pbx_ael.c: AEL load process: verified config file name '/etc/asterisk/extensions.ael'.
[Feb 11 15:13:03] ERROR[7835] res_config_pgsql.c: Postgresql RealTime: Failed to connect database server asterisk on 127.0.0.1. Check debug for more info.
[Feb 11 15:13:03] WARNING[7835] res_config_pgsql.c: Postgresql RealTime: Couldn't establish connection. Check debug.
[Feb 11 15:13:03] NOTICE[7835] config.c: Registered Config Engine pgsql
[Feb 11 15:13:03] ERROR[7835] res_config_mysql.c: MySQL RealTime: Failed to connect database server  on  (err 2002). Check debug for more info.
[Feb 11 15:13:03] WARNING[7835] res_config_mysql.c: MySQL RealTime: Couldn't establish connection. Check debug.
[Feb 11 15:13:03] NOTICE[7835] config.c: Registered Config Engine mysql
[Feb 11 15:13:03] NOTICE[7835] cdr_radius.c: Cannot load radiusclient-ng configuration file /etc/radiusclient-ng/radiusclient.conf.
[Feb 11 15:13:03] WARNING[7835] cdr_addon_mysql.c: MySQL database sock file not specified.  Using default
[Feb 11 15:13:03] NOTICE[7835] cdr_addon_mysql.c: MySQL database table not specified.  Assuming "cdr"
Why this unsupported chan_ooh323.c ? Why res_config_pgsql.c when I have not PostGreSQL installed on this server ? Did I installed some wrong module(s) ? :shock:

If you do sip show peers and the extensions are there in asterisk then it is either firewall or some other network issue
In the hurry, I just looked at the server-manager. But I should be surprised that something goes wrong with the firewall or anything else in the network : nothing changed, I only uninstalled the old version of SAIL with zaptel and installed the last one with dahdi... There is probably another reason ! PostgreSQL ?

Offline jibe

  • ****
  • 128
  • +0/-0
Re: upgrading from an old version
« Reply #11 on: February 15, 2010, 10:48:21 PM »
Hi,

No comments about the log ? Could somebody tell me if those lines with PostgreSQL are normal ? I worry about those errors with PostgreSQL and with MySQL : did I installed a wrong module ?