Cacti Installation

[lydiajere]

Hello I tried installing cacti on my debian jessie with no success. its been 2days now the home page still wont come. can someone please assist.

[robinr]

Hi,

Could you please be a little bit more specific about the problem?

Have you installed cacti with apt or did you compile it yourself?

[lydiajere]

I installed it with apt, i used apt-get install cacti
after that i run apt-get install dbconfig-common fontconfig libcairo2 libdatrie1 libdbi1 rrdtool php5-snmp php5-ldap snmp

tried to access it from http://myip/cacti a black page comes.

[Oldskool]

What do your webserver logs say? Usually located under /var/log/apache2 on Debian installs.

[Lesilhouette]

Hi, I have the exact same problem (CentOS 6.7), but I followed this tutorial: http://www.tecmint.com/install-cacti-ne ... ora-17-12/
I've rebooted the server about half an hour a go, but still no luck.
This is from my /httpd/error_log:

Code: Select all

[Tue Aug 25 17:46:11 2015] [notice] caught SIGTERM, shutting down
[Tue Aug 25 17:46:12 2015] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0
[Tue Aug 25 17:46:12 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Aug 25 17:46:12 2015] [notice] Digest: generating secret for digest authentication ...
[Tue Aug 25 17:46:12 2015] [notice] Digest: done
[Tue Aug 25 17:46:12 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured -- resuming normal operations
[Tue Aug 25 17:46:28 2015] [notice] caught SIGTERM, shutting down
[Tue Aug 25 17:47:31 2015] [notice] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0
[Tue Aug 25 17:47:31 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue Aug 25 17:47:31 2015] [notice] Digest: generating secret for digest authentication ...
[Tue Aug 25 17:47:31 2015] [notice] Digest: done
[Tue Aug 25 17:47:34 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured -- resuming normal operations

How can I fix the white-screen-of-death?

[phalek]

Try disabling SELinux and see if that works. Then go and find out the correct strings to get it working if SELinux is the issue.

[Lesilhouette]

Try disabling SELinux and see if that works. Then go and find out the correct strings to get it working if SELinux is the issue.

Just tried it, still no luck.

[phalek]

It may be a PHP issue then.

Edit your /etc/php.ini file and set "error_log = syslog". Then check your syslog ( /var/log/messages ) for any PHP related errors.

[Lesilhouette]

Done. See attached log. It starts right before I rebooted the system after changing the logging options.

[phalek]

That doesn'T contain anything related to php. Did you also go to the cacti admin/install webpage ?

[Lesilhouette]

That's weird.... No, I've not gotten to the webinstaller yet, that's the exact problem.

[Lesilhouette]

This morning I've fired up a second-vm with the exact same install (from http://www.tecmint.com/install-cacti-ne ... dora-17-12), only difference being no vmware tools, and diffrent ip. No Luck. Just to changed the httpd.conf to
<Directory /usr/share/cacti/>
<IfModule mod_authz_core.c>
# httpd 2.4
Require all granted
</IfModule>
<IfModule !mod_authz_core.c>
# httpd 2.2
Order allow,deny
Allow from all
</IfModule>
</Directory>
And restarted the httpd service, but that did not work either... I'm now gonna reinstall the second-vm, -with- a gui, and install via terminal and see if I can reach the webpage on the localhost...

[Lesilhouette]

I'm now gonna reinstall the second-vm, -with- a gui, and install via terminal and see if I can reach the webpage on the localhost...

With the help of the gui I figured out that the localhost could see the webpage, so via the gui, checked the firewall config, and noticed there was no checkmark before tcp80/http. So I checked the box in front of that, saved the config, reloaded the fw, and voila it worked.

I then opened up a terminal to see what in the firewall config was changed specifically, and after comparison with my 'orignal' fw config, I noticed that the working config read the following:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited

Now the non-working config reads:
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A INPUT -p udp -m state --state NEW -m udp --dport 80 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 80 -j ACCEPT

Notice the location of the -A INPUT -j REJECT --reject-with icmp-host-prohibited line.
I moved that line to beneath the port 80 rule, saved the file, restarted the fw and it worked.... So the solution was really just the location of the deny-rule...
This might be the same issue for the OP.

Thanks for the support!