If this question is too "in the weeds" for this forum, please let me know. I'm not sure where else to ask it, though.
I left my linode Mercury image on Saturday night with a problem with the Drupal installation (messed up bringing across some tables) but everything else was working (web server responded nicely, I think varnish was responding according to the tests I was making, etc.).
When I returned to the task just a half hour ago of moving across the project site, the site does not respond.
The error.log file in /var/log/apache2 shows many segmentation faults. The webserver and mysql are still responding at http://staging.postpeakliving.com/phpmyadmin.
Any ideas why this might be happening? It's a stock image...no extra software except for nano.
Comments
Examples
Here are some examples, in case they help:
[Tue May 11 01:46:51 2010] [notice] child pid 31519 exit signal Segmentation fault (11)[Tue May 11 04:05:22 2010] [notice] child pid 31756 exit signal Segmentation fault (11)
[Tue May 11 06:23:51 2010] [notice] child pid 31991 exit signal Segmentation fault (11)
[Tue May 11 08:42:21 2010] [notice] child pid 32233 exit signal Segmentation fault (11)
Andre Angelantoni
Founder, PostPeakLiving.com
Drupal Stack?
If phpmyadmin is still working, then the problem is somewhere in Drupal. If you can give more information about your Drupal stack, that would be most helpful. Likely there is something in there causing an infinite loop or other problem, resulting in the segfault.
If you haven't yet, try restarting Apache. I've seen issues before where clearing APC's opcode cache (which an apache restart will do) resolves this.
https://pantheon.io | http://www.chapterthree.com | https://www.outlandishjosh.com
Thanks for that, Josh. I
Thanks for that, Josh. I restored the originally installed db and I'm back to the original install. I'll look now to see what's so unique about the install that would cause that. I've transferred it multiple times between machines with no trouble before. I'll post my progress.
Andre Angelantoni
Founder, PostPeakLiving.com
look like a drupal or
look like a drupal or pressflow problem. On a fresh install, I have the same problem. also trying to recreate or find out the problem.
We had the problem with
We had the problem with SEGFAULT when we called node_save with incorrect data in oune of the $node field. There was an array with recursion; related to google map location module.
It took some time to find this, maybe because one can instinctively expect Stack Overfflow in this case but not SEGFAULT.
Task was PHP CLI import tools, execution on Debian; hope this info may be useful for someone.