Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] issues with setting up a maddash mesh

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] issues with setting up a maddash mesh


Chronological Thread 
  • From: Michael Johnson <>
  • To: "Robinson, John-Paul" <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] issues with setting up a maddash mesh
  • Date: Fri, 21 Sep 2018 14:10:54 -0400
  • Ironport-phdr: 9a23:qFRC5R9jwC0YA/9uRHKM819IXTAuvvDOBiVQ1KB42+kcTK2v8tzYMVDF4r011RmVBdqds6oMotGVmpioYXYH75eFvSJKW713fDhBt/8rmRc9CtWOE0zxIa2iRSU7GMNfSA0tpCnjYgBaF8nkelLdvGC54yIMFRXjLwp1Ifn+FpLPg8it2O2+55/ebx9UiDahfLh/MAi4oQLNu8cMnIBsMLwxyhzHontJf+RZ22ZlLk+Nkhj/+8m94odt/zxftPw9+cFAV776f7kjQrxDEDsmKWE169b1uhTFUACC+2ETUmQSkhpPHgjF8BT3VYr/vyfmquZw3jSRMMvrRr42RDui9b9mRhHohikZKjA382/XhcNsg61Goh2svBN/z5LObYyPKPZyYqHQcNUHTmRBRMZRUClBD5u7YYsOE+UBPfxXoJf5p1ATqRW+AgmsBOX0yj9PgH/9wKo30+EjEQzFwgAtBN0OsHDTrNruLqgSVea1zK7UwjnZbvNWxC3x55bVfRA8uPyBW697f8TWyUkqDQzFj1OQpJT+PzOS2eUBqW6b4PR8Ve+plmUpqBlxryCyysojjoTFnJ8Zx1HE+Clj3Yo4K9K1RFR5bNOkFpZbqjuUOJFsQsw4RmFloCY6xaMCuZ68ZCUKzY4oxx/ba/Cdb4eI/g7sWPyeITdignJlf66wiwyz8Ui90OHzSNS70EtSoipElNnDqGwN2gTO5sWITvZx5Fqt1DeP2gzJ9+1JL085mbDZJpMh2rIwk4AcsUXHHi/4gkX2i6qWe10h+uiq6OnrfK7rppCYN49zkQ7xKKAumsq4AeskKAQOXnWb9f6i27L+4E31WK9KgeEukqnFrJDaItwWpranDA9P3IYj8BG/DzG839QChHUHMUlFdwydj4XyP1HOIev4Deukg1iyijtrxvbGPqH/DZXXKHjMjqvhcahn50FC1QUz0IMX25UBQIsGKvP1QUj38JT6CR8/djS93uKtQIF/zpk2RGuFRKKVLfWBn0WP47cKIuKMbYIR8BT6K/4+4Pim2Xo7yQU1cq2u15ITbnezWPV7ZUiVfCy/0Z86DW4Ws19mH6TRg1qYXGsLag==

Hi,

Comments below:

On Fri, Sep 21, 2018 at 05:12:37PM +0000, Robinson, John-Paul wrote:

We suspect something is up with cassandra the status shows somewhat
confusing output "active (exited)":

workshop@soxws14:~/projects/mesh$ sudo systemctl status cassandra
● cassandra.service - SYSV: Starts and stops Cassandra
   Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset:
disabled)
   Active: active (exited) since Fri 2018-09-21 16:43:46 UTC; 24min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5622 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited,
status=1/FAILURE)
  Process: 5934 ExecStart=/etc/rc.d/init.d/cassandra start
(code=exited, status=0/SUCCESS)

Sep 21 16:43:46 soxws14.sox.net systemd[1]: Starting SYSV: Starts and
stops Cassandra...
Sep 21 16:43:46 soxws14.sox.net su[5943]: (to cassandra) root on none
Sep 21 16:43:46 soxws14.sox.net cassandra[5934]: Starting Cassandra: OK
Sep 21 16:43:46 soxws14.sox.net systemd[1]: Started SYSV: Starts and
stops Cassandra.

To clarify a couple points, "active (exited)" means the service is *enabled* (this is
what "active" means in this context), but it is not running (exited).

I would suggest stopping cassandra using
$ sudo systemctl stop cassandra

and then checking to make sure there are no more cassandra processes running:

$ ps aux | grep cassandra

If there are any remaining processes, kill them. Then start cassandra back up.

Your statement that local tests are being archived leads me to believe that
cassandra is running and your other hosts are unable to authenticate (in this
case, your ip auth may not be working).

On the other hand, those Django errors usually mean Cassandra is down/unreachable from the point of view of esmond, regardless of what cassandra itself tells you.
These two ideas do seem to conflict, but I'd try these steps to see where
they gets you.

Thanks,
Michael

Attachment: smime.p7s
Description: S/MIME cryptographic signature




Archive powered by MHonArc 2.6.19.

Top of Page