Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] psconfig service not running

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] psconfig service not running


Chronological Thread 
  • From: Tao Zhang <>
  • To: "" <>
  • Subject: [perfsonar-user] psconfig service not running
  • Date: Thu, 20 Jan 2022 17:05:57 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; 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=OjunvVMnxRH1VJk/oOvk9FVcVSUa7B8SSrL8mNuQvrg=; b=Vq7pGQP1eC+KMJe1e1iJlNg7Y7/TChxSlriSxa0owqMqKda4IWjDZBg7x3kwMttzFnPFxnMWYkZL+ew9Qjh7OjInatkdst9I6jkazlsKnNEzb6pZCCuljZpYSe7UDQmSjjH/bFeGqK6yUEcxt9ErZJ1aYwQgpXXmg5Zts8BLonldlYfiarLik2HAlvemHYOX47yxmZ382NUCkRLN0BpeZ2EpUmSs8nY07Z3pPSMPZ/sv764InioX27zqru/XIUayJoA3PXxMYoZCg+e0nEzWTUK7F6+ISf/tB3SMgOw7uudST5dlnN9R4FrLkd+kWg4H6vDD901zb9FyBuqyUvjPYA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ABC4RQjlDcNZAfMFyL6gGa5G91vg4sz2w0Mw3wlx8CEoCZb3n8DNrtF5jwEicwpRG6SCdumxGPJckRCOFDiZxdpwKJJpn5vjkamv1MENTWpm8Nxb0rHycOH9OkQWIfW2bwuzpUeixt2LqW92QfO1Bv3z9rocchCP2jzzycvzulRg8/AhY+bp3RVxtIgWSjBM1FW5F5qXu1WWsKn/OjAtDX+UeuGKsyH/NtE2jHdngNvEgDqTdw3PoIewLukO3BYp60d2HAe5fbHQcalKL8rTMLLb6b1KYzhoz1o3w8TMSBHyx1+N2jEWOUJT4wpFmxMXfWoSSRwxzKnbmdo+rz8/7A==
  • Suggested_attachment_session_id: 7a89210d-653f-6955-30b5-f5210ffb0ee1

Hi team,
Started from 2021/12/21, the psconfig service on our perfSONAR boxes has been showing 'not running'. I have restarted psconfig-pscheduler-agent service several times, service will go up for a couple of minutes before shutting itself down again.  

service psconfig-pscheduler-agent status
Redirecting to /bin/systemctl status psconfig-pscheduler-agent.service
● psconfig-pscheduler-agent.service - pSConfig PScheduler Agent
   Loaded: loaded (/usr/lib/systemd/system/psconfig-pscheduler-agent.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2022-01-20 11:39:44 EST; 16min ago
  Process: 1917 ExecStart=/usr/lib/perfsonar/bin/psconfig_pscheduler_agent --config=/etc/perfsonar/psconfig/pscheduler-agent.json --logger=/etc/perfsonar/psconfig/pscheduler-agent-logger.conf --pidfile=/var/run/psconfig-pscheduler-agent.pid --user=perfsonar --group=perfsonar (code=exited, status=0/SUCCESS)
 Main PID: 1928 (code=exited, status=25)

Here is the ERROR message in psconfig-pscheduler-agent.log

2021/12/22 02:00:07 INFO pid=17854 prog=main:: line=166 msg=Starting pSConfig pScheduler agent
2021/12/22 02:00:07 INFO pid=17854 prog=main:: line=176 guid=CC32A336-62F4-11EC-AB30-A66E5A4D48ED msg=Running agent...
2021/12/22 02:01:21 ERROR pid=17854 prog=main::__ANON__ line=131 guid=CC32A336-62F4-11EC-AB30-A66E5A4D48ED msg=Died: Invalid date format: 2021-12-21T12:34:09-03:-30 at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Client/PScheduler/TaskManager.pm line 565.
        perfSONAR_PS::Client::PScheduler::TaskManager::_iso_to_ts('perfSONAR_PS::Client::PScheduler::TaskManager=HASH(0x6537df0)', '2021-12-21T12:34:09-03:-30') called at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Client/PScheduler/TaskManager.pm line 395
        perfSONAR_PS::Client::PScheduler::TaskManager::_evaluate_task('perfSONAR_PS::Client::PScheduler::TaskManager=HASH(0x6537df0)', 'HASH(0x67e7fe0)', 1, undef) called at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Client/PScheduler/TaskManager.pm line 368
        perfSONAR_PS::Client::PScheduler::TaskManager::_need_new_task('perfSONAR_PS::Client::PScheduler::TaskManager=HASH(0x6537df0)', 'perfSONAR_PS::Client::PScheduler::Task=HASH(0x66bd548)') called at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/Client/PScheduler/TaskManager.pm line 204
        perfSONAR_PS::Client::PScheduler::TaskManager::add_task('perfSONAR_PS::Client::PScheduler::TaskManager=HASH(0x6537df0)', 'task', 'perfSONAR_PS::Client::PScheduler::Task=HASH(0x66bd548)') called at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/PSConfig/PScheduler/Agent.pm line 210
        perfSONAR_PS::PSConfig::PScheduler::Agent::_run_handle_psconfig('perfSONAR_PS::PSConfig::PScheduler::Agent=HASH(0x2755800)', 'perfSONAR_PS::Client::PSConfig::Config=HASH(0x6b852b8)', 'perfSONAR_PS::PSConfig::PScheduler::Config=HASH(0x64deb00)', 'perfSONAR_PS::PSConfig::Remote=HASH(0x6b8c188)') called at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/PSConfig/BaseAgent.pm line 364
        perfSONAR_PS::PSConfig::BaseAgent::run('perfSONAR_PS::PSConfig::PScheduler::Agent=HASH(0x2755800)') called at /usr/lib/perfsonar/bin/psconfig_pscheduler_agent line 177


From the history email, I saw Bruce Curtis from NDSU had similar issue. Not sure if this issue has been resolved. 

Thanks,
Tao



Archive powered by MHonArc 2.6.24.

Top of Page