Restart Instructions for Expertiza

The Expertiza application runs under the Phusion Passenger server for Apache. Passenger dynamically starts and kills instances of the rails application as demand on the application changes. After making changes to the application code, only the rails application need be restarted, not Apache. Apache only need be restarted when making changes to the Apache web server configuration in /etc/httpd/.

Restarting the rails application

Deprecated

Restarting preferably is done via capistrano. See Deploying_Expertiza_to_Production for capistrano setup instructions.

From your development machine in the expertiza app directory, run

cap deploy:restart

Current System instruction (2023)

If you have sudo access, you can SSH into the production server and run

sudo -u rails touch /var/www/expertiza/current/tmp/restart.txt

If this dosen't work, restart the server using the command - shutdown -r After doing shutdown -r, you might need to restart redis server as well using the command

/etc/init.d/redis_6379 start

Restarting Apache web server

sudo /etc/init.d/httpd restart

SSL Password: expertiza

Troubleshooting

1. Apache needs to be started if you get a Connection Refused error when connecting to the site.

   Stop the /usr/etc/httpd process if it is running.

   ps –ef | grep httpd

   If httpd is running, kill its pid

   kill <process id>

   Start the apache server

   apachectl start

   Enter the SSL password: expertiza

2. MediaWiki will be started as part of the initialization of the environment. There is no further requirement for this processes.
3. It may be necessary to restart MySQL if you are receiving the error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' or Connection refused - /var/lib/mysql/mysql.sock.

   /sbin/service mysqld restart

(Note: If only the MySql server needs to be restarted, simply run: sudo /etc/init.d/mysqld restart )

Back to Expertiza_documentation Main page.