Ticket #3047 (closed Bugs: fixed)

Opened 4 months ago

Last modified 4 months ago

DB Error: already exists

Reported by: giobs Assigned to: p_lindheimer
Priority: major Milestone: 2.5
Component: Core - Trunks/Routing Version: 2.5-branch
Keywords: DB Error Cc:
Confirmation: Need Feedback SVN Revision (if applicable):
Backend Engine: Asterisk 1.4.x Backend Engine Version:

Description

After the last update the problem return... on create one trunk (on save) the error DB appear. I have the Backup set from the 2.5.0alpha1.1 and Online upgrade available (2.5.0beta1.3)...

After the Core 2.5.0Beta1.3 upgrade, the my list trunk "sort" (my creation sort) I have noted "change" and not are possible add any trunk (see error).

I have upgrade ok al other module but if Upgrade the "Core" the problem appear.

Best regards

Change History

08/12/08 06:41:48 changed by p_lindheimer

  • status changed from new to closed.
  • confirmation changed from Unreviewed to Need Feedback.
  • resolution set to worksforme.

In the future, please reference or simply comment on the existing ticket and request it be reopened as your description here is very ambiguous and take time to search for your other tickets in order to figure out what you are talking about.

Second, as requested in the previous ticket, #3019, I again can not repro your issue and you have not provided any detailed repro instructions for us to be able to generate the same error. I again created a SIP trunk as well as a zap trunk. The sip trunk was named the same as an existing sip trunk to try and generate an error that way without success. So again, you need to provide exact repro step of what you created so that we can generate the same error if we are going to be able to see what issue you are having. For now, closing as worksforme again. Please use this same ticket to update the information as we can reopen the ticket if we can see an issue.

08/12/08 09:58:03 changed by giobs

Hi, i have undestand my error sorry.

Because my english I have recorded the session.

The Link: http://www.phonelowcost.com/dberror.htm

Best Regards Giovanni

08/12/08 12:59:24 changed by p_lindheimer

  • status changed from closed to reopened.
  • resolution deleted.

thank you for the details. Turns out this bug exists in 2.4 (and probably 2.3, 2.2, 2.1 and 2.0...) Amazing how such bugs can go un-noticed. The code is flawed and expects all the trunks to be sequential, so if you start creating holes, then you can run into this problem. Anyhow - bug fix coming up shortly.

08/12/08 13:00:33 changed by p_lindheimer

  • status changed from reopened to closed.
  • resolution set to fixed.

(In [6361]) fixes #3047 fixes bug that was supplying an existing trunk id when a new trunk was added in certain circumstances where there had been trunks deleted in the sequence

08/12/08 13:04:04 changed by p_lindheimer

(In [6362]) Merged revisions 6361 via svnmerge from re #3047 http://svn.freepbx.org/modules/branches/2.5

........

r6361 | p_lindheimer | 2008-08-12 13:00:33 -0700 (Tue, 12 Aug 2008) | 1 line

fixes #3047 fixes bug that was supplying an existing trunk id when a new trunk was added in certain circumstances where there had been trunks deleted in the sequence

........

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads