[Spce-user] Spce-user Digest, Vol 10, Issue 15

cappellari at connectlife.it cappellari at connectlife.it
Wed Apr 15 14:06:19 EDT 2020

Hi, thanks for replying. I confirm that DB encryption is active. I installed sipwise on the new server from the ISO. After the installation I launched the ngcp-initial-configuration command. Then I restarted the server and replaced the ngcp-config, import db etc. Do I need to also import /etc/mysql/debian.cnf?

----- Messaggio originale -----
Da: spce-user-request at lists.sipwise.com
A: "spce-user" <spce-user at lists.sipwise.com>
Inviato: Mercoledì, 15 aprile 2020 18:00:04
Oggetto: Spce-user Digest, Vol 10, Issue 15

Send Spce-user mailing list submissions to
	spce-user at lists.sipwise.com

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
	spce-user-request at lists.sipwise.com

You can reach the person managing the list at
	spce-user-owner at lists.sipwise.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Spce-user digest..."

Today's Topics:

   1. Re: Move Sipwise 8.3.1 to another server (Alex Lutay)


Message: 1
Date: Tue, 14 Apr 2020 22:37:50 +0200
From: Alex Lutay <alutay at sipwise.com>
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Move Sipwise 8.3.1 to another server
Message-ID: <9d803207-0125-01cd-20da-31860e584886 at sipwise.com>
Content-Type: text/plain; charset=utf-8

Hi all,

re: /etc/mysql/sipwise.cnf

mr8.3.1 doesn't operate with /etc/mysql/sipwise.cnf
It was deprecated and removed in mr8.1.1+:

> https://www.sipwise.com/doc/mr8.1.1/spce/?_href=ar01s14.html
> Deprecated and removed /etc/mysql/sipwise.cnf, please use /etc/mysql/sipwise_extra.cnf [TT#68021] 

Anyway both those files are generated from templates in a modern release
~mr6.5+, so no need to copy it manually.
Please report if you still see in a modern documentation:

> The system configuration files such as /etc/mysql/sipwise.cnf and the
> /etc/ngcp-config/ directory should be included in the backup

On my side:

> 22:36:27 ? taurus:(master)~/sipwise/git/documentation$ ack "sipwise.cnf"
> debian/changelog
> 67:  * [80136c1] TT#68021 Add remark about Deprecated /etc/mysql/sipwise.cnf to mr8.1 release notes
> 68:  * [736174d] TT#68035 Remove /etc/mysql/sipwise.cnf from documentation
> 22:36:30 ? taurus:(master)~/sipwise/git/documentation$ 


re: mysql start issue

Good to check mysql error log: /var/log/mysql/error.log
also systemd can print something to /var/log/syslog

Maybe it is somehow related to DB encryption, is it enabled for
your installation? It is enabled by default for mr8.3.1:

> root at spce:~# grep crypt /etc/mysql/my.cnf 
> # Encryption options
> innodb_encrypt_tables             = force
> innodb_encrypt_log                = 1
> encrypt_binlog                    = 1
> innodb_encryption_threads         = 1
> innodb_tablespaces_encryption
> root at spce:~# 

Or there could be the issue with credential in /etc/mysql/debian.cnf for
user debian-sys-maint.

Please share your findings.

On 4/14/20 12:12 PM, Robert Cuaresma wrote:
> On the Handbook:
> ? System configuration
> The system configuration files such as /etc/mysql/sipwise.cnf and the
> /etc/ngcp-config/ directory should be included in the backup
> Is it possible that you didn?t copy /etc/mysql/sipwise.cnf?
> Saludos,
> Robert Cuaresma
> ?
> *De:* cappellari at connectlife.it <cappellari at connectlife.it>
> *Enviado el:* martes, 14 de abril de 2020 12:06
> *Para:* spce-user at lists.sipwise.com
> *Asunto:* [Spce-user] Move Sipwise 8.3.1 to another server
> ?
> Hello everyone! I need to move a sipwise installation to another server.
> I copied the ngcp-config folder to the new server, exported the DB with
> mysqldump and reimported to the new server, applied the configuration
> with ngcpcfg apply. Everything works, but when I restart the server the
> mysql service does not start, as a consequence also the kamailio proxy
> and dependent services. I need to delete the idbdata file from /
> ngcp-data / mysql to restart mysql. It looks like an innodb corruption
> issue. Some advice?

Alex Lutay


Subject: Digest Footer

Spce-user mailing list
Spce-user at lists.sipwise.com


End of Spce-user Digest, Vol 10, Issue 15

More information about the Spce-user mailing list