Hello,

I've upgrade our ganglia server to ganglia-gweb 3.4.2.

We use external authentification to ganglia. In httpd.conf we have:

<Directory "/var/www/htdocs/ganglia">
AuthType Basic
AuthName "Ganglia"
AuthUserFile /opt/freeware/etc/httpd/http_user
Require valid-user

</Directory>

When I first open the Web frontend, I have to enter username and
password and can then use Ganglia.

When I try to inspect a graph, I get in the error_log:

[Tue May 22 14:23:43 2012] [error] [client x.y.z.7] PHP Warning: 
file_get_contents(http://ganglia.example.com/ganglia/graph.php
?flot=1&amp;h=myhost&amp;m=cpu_used&amp;r=hour&amp;s=by%20name&amp;hc=4&amp;mc=2&amp;st=1337689406&amp;g=cpu_used_report&amp;z=la
rge&amp;c=B3) [<a
href='function.file-get-contents'>function.file-get-contents</a>]: failed
to open stream: HTTP request failed! HT
TP/1.1 401 Authorization Required\r\n in
/var/www/htdocs/ganglia/inspect_graph.php on line 28, referer:
http://ganglia.example.com/g
anglia/?r=hour&cs=&ce=&m=cpu_used&s=by+name&c=B3&h=myhost&host_regex=&max_graphs=0&tab=m&vn=&sh=1&z=small&hc=4
[Tue May 22 14:23:43 2012] [error] [client x.y.z.7] PHP Warning:  Invalid
argument supplied for foreach() in /var/www/htdocs/ga
nglia/inspect_graph.php on line 30, referer:
http://ganglia.example.com/ganglia/?r=hour&cs=&ce=&m=cpu_used&s=by+name&c=B3&h=myhost&host_regex=&max_graphs=0&tab=m&vn=&sh=1&z=small&hc=4
ERROR: Garbage found where STACK expected

Any ideas how that can be fixed?

Jochen



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general

Reply via email to