perfsonar-user - Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration
Chronological Thread
- From: Zhi-Wei Lu <>
- To: Andrew Lake <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration
- Date: Thu, 6 Sep 2018 16:26:36 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is ) ;
- Ironport-phdr: 9a23:E/d47BdnasH++xNr7OvJnDm8lGMj4u6mDksu8pMizoh2WeGdxc25ZRKN2/xhgRfzUJnB7Loc0qyK6/+mATRIyK3CmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+KPjrFY7OlcS30P2594HObwlSizexfbF/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbDVwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4qF2QxHqlSgHLSY0/mHJhMJtkKJVrhGvpxJ9zI7VfI6aO+FzcbnBcd8GX2dNQtpdWixHD4ihb4UPFe0BPeNAoob+p1sOrAKyCgmyC+Pu1zRGgGL21rA93uUgHwDG2BEgEskTsHvIsdr6LrkSUeGuzKXS0zrMcu5W1C775YPVfB4hpvSMUqhxccrX0UQvCh/KgUiKpoz7PjOVzf4BvHaG4Op9Te6vimgnqx1vrTi1wMcjlJXJipwPxl/a6Cp53Z45JdqlSE5nZd6kF5xQtyKAO4RqRcMiRmdlszs5xL0eoZO3YjIFxIg6yxPadvCLbpWE7xftVOuePTt0mHdoeLyhiBu970etz+jxW8io3FlUtiZIk9vBumoQ2xHS68WLUOZx80ig1DqVygzf9PxILVg6laXFKJMt3rs9m58RvEjfESL7lkD7jKGWe0Uq5+Sl7vrob7rmq5+SMoJ5hBzxPbkol8eiG+o3KBIOUHKe+emk1L3s40n5QLJSg/MujqTXt4zWKMsCqqOkGwFY3J8v6xGkADi4ytgYmmQHLE5edxKAkojpPUzBLOrgDfelhFSsjClkyOzaPr3gBZXNKGLPkLD8fbZh705czw0zzdNF651IDbEBJer/Wk73tNPGEh80KxK4zPz7BNlg044SRH+DDrKcPaPcvlKE+v4jLuyCZIALtzvyNf0o6vvvgHMlh1ARZayp0oEWaHC8EPRmOUKZYX/0j9YAH2YKuhc+Qff3iFKeTDFcfWiyX6Mn5j0hFo2pEJrDSpi3gLOdxCe7AoFWZmdeB1CUD3jobYuEW+wLaCKUOMBhiCUIVaW6S4A/zxGjrwv6y7t8LurI4S0Uq4jv1Nlz5+3Pix4y7zp0ANqB022TVW17gH4HRyJllJ15ulF3n1efzbBj0bsfE9ULvrVSWwk3MZ/azPc8E8r1Rg/KYtaOThDgRci6BTY2TZQ6xNpJNFtnH4CikgzbxGfxKvJPufHRKpg16b7HmXn3O8tnzXvaju8sg0RrGOVUJGi+j+Ml2RPSCIjOnUvUzYiyeL4SxynL/X3G0HGDpg9UWRJ5BP2fSShGcl+Pp4Sk7BmTRrH3Auh7OFAblsWPevMaZoOw1lsXFf68YsDXMzrtxWnuWUjWzevQYtKyKj1Bgi6NBEEKwlod8yjcPxxmEn+1/TmAU2U+Tgy3OxK1rrUk8S7nAFQ4xh2DOkxCj7Szt0Q7g8W2QehIgbs0vzYbpRZ9OQbg+O7RDICu9idrYfUEX+gDwlFOhS+Cm0JnM4etNb5vigtGIDlxpF7kghVrFp1bw49tqHIx0BE0KKSE3UlHei/Cm538J/rMO2zq9Ve0aqHQ3V/Ql86b4KkU7/IxsRD+pwyzRXYlplxh38NYzDO475bHRF4bV57geksssR53u+eJTDM64tbm1XwpDqS1+hvfk4Y7G+844gurc95BMbjCGQPvRZ5JT/OyIfAnzgD6JikPO/pfofZuZZGvaueG1ai3Pe1pgDOhiyFd7Ztg1l6XqnsuUfbGipACxfzQnhCKUTvxlh+Aioj2gsgFAFNaBW+j0W7hDY9VaLd1eNMZFmOzC9C8ytxghoWrVnJFpxau
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Thanks, Andy!
It turns out that the "authtoken_token" in the esmond database has the "NEW" value rather than the migrated value. I looked at the backup and restore scripts and examined the postgresql database. I re-"restore" the database, but it didn't replace the "new" value. I had to drop the authtoken_token table (one table only) and re-run the restore script one more time. It then restored the "old" authtoken values. After that I ran the scirpt again and restarted a few daemon last night,
/usr/lib/perfsonar/scripts/system_environment/configure_esmond --force
In the /var/log/pscheduler/pscheduler.log, we can see successful runs, ...
Sep 6 09:18:39 mammoth-owamp-v4 journal: runner INFO 1575526: Running https://mammoth-v4.noc.ucdavis.edu/pscheduler/tasks/dbc2f80b-d785-4366-94fd-bc64d2a042ba/runs/5e0f34cc-1f84-4499-93ce-1774a0df7f1c
Sep 6 09:18:39 mammoth-owamp-v4 journal: runner INFO 1575526: With traceroute: trace --dest melange-v4.noc.ucdavis.edu --length 40 --source mammoth-v4.noc.ucdavis.edu --hops 64
Sep 6 09:18:39 mammoth-owamp-v4 journal: runner INFO 1575526: Run succeeded.
...
However, I do not see any new data in the web-gui
http://mammoth.noc.ucdavis.edu/toolkit/
Maybe, there are still inconsistency in the postgresql esmond database with cassandra data sources (mixing with new values which were not restore properly). I will try to drop all esmond tables and re-run restore script.
Thanks again Andy!
Zhi-Wei Lu
IET-CR-Network Operations Center
University of California, Davis
(530) 752-0155
From: Andrew Lake <>
Sent: Thursday, September 6, 2018 6:06:44 AM To: Zhi-Wei Lu Cc: Subject: Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration Hi,
I think maybe one of the steps you have done has gotten things working again, possible it took some time to propagate. If I look at your newest tasks they seem to be archiving successfully to localhost. For example see:
Notice the first JSON blob labelled "archivings" and how it indicates it succeeded in the "diags" section.
Andy
On Wed, Sep 5, 2018 at 1:46 PM, Zhi-Wei Lu
<> wrote:
|
- [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/05/2018
- Message not available
- RE: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/05/2018
- Message not available
- Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Andrew Lake, 09/05/2018
- RE: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/05/2018
- Message not available
- RE: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/05/2018
- Message not available
- RE: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/05/2018
- Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/06/2018
- Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/06/2018
- RE: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/07/2018
- Re: [perfsonar-user] Archiving to esmond failed after CentOS6 -> CentOS7 migration, Zhi-Wei Lu, 09/06/2018
Archive powered by MHonArc 2.6.19.