perfsonar-user - Re: [perfsonar-user] Failed perfSONAR upgrade
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Raul Lopes <>
- To: Mark Feit <>, "" <>
- Subject: Re: [perfsonar-user] Failed perfSONAR upgrade
- Date: Wed, 17 May 2023 15:04:08 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jisc.ac.uk; dmarc=pass action=none header.from=jisc.ac.uk; dkim=pass header.d=jisc.ac.uk; 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=oSJn3HD4sQnN+8KS0jen9xHmyVBz5G/MLnCOlaOU+AY=; b=hiwBv63p5CB5X+YSYjW7Fy+5ueEQ1wc6UFyYRT2PWdI3QSSnmm12CQMHzo2faJsJLqAGmplx+uM/mjnnW+ePn8EKS8Nq9WHnZxw66ZLbvvXZyVHTb2csBZBXtlZrq3wJLxtqw4yxh0O+XOr1oBEtc6y01c2Wsxw50x3DNMgKtYjbsPDh2Qy0dfGP8k/yvJcEUiKQACrSJyfur9nMsp1y5460UjYLa8/g/d3OuPVE7kVnQaDPR5QqybsEXJgiv0KLGMI5gzsUCHMkEHqli7TGf9UercO85EDBex9LVSyBOZInse2HY3iq67sSFLIKr4CY0Kt7eADb2TWqmtdcwH8C0w==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fn4xp5AgysoEfIp485pOgPH5ZIcmKe7TiVc8KoSPpJ2mwJ0QFLEikJeChfs0Sj+r96bB6tAMbqbNT3nUiOHnMZtXQnZDXdR/rWj5xNxlFGqVMU3LeZzM8Ck/mDX6HRiAD8+xa1R6fs6rkGWgyFwehp3Mn6aZPd3Wkk+8vaws8IQ06DiTOa82eQecyHqBoIR/yOLjqmYY+veOxOMUXFDB/zOL/vMIwqUI0vMlYbFzPC8+NanICHHHHXRhJQ6tdg1HND4dta6fvhNmRn4Tyjeg9lyirlOJCOMHCJub4n54Zsq3O2B1hZplwBNLankijLhf95k5hVazmqTaYZQoFOJKug==
- Msip_labels:
Sent: 17 May 2023 15:46
To: Raul Lopes <>; <>
Subject: Re: Failed perfSONAR upgrade
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
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under company number. 05747339, VAT number GB 197 0632 86. Jisc’s registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 02881024, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800.
Jisc Commercial Limited is a wholly owned Jisc subsidiary and a company limited by shares which is registered in England under company number 09316933, VAT number GB 197 0632 86. The registered office is: 4 Portwall Lane, Bristol, BS1 6NB. T 0203 697 5800.
For more details on how Jisc handles your data see our privacy notice here: https://www.jisc.ac.uk/website/privacy-notice
- [perfsonar-user] Failed perfSONAR upgrade, Raul Lopes, 05/16/2023
- Re: [perfsonar-user] Failed perfSONAR upgrade, Mark Feit, 05/17/2023
- Re: [perfsonar-user] Failed perfSONAR upgrade, Raul Lopes, 05/17/2023
- Re: [perfsonar-user] Failed perfSONAR upgrade, Mark Feit, 05/17/2023
Archive powered by MHonArc 2.6.24.