perfSONAR User Q&A and Other Discussion

[Oleg Moiseichuk <>]

Hi Casey,

Actually the next logins as root never produced the mentioned warning.
I removed the directory using 'abrt-cli remove' as you proposed.
I'll wait till the next 'yum update' and check root login once again.

Thanks for the info.

--
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

30.05.2018 17:03, Casey Russell пишет:
> 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 <http://www.kanren.net>
> phone785-856-9809
> 2029 Becker Drive, Suite 282
> Lawrence, Kansas 66047
> linkedin
> <https://www.linkedin.com/company/92399?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A92399%2Cidx%3A1-1-1%2CtarId%3A1440002635645%2Ctas%3AKanREN>
> twitter <https://twitter.com/TheKanREN> twitter
> <http://www.kanren.net/feed/> need support? 
> <mailto:>
>
>
> On Wed, May 30, 2018 at 4:44 AM, Oleg Moiseichuk 
> <
> <mailto:>>
>  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
>     <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

Attachment: smime.p7s
Description: Криптографическая подпись S/MIME