Hi,

I've downloaded the latest 7.x-2.42 of OA2, but I'm not able to install it on any system.
Neither a running web server (PHP 5.5.9-1, MySQL 14.14) nor a fresh / clean installed VM Ubuntu 15.04 (PHP 5.6.4-4, MySQL 14.14).

The standard installation works, but not the quick installation (which is recommended).
Running the quick install encounters the error I've captured (see attachment).

/var/log/apache2/error.log sys:

[Thu Jun 25 16:13:10.491190 2015] [:error] [pid 1031] [client 10.10.100.70:64223] PHP Fatal error: Call to undefined function node_types_rebuild() in /myatriumpath/includes/common.inc on line 7618, referer: http://url/install.php?profile=openatrium&locale=en&db_import_filename=/...

I don't know what to do.

Thank you.

CommentFileSizeAuthor
#11 oa1.PNG31.44 KBflb
#5 database.PNG54.21 KBflb
#4 atrium.PNG625.91 KBflb
screen5.png45.3 KBflb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mpotter’s picture

MySQL 14.14? That doesn't sound right.

However, it sounds like your hosting infrastructure isn't up to the System Requirements. If it's the Quick install not working, be sure your MySQL is set up with max_allowed_packets at 32M or larger. Also your php memory settings and max execution time are important. The Quick Install is doing a large number of SQL Table imports that are large in size. But unless you have an incompatible version of MySQL it should work fine.

Works fine on Pantheon, Acquia, local VMs, Mac MAMP which are the main test systems here.

mpotter’s picture

Priority: Major » Normal

Also, on drupal.org you should never mark support requests as anything other than Normal priority.

flb’s picture

Hi mpotter,
thanks.

As I said: I've setup a local VM, especially for Open Atrium.
Here are my current settings (which don't work):

/etc/php5/apache2/php.ini:

max_execution_time = -1
max_input_time = -1
max_input_nesting_level = 300
memory_limit = 768M

/etc/mysql/mysql.conf.d/mysqld.cnf:

key_buffer_size = 32M
max_allowed_packet = 64M

I really don't know what to do.

@request priority: Okay. Thanks for the advice.

flb’s picture

FileSize
625.91 KB

I've just played with memory_limit and max_input_nesting_level:

max_input_nesting_level = 600
memory_limit = 1024M

Result: Quick Installation works! 100%, then intranet name etc. Afther that klicked on the "view your intranet page now" link and got that: (see attachment).

Is this also a known problem?

Thank you.

flb’s picture

FileSize
54.21 KB

I've got the problem!
It's not (not only?) the 1024M memory_limit...

There's a database admin user with many rights (see attachment).
If I choose root during the OA installation, 100%, win!
If I choose this db admin, 98%, fail...

Does the db user (for OA) need any special rights? I'm confused?!

Thanks.

#Edit
I've just figured out the 'LOCK TABLES' value (within the administration part) has to be enabled for the MySQL user which is used in OA.

mpotter’s picture

Status: Active » Fixed

Yes, the LOCK TABLES permission is required to install Atrium. Actually thought this was a normal Drupal requirement as well but appears it's just needed for doing the large DB import. Good to know in case other people have this problem so thanks for digging into the details of this one!

flb’s picture

Yup, that took some doing.
Actually the problem from #4 still persists. (see file atrium.PNG)

mpotter’s picture

Also make sure your site has Clean URLs enabled. The screenshot in #4 was for a using a Tour on the page, so if you still have trouble with Tours, please open another issue.

flb’s picture

Nope, the errors/warnings from #4 do not only appear on the tour page - they appear everywhere, on each page.
(I've disabled the warning and error output via the OA or Drupal settings at the moment.)

mpotter’s picture

Did you confirm that you have Clean URLs enabled?

flb’s picture

FileSize
31.44 KB

I'm sorry, forgot to post that, my mistake.

"cannot be enabled" (see attachment)

(Reading https://www.drupal.org/getting-started/clean-urls atm)

mpotter’s picture

OK, well that's the problem then. Open Atrium requires Clean URLs and you'll have lots of weird problems if you don't fix that. That page you linked should help you resolve it.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.