[Spce-user] 500 Internal server error when saving Peer Group changes on mr3.2.1

Joel S. | VOZELIA joel at vozelia.com
Mon May 12 20:54:50 EDT 2014


Hi, 

I have seen some package updates recently for MR3.2.1, I have updated following the usual steps but this problem persists.

I know you have it fixed already and it is just a matter of time until you push it to the repos... Any ETA?

Thanks!

Best regards, 
Joel.

----- Original Message -----
> From: "Joel Smith | VOZELIA" <joel at vozelia.com>
> To: "Andreas Granig" <agranig at sipwise.com>
> Cc: "Spce-user" <spce-user at lists.sipwise.com>
> Sent: Friday, April 25, 2014 9:38:53 AM
> Subject: Re: 500 Internal server error when saving Peer Group changes on mr3.2.1
> 
> Hi Andreas,
> 
> Could you confirm if the next update will fix also the 500 error when saving
> peer group changes on MR3.2.1?
> 
> Best regards,
> Joel.
> 
> ----- Original Message -----
> > From: "Joel Smith | VOZELIA" <joel at vozelia.com>
> > To: "Spce-user" <spce-user at lists.sipwise.com>
> > Sent: Friday, April 4, 2014 11:51:34 AM
> > Subject: Re: 500 Internal server error when saving Peer Group changes on
> > mr3.2.1
> > 
> > Hi,
> > 
> > This seems to be the same problema as:
> > 
> > [Spce-user] Internal 500 error - when i acess GUI-> security bans
> > 
> > I'll wait until the next update.
> > 
> > Thanks.
> > 
> > Best regards,
> > Joel.
> > 
> > 
> > ----- Original Message -----
> > > From: "Joel Smith | VOZELIA" <joel at vozelia.com>
> > > To: "Spce-user" <spce-user at lists.sipwise.com>
> > > Sent: Wednesday, April 2, 2014 6:19:34 PM
> > > Subject: 500 Internal server error when saving Peer Group changes on
> > > mr3.2.1
> > > 
> > > Hi,
> > > 
> > > I am having issues saving any changes on a peering group in mr3.2.1.
> > > Every
> > > change I make to an existing peering groups get saved but I get the
> > > following error:
> > > 
> > > 
> > > Sorry!
> > > 
> > > 500 Internal server error
> > > 
> > > We are terribly sorry, an exceptional error has occured:
> > > 
> > > incident number: 136134E0C3C85850
> > > time of incident: 2014-04-02T16:18:19.423570000Z
> > > 
> > > 
> > > In oss.log I can see this when I push the "save" button:
> > > 
> > > Apr  2 18:18:15 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:15 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto skip authn, grant access to back
> > > Apr  2 18:18:15 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:15 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:15 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Peering::auto
> > > Apr  2 18:18:16 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:16 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:16 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Peering::auto
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Peering::auto
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Peering::auto
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:18 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Contract::auto
> > > Apr  2 18:18:19 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto called
> > > Apr  2 18:18:19 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: ***
> > > Root::auto grant access for authenticated user
> > > Apr  2 18:18:19 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > NGCP::Panel::Controller::Peering::auto
> > > Apr  2 18:18:19 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl:
> > > dispatching xmlrpc proxy-ng request to 127.0.0.1:5062/
> > > Apr  2 18:18:19 spce1 /usr/share/ngcp-panel/ngcp_panel_fastcgi.pl: fatal
> > > error, id=136134E0C3C85850, timestamp=2014-04-02T16:18:19.423570000Z,
> > > error=Caught exception in NGCP::Panel::Controller::Peering->edit "Not a
> > > CODE
> > > reference at /usr/share/perl5/NGCP/Panel/Controller/Peering.pm line 124."
> > > 
> > > 
> > > 
> > > Is anyone on mr3.2.1 having this same problem? Any ideas how ti solve it?
> > > 
> > > Best regards,
> > > Joel.
> 




More information about the Spce-user mailing list