[Spce-user] Observations/issues after upgrading to 3.6.1 - nginx

Alex Lutay alutay at sipwise.com
Wed Nov 19 03:48:58 EST 2014


Dear Thomas,

To prevent this situation for the following SPCE users,
we have updated upgrade scripts (released as mr3.6.1 hotfix).
We are going to check availability of file /etc/ngcp_nodename,
it's content and content of DB fields ngcp.[db|cfg]_schema.node.

I hope it helps old SPCE users fix the system integrity before upgrade
and prevent mystery issues during/after upgrade.

Stay tuned!

On 18/11/14 11:50, Thomas Odorfer wrote:
> many thanks for the explanation and all your efforts.
> I probably missed the change of procedure concerning the handling of
> node name (versus the older variant relying on the hostname) during on
> of the previous releases - I remember that I had once modified
> cfg_schema.node back to my hostname as one of the upgrade scripts for
> the accounting database got stuck.
> Good move to separate node name from host name.

-- 
Alexander Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Office: +43(0)13012036
Email: alutay at sipwise.com
Website: http://www.sipwise.com

Meet us @ AFRICACOM : Booth A17/A18
11-13 November 2014 : CTICC Cape Town, South Africa



More information about the Spce-user mailing list