Blame
| 68d6c8 | Anonymous | 2026-04-14 00:10:19 | 1 | # Vip Docs: Important Vip server controls |
| 2 | ||||
| 3 | **Stopping and starting Vip instances** |
|||
| 4 | ||||
| 5 | for all stopping and starting of vip instances you must be in nathans home directory |
|||
| 6 | ||||
| 7 | This stops all instances: |
|||
| 8 | ``` |
|||
| 9 | ./run_vip_instances.sh stop |
|||
| 10 | ``` |
|||
| 11 | ||||
| 12 | This starts n number of instances (18 is the max) |
|||
| 13 | ``` |
|||
| 14 | ./run_vip_instances.sh start <n> |
|||
| 15 | ``` |
|||
| 16 | ||||
| 17 | ||||
| 18 | **Stopping and starting the pixel streaming server** |
|||
| 19 | ||||
| 20 | This stops pixel streaming: |
|||
| 21 | ||||
| 22 | ``` |
|||
| 23 | systemctl stop signalling |
|||
| 24 | ``` |
|||
| 25 | ||||
| 26 | This starts pixel streaming: |
|||
| 27 | ``` |
|||
| 28 | systemctl start signalling |
|||
| 29 | ``` |
|||
| 30 | ||||
| 31 | ||||
| 32 | **Stopping and starting vip-sentinel (the booking system)** |
|||
| 33 | ||||
| 34 | This stops sentinel: |
|||
| 35 | ||||
| 36 | ``` |
|||
| 37 | systemctl stop vip-sentinel |
|||
| 38 | ``` |
|||
| 39 | ||||
| 40 | This starts sentinel: |
|||
| 41 | ``` |
|||
| 42 | systemctl start vip-sentinel |
|||
| 43 | ``` |
|||
| 44 | ||||
| 45 | > [!WARNING] |
|||
| 46 | > BOOT ORDER: From a state of VIP instances and Pixel streaming both being offline, first boot your VIP instances, wait until their activity is stable (i.e. watch in nvtop) and then launch the pixel streaming server. FIRST VIP THEN PIXEL |