SSB services ++---

The SSB is running on the following machines:

• Web services:
  • CMS production: dashboard02 (aka dashb-ssb)
  • ATLAS production: dashboard18 (aka dashb-atlas-ssb)
  • ALICE production: dashb-alice-ssb (load balanced between dashb-virtual03 and dashb-virtual10)
  • LHCb production: dashb-lhcb-ssb (load balanced between dashb-virtual03 and dashb-virtual10)

• Collectors: * CMS : in dashboard09 , siteviewcms and siteviewcmstext. In dashboard03, siteviewdebug (which does the maintenances) * ATLAS: dashboard18 siteviewatlastext and siteviewg_atlas * LHCb and ALICE production: dashboard17

You can see all this in Dashboard Cluster

There is a cronjob in each of the machines running a collector that checks that the services are running. To check that the collectors are running, just do 'dashb-agent-list'. To restart the collectors, '/opt/dashboard/cron/dashbCollectorsSSB.sh'

In case of problems with the CMS collectors: Sometimes I've seen in the Oracle session manager that there are connections from old processes in dashboard09 that lock the collectors. In that case, the best way to proceed is to kill all the session with 'error lock', and restart the collectors.