Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Failed perfSONAR upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Failed perfSONAR upgrade


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Raul Lopes <>, "" <>
  • Subject: Re: [perfsonar-user] Failed perfSONAR upgrade
  • Date: Wed, 17 May 2023 14:46:18 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.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=yTV8g+q9PVQuowkMLPCx1MH96cc3t47XA3p+yyYGx9k=; b=ASWhgTHxbeD30eYerUkDU3QCD2tML6pgJh1vOq19hsYalkFxpkcSkWf1KkLUmm5mt/JE5AfyevZv8vM0Z2dEqK3yMhn5MzZdhXhvmD6SvmRDoF6B0YNJ/f1X8upDFMrDOID1tggaGPui2/M/P3PkTV6gt7LF8fZ9mphnfvkjVl6zRBBSajHwfNjBa1ry5Vs8WLPCf3s3LBzrO7P0ApzOElJG5YQxqtpwhRIFwXTYI6J6u/HjNfh5/WOPGLvgxGdHEJ43VQKXgaEepG+2vX+NdtKEI2c5fe0/louTcnea7YLzU47DjwEZMPT8lbTFI11qpmh7WKtNll3rRBlLHBCIZw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fyuYiGZW8PVs060uAwr91WfYoNfbadlvEoWIpi+zXSCfaS12CV6zCwdHibbQmzsWvqQzYkrRmzdlfjCP6rpPcXIt4ZnTRk8KrEE9nA2NBhrJwsr6fXyPx1jnR9Vy3Dg/4d3ydqTVeJjlf5CH/FP9HSaiaF5Y7KjWEyEcJcGLbj6Cop1iucYTgz+uSrMnri6Q2dEmJMyPCtNWzZ56nPfyyzLon8mo/LKTVyGYrfC53FlksuG9rfcr7KU6277A5lYMmlOc6M/Ka6J5XrijYO0iOJTj48FWiEGc//RHzTpj3FfzoNbZy1i1ux+e/VKRZTXLMAVFPawkDIcLclf6H9A8cQ==
  • Msip_labels:

Raul Lopes writes:

 

We have a failed perfSONAR upgrade with errors seemin g to indicate a DB error: see  [0].

 

Would you have advice on recovery?

 

The errors look like something went wrong during the upgrade.  If you’re on a RPM-based system, any errors will have been sent to syslog.  Look for the string “db-update-pscheduler” and let me know what you find.

 

RPM has a limitation where failures in post-install scripts are ignored, largely because there’s no way to roll the entire system back to its prior state while installing a bunch of packages.   (There are links to discussion about this in a very-old ticket:  https://github.com/perfsonar/pscheduler/issues/110.)

 

To get your database back into a usable state, become root, run “pscheduler internal db-update” to refresh the database code.  This is the same step done by the package when it upgrades and is safe to run as many times as you want.    If it emits any errors, let me know what they are.  If it appears to have gone cleanly, do a “pscheduler troubleshoot” to make sure the whole system is working properly.

 

--Mark


Archive powered by MHonArc 2.6.24.

Top of Page