Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] ABRT: permission error on /run/pscheduler-ticker.pid

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] ABRT: permission error on /run/pscheduler-ticker.pid


Chronological Thread 
  • From: Mark Feit <>
  • To: Brian Candler <>, "" <>
  • Subject: Re: [perfsonar-user] ABRT: permission error on /run/pscheduler-ticker.pid
  • Date: Thu, 13 Dec 2018 15:23:27 +0000
  • Accept-language: en-US
  • Authentication-results: pobox.com; dkim=none (message not signed) header.d=none;pobox.com; dmarc=none action=none header.from=internet2.edu;
  • Ironport-phdr: 9a23:mKJGpBEyAuyOu3lZKXMmdJ1GYnF86YWxBRYc798ds5kLTJ7yos2wAkXT6L1XgUPTWs2DsrQY07qQ6/iocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbAhEmDmwbaluIBmqsA7cqtQYjYx+J6gr1xDHuGFIe+NYxWNpIVKcgRPx7dqu8ZBg7ipdpesv+9ZPXqvmcas4S6dYDCk9PGAu+MLrrxjDQhCR6XYaT24bjwBHAwnB7BH9Q5fxri73vfdz1SWGIcH7S60/VC+85Kl3VhDnlCYHNyY48G7JjMxwkLlbqw+lqxBm3oLYfJ2ZOP94c6jAf90VWHBBU95RWSJfH428c4UBAekPPelaronyu1QAohSlCAmwH+zvzyNEimPq0aA41ekqDAHI3BYnH9ILqHnaq8/6NL0RUeuozKfH0zTDb+9L0jr67YjIfA4uofCQXb9rcMrRz1UvGB3fjlWWt4PlIy2Z2v4TvGeG8uptTOSigHMkpQFpujWj29sgh4bTio8ayF3I7yp0zYUvKdC4SEN3ecOoHZleui2ANYZ7RtkuT3x2tCon0LEKpJC2cSkSxJQp2RHSaOCLfo2N7x39V+udPzl4iXd+d7KxiRa/9EitxfHmWcWq1VtHoCtIn93Qun0Lyhfd8NKISuFn8UekwTuP1x7c6uVDIU0sjaTWN5kvzqIwm5YKr0nNBzL6lFzxjKCNaEoo4O+o6/n7Yrr9oZ+cKol0hRzkPqQ2gMy/Bvg4PRYSUGiH+OS807vj8Vf+QLVXkv02lq7ZsJfZJcgBuqG5BApV3p4i6xa5ETimzMwVkWQbIF9KYh6KgIrkN0vBLf37F/uyg1ShnC9ux//cP73hBpvNLmLEkLfkZbt97kBcxxQyzdBD/J9UC7cBIO7tVU/rstzXEAM5PxKuz+n5Fdp9y5sSWXiTDa+BLKPSrViI6/o3I+aSfo8Vti39K/8j5/H0l381gEIdfbK30psNc324GvVmI16FYXr3nNsNC2YKvgwiTOP0kl2CVyBcZ2qsU64m+D40FZ+mXs//QdWHmr2I2m+QF5taYm1cQgSGV3zhcYmAVu0kcCWYJd8nmTsBA/zpAZcszx+1swnz0f96NefO0iweqZ/50tVpvavemQx4vWhsAt6TyGaLRnsxg3gFXRc32rxyu0pw1g3F3KRl1a92D9tWstZASARyG5Pd06QuDt7/Wx7pf9GVRUygT8n8Rzw9U4RikJc1f09hFoD63Vj41C2wDupQzuTTXsZm+7/A33X3O8d2wmrH069klVQ9X89TLjT/1vxn8ALUF8jClEDK36qpdKFJ2inL+S/DyGeVp0hXXUZ2VrmNRnEQYEba7LGbrkPPRrOjE/IrZw1Gz8PRMqxAbc2vhlJDF7/vPd3EaDe3nGG9TR+D2rKLat/sfGMQlCXQAUQJiUYd53GDYAk4Giq7pW/CVnpjGU+8bg==
  • Spamdiagnosticoutput: 1:0

Brian Candler writes:

> Anything in /var/log/pscheduler/pscheduler.log other than the
complaint about the failure?


I don't see the exception which abrt showed. I do see several cases of
what look like SQL exceptions:

Dec 12 08:38:56 perfsonar0 journal: ticker INFO Started
Dec 12 08:39:18 perfsonar0 journal: ticker WARNING Queue maintainer got
exception server closed the connection unexpectedly
Dec 12 08:39:18 perfsonar0 journal: ticker WARNING #011This probably
means the server terminated abnormally

This and its variants are normal behavior around startup. As long as they
eventually stop, everything's good. You're not the first to have spotted
this, and I've often thought about catching that and putting something less
dramatic in the logs. The pScheduler services are all pretty robust
internally and are also backed up by systemd's restart features.

--Mark



Archive powered by MHonArc 2.6.19.

Top of Page