Installation problems - Fatal memory errors on initial propel build

[RobRoyAus]

I'm trying to install the Sandbox on my reseller host at A2Hosting
(Centos with Apache 2.2.8, PHP 5.2.5, MySql 4.1.22-standard). Symfony
1.0.11 is a PEAR install by the

I unpacked the sandbox at ~/mysymfony/steerCMS/ and added a symbolic
link to ~/public_html/steer/

The public site address is http://www.roblog.com/steer/

Now for the problem. Whenever I try to do the step 5 of the sandbox
installation ($ symfony propel-build-all-load backend) I see the
following:
<pre>
[~/symfonyprojects/steerCMS]# symfony propel-build-all-load backend
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...-sfErrorLoggerPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...erated-sfGuardPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...ggableBehaviorPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...onableBehaviorPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...d-steerCMSBlogPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...eerCMSCalendarPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...teerCMSCommentPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...d-steerCMSCorePlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...ms_bookmarks_schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...n-steercms_bookmarks_schema.xml
>> schema converting "/home/xxxxxx/symfon...uard_profile_schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...gin-sf_guard_profile_schema.xml
>> schema converting "/home/xxxxxx/symfon...nfig/project_schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...rojectPlugin-project_schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...ertiesBehaviorPlugin-schema.xml
>> schema converting "/home/xxxxxx/symfon...lugin/config/schema.yml" to XML
>> schema putting /home/xxxxxx/symfonypro...steerCMSSearchPlugin-schema.xml
>> file+ config/generated-sfErrorLoggerPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...-sfErrorLoggerPlugin-schema.xml
>> file+ config/generated-sfGuardPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...erated-sfGuardPlugin-schema.xml
>> file+ config/generated-sfPropelActAsTaggableBehaviorPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...ggableBehaviorPlugin-schema.xml
>> file+ config/generated-sfPropelVersionableBehaviorPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...onableBehaviorPlugin-schema.xml
>> file+ config/generated-steerCMSBlogPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...d-steerCMSBlogPlugin-schema.xml
>> file+ config/generated-steerCMSCalendarPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...eerCMSCalendarPlugin-schema.xml
>> file+ config/generated-steerCMSCommentPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...teerCMSCommentPlugin-schema.xml
>> file+ config/generated-steerCMSCorePlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...d-steerCMSCorePlugin-schema.xml
>> file+ config/generated-steerCMSFounda...gin-sf_guard_profile_schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...gin-sf_guard_profile_schema.xml
>> file+ config/generated-steerCMSFounda...n-steercms_bookmarks_schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...n-steercms_bookmarks_schema.xml
>> file+ config/generated-steerCMSProjectPlugin-project_schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...rojectPlugin-project_schema.xml
>> file+ config/generated-steerCMSPropertiesBehaviorPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...ertiesBehaviorPlugin-schema.xml
>> file+ config/generated-steerCMSSearchPlugin-schema.xml
>> file- /home/xxxxxx/symfonyprojects/st...steerCMSSearchPlugin-schema.xml

Fatal error: Out of memory (allocated 3932160) (tried to allocate
30720 bytes) in /home/xxxxxx/symfonyprojects/steerCMS/lib/symfony/
vendor/phing/system/io/PhingFile.php on line 67
</pre>

I checked with the host and my account has 128M available.

I tried increasing the memory available in [~/symfonyprojects/steerCMS/
lib/symfony/vendor/phing/Phing.php and the location of the error moved
around, but they all still seemed to occur after reaching the above
file.

I'm out of ideas! Help!

[Piers Warmers]

Hi RobRoyAus,

Well it looks like the issue is memory.

> I checked with the host and my account has 128M available.

That's plenty, but I don't think it is actually the case :)

> Fatal error: Out of memory (allocated 3932160) (tried to allocate
> 30720 bytes) in /home/xxxxxx/symfonyprojects/steerCMS/lib/symfony/
> vendor/phing/system/io/PhingFile.php on line 67
> </pre>

So that is PHP complaining about a lack of memory, and also saying how
much it has at its disposal.... 3.75 MB.

You could try and split the command into:

$ symfony propel-build-all

and then

$ symfony propel-load-data backend

But you seem to be out of memory very early...

The only way forward is more memory.... with only 3.75MB, you are
going to be running into issues one way or another.

I'd usually say something like 16 should be min... but for big Symfony
builds, I'd say 32 would be be better.

Hope this helps...

- Piers

[RobRoyAus]

Hi Piers,

> You could try and split the command into:
> $ symfony propel-build-all
> and then
> $ symfony propel-load-data backend
>
> But you seem to be out of memory very early...

Tried this - the failure is actually in the first propel-build-all

> So that is PHP complaining about a lack of memory, and also saying how
> much it has at its disposal.... 3.75 MB.

phpinfo() returns memory_limit of 128M.

> The only way forward is more memory.... with only 3.75MB, you are
> going to be running into issues one way or another.
>
> I'd usually say something like 16 should be min... but for big Symfony
> builds, I'd say 32 would be be better.
>

This seems to be happening at a level higher than steer (as even pear
commands are showing memory errors) so I'll do more investigation
elsewhere. Very frustrating - I want to give steer a run!

Thanks
Rob