SOLVED Trouble after Upgrade from Ubuntu 17.04 to 17.10

[seveny13]

Hi there,

Ubuntu 17.10 uses PHP 7.1 (therefore I had to activate PHP7.1 manually (a2enmod php7.1) for my mediawiki installation and stuff) and cacti was upgraded automatically to 1.1.8 (from the old 0.8.x). Great!

I can log in cacti and see the frameset. But clicking on "Graphs" results in downloadung the php-source-file instead of showing the graphs.

At the moment I have no clue where to look, can anyone help?

Thx,
Sven

[paulgevers]

I can log in cacti and see the frameset. But clicking on "Graphs" results in downloadung the php-source-file instead of showing the graphs.

Do you see sensible configuration in /etc/apache2/conf-available/cacti.conf ? Is that configuration enabled?

[seveny13]

Hi Paul,

UPDATE It works now, with changing anything... Maybe a cache thingy? Strange, but I am happy now.

The strange thing is, that the other *.php files (and graphs in the diagram section) are showing correctly in the browser (firefox 56.0.2 on MacOSx) just not the graphs_view.php.

The file is there, wasn' t change since march 2016, as it seems:

Code: Select all

Alias /cacti /usr/share/cacti/site

<Directory /usr/share/cacti/site>
	Options +FollowSymLinks
	AllowOverride None
	<IfVersion >= 2.3>
		Require all granted
	</IfVersion> 
	<IfVersion < 2.3>
		Order Allow,Deny
		Allow from all
	</IfVersion>

	AddType application/x-httpd-php .php

	<IfModule mod_php.c>
		php_flag magic_quotes_gpc Off
		php_flag short_open_tag On
		php_flag register_globals Off
		php_flag register_argc_argv On
		php_flag track_vars On
		# this setting is necessary for some locales
		php_value mbstring.func_overload 0
		php_value include_path .
	</IfModule>

	DirectoryIndex index.php
</Directory>

[paulgevers]

The strange thing is, that the other *.php files (and graphs in the diagram section) are showing correctly in the browser (firefox 56.0.2 on MacOSx) just not the graphs_view.php.

I experienced something similar the other day with another website I control. Using a different browser (at the same time) did not show the issue, so in my case I was convinced that my local browser cache was playing tricks on me.