perfSONAR User Q&A and Other Discussion

[Kashif Mohammad <>]

Hi Trond

I was also having the same problem with Cassandra not talking to other 
components. It looks like that it is a problem with firewall. I disabled 
firewall and its working now.  

Cheers

Kashif



>>>>-----Original Message-----
>>>>From: 
>>>>
>>>>[mailto:]
>>>>Sent: 06 October 2017 08:16
>>>>To: 
>>>>
>>>>Subject: Re: [perfsonar-user] Test results unavailable on dashboard
>>>>
>>>>On Thu, 5 Oct 2017 08:31-0700, Andrew Lake wrote:
>>>>
>>>>> How about anything in any of the files under /var/log/esmond/?
>>>>
>>>>Recent log files for esmond are attached for anyone knowledgeable to
>>>>grok. install.log is empty.
>>>>
>>>>Logging in as root (using su) on one of my nodes revealed:
>>>>
>>>>ABRT has detected 1 problem(s). For more info run: abrt-cli list --since
>>>>1507185892
>>>>
>>>>[root@perfsonar ~]# abrt-cli list --since 1507185892 id
>>>>994a88e8eff586a98ff71a614bcd25756aaf3f68
>>>>reason:         pidfile.py:42:__exit__:OSError: [Errno 13] Permission 
>>>>denied:
>>>>'/var/run/pscheduler-ticker.pid'
>>>>time:           Fri 06 Oct 2017 06:10:25 AM CEST
>>>>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.1.1-1.el7.centos
>>>>uid:            1000 (pscheduler)
>>>>count:          8
>>>>Directory:      /var/spool/abrt/Python-2017-10-06-06:10:25-1639
>>>>
>>>>The Autoreporting feature is disabled. Please consider enabling it by
>>>>issuing 'abrt-auto-reporting enabled' as a user with root privileges
>>>>
>>>>[root@perfsonar ~]# ll /var/run/pscheduler-ticker.pid
>>>>-rw-r--r-- 1 pscheduler pscheduler 4 Oct  6 06:13 /var/run/pscheduler-
>>>>ticker.pid [root@perfsonar ~]# ll /var/run lrwxrwxrwx. 1 root root 6 Oct  
>>>>4
>>>>15:58 /var/run -> ../run [root@perfsonar ~]# ll -d /run drwxr-xr-x 35 root
>>>>root 1280 Oct  6 08:03 /run [root@perfsonar ~]#
>>>>
>>>>> Also maybe be worth just trying a restart of cassandra: systemctl
>>>>> restart cassandra
>>>>
>>>>I have done that to no avail.
>>>>
>>>>It seems all processes are up & running, yet they are not able to talk to 
>>>>one
>>>>another.
>>>>
>>>>--
>>>>Trond.