perfsonar-user - Re: [perfsonar-user] Trouble after upgrade
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Andrew Lake <>
- To: Orion Poplawski <>,
- Subject: Re: [perfsonar-user] Trouble after upgrade
- Date: Wed, 28 Jun 2017 15:02:30 -0400
- Ironport-phdr: 9a23:sXDfWhxtXUwek//XCy+O+j09IxM/srCxBDY+r6Qd0eseIJqq85mqBkHD//Il1AaPBtqLra8cw8Pt8IneGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2TxTor3az9T8fHAnkfUowf7ytW92as8Pi8Pqz/JubWwJQgDOierBzZEGxtwTWsOEdhpFrbKAu0BKPqXxNLaAe3W5yK0mUmR/mo9qr8YRL8iJMtugn+tIaF6j2YvcWV7tdWR0gP3o4+4XPvBrOBV+G4HcNemgN1BxFH16Wv1nBQp7tv36i5aJG0y6AMJizFOhsVA==
Hi, Looks like its complaining that its using the wrong API token to store results. You should be able to get it back in sync by doing the following: 1. Remove any <measurement_archive> blocks in /etc/perfsonar/meshconfig-agent-tasks.conf. There should be 3 blocks and removing everything between <measurement_archive>...</measurement_archive> including the measurement_archive tags themselves. 2. Run "/usr/lib/perfsonar/scripts/system_environment/configure_esmond —force” to recreate the blocks with the correct key It will take some time for it to recreate the tasks with the correct key so you might still see the errors for awhile afterwards. You will have a good idea it worked if /etc/perfsonar/meshconfig-agent-tasks.conf has new <measurement_archive> blocks with a different “password” field after running the command above. Out of curiosity, did you use the option to migrate your database data or did you just have the script migrate your configuration files? Thanks, Andy On June 28, 2017 at 11:15:16 AM, Orion Poplawski () wrote:
|
- [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/28/2017
- Re: [perfsonar-user] Trouble after upgrade, Andrew Lake, 06/28/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/29/2017
- [perfsonar-user] perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- Re: [perfsonar-user] RE: perfSONAR v4 and IPv6, Andrew Lake, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- [perfsonar-user] RE: perfSONAR v4 and IPv6, Garnizov, Ivan (RRZE), 06/30/2017
- [perfsonar-user] perfSONAR v4 and IPv6, Charley Kneifel, 06/30/2017
- RE: [perfsonar-user] Trouble after upgrade, Garnizov, Ivan (RRZE), 06/30/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/30/2017
- Re: [perfsonar-user] Trouble after upgrade, Orion Poplawski, 06/29/2017
- Re: [perfsonar-user] Trouble after upgrade, Andrew Lake, 06/28/2017
Archive powered by MHonArc 2.6.19.