Difference between revisions of "AM FAQ"
Jump to navigation
Jump to search
(Add instructions for getting a stack trace for Dashboard errors) |
|||
(One intermediate revision by the same user not shown) | |||
Line 24: | Line 24: | ||
# SSH to the Archivematica server | # SSH to the Archivematica server | ||
− | # With your preferred text editor, open the dashboard settings file (vim shown in example): <pre>sudo vim /usr/share/archivematica/dashboard/settings/common.py</pre> | + | # With your preferred text editor, open the dashboard settings file (vim shown in example; Note that you must use sudo to edit this file): <pre>sudo vim /usr/share/archivematica/dashboard/settings/common.py</pre> |
# Change the "DEBUG" flag from "False" to "True" <pre>DEBUG = True</pre> | # Change the "DEBUG" flag from "False" to "True" <pre>DEBUG = True</pre> | ||
# Save the file | # Save the file | ||
# Restart Apache <pre>sudo apache2ctl restart</pre> | # Restart Apache <pre>sudo apache2ctl restart</pre> | ||
# Reload the dashboard page reporting the error in your browser | # Reload the dashboard page reporting the error in your browser | ||
− | # | + | # ''Debug or report error'' |
# Restore DEBUG to False and restart Apache to turn error reporting off again | # Restore DEBUG to False and restart Apache to turn error reporting off again |
Latest revision as of 11:12, 2 April 2014
Main Page > Development > Administrator_manual > FAQ
How to restart the Archivematica services?[edit]
Stopping[edit]
sudo stop archivematica-mcp-server sudo stop archivematica-mcp-client sudo /etc/init.d/apache2 stop sudo /etc/init.d/gearman-job-server stop sudo stop mysql sudo /etc/init.d/elasticsearch stop
Starting[edit]
sudo /etc/init.d/elasticsearch start sudo start mysql sudo /etc/init.d/gearman-job-server start sudo /etc/init.d/apache2 start sudo start archivematica-mcp-server sudo start archivematica-mcp-client
I am getting a white error page in the Dashboard. How can I find out what the error is?[edit]
Seeing an full error stack trace for the Dashboard requires knowing how to edit a configuration file from the command line.
- SSH to the Archivematica server
- With your preferred text editor, open the dashboard settings file (vim shown in example; Note that you must use sudo to edit this file):
sudo vim /usr/share/archivematica/dashboard/settings/common.py
- Change the "DEBUG" flag from "False" to "True"
DEBUG = True
- Save the file
- Restart Apache
sudo apache2ctl restart
- Reload the dashboard page reporting the error in your browser
- Debug or report error
- Restore DEBUG to False and restart Apache to turn error reporting off again