Hi Jeff,

Thanks for the link .We have started the installation for creating a devel
environment on Red-Hat5.

These are the Steps which we have used :-

1)We have installed spacewalk using rmp (yum install spacewalk)
2)at the time of configuration (spacewalk-setup --disconnected), we found
tomcat failed to start just before the installation ,but somehow we found
the solution and fix it.
3)we opened  GUI interface (https://localhost.localdomain) and created a
administrator user and password wow :-)
4) we installed/configured git(using rpm) and also clone the spacewalk
repository  successfully
5)Now at the time of installation "WEB APPLICATION" ,we performed all the
Steps mentioned in the wiki successfully.

But whenever i am trying to  open browser for spacewalk server(
https://localhost.localdomain)
 i am getting this error message

Forbidden

You don't have permission to access / on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an
ErrorDocument to handle the request.
------------------------------
Apache/2.2.3 (Red Hat) Server at 127.0.0.1 Port 80

it look like a Apache issue but i am not able to solve it.

Any idea how to solve this ?

thanks in advance,
                                               ---
                                              regards,tushar


On Thu, Jan 15, 2009 at 12:27 AM, Jeff Ortel <jor...@redhat.com> wrote:

> Hey Vikram,
>
> I'd suggest you follow the developer setup instructions on the Spacewalk
> wiki:
>
> https://fedorahosted.org/spacewalk/wiki/DevelopmentWorkstationSetup
>
> ~jeff
>
>
> Vikram Rai wrote:
>
>> Hi,
>>
>> We were trying to install spacewalk using souce on Redhat 5 Enterprise
>> Server and after giving the command:
>>
>> make spacewalk-clean spacewalk-release TBS=USERS
>> SQLUSER=spacewalk/spacew...@xe
>>
>> We are getting the below error after the schema is created:
>> Attached is the log file of make command
>>
>> 1 row created.
>>
>>
>> Commit complete.
>>
>>
>> SQL_FILE
>> ---------------
>> rhnsat/quit.sql
>>
>> Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 -
>> Production
>>
>> SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jan 14 19:50:24 2009
>>
>> Copyright (c) 1982, 2005, Oracle.  All rights reserved.
>>
>> ERROR:
>> ORA-12154: TNS:could not resolve the connect identifier specified
>>
>>
>> Enter user-name:
>> SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jan 14 19:50:24 2009
>>
>> Copyright (c) 1982, 2005, Oracle.  All rights reserved.
>>
>> ERROR:
>> ORA-12154: TNS:could not resolve the connect identifier specified
>>
>>
>> Enter user-name: SP2-0306: Invalid option.
>> Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
>> where <logon>  ::= <username>[/<password>][@<connect_identifier>] | /
>> SP2-0306: Invalid option.
>> Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
>> where <logon>  ::= <username>[/<password>][@<connect_identifier>] | /
>> SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
>> make[1]: *** [universe.satellite-synonyms.lst] Error 255
>> make[1]: Leaving directory `/opt/spacewalk/schema/spacewalk'
>> make: *** [test-make-release] Error 2
>>
>> I am sure this is not a tns issue as I am able to connect to the spacewalk
>> user from another terminal at the time the error is generated.
>>
>> Any suggestions as to what may be the cause of this, would be appreciated.
>>
>>
>> --
>> Regards
>>
>> Vikram Rai
>> Member Technical Team,
>> EnterpriseDB
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Spacewalk-devel mailing list
>> Spacewalk-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-devel
>>
>
> _______________________________________________
> Spacewalk-devel mailing list
> Spacewalk-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-devel
>



-- 
--
regards, tushar
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to