Synology DSM6+ - Xibo Docker 1.8+ Installation


#47

Hello!
thanks for the great tutorial @cslaughter.
i tried to install xibo in docker! when i start mysql (5.7.22) then everytime i get the message: Docker-Container: cms-db stopped. if i open the protocol it shows the following picture:


Can someone help me?
I’ve tried the routine several times but it is always the same problem!?
Thanks for any replies.


#48

The error shows that it could not create the database because it already exist. I hate to say it, but you need to wipe out the containers and start again. I know, that isn’t fun, but that should fix your issue

NOTE: If at any point you make a configuration error or want to make a change to either the cms-web or cms-db containers, it is best to delete the containers and start new. (Unless you have previous data. Always backup before anything) Also make sure to remove all files from the database folder before creating a new cms-db container, or you will need to start again.


#49

Hi and thands for the fast reply.
OK. is it a problem if i have installed the php package in the DSM?
Is there a conflict?
greetz


#50

Should not be a problem, as I also have PHP installed.


#51

OK!
So. i deleted every Container, unsinstalled docker.
New(re) install docker.
download: mysql 5.7.18, xibo-cms:release-1.8.9, sivo-xmr:latest.
done with vontainer cms-xmr!
then i configured the container for cms-db.
start aaannnndddd - tadaaaa, same problem.
try to find out the error:
starting putty via ssh conect to synology. and i found out, there is adirectory /var and the next /var/lib too, but there ist no directory /var/lib/mysql

i don’t understand my error!
can someone help me?
thanks
michael


#52

here is what the protocol says:

Initializing database

mysqld: Can’t create directory ‘/var/lib/mysql/’ (Errcode: 17 - File exists)

2018-06-11T20:46:14.788278Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2018-06-11T20:46:14.792952Z 0 [ERROR] Aborting


#53

Milo_r,

Sorry I was on a short vacation.

Looks like you traced the problem back to missing the “mysql” folder, and it not being generated.

In the Docker control panel, on the cms-db container, when you go to volume, does it look like this?

Possible reasons you are missing the “mysql” folder is the “Mount Path” was not set correctly, or that the username and password for SQL have not been setup. I came from an existing database, so I did not need to configure the database Administrator username and password. This article might be helpful.

I think though the SQL Container on the first run sets the all the connection information that it has been supplied with. You did set the “MYSQL_ROOT_PASSWORD”, “MYSQL_PASSWORD”, “MYSQL_DATABASE”, and “MYSQL_USER” before allowing the container to start? If not, then try setting those and see if a folder and database are created then.


#54

Hello @cslaughter!

Everything works fine but I have problems with the XMR, getting this type of errors in all players (Android with 1.8 version):

346997 4aca2e6 2018-07-16 15:07 PLAYER POST ERROR Android Miguel XmrMessageReceiver java.net.UnknownHostException: Unable to resolve host “cms-xmr”: No address associated with hostname 346996 4aca2e6 2018-07-16 15:07 PLAYER POST ERROR Android Miguel onEventBackgroundThread - HeartBeatEvent XMR unresponsive, issue reconfigure.

I have configured the XMR address in Preferences and in the profile with the next address: tcp://cms-xmr:9505. And I also tried with tcp://myhostname:9505 and it didn’t work.
I read all the community posts about this but the problems are still there. I can’t take an instant screenshot and also the content takes so much time to be downloaded to the displays.

Thank you so much for your support!


#55

I believe the problem is with the links on the cms-web docker configuration.

I will look into it more, if that doesn’t help, when I have time.


#56

Hello everybody,

First, thank you for all the job and the help.

My config:

  • Synology DS128+
  • DSM 6.2-23739 Update 2
  • Docker 17.05.0
  • Maria DB 10.3
  • Xibo Docker 1.8.10
  • Xibo player 1.8.10

This is my problem :
After many tries and tests my xibo cms finally work on my synology server. Thank’s again cslaughter.
The only way for me to acces xibo is by the public adress : http*s://MYDOMAINENAME
Impossible to acces by lan adress like 192.168.0.50 or localhost. No matter…

Now I’m trying to connect my display.

  • CMS address : http*s://MYDOMAINENAME
  • Key : Test (same as in xibo - settings - CMS secret key)

The result is : La connexion sous-jacente a été fermée : Une erreur inattendue s’est produite lors de l’envoi.
Which can be transleted by “The underlying connection was closed: An unexpected error occurred while sending.” Sorry I’m french.

I tried with:
http://MYDOMAINENAME - The request failed with HTTP status 405: Not Allowed
http
s://MYDOMAINENAME:443 - The underlying connection was closed:An unexpected error occurred while sending
http*s://MYDOMAINENAME:8888 - Saving with CMS… Please wait… then Can not connect to the remote server

