[Spce-user] This script should not run on an existing sip:provider installation

[Martin Stix]

Hi,


did this:


PKG=ngcp-installer-latest.deb
wget http://deb.sipwise.com/spce/${PKG}
dpkg -i ${PKG}regards


 


mit freundlichen Grüßen
best regards


Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 50



 Von:   Marc Storck <mstorck at voipgate.com> 
 An:   Martin Stix <ms at pluteus.at> 
 Kopie:   Alex Lutay <alutay at sipwise.com>, "spce-user at lists.sipwise.com" <spce-user at lists.sipwise.com> 
 Gesendet:   30.12.2015 17:12 
 Betreff:   Re: [Spce-user] This script should not run on an existing sip:provider installation 


It’s a known issue and there exists a ticket #15903: https://lists.sipwise.com/pipermail/spce-user/2015-October/009663.html


According to release notes, this was fixed in mr4.0.2, see https://www.sipwise.org/news/announcements/sipprovider-mr4-0-2-released/
and mr4.1.1, see https://www.sipwise.org/news/announcements/sipprovider-mr4-1-1-released/


As the switch to httpS happend in mr4.0.1, it seems like the dependancy is not fixed.


@Martin which version where you trying to install?


Regards,


Marc
 



On 30 Dec 2015, at 17:01, Martin Stix <ms at pluteus.at> wrote:

 
Hi!


I think the only thing missing was apt-get install ca-certificates


regards



 



mit freundlichen Grüßen
best regards


Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 50



 Von:   Martin Stix <ms at pluteus.at> 
 An:   Alex Lutay <alutay at sipwise.com>, <spce-user at lists.sipwise.com> 
 Gesendet:   30.12.2015 16:56 
 Betreff:   Re: [Spce-user] This script should not run on an existing sip:provider installation 

ok got it.


delete following in  /usr/share/ngcp-installer/check.inc



#Check if this is a clean install
if [ -f /etc/sipwise_ngcp_version ]
then
        echo $MSG006 >&2
        exit 1
else
        echo $MSG007
fi


 



mit freundlichen Grüßen
best regards


Martin Stix
CEO
pluteus communication solutions
ms at pluteus.at
Dampfsägestraße 17
3300 Amstetten
Austria
tel.: +43 7472 28165 20
fax.: +43 7472 28165 50



 Von:   Alex Lutay <alutay at sipwise.com> 
 An:   <spce-user at lists.sipwise.com> 
 Gesendet:   30.12.2015 12:36 
 Betreff:   Re: [Spce-user] This script should not run on an existing sip:provider installation 

Dear Martin, 
 
1) Yes you can force installer, just remove the file: 
> install/messages.inc 
> 120:MSG006="ERROR: This script should not run on an existing sip:provider installation." 
... 
> # Check if this is a clean install 
> if [ -f /etc/sipwise_ngcp_version ] ; then 
>         echo $MSG006 >&2 
>         exit 1 
 
Sill, I am not sure about the success story here. 
It depends on the point where previous installer has failed. 
 
2) Can you please share details about the initial installer error. 
I would like to have it fixed. Installer must care about all the 
necessary dependencies. 
 
Tnx! 
 
 
On 12/29/2015 10:35 PM, Martin Stix wrote: 
> I missed some dependencies on a fresh wheezy install and so the 
> installer failed first hand. 
>  
> I resolved all dependencies now but I always get this error running 
> ngcp-installer: 
>  
> ERROR: This script should not run on an existing sip:provider installation. 
>  
> How can I force an install? 
 
--  
Alex Lutay 
_______________________________________________ 
Spce-user mailing list 
Spce-user at lists.sipwise.com 
https://lists.sipwise.com/listinfo/spce-user 


_______________________________________________ 
Spce-user mailing list 
Spce-user at lists.sipwise.com 
https://lists.sipwise.com/listinfo/spce-user 
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20151230/ad8129c8/attachment-0001.html>