Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] PID file permission denied

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] PID file permission denied


Chronological Thread 
  • From: Casey Russell <>
  • To: Oleg Moiseichuk <>
  • Cc:
  • Subject: Re: [perfsonar-user] PID file permission denied
  • Date: Wed, 30 May 2018 09:03:40 -0500
  • Ironport-phdr: 9a23:eaTKShfckfXORZzlduNbyrPXlGMj4u6mDksu8pMizoh2WeGdxcW7bR7h7PlgxGXEQZ/co6odzbaO7ua4ASQp2tWoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7Ovr6GpLIj8Swyuu+54Dfbx9HiTahYb5+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYeRWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZTAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v9LlgRgP2hygbNj456GDXhdJ2jKJHuxKquhhzz5fJbI2JKPZye6XQds4YS2VcRMZcTy5OAo28YYUBDOQPIPhWoJXmqlQUsRezHxOhCP/zxjJKgHL9wK000/4mEQHDxAEtAcgBsG/Ko9T1KawcTf21zLLTzTrda/NW3Sr25Y/UfRA7vPGMRqlwftTVyUkrDA7FjU+fqYr/PzyL0OQBqW6b4PR8Ve+2jWMstg9/oj+qxsg2i4nJgJoYylTF9SV/w4Y6O8C3SE99YdK+DJRQsCSaO5NqQsIsQmFopDo6xaMcuZKhYCcKz5EnywbQa/yGb4iI4g/jW/2LLThkg3JlfaqzhxWo/kim0O3zSM+03ExMriVbjtnBsG0G2R/L6sWfVPdw/1ut1DSK2gDd6exLOlw4mK/UJpI93rI9mJ8evljfEiL3nUj7ibGae0o59uWu9u/peK/ppoWGOI9xkgz+Mrohmsi4AekgNwgBRWmb+eCl2L3k/E31XKxGj/IonqTWrZzWP8sbpqm+Aw9a1oYs9QyzACuh0NQdhXUHLVRFdwybj4XxJV3DIez0APW6jlSikzpk3OzKM7juD5nRMnTOnrLscqph50NdzQc+yM5T6p1JBr0ZJfL8QE7xtNjWDh8jNAy0xv7qB8ln1oMDQmKPGbGWMKfWsVKT5eIgOe+MZJULtzb7MfQl4eDhjWMhlV8HYaapxYcXaGy/Hvl+O0WWf2DsgtkaEWcNuAoxVvbqhESfUT5IeXmyRbkx5jU6CIK9EYfDXZ6hjKaA3Ce9Ap1ZeHpGClaSHnf0aYmIQekDZz+PIpwprjtRcrysRMcE0hC1uQ7xy6dkZr7T/wUSvInl2cQz7fyFxj8o8jkhJM2G3nDFdXxvhW4MQ3di17piuldwzlOr0qF+mfFeU9pe+6UaAU8BKZfAwrkiWJjJUQXbc4LMEQ7+Tw==

Oleg,

     My experience with this has been that this problem exists in the 4.02 ISO, but is fixed after a "yum update".  

     However, since the abrt-cli daemon caught it (before the updates were run) it will still report it to you when you log in as root.  Every time you log in as root, until you delete that particular error.  If you (as root) go in and run "abrt-cli list" it will show you each instance of a crash that it has captured.  You can use "abrt-cli rm <directory path>" to clear the crashes one at a time until they're all cleared.  After that, you should stop seeing the crashes that relate to the pid files for pscheduler-ticker and pscheduler-archiver.

     Unfortunately, my experience has also been that iperf and iperf3 continue to crash dozens and dozens of times a week.  Sending me hundreds of emails a month from abrt-cli.  Iperf is not a package that our PerfSONAR developers have any control over, so as far as I know, no amount of patching on their part is going to fix this.  So I have grudgingly disabled abrt-cli on my boxes.  Maybe someone else in the group has a better suggestion for the iperf crashes.  (example below)

reason:         iperf killed by SIGSEGV
cmdline:        iperf -B 192.33.10.254 -s -f b -P 1 -m -p 5272 -t 30
executable:     /usr/bin/iperf
package:        iperf-2.0.10-1.el7
component:      iperf
pid:            31541
pwd:            /




Sincerely,
Casey Russell
Network Engineer
KanREN
phone785-856-9809
2029 Becker Drive, Suite 282
Lawrence, Kansas 66047
linkedin twitter twitter


On Wed, May 30, 2018 at 4:44 AM, Oleg Moiseichuk <> wrote:
Hello.

I met with the error on one of perfSONAR v4.0.2 nodes installed not long ago. Right after "yum update" I connected to this node as a root and got a warning:

-----------------------------------------------------------------------------------
$ sudo -i
[sudo] password for admin:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1526546246
[root@psmall-b-3 ~]# abrt-cli list --since 1526546246
id 637075843e4ee32e98d3afd56f4248e942f6ee3b
reason:         pidfile.py:48:__exit__:OSError: [Errno 13] Permission denied: '/var/run/pscheduler-ticker.pid'
time:           Пн 07 май 2018 16:25:26
cmdline:        /usr/bin/python /usr/libexec/pscheduler/daemons/ticker --daemon --pid-file /var/run/pscheduler-ticker.pid --dsn @/etc/pscheduler/database/database-dsn
package:        pscheduler-server-1.0.2-1.el7.centos
uid:            1000 (pscheduler)
count:          20
Directory:      /var/spool/abrt/Python-2018-05-07-16:25:26-1525

The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
-----------------------------------------------------------------------------------

It seems that exactly the same error was already reported:
https://github.com/perfsonar/toolkit/issues/165
It looks like it hasn't gone away.

I've got 3 more nodes, not updated yet. I can send a word if the same error will be thrown on them or leave them not updated for the debugging purpose.

--
Best regards,
Oleg Moiseichuk,
Engineer of the Department of Network Communications,
UIIP of the National Academy of Sciences of Belarus
Phone: +375 17 294-92-29







Archive powered by MHonArc 2.6.19.

Top of Page