Can't edit trunks (fatal sql error) after upgrading to the latest version

[V4705]

It worked yesterday, today I upgraded to the latest version (Asterisk v1.8.3.2, FreePBX v2.10.0.0) and when I'm trying to edit an existing trunk, I get a long, long error, starts with:
FATAL SQL ERROR! ::::: SELECT tech FROM devices WHERE id = OUT_3 [nativecode=1054 ** Unknown column 'OUT_3' in 'where clause']SQL -

There's no problem creating new trunk, just edit (even new ones).

Edit: I can't use "duplicate trunk" also.


Many thanks!

 

[darmock]

what do you mean you upgraded?

Of course you did not include a copy of the output from status as we request. That being said it will be impossible to assist you until you do.

See this post

http://pbxinaflash.com/community/threads/need-help-post-better-info-first.1858/?t=1858


Then perhaps someone can answer your question. I assume from your version you are using PIAF 1757. Unfortunately if you updated from 2.8 (default in 1757) to 2.10 you may not have the best results. If you have a burning actual need for 2.10 then install PIAF 2062X


Tom

 

[V4705]

Sorry I thought you mean the system status in FreePBX so I just posted the version number, thats the status info through the command line:

Asterisk = ONLINE | Zap/Dahdi = UNKNOWN | MySQL = ONLINE
SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE
Fail2ban = ONLINE | Internet = OFFLINE | Ip6Tables = OFFLINE
BlueTooth = ONLINE | Hidd = ONLINE | NTPD = ONLINE
SendMail = ONLINE | Samba = OFFLINE | Webmin = OFFLINE
Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A

PBX in a Flash Version = 1.7.5.5 Running on *HARDWARE*
FreePBX Version = 2.10.0.0
Running Asterisk Version = 1.8.3.2
Asterisk Source Version = 1.8.3.2
Zap/Dahdi Source Version = N/A
Libpri Source Version = 1.4.11.5
IP Address = 192.168.1.211 on eth0
Operating System = CentOS release 5.5 (Final)
Kernel Version = 2.6.18-194.26.1.el5 - 64 Bit




I'm running 1.7.5.5 purple and upgrading always just through "Module admin", last update was around 10-20 modules, so I guess that's a big update.

Anyway I have many issues,
The PBX box froze around 7am, nobody even was in the office (just got an email from a monitoring app).

What's your suggestion?

 

[darmock]

Regardless we require the posting of the status output. if you notice in your original post 1755 was NOT mentioned. This is why we want this information.

Why did you update? What was your reasoning doing this? Was your PBX not working?

Unfortunately I suspect you are hosed and the simplest thing is to reinstall with PIAF 206X. (1757 is deprecated and in security fix only mode) We still do not recommend using freepbx 2.10 on production servers AT ALL. Lats time I looked it was release candidate status thus still BETA.

Unfortunately users don't realize that a PBX is not a windoze box that needs to be upgraded every 10 secs. There IS NO REASON to EVER upgrade a box unless there is a REAL and VERIFIABLE security problem. Commercially in my business where I maintain a lot of PIAF systems I NEVER upgrade the boxes once the system is stable. This includes CENTOS/Freepbx/Asterisk/et al. I finally replaced my last original piaf box which had an uptime of 4 years. Never did an upgrade on that box ever.

So if your business depends on the phone to make money is it the right choice to "fiddle" with it if it is working?

I am sure you dont like rants but....


so

1. Backup your system
2. Scrub and reinstall with the latest PIAF 2062x


Or you can pay someone to go in and attempt to fix your existing machine.... big $$$


Have fun

Tom

BTW If there is a new feature that you just have to have then you should think carefully about it and if you decide make to go ahead make a bunch of backups and test the crap out of the backup/restore capability prior to doing any changes. We put out working versions however as soon as the user does upgrades all bets are off. Impossible to support sorry.

 

[V4705]

I made a clone hdd before upgrade so I can switch back in a second.
I'm upgrading for security and stability reasons, I thought there might be some small issues that got fixed in the next version.

Plus, ChanSpy never worked for me (dropping calls) and my managers asking for that every time, so I hoped it will fix that also...



Many thanks!

 

[darmock]

install PIAF 2602 it is stable and does run 2.10 plus it directly supports the freepbx commercial modules. Course I would not install freepbx 2.10 on a production machine until it has more history and is stable.

Tom


Tom

 

[V4705]

Thanks!

On production server, what's the recommended version right now?
I see there are 3 versions of 206X available for download (1.1, 1.2 & 2.1), and I can always go back to my original 1.7.5.5 with no updates.

 

[gregc]

I can confirm that freepbx 2.10 is out of rc stage and is now 2.10.0.0

2.10 is really growing on me though I did have it up on a test system for nearly two months before moving to live status. Our 'old' box remains right there at the ready in case something bad happens.

-Greg

 

[darmock]

You should only ever use the latest versions this will be the last version you will be able to install with using older versions of the iso. So only use 20621.

As for freepbx out of testing Great! We still think of it as beta till it has been around a while. Once there is some historical data about how stable and reliable it is we will move it out of our beta status. Thus at the moment we can only recommend freepbx 2.9 as it has sufficient history and is stable enough for us.

NOTE This is not denigrating freepbx we are CAUTIOUS! Things have bitten us in the butt before so we take the show me and prove to me I am skeptical approach.


Tom

 

[V4705]

I will adapt your system, stability and reliability are my top concerns.

 

[tm1000]

This is an endpoint manager problem and is described in several freepbx tickets

 

[tm1000]

The fix has already been released through SVN

 

[V4705]

How can I implement this fix on my current machine (all info on 1st page).

Many thanks!

 

[tm1000]

Module admin, check for updates

How can I implement this fix on my current machine (all info on 1st page).

Many thanks!

 

[tm1000]

freepbx.org/trac/ticket/5638

 

[V4705]

Great! that fixed my problem.

Many thanks!