Dreamhost says I must upgrade to VPS to fix error with 2.2.6 installation. Claims MODx uses too much memory.

Warning: session_start() [function.session-start]: open(/tmp/sess_5n6s7qrse8528vg3ulirg63ak2, O_RDWR) failed: Permission denied (13) in /home/iamdave220/robyn.ravenflight.net/setup/index.php on line 32
 
Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/iamdave220/robyn.ravenflight.net/setup/index.php:32) in /home/iamdave220/robyn.ravenflight.net/setup/index.php on line 32
FATAL ERROR: MODX Setup cannot continue.
 
Make sure your PHP session configuration is valid and working.
 
 
Warning: Unknown: open(/tmp/sess_5n6s7qrse8528vg3ulirg63ak2, O_RDWR) failed: Permission denied (13) in Unknown on line 0
 
Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0

Hello David,

Thanks for contacting support. You would have to install MODx on a VPS or
a dedicated virtual server. The shared hosting environment doesn't allow
for root access. You can however, provision a VPS for a one week trial
period, and use sudo to gain the access you need to install MODx.

The reason I suggested a VPS or Dedicated is because we've run into a few
customers who installed MODx on their shared, and were hitting memory
allocation limits for shared hosting. I just wanted to make sure your
site won't go down due to memory limits.

However, there are work arounds. I did find this article for you:

http://rtfm.modx.com/display/revolution20/Server+Requirements

I ran a check for the user 'iamdave220' and yep, you're already hitting
procwatch:

Mar 31 08:06:17 2013 procwatch3 INFO: PID 47158 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:17 2013 procwatch3 INFO: PID 56152 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:17 2013 procwatch3 INFO: PID 56180 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:17 2013 procwatch3 INFO: PID 56179 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:17 2013 procwatch3 INFO: PID 56184 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:17 2013 procwatch3 INFO: PID 56181 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 56177 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 56185 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 56182 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 56183 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 57152 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 57153 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 57165 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 56178 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 57159 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:27 2013 procwatch3 INFO: PID 57170 (php53.cgi)
iamdave220:pg1980292
Mar 31 08:06:37 2013 procwatch3 INFO: PID 57167 (php53.cgi)
iamdave220:pg1980292
Mar 31 11:09:26 2013 procwatch3 INFO: PID 41650 (php53.cgi)
iamdave220:pg1980292

That's why I suggested a VPS. MODx is notorious for memory consumption:

https://forums.modx.com/index.php?topic=63714.0;wap2