Please, is someone could help me. Thank’s in advance.

Arnaud


#57

I believe your issue with accessing the Xibo via the IP address is with the reverse proxy. By design you will need a FQDN to work with the reverse proxy.

This might help explain wha the reverse proxy does and why you cannot access a server behind it by direct IP without setting up some other routing rules.

https://en.wikipedia.org/wiki/Reverse_proxy

This link might explain to you more the about the 405 error:
https://airbrake.io/blog/http-errors/405-method-not-allowed

Not being able to connect a player is a different issue. You do not need to specify port 443 when using https prefix.

Other things to do is check the date and time on your device and make sure it is correct.
Check you r password


#58

Hi cslaughter, I saw that I have a real problem to acces my nas safely. I’ll look to configure all that. I will keep you updated.

Thanks for your answer.

Arno.


#59

Hello cslaughter,

As I said above, all my configuration work fine. Xibo cms is installed and work fine, reverse proxy too. I can acces to the cms with something like https://xibo.domaine.com.
I took the opportunity to configure the reverse proxy for DSM (files.domaine.com, video.domaine.com, etc), and jeedom (jeedom.domaine.com). Everything work well, from outside and I finally tested all with Quallys SSL labs to check my SSL configuration.

Return is a A note with all indicators in green.

I’m in peace with security !! :grinning:

Alex told to me " Please can you ensure that the reverse proxy is passing through the Host header, and X-Forwarded headers (including X-Forwarded-Proto) to the container? "

I must admit that I am a little overwhelmed by his request. Does that tell you anything?
Do you connect your display with the ip adress or the host name ?

Thank you for your involvement.

@rno.


#60

I just cheked my synology reverse proxy configuration
For me it’s all right :

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;

server_name xibo.domaine.com;

ssl_certificate /usr/syno/etc/certificate/ReverseProxy/c9817a70-f8ce129c3213/fullchain.pem;

ssl_certificate_key /usr/syno/etc/certificate/ReverseProxy/c9817a70-f8ce129c3213/privkey.pem;

location / {
    proxy_set_header        Host                $http_host;
    proxy_set_header        X-Real-IP           $remote_addr;
    proxy_set_header        X-Forwarded-For     $proxy_add_x_forwarded_for;
    proxy_set_header        X-Forwarded-Proto   $scheme;
    proxy_intercept_errors  on;
    proxy_http_version      1.1;

    proxy_pass http://localhost:8888;

}

Do you have the same thing ? It’s located in /etc/nginx/app.d#/server.ReverseProxy.conf

Thanks again.

@rno


#61

I am not sure what mine looks like. I did not change mine manually. I would suggest accessing the reverse proxy settings this way:

I took a screen shot of what mine basically looks like, hopefully that will help you.

I point the displays to an address like https://subdomain.domain.com


Edit: Looking at your reverse proxy .conf file, it does look like it is forwarding what @alex asked you to check.

#62

Good morning everyone,

This is the second time that I have the same problem with this installation. I get the next log errors in the DB container and because of this the page doesn´t load, I don’t know why this happens:

