Content
Fresh Centos server, packaged installation, can't access webserver.
Added by Michael Shadow over 9 years ago
Just installed the packaged version on Centos and everything appears to have been installed correctly. Ran the post install commands per the instructions and can not access the website. I did a portscan on the server and no port 80. Does anyone know if I am missing anything?
Here’s the history
4 sudo rpm —import https://rpm.packager.io/key
5 echo “[pkgr-openproject-community]
6 name=Repository for finnlabs/pkgr-openproject-community application.
7 baseurl=https://rpm.packager.io/gh/finnlabs/pkgr-openproject-community/centos6/stable/4.2
8 enabled=1” | sudo tee /etc/yum.repos.d/pkgr-openproject-community.repo
9 sudo yum install openproject-ce
10 sudo openproject-ce configure
11 openproject-ce logs —tail
bunch of directory browsing and a server reboot
34 service openproject-ce start
35 chkconfig httpd on
36 chkconfig memcached on
37 sudo openproject-ce configure
38 sudo yum update
39 sudo yum install openproject-ce #latest version
40 sudo openproject-ce configure
41 cd /etc/apache2 #this directory does not exist
42 yum -y install httpd
Package httpd-2.2.15-39.el6.centos.x86_64 already installed and latest version
Nothing to do
43 chkconfig —levels 235 httpd on
44 /etc/init.d/httpd start
45 cd /etc
46 ls
47 cd httpd
48 ls
49 cd conf.d
50 ls
51 more openproject-ce.conf
52 cd /
53 vi ~/refresh #this is a script to restart httpd, mysql, and memcached
54 ~/refresh
55 chmod 755 ~/refresh
56 ~/refresh
Stopping httpd: [ OK ]
Starting httpd: [Wed Aug 05 00:58:03 2015] [warn] module deflate_module is already loaded, skipping
[Wed Aug 05 00:58:03 2015] [warn] module expires_module is already loaded, skipping
[Wed Aug 05 00:58:03 2015] [warn] module headers_module is already loaded, skipping
[Wed Aug 05 00:58:03 2015] [warn] module proxy_http_module is already loaded, skipping
[Wed Aug 05 00:58:03 2015] [warn] module proxy_module is already loaded, skipping
httpd: Could not reliably determine the server’s fully qualified domain name, using ****
57 ls
58 cd /etc/httpd/
59 ls
60 cd logs
61 ls
62 tail access_log
63 tail error_log
64 more error.log
65 ls
66 more error_log
67 ls
68 mv error_log error_log2
69 ~/refresh
70 more error_log
71 ls
72 tail *
73 ps aux |grep apache
apache 8008 0.0 1.5 266588 7604 ? S 01:08 0:00 /usr/sbin/httpd
apache 8009 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8010 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8011 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8012 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8013 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8014 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
apache 8015 0.0 1.5 266588 7592 ? S 01:08 0:00 /usr/sbin/httpd
root 10013 0.0 0.1 103244 844 pts/0 S+ 01:32 0:00 grep apache
Replies (4)
Hi Michael,
there is a known reboot issue with the centos6 version. Maybe this is related to your problem? I’m wondering why you assume the directory
/etc/apache2
should exist. As far as I know it is called/etc/httpd
.Hopefully this little information helps. Else please give me some information about the output of
openproject-ce run check
.Cheers,
Karsten
Thanks for the response Karsten. Some of the documentation on openproject mentioned /etc/apache2.
Here are the results of openproject-ce run check
[ok] MySQL configuration is working
[ok] Web server is running
[ok] openproject server is running
[ok] openproject background job worker is running
sending test email using sendmail…
[ok] test email sent to admin
hi Michael,
so everything seems to be fine according to the output of the check command. So I have to ask: What is the problem you have? If you can not access the OpenProject instance it should be related to a network issue (Firewall, wrong hostname, missing route on the client to connect to the server and so on). Can you check step by step what ich causing the problems.
If you need help on how to tackle such a network issue in general please let me know (yes it is an assumption that this is network related - but it seems the right direction to go.)
Cheers,
Karsten
I figured out that it is a firewall problem.
I ran:
nmap -T4 -sV -p 1-99 -Pn server.name.com
both from the server I am working on and another server and noticed that on localhost I could access port 80. I couldn’t access it from outside.
I can access it if I flush the iptables. #iptables -F
Now I am working on configuring the iptables.
Thanks for all of your help.