Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfSONAR User Q&A and Other Discussion

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfSONAR User Q&A and Other Discussion


Chronological Thread 
  • From: Mark Feit <>
  • To: "Ahuja, Satish (Exchange)" <>
  • Cc: Conan F Moore <>, Satish Ahuja <>, "" <>
  • Subject: Re: [perfsonar-user] perfSONAR User Q&A and Other Discussion
  • Date: Fri, 24 Feb 2023 17:28:05 +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=D7GqliJBehvCyKu/890KECECtdEWHIohA7XhPRRDAqg=; b=XSdazQwIHmVXSRu0Is6ExkxOWFFP/VFktR4nVd0wbauMY4yyRAQb1B5J/Avh6RqbfuGsZByxzziVLE5G3JcKXwF8zmYmIU5e7bEO+V7zdaaDxYYBQCFvzct1lMm8In9kpxK3Q4a+j3o6faUpUmjhkKMPTGwB6G4ZbOrTsqxGyoUOMg/b9H103PpKDHsCfXcX1xzkpQj7UsQlSiNstJUFGSJqVuEohhj4/J/vuZrBh+9ykWwxq1QcfnL8nIC94pYFhlZWMfhIvQdfEsYK48pSR0SF+nz7kecQqYBMJyvNXZ/sM8ESW8sao8oDbH+vfO4MrxMmc8RMlBh2TF6CAIVeig==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=excCrACFTNoVdkaXUym3yJzfMFjqutAS1LMaSoNmo0Fp2VVWTWwJ75nBphZoUifMCcqtkpEz9NA+nCIBu4PdGnxL0W+Em1D9jnZpjvRQuhUTkkOqNj1PxfFglpJHZqIOGh1IVEjVmcXCOPA73OWUUmJ9k8TfRa/FZQ54BA3D9uUNgi7jXgw6aEJdzzDV8Awun1ONgSoiPwL7cAJcWlf8Jx7xj6Kkp8XdtP3WY1xbNDj9CaM3Y3FfKHMO3ezPDMw5dQelgtIjGg2mtJ/gJg6iz8zdJeMgDFt0I++2ZI3KiRI4Hkc3nQ/JXgPmSk+SpAxZekxkz5oQsfPlqGzGtw0z7w==

Ahuja, Satish (Exchange) writes:

 

I ran the troubleshooting steps you mentioned and found error on perfSonar node1. The process or daemon is unable to connect to database. The other node is working fine. I wonder I followed the same steps while installing image but somehow node1 got into some errors. I will try to troubleshoot this otherwise I will start over on node1. I will keep you updated once I’m done with this.

 

Based on what you sent, it looks like PostgreSQL, which underpins both pScheduler and Esmond, didn’t come up properly on that system.  We’d have to do a lot of forensics to figure out why and would ultimately end up doing a forced reinstallation of the affected packages.  I’d recommend doing that, which involves running these two commands as root (assuming you’re on CentOS and not Debian or Ubuntu):

 

  • yum -y erase ‘postgresql*’  (This will erase a lot of packags.  Do not panic.)
  • yum -y install perfsonar-toolkit

 

That should put the system back in order and into its unconfigured state.  If it doesn’t work after that step and setting pSConfig to grab your mesh file, something isn’t right on that system and I’d recommend nuking it from orbit and rebuilding the system from the OS.

 

--Mark

 




Archive powered by MHonArc 2.6.24.

Top of Page