perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Winnie,

A reboot is probably easiest, but you should only need to restart 
“regular_testing”. The rest should be fine.

Cheers,
Aaron

> On Feb 2, 2015, at 9:22 AM, Winnie Lacesso 
> <>
>  wrote:
> 
> 
> Dear Perfsonar experts,
> 
> Finally having cleared out all the crufty old broken test stuff,
> root@lcgnetmon>
>  df -kh /; df -i /
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/mapper/vg_lcgnetmon-lv_root
>                      143G   39G   97G  29% /
> Filesystem            Inodes  IUsed   IFree IUse% Mounted on
> /dev/mapper/vg_lcgnetmon-lv_root
>                     9478144 202234 9275910    3% /
> 
> with *no* perfsonar services running at all, ran
> sudo -u perfsonar /opt/perfsonar_ps/mesh_config/bin/generate_configuration 
> --verbose
> & it looks healthy!
> 
> Now according to the startup order in /etc/rc3.d a plan is to start up 
> each service (or a few at a time) & confirm they are 100% ok. The order is
> 
> config_daemon
> cassandra
> oppd
> simple_ls_bootstrap_client 
> ls_cache_daemon
> ls_registration_daemon
> owampd
> traceroute_ma
> traceroute_master
> traceroute_ondemand_mp
> traceroute_scheduler
> mysqld
> postgresql
> perfsonarbuoy_ma
> perfsonarbuoy_owp_collector
> perfsonarbuoy_owp_master
> PingER
> regular_testing
> abrt-ccpp
> abrtd
> abrt-oops
> httpd
> fail2ban
> configure_nic_parameters
> generate_motd
> psb_to_esmond
> 
> There are an awful lot of things to check. :(
> Also there are some crontabs that are disabled that will be enabled last.
> 
> Q to experts: is the above a bad/insane idea?! Advice welcome!
> 
> OTOH might just reboot it & see if it works now....
> 
> Winnie Lacesso / Bristol University Particle Physics Computing Systems
> HH Wills Physics Laboratory, Tyndall Avenue, Bristol, BS8 1TL, UK