Fatal error after yum update

adopilot

Joined
Oct 2, 2009
Messages
20
Likes
0
Points
0
#1
I have installed Elastix 1.5.2-3
And until today (27.10.2009) everything worked well.
I used sometime unembed FreePBX and always check for updates trought module admin and do update
when FreePBX framework offers it. I did already updates few times on this way and it was ok untill today.
I also from time to time call yum update from console.
Today afert I called yum update from console,
I noticed that there are around 130 MB from install
I said yes and update process did it wihout any errors.
After that I am not able amymore to open PBX tab on elasix main pange.
And also a can't open unembeld FreePBX framwork from internet explorer.
Message I got is
FATAL ERROR
DB Error: no such field

I did yum update again and console said to me "No Packages marked for Update"
I see that asterisk still working and I am able to make calls .
But incamming calls do not working as well.
No response from IVR.

How I can deeply debug what is missing and what is went wrong in update precess.

Thans in advanced
Admir.:eek:hmy:
 

adopilot

Joined
Oct 2, 2009
Messages
20
Likes
0
Points
0
#2
First at all excuse me if I was rude in the previous post.
I just was lose my mind when things went wrong.
also excuse me if my English is terrible.
Here is one past midnight.

From My point of view I thing that I know now what was wrong and I also know (did) corrected things on my server.
Here is some explanation for other if get in similar problems.

As I am freak about last version of everything I did update my unembed FreePBX to last version
trough internet explorer using module admin. That is 2.6.0.0 but this is Relase Candidate

That is worked well until today when I called yum update -y trought putty.
What was append is that last update of elastix trough ports downloaded last stable version
of FreePBX which is freepbx-2.5.2
In fact I downgraded version of freepbx-2.6.0RC2 to freepbx-2.5.2
And probably these two version had different structures of bases and that is way my sever could not work well.

What I did to solve problem is:

First coold my head.
Aftet read elastix withatut tears
and finaly trought console make update FreePBX again to 2.6.0RC2
typing folowing code:

cd /usr/src/
wget http://mirror.freepbx.org/freepbx-2.6.0RC2.tar.gz
tar zxvf freepbx-2.6.0RC2.tar.gz
cd freepbx-2.6.0RC2
./install_amp
asterisk -r
reload
restart now

Another one explanation
Why I was not able to recive calls ?
Because I have custom trunks in /etc/asterisk/sip.conf
and every time I make update i need to add these configuration again
:blush:
 

ramoncio

Joined
May 12, 2010
Messages
1,663
Likes
0
Points
0
#3
Hi adopilot, wellcome to the forum!

You shouldn't touch sip.conf, as it gets overwritten by freepbx everytime you restart amportal. You can only modify sip_custom.conf or sip_general_custom.conf, this last one if you want to add something to the [general] section of sip.conf, as language=es
 

ramoncio

Joined
May 12, 2010
Messages
1,663
Likes
0
Points
0
#4
Also, it is not a good thing to happily install all updates into a production machine, as sometimes things break with updates.
You should make some tests before the update in another box or virtual machine (vmware, virtualbox) or into another hard drive.
Clone your working production hard drive using clonezilla or mondoarchive to a new one and make all updates into this new hard drive, so you always can go back to your original hard drive if problems occur.
 

adopilot

Joined
Oct 2, 2009
Messages
20
Likes
0
Points
0
#5
Thank you on point me to right direction about updates and production servers.
I learned a lesion, not to update everything.
I also did know till yesterday how am I involved into Elastix,
I tested a lot of distros for PBX and did not noticed how I am addicted to Elastix.
Now Ill install yet another server for testing proposes.

When You already mentored edits in sip.conf
Where I need to put corrections like

[sip01]
type=peer
insecure=very
host=80.65.XXX.XXX
username=38733XXXXXXX
permit=80.65.XXX.XXXX/255.255.255.255
qualify=yes
call-limit=20
context = from-trunk
disallow=all
allow=alaw
allow=ulaw

I am still new in all this stuff like CetOS, FreePBX, Asterisk and other
Thank you in advanced
 

ramoncio

Joined
May 12, 2010
Messages
1,663
Likes
0
Points
0
#6
That should go into sip_custom.conf
 

kingmony

Joined
Nov 12, 2009
Messages
3
Likes
0
Points
0
#7
thank you so much. You solved my problem with this post.
 

voya

Joined
Apr 6, 2009
Messages
15
Likes
0
Points
0
#8
th very much, you saved my day.
 

Patrick_elx

Joined
Dec 14, 2008
Messages
1,120
Likes
0
Points
0
#9
just make sure that you exclude freepbx from the yum update as it will not check if you already upgraded freepbx manually and can downgrade it. And there were a lot of DB changes between 2.5 and 2.6.
 

voya

Joined
Apr 6, 2009
Messages
15
Likes
0
Points
0
#10
thanks for the tip.So what do you suggest.meybe I should backup first,then install 2.6,and restore backup.

Thanks again.
 

Patrick_elx

Joined
Dec 14, 2008
Messages
1,120
Likes
0
Points
0
#11
you should always do a full backup before any (major) update.

you can use the command:
Code:
yum update --exclude=freePBX*
or better to hard code it in /etc/yum.repos.d/elastix.repo
add in [elastix-updates] the line
Code:
exclude=freePBX.noarch
 

Joshoua

Joined
Jul 14, 2009
Messages
15
Likes
0
Points
0
#12
Thanks man.
This worked for me also.
;)
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,912
Messages
130,916
Members
17,589
Latest member
cristian.saiz
Top