Step in question:
shell> mysql cactiWhy would I have skipped this very crucial step you might say?
Well, the installation was done in two sessions with enough time having elapsed between the initial and final sessions that I had gotten hazy on what was and wasn't done. I had created the database but just never took the next step.
After completing the rest of the configuration I fired Cacti but via my browser and php promptly did a segfault and lay there on the ground haemorrhaging. From my recent experience php has a propensity to do this in two specific cases:
- Something went awry with a database connection or using a database resource
- You're pushing the php boundaries with recursive regexps in a pre_match*() function