We have this error in our custom perl probe log.
Oct 12 15:32:48:429 action_umi_requests: nimSessionRequest - get SID for the probe action_umi_requests
Oct 12 15:32:48:447 action_umi_requests: nimSessionWaitMsg: got error on client session: 0
It's just after the probe starts. The probe then does not have any access for probe callbacks, which we would normally expect to have for code running as a probe on the hub. Anyone seen it before?