Page 1 of 2
Graphs stop working after upgrading to 2.1.15
Posted: 17 Jun 2013, 18:51
by dtamajon
Hi,
I'm quite confused after upgrading Mantis from 2.1.8 to 2.1.15,because Graphs have stopped working. I have duplicated the virtual machine and just upgraded Mantis, and it looks it's working properly with all plugins working perfectly as they were in the previous versions... except for MantisGraphs.
The problem is that the image is broken, with no errors on any log I checked.
My environment is (I think I followed all troubleshooting threads, so maybe I have over-installed):
Ubuntu 10.02 (waiting to be updated
)
MySQL 5.1.49
Apache2
Mantis 1.2.5
libphp-jpgraph
php5-gd
ezComponents
ttf-mscorefonts
jpGraph 3.5.0b1 (which is working properly in 2.1.8 )
Any idea what is happening after upgrading?
Thanks!!
Re: Graphs stop working after upgrading to 2.1.15
Posted: 17 Jun 2013, 21:54
by atrol
I assume you are talking about upgrading from 1.2.8 to 1.2.15 (and not 2.1.8 to 2.1.15)?
RIght click on the broken image and choose something like "Open in new tab" (depends on your browser)
Do you see any message in new tab?
Re: Graphs stop working after upgrading to 2.1.15
Posted: 17 Jun 2013, 22:22
by dtamajon
Sorry... I upgraded from 1.2.8 to 1.2.15. When I open in new tab, I just see the broken image.
I'm using Chrome.
I'm missing some configuration in Mantis, because I can execute jpGraph examples.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 17 Jun 2013, 22:29
by atrol
Do you get the same issue when using the bundled graph library?
Re: Graphs stop working after upgrading to 2.1.15
Posted: 17 Jun 2013, 22:57
by dtamajon
Yes, it's the same
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 07:38
by atrol
Which PHP version do you use?
dtamajon wrote:
I'm using Chrome.
Same with other browsers?
Might help to get some more information
temporarily configure your system as follows:
Code: Select all
$g_display_errors = array(
E_WARNING => 'halt',
E_NOTICE => 'halt',
E_USER_ERROR => 'halt',
E_USER_WARNING => 'halt',
E_USER_NOTICE => 'halt'
);
$g_show_detailed_errors = ON;
the 'show_detailed_errors' config can cause MantisBT to display sensitive information about your system. We recommend to restrict its activation to a Test environment, only for as long as necessary. If possible, do not turn it ON globally, instead limit it for specific user(s) using the Manage Configuration page.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 21:07
by dtamajon
Hi again,
I have tested in FF and IE8 too, with the same results: a broken image.
I have followed your instructions, and I see no log anywhere. I have done the same operations to reproduce the problem, but my apache log does not show any problem. Am I missing something?
I have tried to uninstall all plugins, but neither works.
Thank you!
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 21:13
by atrol
Still missing this information
atrol wrote:Which PHP version do you use?
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 21:21
by atrol
dtamajon wrote:
Ubuntu 10.02 (waiting to be updated
)
Didn't realize that it's 10.02, I thought it's 10.04 (which is a quite stable LTS version)
You should not wait any longer.
Maybe this fixes your issue.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 22:08
by dtamajon
Now I'm running on Ubuntu 10.10 (from Amazon ESB) and PHP 5.3.3.
I have copied the installation to a Windows machine, and there I can see graphs!!! I'd say I'm missing something on Mantis config in Ubuntu server... but I copied full folder to Windows and export-import in a fresh MySql. I have alse checked jpGraph is working properly on the Ubuntu machine.
If I follow the Network on the browser console, I can see the message "This request has no response data available". Browser is not getting the response from the plugin.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 22:21
by atrol
run admin/check.php
Do you get any errors/warnings?
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 23:21
by dtamajon
I attach the result.
The "only" BAD message is => "
check configuration: jpgraph (if used) requires php bundled gd for antialiasing support"
I have tried the GD installation again with the following results. What should I check?
Code: Select all
$ sudo apt-get install libphp-jpgraph
Reading package lists... Done
Building dependency tree
Reading state information... Done
libphp-jpgraph is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
Code: Select all
$ sudo apt-get install php5-gd
Reading package lists... Done
Building dependency tree
Reading state information... Done
php5-gd is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 19 Jun 2013, 23:54
by dtamajon
I have uninstalled GD, and now I'm getting the error "JpGraph Error: 25001 This PHP installation is not configured with the GD library. Please recompile PHP with GD support to run JpGraph. (Neither function imagetypes() nor imagecreatefromstring() does exist)"
At this situation, if I change configuration to use integrated graphs, the broken image remains.
So, I have installed GD again to avoid such error. Now it continues showing a broken image (with integrated and jpgraph) and I'm sure GD is installed.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 20 Jun 2013, 00:53
by dtamajon
I have the same problem when using the relationship graphs. It's working properly in Windows but not in the Ubuntu install. So now, I'm focused on why PHP is not serving the image content properly.
Re: Graphs stop working after upgrading to 2.1.15
Posted: 20 Jun 2013, 01:01
by dtamajon
Solved!!! After uninstalling all plugins, I could see images again. So I have added plugins one by one until (the last one) crashed the images.
I have read about problems serving images on PHP when using an extra line after ?>. I have deleted the line and the end of the PHP, and now is working properly.
It's stunning that the problem were in a plugin quite far from image management: Traceability!!! :-O
Thank you for your time!!!