Reports until 09:02, Monday 08 January 2024
H1 CDS
patrick.thomas@LIGO.ORG - posted 09:02, Monday 08 January 2024 (75242)
Restarted IOC service on h1digivideo3 for FCES IR TRANS B camera
Dave alerted me that this had frozen as indicated by a blue screen on the client. The systemd service status reported:

● pylon-camera-server@H1-VID-CAM-FCES-IR-TRANS-B.service - Basler 2D GigE camera RTP H264 UDP server
     Loaded: loaded (/etc/systemd/system/pylon-camera-server@.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/pylon-camera-server@.service.d
             └─lho.conf
     Active: active (running) since Tue 2023-10-03 10:00:32 PDT; 3 months 3 days ago
   Main PID: 402217 (pylon-camera-se)
      Tasks: 40 (limit: 77094)
     Memory: 114.8M
        CPU: 3w 3d 1h 32min 52.488s
     CGroup: /system.slice/system-pylon\x2dcamera\x2dserver.slice/pylon-camera-server@H1-VID-CAM-FCES-IR-TRANS-B.service
             └─402217 /usr/bin/pylon-camera-server H1-VID-CAM-FCES-IR-TRANS-B.ini

Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Height: 540
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting GevSCPSPacketSize (packet size): 8192
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting GevSCPD (inter-packet delay): 25000
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Starting grabbing.
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting auto exposure: 0
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting exposure time: 200000
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting auto gain: 0
Jan 05 13:11:05 h1digivideo3 pylon-camera-server[402217]: Setting gain: 360
Jan 05 22:33:53 h1digivideo3 pylon-camera-server[402217]: The grab failed.
Jan 05 22:33:53 h1digivideo3 pylon-camera-server[402217]: The buffer was incompletely grabbed. This can be caused by performance problems of the network hardware used, i.e. network adapter, switch, or ethernet

I ran 'service pylon-camera-server@H1-VID-CAM-FCES-IR-TRANS-B restart' and it came back.

This is the first I can recall of this occurring on this new server and code.