Difference between revisions of "AM FAQ"

From Archivematica
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 18: Line 18:
 
sudo start archivematica-mcp-server
 
sudo start archivematica-mcp-server
 
sudo start archivematica-mcp-client</pre>
 
sudo start archivematica-mcp-client</pre>
 +
 +
=I am getting a white error page in the Dashboard. How can I find out what the error is?=
 +
 +
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): <pre>sudo vim /usr/share/archivematica/dashboard/settings/common.py</pre>
 +
# Change the "DEBUG" flag from "False" to "True" <pre>DEBUG = True</pre>
 +
# Save the file
 +
# Restart Apache <pre>sudo apache2ctl restart</pre>
 +
# 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

Latest revision as of 12: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.

  1. SSH to the Archivematica server
  2. 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
  3. Change the "DEBUG" flag from "False" to "True"
    DEBUG = True
  4. Save the file
  5. Restart Apache
    sudo apache2ctl restart
  6. Reload the dashboard page reporting the error in your browser
  7. Debug or report error
  8. Restore DEBUG to False and restart Apache to turn error reporting off again