Check-list Of useful information which helps us help you. Please run through this before posting.
Each instance of statusnet provides information, about the plugins running. navigate to http://sitename.com/main/version
1) Start a new thread, and give it a meaningful name. I cant stress this enough, I have a really hard time helping everyone come to a solution in a big mess of a thread, make your own thread for your own problem, you are unique! This way you are more likely to get personal support.
2) Hosting environment, I need to know who your host is, unfortunately shared hosting often has limitations that will be felt running the more advanced plugins that StatusNet offers.
a)Please let me know Do you have shell access? can you install packaged? It can be really hard to help you if you dont have these, this is my own limitation, as i've i've allways worked on dedicated hosts. A sticky post for each of the big hosting environments would be a good thing,
b)Output of the following
cat /etc/lsb-release (or cat /etc/redhat-release)
3) provide statusnet related information
a) what works.
b) what doesn't
c) log file pastie (see: pastebin.org) from around the time of the failure
d) sanitized conifg.php and or statusnet/scripts/setconfig -a (if you dont have the -a switch, dont worry its only in > 0.9.2)
Okay, so this is how you get you log files, generally they are going to /var/log/user.log but we can change this.
$config['site']['logfile'] = '/tmp/statusnettmp.log';
to see more database debugging : $config['site']['logdebug'] = true;
maximum debugging: $config['db']['debug'] = create_function('$class, $message, $logtype, $level','common_log(LOG_DEBUG,"DBDO: $class / $message / $logtype");');
Session problems? try these below
$config['sessions']['debug'] = true;
$config['sessions']['handle'] = true;
That said, try to keep your pasties of a reasonable size, no more that 1000 lines, thanks.