In the event Halo application needs to be started or restarted

---

Halo administrators or systems administrators

---

Technology, Halo support

---

n/a

---

1. Log into Halo application server as Halo admin (Halo-adm) user

• Connect to centrexIT VPN (CIT-Meraki-Anyconnect via Cisco Secure Client)

• ssh Halo.adm@10.20.21.11 (enter Halo.adm password when prompted; can use Windows, PowerShell, or WSL terminal/prompt)

• sudo -su root (enter Halo.adm password again when prompted)

2. Shut down Halo UI service

• /f8/sites/centrexit/ui/bin/shutdown.sh

3. Shut down Halo DS service

• /f8/sites/centrexit/ds/bin/shutdown.sh

4. Verify services have halted

• ps -ef | grep f8 (no active services should be listed)

5. Clean up old log files

• cd /f8/sites/centrexit/ui/work/log

• find . -name “app.log*” -type f -mtime +7 -delete

• find . -name “stats.log*” -type f -mtime +7 -delete

• cd /f8/sites/centrexit/ds/work/log

• find . -name “app.log*” -type f -mtime +7 -delete

• find . -name “stats.log*” -type f -mtime +7 -delete

6. Start Halo DS service

• /f8/sites/centrexit/ds/bin/startup.sh

• cd /f8/sites/centrexit/ds/work/log (if not already in directory)

• tail -f app.log

• monitor log activity until it slows/stops, then halt (Control+C)

7. Start Halo UI service

• /f8/sites/centrexit/ui/bin/startup.sh

• cd /f8/sites/centrexit/ds/work/log (if not already in directory)

• tail -f app.log

• monitor log activity until it slows/stops, then halt (Control+C)

8. Verify application is available via UI ((legacy URL removed))

• If subspaces don’t fully load can try reloading the space, otherwise need to repeat cycling of application

---

n/a

---

n/a

---

1. Link to process map.