Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.WARNING: THIS MAY BE A DUPLICATE - DELETE IF NEEDED
I am not sure what the issue was, how it occured or if maybe this has already been resolved, but I installed the chatroom module as outlined (in the root modules directory), enabled it and everything worked dandy. Then I realized I had dropped it into the wrong directory, disabled the module, moved it too the sites/default/modules/ directory only to have my hosting colo company contact me about 2 hours later saying that customers were contacting them saying their sites were down. The server would crash, do a php-core dump, and the start all over again.
Come to find out the chatroom module was spawning php threads so fast and crazy due to errors looking for chatroomread.php. I pulled the module from the directory thinking this would kill the issue, but it did not. I had several of the blocks created by the module active when I pulled the module files, but the blocks continued to crash the server.
Not sure how this all works since I am more of a design person than a coding person, but in the end I had to manually edit the MySQL tables to remove all chatroom tables and references to chatroom in the menu table, node table, block table and module table before the server would stabilize.
I will retest the module once I have tested the module again locally. My users were really loving it.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | chatroom.module_2.patch | 10.37 KB | darren oh |
Comments
Comment #1
darren ohThis doesn't solve the original problem, but the proper way to disable chatroom is on the modules administration page.
Comment #2
darren ohNo follow-up. I'm assuming this has been resolved.
Comment #3
jlmeredithSorry for the slow response.
I could not disable the module in the traditional manner. As soon as we rebooted the server it would crash as soon as the first page loaded ..... over 450 php threads were almost instantly created by all of the blocks that were active for chatroom. The only solution was to pull the module from the directory and edit the database manully to remove references.
Hopefully the issue of placing the module in the sites folder has been resolved. I have not seen any note of this specific issue in the bug tracker.
Comment #4
darren ohTry this patch. It has already been committed to address another file-does-not-exist error.
Comment #5
darren ohBy the way, the problem with placing the module in the sites folder has been fixed.
Comment #6
darren ohAssuming this is fixed.