I should have been more clear. This is actually a fresh install of 3.1.0,
with data migrated from a server that was upgraded to 3.1.0. Both the clean
install on the new server, and the upgrade to 3.1.0 on the old server worked
without issue.
Following the migration, I was able to access all the subfolders of /admin
without a problem. I followed the steps outlined here for the upgrade:
http://docs.opsview.org/doku.php?id=opsview3.1:upgrading and here for the
migration: http://docs.opsview.org/doku.php?id=opsview3.1:migratinghardware
I had a look at Web.pm and I can see the access definitions defined, rougly
between lines 174 and 244. They appear to be fine, but I¹ll compare with
source to verify.
No path changes - I am just proxying http://server:3000/ to http://server/
.
Here is my opsview httpd.conf:
<VirtualHost *>
ServerName <IP Address>
ServerAdmin [email protected]
DocumentRoot /usr/local/nagios/share
Alias /static/nmis/ "/usr/local/nagios/nmis/htdocs/"
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass /error_pages !
ProxyPass /javascript !
ProxyPass /stylesheets !
ProxyPass /help !
ProxyPass /images !
ProxyPass /xml !
ProxyPass /favicon.ico !
ProxyPass /graphs !
ProxyPass /static !
ProxyPass /media !
Alias /nagvis /usr/local/nagios/nagvis
ProxyPass /nagvis !
TKTAuthSecret "<protect the innocent>"
<Location /nagvis>
AuthType None
TKTAuthLoginURL /login?app=nagvis
TKTAuthTimeout 86400s
require valid-user
</Location>
ErrorDocument 502 /error_pages/http502.html
ErrorDocument 503 /error_pages/http502.html
ProxyPass / http://127.0.0.1:3000/ retry=5
ProxyPassReverse / http://127.0.0.1:3000/
</VirtualHost>
On 6/24/09 9:30 AM, "Ton Voon" <[email protected]> wrote:
>
> On 24 Jun 2009, at 16:03, Craig Pendleton wrote:
>
>> Thanks for the reply and the FAQ, Ton. I¹m pretty certain that no change
>> was made manually to cause this I am the primary user of opsview and didn¹t
>> make any changes following the upgrade.
>>
>> I followed the directions in the FAQ entry, and ADMINACCESS is already
>> defined for our admin contacts. Each admin contact looks like the
>> following:
>>
>> +-----------------------+--------+----------+----------------+
>> | contact_name | roleid | accessid | name |
>> +-----------------------+--------+----------+----------------+
>> | admin | 10 | 1 | VIEWALL |
>> | admin | 10 | 3 | ACTIONALL |
>> | admin | 10 | 6 | NOTIFYSOME |
>> | admin | 10 | 7 | CONFIGUREHOSTS |
>> | admin | 10 | 8 | RELOADACCESS |
>> | admin | 10 | 9 | ADMINACCESS |
>>
>>
>> I tried again with the ³admin² contact as well as my own contact (which
>> previously had admin rights) and still no luck. I get ³Access Denied² for
>> anything under /admin.
>>
>> Anything else I should be looking at? I am proxying with Apache, if that
>> makes any difference.
>
> Are you proxying under a different path?
>
> Did this work after the upgrade?
>
> The definitions for what is allowed under particular paths are in
> /usr/local/opsview-web/lib/Opsview/Web.pm, but I can't see how that would have
> been changed.
>
> Ton
>
>
>
> _______________________________________________
> Opsview-users mailing list
> [email protected]
> http://lists.opsview.org/listinfo/opsview-users
Thanks,
Craig
----
NOTICE BY HEALTH LANGUAGE, INC.
This message, as well as any attached document, contains information from
Health Language, Inc. that is confidential. The information is intended only
for the use of the addressee named above. If you are not the intended
recipient, you are hereby notified that any disclosure, copying, distribution
or the taking of any action in reliance on the contents of this message or its
attachments is strictly prohibited, and may be unlawful. If you have received
this message in error, please delete all electronic copies of this message and
its attachments, if any, destroy any hard copies you may have created, without
disclosing the contents, and notify the sender immediately. Unless expressly
stated otherwise, nothing contained in this message should be construed as a
digital or electronic signature, nor is it intended to reflect an intention to
make an agreement by electronic means._______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users
