Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Still fighting with perfsonar-archive and maddash bundles, in both Centos7 and Ubuntu

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Still fighting with perfsonar-archive and maddash bundles, in both Centos7 and Ubuntu


Chronological Thread 
    < Chronological >      < Thread >
  • From: Phil Reese <>
  • To: "" <>
  • Subject: [perfsonar-user] Still fighting with perfsonar-archive and maddash bundles, in both Centos7 and Ubuntu
  • Date: Sun, 25 Jun 2023 16:35:03 -0700
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stanford.edu; dmarc=pass action=none header.from=stanford.edu; dkim=pass header.d=stanford.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=joaRmr0K54U0ayAUV2d+tAi1CUvewdOGIgRvPeUze5M=; b=QQi4veA8xwdfwy38jdT4pGgD9n0/NWP1uapnDn4tzrNjG7WhjIpmtX8XUUYe0RNzPdvfurEpUxo8FTfA2TMQty0vKWbVBQawMOM9ZZIHbF7E0FcdR+E90OGnRwSNFG5ip2UGhq2B9eJLZrPy2RSdKsI8AQzxv45SjlrVhUvxzBly7htElSuqZ07GRBT9RjgFiZeDzJxMUajJ2i1Xriok9qBp5umk7O7ghGEFCvwRsR+vWid1AeM7K49tTBpuCZATtql28GF5PntH3BNXZXfbnCs9FvmgK3hE0wxo9gSi/9wNsHpqMTEQ/ZmzUnPigZNDRf6TZy/VGUlYHNnlvroTJQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Bw3+3zI/Go1a/IkfFKPVSrGmvyO8GUB79D5fRPBdwSpC0MLUkRmGGzEUF1YEO/y1XEZCh2vgtRaHM/966fFmcoCXB5C3KPmpsmxkbhLHgHr/oP1iloZyrgP6/bKNc1WHO3Gj6/0Bz7hEscCAl8YeKGhZ8G/RzMLbD9EpKzNc40te3dk+AcR4IOAbGhx2reSW6hh3qenHqeVvR4RRqi5j623vZ6ifHQQN2ocfw5bFVWt9Sduyhr7Un69HCRuiiBRYO0j9NeIfvQQTqMgzXi98E4LBG+w/GmyxGNsKA6po2X8T+txsdGrMtGME3jkZ7fJn0aTZ7T6cdNgIDoCK4thLAg==
Hi,

My Maddash woes continues.

I can now confirm that the Centos and Ubuntu branches produce the same results, right down the  same maddash.yaml files.

The only 'archive' solution I can get working is to build a Tooklit node which has everything and use that for the archive host.  The bundles for Centos and Ubuntu all seem to install smoothly but neither can be used as a Data Source in Grafana.

Ubuntu give  this error in Grafana:
OpenSearch error: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> <hr> <address>Apache/2.4.41 (Ubuntu) Server at vag-md.ufixu.com Port 443</address> </body></html>

Centos shows this:
OpenSearch error: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>503 Service Unavailable</title> </head><body> <h1>Service Unavailable</h1> <p>The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.</p> </body></html>

Further, Ubuntu is unable to start opensearch (Centos does start opensearch but has the same error from the Grafana data source plugin):
● opensearch.service - OpenSearch
     Loaded: loaded (/lib/systemd/system/opensearch.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Sun 2023-06-25 22:38:10 UTC; 4s ago
       Docs: https://opensearch.org/
    Process: 72799 ExecStart=/usr/share/opensearch/bin/systemd-entrypoint -p ${PID_DIR}/opensearch.pid --quiet (code=killed, sign>
   Main PID: 72799 (code=killed, signal=KILL)

Jun 25 22:38:02 vag-md systemd[1]: Starting OpenSearch...
Jun 25 22:38:10 vag-md systemd[1]: opensearch.service: Main process exited, code=killed, status=9/KILL
Jun 25 22:38:10 vag-md systemd[1]: opensearch.service: Failed with result 'signal'.
Jun 25 22:38:10 vag-md systemd[1]: Failed to start OpenSearch.

A final data point is that the Maddash grid page opens, shows the expected name of the dashboard but never shows any grids (the name is from the .json file).  There are no grids listed under the 'All Grids" dropdown.  Both OS bundles show this same behavior.

I now have a vagrant/ansible project, one for Centos and one for Ubuntu, which builds 3 testpoints, an archive and md node.  This makes retesting easy though it takes a long time to build all those nodes (for some reason Ubuntu takes considerable longer!)  Happy to share if interested.

Out of curiosity, has anyone in the community been able to get the PS5 v5.0.3 Archive and/or Maddash bundles working?    Would you have any tips to share?

Thanks,
Phil




Archive powered by MHonArc 2.6.24.

Top of Page