date stream content
2018-10-29 09:24:28 stdout Version: ‘5.6.39’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
2018-10-29 09:24:28 stdout 2018-10-29 09:24:27 1 [Note] mysqld: ready for connections.
2018-10-29 09:24:27 stdout 2018-10-29 09:24:27 1 [Note] Event Scheduler: Loaded 0 events
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Warning] ‘proxies_priv’ entry ‘@ root@cms-db2’ ignored in --skip-name-resolve mode.
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] Server socket created on IP: ‘::’.
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] - ‘::’ resolves to ‘::’;
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] IPv6 is available.
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] InnoDB: 5.6.39 started; log sequence number 5230838672
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] InnoDB: Waiting for purge to start
2018-10-29 09:24:26 stdout 2018-10-29 09:24:26 1 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-29 09:24:24 stdout 2018-10-29 09:24:24 1 [Note] InnoDB: from the doublewrite buffer…
2018-10-29 09:24:24 stdout 2018-10-29 09:24:24 1 [Note] InnoDB: Restoring possible half-written data pages
2018-10-29 09:24:23 stdout 2018-10-29 09:24:23 1 [Note] InnoDB: Reading tablespace information from the .ibd files…
2018-10-29 09:24:23 stdout 2018-10-29 09:24:23 1 [Note] InnoDB: Starting crash recovery.
2018-10-29 09:24:23 stdout 2018-10-29 09:24:23 1 [Note] InnoDB: Database was not shutdown normally!
2018-10-29 09:24:23 stdout 2018-10-29 09:24:23 1 [Note] InnoDB: The log sequence numbers 5230838662 and 5230838662 in ibdata files do not match the log sequence number 5230838672 in the ib_logfiles!
2018-10-29 09:24:23 stdout 2018-10-29 09:24:23 1 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Completed initialization of buffer pool
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Using CPU crc32 instructions
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Using Linux native AIO
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Memory barrier is not used
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 1 [Note] Plugin ‘FEDERATED’ is disabled.
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 0 [Note] mysqld (mysqld 5.6.39) starting as process 1 …
2018-10-29 09:24:22 stdout 2018-10-29 09:24:22 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-10-29 09:23:03 stdout
2018-10-29 09:23:03 stdout 2018-10-29 09:23:03 1 [Note] mysqld: Shutdown complete
2018-10-29 09:23:03 stdout 2018-10-29 09:23:03 1 [Note] Shutting down plugin ‘binlog’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘mysql_native_password’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘mysql_old_password’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘sha256_password’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘CSV’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘MEMORY’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘MyISAM’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘MRG_MYISAM’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘ARCHIVE’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] Shutting down plugin ‘BLACKHOLE’
2018-10-29 09:23:02 stdout 2018-10-29 09:23:02 1 [Note] InnoDB: Shutdown completed; log sequence number 5274495201
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] InnoDB: Starting shutdown…
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] InnoDB: FTS optimize thread exiting.
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘InnoDB’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_TRX’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_LOCKS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMP’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_METRICS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down plugin ‘partition’
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Binlog end
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Forcefully disconnecting 0 remaining clients
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Shutting down slave threads
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Event Scheduler: Purging the queue. 0 events
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] Giving 0 client threads a chance to die gracefully
2018-10-29 09:22:57 stdout
2018-10-29 09:22:57 stdout 2018-10-29 09:22:57 1 [Note] mysqld: Normal shutdown
2018-10-08 10:22:52 stdout Version: ‘5.6.39’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] mysqld: ready for connections.
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] Event Scheduler: Loaded 0 events
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Warning] ‘proxies_priv’ entry ‘@ root@cms-db2’ ignored in --skip-name-resolve mode.
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] Server socket created on IP: ‘::’.
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] - ‘::’ resolves to ‘::’;
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] IPv6 is available.
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] InnoDB: 5.6.39 started; log sequence number 5230838692
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Waiting for purge to start
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Completed initialization of buffer pool
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Using CPU crc32 instructions
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Using Linux native AIO
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Memory barrier is not used
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 1 [Note] Plugin ‘FEDERATED’ is disabled.
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 0 [Note] mysqld (mysqld 5.6.39) starting as process 1 …
2018-10-08 10:22:51 stdout 2018-10-08 10:22:51 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-10-08 10:22:46 stdout
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] mysqld: Shutdown complete
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘binlog’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘mysql_native_password’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘mysql_old_password’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘sha256_password’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘CSV’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘MEMORY’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘MyISAM’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘MRG_MYISAM’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘ARCHIVE’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] Shutting down plugin ‘BLACKHOLE’
2018-10-08 10:22:46 stdout 2018-10-08 10:22:46 1 [Note] InnoDB: Shutdown completed; log sequence number 5230838692
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] InnoDB: Starting shutdown…
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] InnoDB: FTS optimize thread exiting.
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘InnoDB’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_TRX’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_LOCKS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMP’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_METRICS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down plugin ‘partition’
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Binlog end
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Forcefully disconnecting 0 remaining clients
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Shutting down slave threads
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Event Scheduler: Purging the queue. 0 events
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] Giving 0 client threads a chance to die gracefully
2018-10-08 10:22:44 stdout
2018-10-08 10:22:44 stdout 2018-10-08 10:22:44 1 [Note] mysqld: Normal shutdown
2018-10-08 10:18:35 stdout Version: ‘5.6.39’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] mysqld: ready for connections.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] Event Scheduler: Loaded 0 events
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Warning] ‘proxies_priv’ entry ‘@ root@cms-db2’ ignored in --skip-name-resolve mode.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] Server socket created on IP: ‘::’.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] - ‘::’ resolves to ‘::’;
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] IPv6 is available.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: 5.6.39 started; log sequence number 5230838682
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Waiting for purge to start
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Completed initialization of buffer pool
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Using CPU crc32 instructions
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Using Linux native AIO
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Memory barrier is not used
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 1 [Note] Plugin ‘FEDERATED’ is disabled.
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 0 [Note] mysqld (mysqld 5.6.39) starting as process 1 …
2018-10-08 10:18:35 stdout 2018-10-08 10:18:35 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-10-08 10:17:39 stdout
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] mysqld: Shutdown complete
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘binlog’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘mysql_native_password’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘mysql_old_password’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘sha256_password’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘CSV’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘MEMORY’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘MyISAM’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘MRG_MYISAM’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘ARCHIVE’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] Shutting down plugin ‘BLACKHOLE’
2018-10-08 10:17:39 stdout 2018-10-08 10:17:39 1 [Note] InnoDB: Shutdown completed; log sequence number 5230838682
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] InnoDB: Starting shutdown…
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] InnoDB: FTS optimize thread exiting.
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘InnoDB’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_TRX’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_LOCKS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_LOCK_WAITS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMP’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMP_RESET’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMPMEM’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMPMEM_RESET’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_CMP_PER_INDEX_RESET’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_PAGE_LRU’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_BUFFER_POOL_STATS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_METRICS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_DEFAULT_STOPWORD’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_DELETED’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_BEING_DELETED’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_CONFIG’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_CACHE’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_FT_INDEX_TABLE’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLES’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESTATS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_INDEXES’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_COLUMNS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FIELDS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_FOREIGN_COLS’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_TABLESPACES’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘INNODB_SYS_DATAFILES’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘PERFORMANCE_SCHEMA’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down plugin ‘partition’
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Binlog end
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Forcefully disconnecting 0 remaining clients
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Shutting down slave threads
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Event Scheduler: Purging the queue. 0 events
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] Giving 0 client threads a chance to die gracefully
2018-10-08 10:17:37 stdout
2018-10-08 10:17:37 stdout 2018-10-08 10:17:37 1 [Note] mysqld: Normal shutdown
2018-10-08 10:16:14 stdout Version: ‘5.6.39’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)
2018-10-08 10:16:14 stdout 2018-10-08 10:16:14 1 [Note] mysqld: ready for connections.
2018-10-08 10:16:14 stdout 2018-10-08 10:16:14 1 [Note] Event Scheduler: Loaded 0 events
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Warning] ‘proxies_priv’ entry ‘@ root@cms-db2’ ignored in --skip-name-resolve mode.
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] Server socket created on IP: ‘::’.
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] - ‘::’ resolves to ‘::’;
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] IPv6 is available.
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] Server hostname (bind-address): ‘*’; port: 3306
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] InnoDB: 5.6.39 started; log sequence number 5230838672
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] InnoDB: Waiting for purge to start
2018-10-08 10:16:13 stdout 2018-10-08 10:16:13 1 [Note] InnoDB: 128 rollback segment(s) are active.
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Highest supported file format is Barracuda.
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Completed initialization of buffer pool
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Using CPU crc32 instructions
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Using Linux native AIO
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Memory barrier is not used
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: The InnoDB memory heap is disabled
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 1 [Note] Plugin ‘FEDERATED’ is disabled.
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 0 [Note] mysqld (mysqld 5.6.39) starting as process 1 …
2018-10-08 10:16:12 stdout 2018-10-08 10:16:12 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

