Update MySQL 5.1 to latest 5.6 version (1 Viewer)

[Arturas1976]

Yep - InnoDB

 

[Hawkeye]

In your folder MySQL Server 5.6 you´ll find the file my.ini - there you can verofy whether innodb is used or not:

Spoiler

[client]
port=3306
[mysql]
default-character-set=utf8
[mysqld]
port=3306
basedir="C:/Program Files/MySQL/MySQL Server 5.6/"
datadir="C:/ProgramData/MySQL/MySQL Server 5.6/Data"
default-storage-engine=INNODB
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
max_connections=100
query_cache_size=32M
tmp_table_size=18M
thread_cache_size=4
thread_concurrency=4
myisam_max_sort_file_size=100M
myisam_sort_buffer_size=64M
key_buffer_size=16M
read_buffer_size=2M
read_rnd_buffer_size=16M
sort_buffer_size=2M
innodb_additional_mem_pool_size=2M
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=96M
innodb_log_file_size=50M
innodb_thread_concurrency=8

But that only shows you the default engine not which engine is actually used by the tables.

 

[Arturas1976]

Workbench showed that it actually used Innodb. So not that is the problem.

 

[catavolt]

Hmm, I think that´s the engine used (in the old 5.1 directory the default is set to myisam - which was used there for tv db)

 

[Arturas1976]

So what to check/do else?

 

[Holzi]

So what to check/do else?

Have you tried to open a command prompt and then navigate to your MySQL bin folder (cd C:\Program Files\MySQL\MySQL Server 5.6\bin) and type: mysql -u root -p

You will get asked for a password, by default it is: MediaPortal (case sensitive)

Once you have done that type: SHOW ENGINES;

INNODB should be the default engine in your case.

Attached screenshot (with MyISAM as default engine):

 

[Arturas1976]

I repeat - yes, default is Innodb. What else could be?

I did uninstall MySQL 5.1 and MP, then made all new installation with 5.6 and then got back the backup.
May be there is some stuff that is not talking well? But anyway I started having such behaviour on 5.1 also.

 

[Hawkeye]

Once again: it's not important which engine is set as default but which one is used by the tables. And that depends on how you restored from backup. If only the data is inserted (SQL command INSERT) there should be no problem with the table type. But if the tables are restored complete (SQL command CREATE) the engine could be set to MyISAM by the query.

To cut a long story short, if I understand you right you checked the tables with workbench and all are using InnoDB, right? So that should not be the problem.

 

[Arturas1976]

Workbench shows tables uses Innodb.

So the problem is not here. The backup was restored by Backup plugin, I do not know how it works.

Can anyone look at the logs and tell why the connection to db is refused?

 

[Vasilich]

[2013-10-17 07:04:03,492] [Log ] [DVB EPG timer] [ERROR] - Exception ystem.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.0.151:31456

Do you have any firewall running on 192.168.0.151? or what else can deny socket connecting?