Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm migrating a Rails project onto an Apache server. I've followed the steps similarly to this link (installed passenger as ruby gem, added some lines to /etc/apache2/apache2.conf, set Vitual Host to rails app ~/public directory.)

When I visit the site, I only see content of dispatch.fcgi. That link mentions that the problem is solved by rebooting whole server (apache reboot didn't suffice). I'm not familiar with servers, and I'm not sure what rebooting the whole server means, or how I can do it.

share|improve this question

closed as not a real question by MDMarra, Wesley, mdpc, Jenny D, James O'Gorman Jun 14 '13 at 22:34

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

    
You can reboot the whole server from the terminal by issuing sudo reboot –  adamo Jun 14 '13 at 15:20

2 Answers 2

up vote 0 down vote accepted

Before trying to reboot the complete server, try to restart Apache first.

Depending on your distribution, one of this commands should work:

service httpd restart

service apache2 restart

/etc/init.d/httpd restart

/etc/init.d/apache2 restart

Depending on the distribution and your user rights, you might need to prepend sudo in front of the commands.

share|improve this answer

To reboot, I have always used the following sequence:

cd //
sync
init 6
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.