I’d appreciate so much your help, thanks!


#63

Maybe the problem that I showed up is that I’m trying to create two different and independent CMS in the same NAS Synology. It’s possible that I have an IPs and ports problem.
I’d appreciate so much your help.


#64

2018-10-08 10:22:52 stdout 2018-10-08 10:22:52 1 [Note] Server socket created on IP: ‘::’.

If you are trying to setup two cms instances on the same server, it should be possible, however from the log above, which I don’t fully understand, it looks like the db container is listening on all ips. Which is fine, however the reverse proxy will need to be specific on how everything is being routed. Also the two setups will need to also use different ports and different file paths.

I have not tried to setup two Xibo instances on one server so I can’t really tell you more than that. You may want to shutdown one instance at a time and see if by themselves they work. If so, I think you have either a port or file paths conflict.


2.0 Beta Synolgy
#65

I have installed the two CMS in different paths and redirected to different ports, but on the same IP, and maybe there is the problem. I’m looking for information if it’s possible in Docker to connect the containers to different networks. My DSM model has 4 different LAN connections, so I’d like to say to Docker to connect to a different IP. Idon’t know if someone has the experience doing this.

Thank you so much!


#66

Hello everyone,

I’m having issues with download times of the media, that it is too much. I think that it’s a XMR issue. I’ve tried all the configurations that I read here in the community and I didn’t find the correct way. I don’t know what IP o address I have to write, I’ve tried all of mine, even the XMR docker container Ip, but it didn’t work.

I’d appreciate so mucho your help.

In the next days I will post how to create other CMS in the same Synology DSM.

Thank you!

Miguel