Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Simon Fishley
Error: "This instance is inactive. Please contact..."
April 29, 2012 10:56 AM
Answer

Simon Fishley

Rank: New Member

Posts: 2

Join Date: April 29, 2012

Recent Posts

Hi

I am setting up the community edition on a Debian6 machine using the tomcat bundled version. IF I use the system with the bundled hypersonic DB it works fine. If I reinstall and point the server at my mSQL server, the DB is populated during the install which suggests permissions are all ok but then after the installation process the message "This instance is inactive. Please contact the administrator." is displayed in the browser window.

I found a entry on the issue tracker here: http://issues.liferay.com/browse/LPS-22971 but to be honest it does not suggest a resolution to the problem although the bug seems to be resolved?

Can anyone suggest a solution?

Thanks
Simon

/edit

This shows in catalina.out as the error occurs:
==> catalina.out <==
13:50:30,614 INFO [BaseDB:409] Database does not support case sensitive queries
13:50:30,668 ERROR [JDBCExceptionReporter:75] Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
13:50:30,672 INFO [PortalImpl:4873] Current URL /c/portal/setup_wizard generates exception: Unable to get class name from value com.liferay.portal.model.Group
Simon Fishley
RE: [Resolved] Error: "This instance is inactive. Please contact..."
April 29, 2012 10:55 AM
Answer

Simon Fishley

Rank: New Member

Posts: 2

Join Date: April 29, 2012

Recent Posts

The error above pointed me in the correct direction. The problem lies with mySQL in the binlog format. See below:

mysql> show global variables like "%binlog%";
+-----------------------------------------+------------+
| Variable_name | Value |
+-----------------------------------------+------------+
| binlog_cache_size | 32768 |
| binlog_direct_non_transactional_updates | OFF |
| binlog_format | STATEMENT |
| innodb_locks_unsafe_for_binlog | OFF |
| max_binlog_cache_size | 4294963200 |
| max_binlog_size | 1073741824 |
| sync_binlog | 0 |
+-----------------------------------------+------------+
7 rows in set (0.00 sec)

mysql> SET @@global.binlog_format=mixed;
Query OK, 0 rows affected (0.00 sec)

mysql> show global variables like "%binlog%";
+-----------------------------------------+------------+
| Variable_name | Value |
+-----------------------------------------+------------+
| binlog_cache_size | 32768 |
| binlog_direct_non_transactional_updates | OFF |
| binlog_format | MIXED |
| innodb_locks_unsafe_for_binlog | OFF |
| max_binlog_cache_size | 4294963200 |
| max_binlog_size | 1073741824 |
| sync_binlog | 0 |
+-----------------------------------------+------------+
7 rows in set (0.00 sec)

Note, this change will only be effective as long as the current instance of mySQL runs. To make it permanent add this to your my.cnf


binlog_format=mixed

Cheers.
peter muiga -----------------------
RE: Error: "This instance is inactive. Please contact..."
May 23, 2013 2:26 AM
Answer

peter muiga -----------------------

Rank: New Member

Posts: 1

Join Date: February 18, 2013

Recent Posts

it turned out that in my case i was using MySQL 5.0 which does not support 4byte UTF8-characters. i changed the mysql version and it worked.