Dashboard service fails to Start

[claude fortune]

Hi All

I am new here.

 

I have been tasked with exploring the possibilities of using Archivematica in our organization.

I followed the automated install guide using Ansible on Ubuntu 22

Vagrant up kick off the deployment which failed.

Vagrant provision seemed to rectify the issue.

At this point I am not able to reach the dashboard. On my fresh install the dashboard service fails to start and cannot be started manually

vagrant@am-local:~$ sudo service archivematica-dashboard restart
vagrant@am-local:~$ sudo service archivematica-dashboard status
● archivematica-dashboard.service - Archivematica Dashboard
     Loaded: loaded (/etc/systemd/system/archivematica-dashboard.service; enabled; vendor preset: enabled)
     Active: deactivating (stop-sigterm) (Result: exit-code) since Thu 2024-04-18 11:43:34 UTC; 412ms ago
    Process: 166683 ExecStart=/usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config /etc/archivematica/dashboard.gunicorn-config.py wsgi:>
   Main PID: 166683 (code=exited, status=1/FAILURE)
      Tasks: 1 (limit: 4647)
     Memory: 45.6M
        CPU: 12.416s
     CGroup: /system.slice/archivematica-dashboard.service
             └─166686 /usr/share/archivematica/virtualenvs/archivematica/bin/python /usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config>

Apr 18 11:43:34 am-local gunicorn[166683]:   File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/gunicorn/arbiter.py", line>
Apr 18 11:43:34 am-local gunicorn[166683]:     self.stop()
Apr 18 11:43:34 am-local gunicorn[166683]:   File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/gunicorn/arbiter.py", line>
Apr 18 11:43:34 am-local gunicorn[166683]:     time.sleep(0.1)
Apr 18 11:43:34 am-local gunicorn[166683]:   File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/gunicorn/arbiter.py", line>
Apr 18 11:43:34 am-local gunicorn[166683]:     self.reap_workers()
Apr 18 11:43:34 am-local gunicorn[166683]:   File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/gunicorn/arbiter.py", line>
Apr 18 11:43:34 am-local gunicorn[166683]:     raise HaltServer(reason, self.WORKER_BOOT_ERROR)
Apr 18 11:43:34 am-local gunicorn[166683]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>
Apr 18 11:43:34 am-local systemd[1]: archivematica-dashboard.service: Main process exited, code=exited, status=1/FAILURE

The dashboard logs are as follows:

vagrant@am-local:~$ sudo tail -n30 /var/log/archivematica/dashboard/dashboard.log
ConnectionRefusedError: [Errno 111] Connection refused

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/elasticsearch/connection/http_urllib3.py", line 232, in perform_request
    response = self.pool.urlopen(
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connectionpool.py", line 844, in urlopen
    retries = retries.increment(
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/util/retry.py", line 445, in increment
    raise reraise(type(error), error, _stacktrace)
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/util/util.py", line 39, in reraise
    raise value
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connectionpool.py", line 790, in urlopen
    response = self._make_request(
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connectionpool.py", line 496, in _make_request
    conn.request(
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connection.py", line 395, in request
    self.endheaders()
  File "/usr/lib/python3.9/http/client.py", line 1280, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib/python3.9/http/client.py", line 1040, in _send_output
    self.send(msg)
  File "/usr/lib/python3.9/http/client.py", line 980, in send
    self.connect()
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connection.py", line 243, in connect
    self.sock = self._new_conn()
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.9/site-packages/urllib3/connection.py", line 218, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7fb8bdeaa370>: Failed to establish a new connection: [Errno 111] Connection refused

Any advice at this point would be welcome, thanks in advance

[Amaya Rodrigo]

HI!

Please make sure your MCP server and client are up and running.

This is the right order to start your services:

systemctl reset-failed
service archivematica-mcp-server restart

service archivematica-mcp-server status
service archivematica-mcp-client restart

service archivematica-mcp-client status
service archivematica-dashboard restart

service archivematica-mcp-client status

service archivematica-storage-service restart

service archivematica-mcp-client status

Re-start each service and then run the status command to make sure each one is up before restarting the next

Hope that helps!

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/0fb965b9-d2bc-4db8-9d15-c5bc843fa402n%40googlegroups.com.

--

Amaya M Rodrigo Sastre (she/her/bofh) - sysadmin@artefactual 

<arod...@artefactual.com >|< https://www.artefactual.com >

[claude fortune]

Hi 

Thanks for info, 

I followed the services restart procedure you listed. The after the dashboard service is restarted the status shows it is good. 

vagrant@am-local:~$ sudo service archivematica-dashboard restart
vagrant@am-local:~$ sudo service archivematica-dashboard status
● archivematica-dashboard.service - Archivematica Dashboard
     Loaded: loaded (/etc/systemd/system/archivematica-dashboard.service; enabled; vendor preset: enabled)

     Active: active (running) since Thu 2024-04-18 14:34:57 UTC; 7s ago
   Main PID: 169614 (gunicorn)
      Tasks: 5 (limit: 4647)
     Memory: 137.7M
        CPU: 10.723s
     CGroup: /system.slice/archivematica-dashboard.service
             ├─169614 /usr/share/archivematica/virtualenvs/archivematica/bin/python /usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config>
             ├─169615 /usr/share/archivematica/virtualenvs/archivematica/bin/python /usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config>
             ├─169616 /usr/share/archivematica/virtualenvs/archivematica/bin/python /usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config>
             └─169617 /usr/share/archivematica/virtualenvs/archivematica/bin/python /usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config>

Apr 18 14:34:57 am-local systemd[1]: Started Archivematica Dashboard.
Apr 18 14:34:58 am-local gunicorn[169614]: [2024-04-18 14:34:58 +0000] [169614] [INFO] Starting gunicorn 21.2.0
Apr 18 14:34:58 am-local gunicorn[169614]: [2024-04-18 14:34:58 +0000] [169614] [INFO] Listening at: http://127.0.0.1:8002 (169614)
Apr 18 14:34:58 am-local gunicorn[169614]: [2024-04-18 14:34:58 +0000] [169614] [INFO] Using worker: gevent
Apr 18 14:34:58 am-local gunicorn[169615]: [2024-04-18 14:34:58 +0000] [169615] [INFO] Booting worker with pid: 169615
Apr 18 14:34:58 am-local gunicorn[169616]: [2024-04-18 14:34:58 +0000] [169616] [INFO] Booting worker with pid: 169616
Apr 18 14:34:58 am-local gunicorn[169617]: [2024-04-18 14:34:58 +0000] [169617] [INFO] Booting worker with pid: 169617

I try and connect on port 80 and get a bad 502 bad gateway

vagrant@am-local:~$ sudo service archivematica-dashboard status^C
vagrant@am-local:~$ curl -v localhost:80
*   Trying 127.0.0.1:80...
* Connected to localhost (127.0.0.1) port 80 (#0)
> GET / HTTP/1.1
> Host: localhost
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< Server: nginx
< Date: Thu, 18 Apr 2024 14:35:17 GMT
< Content-Type: text/html
< Content-Length: 150
< Connection: keep-alive
<
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
* Connection #0 to host localhost left intact

when I check the dashboard service it has failed

vagrant@am-local:~$ sudo service archivematica-dashboard status
● archivematica-dashboard.service - Archivematica Dashboard
     Loaded: loaded (/etc/systemd/system/archivematica-dashboard.service; enabled; vendor preset: enabled)

     Active: activating (auto-restart) (Result: exit-code) since Thu 2024-04-18 14:35:16 UTC; 22s ago
    Process: 169614 ExecStart=/usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config /etc/archivematica/dashboard.gunicorn-config.py wsgi:>
   Main PID: 169614 (code=exited, status=1/FAILURE)
        CPU: 11.571s

The Dashboard service runs for a few seconds after the service is restart and fails.

All other services active and running.

[claude fortune]

Hi 

Thanks for the info, I followed the procedure but I did not get any joy. After the dashboard service is restarted, the dashboard service runs for a few second before it fails again.

vagrant@am-local:~$ sudo service archivematica-dashboard status
● archivematica-dashboard.service - Archivematica Dashboard
     Loaded: loaded (/etc/systemd/system/archivematica-dashboard.service; enabled; vendor preset: enabled)

     Active: activating (auto-restart) (Result: exit-code) since Thu 2024-04-18 15:12:17 UTC; 19s ago
    Process: 170327 ExecStart=/usr/share/archivematica/virtualenvs/archivematica/bin/gunicorn --config /etc/archivematica/dashboard.gunicorn-config.py wsgi:>
   Main PID: 170327 (code=exited, status=1/FAILURE)
        CPU: 11.653s

Apr 18 15:12:17 am-local systemd[1]: archivematica-dashboard.service: Consumed 11.653s CPU time.

On Thursday, April 18, 2024 at 4:14:39 PM UTC+2 arod...@artefactual.com wrote:

[Amaya Rodrigo]

Claude,

There's something going on between nginx and the dashboard, that's all I can see from my end.

Can you check that the mysql server is installed and has the MCP and SS db?

Can you check that at least  these porst are open and listening?

root@am# netstat -putan | grep 800
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      977/nginx: master p
tcp        0      0 127.0.0.1:8001          0.0.0.0:*               LISTEN      184514/python      
tcp        0      0 127.0.0.1:8002          0.0.0.0:*               LISTEN      184601/python

      

Leaving the error logs you provided down here for (my) future reference:

[Lou Hines]

I'm having the same error on my end. All the ports you list are open and listening.

[Alberto Villalobos]

Hello, 

I am having the same error of Claude.  I have just installed Archivematica in Ubuntu 22.04 using the manual procedure (https://www.archivematica.org/en/docs/archivematica-1.16/admin-manual/installation-setup/installation/install-ubuntu/#ubuntu-instructions) . 

1. The storage process is working, and I can login in.

2. The dashboard seems to restart and falls.

Any solution for this problem reported in July 2024?