ID:               36013
 Comment by:       no at thanks dot com
 Reported By:      xenon54 at generationphp dot net
 Status:           No Feedback
 Bug Type:         Session related
 Operating System: Centos 4.2
 PHP Version:      5.1.1
 New Comment:

When I ran into this issue, it turned out I didn't actually import the

cacti.sql into mysql.  After doing that, no more "Segmentation fault".
Hope that helps someone.


Previous Comments:
------------------------------------------------------------------------

[2009-08-16 10:38:44] jef at superior dot nl

Same problem on 5.2.10 and 5.3.0 :/ plz resolve this issue

------------------------------------------------------------------------

[2008-12-10 08:14:02] fb at smartterra dot de

Hm, strange. Same behavior with PHP 5.2.6 :-(

------------------------------------------------------------------------

[2008-12-10 08:06:42] fb at smartterra dot de

Same here:

- CentOS 5
- PHP 5.1.6
- mysql  Ver 14.12 Distrib 5.0.45

Browsing to any cacti webpage results in a white page.
# tail /var/log/httpd/error_log 

[Tue Dec 09 18:00:41 2008] [notice] child pid 24763 exit signal
Segmentation fault (11)

------------------------------------------------------------------------

[2008-09-06 13:15:19] test at example dot com

I find it quite funny that this problem in connecting to MySQL leads to
a segmentation fault. I can reproduce any it by installing OpenSuSE 10.x
or OpenSuSE 11 and the 'cacti' package, and this has not changed for at
least a couple years.

------------------------------------------------------------------------

[2006-03-12 17:40:54] alexdg at gmail dot com

I think I know what the issue is, bad user/passwd login configuration
for the cacti mysql account in include/config.php. When running thru
Apache the error_log will only output "segmentation fault" but if you
run the poller.php script on its own, you'll get the typical error msg
of a failed mysql login (some 10 times?), until it crashs.

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/36013

-- 
Edit this bug report at http://bugs.php.net/?id=36013&edit=1

Reply via email to