Hi, I'm not sure if this is a bug in the module or a misconfiguration on my server or what, but when I enable Mobile Tools on my production site, the server just gets pounded. It seems like Drupal is somehow creating a bunch of extra anonymous sessions when Mobile Tools is enabled, and Apache and MYSQL just get slammed until it just dies.
I didn't see anything in the apache error log, but Drush spits out the following errors (this is from the dev site, and I got the same on production):
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
/home/sean/almagdev/modules/system/system.admin.inc).
WD php: Notice: Undefined index: name in system_sort_modules_by_info_name() (line 789 of [error]
I seem to get the same effect on the current release and the dev release of the module. Any ideas what could be causing this or how I could begin troubleshooting? What additional info should I provide here?
Many thanks,
Sean
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | my.txt | 4.25 KB | seanfitzpatrick |
| #5 | php.txt | 65.88 KB | seanfitzpatrick |
Comments
Comment #1
twom commentedHi,
Thank you for the report.
How do you see the extra anonymous sessions?
I'll have a look if the notices are related to the module.
Comment #2
seanfitzpatrick commentedThanks for your reply. I'm seeing a trace of additional anonymous sessions in the right side of Admin Menu (I'm not sure where Admin Menu gets the data). On a normal day, we'll have around 4,000 to 6,000 total visits, but at its peak yesterday, Admin Menu was showing over 1,400 anonymous users at once. Neither Apache access logs nor Google Analytics was showing anything close to that.
HTH, the module is *awesome* except that it's killing my server :) Hope I can get running.
Sean
Comment #3
jarchowk commentedHow big of an issue is this? (also this http://drupal.org/node/1003732) I was going to enable this on a production box, it sounds like I should wait until this is fixed.
Comment #4
rmjackson commentedHi Sean,
I'm trying to help Tom with some of the open issues. Can you help me try to reproduce this issue. Any server/Drupal/PHP/Apache/my.cnf/LAMP configuration/settings and versions would be great.
My first guess would be conflicts with other modules.
Thanks,
Robbie Jackson
Comment #5
seanfitzpatrick commentedRobbie and Tom,
I'm sorry for a delayed response on my end. I'm running Ubuntu 10 on a 1.5GB Slicehost VPS with the Pantheon/Mercury 1.1 profile. It's PHP 5.2.10, Apache 2, MySQL 5.5, Varnish, MemCache, Pressflow 6.19. I'll attach my.cfn and php.ini (with .txt extensions).
I am getting out of my depth here... Actually the Pantheon was recommended to us as we started facing big growth in anon and auth users, but I don't know a lot about it. What else can I provide or how can I help you troubleshoot? I, too, suspect it conflicts with another module. The same problem seems to occur on the dev site on the same server, though to a lesser degree, because there's no actual traffic. The dev site is actually standard Drupal rather than Pressflow.
Sean
Comment #6
minoroffense commentedThe 1.x branch is no longer supported. Closing.