Powered on a Rackspace server and followed the guide outlined here
http://wiki.otterhub.org/index.php?titl ... CentOS_5.5
at the very end when i have to launch to http://localhost/otrs/installer.pl i get nothing to load (keeping in mind i did change localhost to the ip of the server)
I've modified the httpd.conf file and restarted but no luck
any suggestions, i have not received any errors during the install portion
What can i do to collect more information and be able to resolve this
Thanks
EDIT:
#
ServerRoot "/etc/httpd" is in httpd.conf file
quick search shows
[root@OTRS /]# cd /etc/httpd
[root@OTRS httpd]# ls
conf conf.d logs modules run
EDIT:
after fixing the port 80 issue i relized i hat to go to installer.pl not install.pl
should i not be seeing otrs?
[SOLVED] Unable to launch otrs/installer.pl
Moderator: crythias
-
- Znuny newbie
- Posts: 3
- Joined: 21 Jun 2012, 06:07
- Znuny Version: 0:3.0.6-01
- Real Name: Mike Leger
[SOLVED] Unable to launch otrs/installer.pl
Last edited by mleger on 21 Jun 2012, 20:48, edited 1 time in total.
-
- Znuny newbie
- Posts: 3
- Joined: 21 Jun 2012, 06:07
- Znuny Version: 0:3.0.6-01
- Real Name: Mike Leger
No such file or directory at /usr/lib64/perl5/vendor_perl/5.
port 80 not opened, followed http://www.cyberciti.biz/faq/linux-ipta ... n-port-80/ to open it
however now getting slurp_filename('/opt/otrs/bin/cgi-bin/install.pl') / opening: (2) No such file or directory at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/ModPerl/RegistryCooker.pm line 541
searched forums, no clear answer as how to resolve this
EDIT: when i run the pl right from the box, it seems to load. its almost as if there is something wrong with the httpd.conf
however now getting slurp_filename('/opt/otrs/bin/cgi-bin/install.pl') / opening: (2) No such file or directory at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/ModPerl/RegistryCooker.pm line 541
searched forums, no clear answer as how to resolve this
EDIT: when i run the pl right from the box, it seems to load. its almost as if there is something wrong with the httpd.conf