CQCRemVSrv errors in the logs

[bbrendon]

I'm getting these errors every about 2 minutes in the logs. It seems to be about 1:30 to 2:30 between log entries. Its not exact.

I have no clients open and there is nothing connected to the CQCRemVSrv process according to resource monitor.

Based on google research, I'm guessing something in CQC went corrupt?

Code:

Seq#212740 - 07/10 18:36:45-cqc,CQCRemVSrv,CQCRemVSrvWThr4
{
    CIDSock,CIDSock_StreamSocket.cpp.692,Failed/Not All Data Read,Error:5014/0/0
    Could not read or write all requested bytes
}
Seq#212741 - 07/10 18:36:45-cqc,CQCRemVSrv,CQCRemVSrvWThr4
{
    CQCRemVSrv,CQCRemVSrv_WorkerThread.cpp.813,Failed/App Status
    An exception occured in worker thread 3
}
Seq#212742 - 07/10 18:36:45-cqc,CQCRemVSrv,CQCRemVSrvWImgThr4
{
    CIDSock,CIDSock_StreamSocket.cpp.692,Failed/Not All Data Read,Error:5014/0/0
    Could not read or write all requested bytes
}
Seq#212743 - 07/10 18:36:45-cqc,CQCRemVSrv,CQCRemVSrvWImgThr4
{
    CQCRemVSrv,CQCRemVSrv_ThisFacility2.cpp.994,Failed/App Status
    An exception occured in the image download thread
}

If someone cares, here is a full logdump.
https://www.dropbox.com/s/0w31p8lnh266v2...712_050000

[Dean Roddey]

You couldn't possibly get there unless something connected to the RIVA server's port. Because it requires that the listener socket get a connection, create a socket, and pass it on to the worker thread.

Do you have anything in your network that is scanning ports? That would cause it, because it would just connect to the port but wouldn't send anything so the worker thread just fails to read an initial incoming packet and gives up again.

[bbrendon]

Ahhhh.... Yes.

In an attempt to monitor CQC's behavior I've setup our monitoring system at work for all of the CQC ports. I just does a TCP connect and disconnect and logs success/failure.

Oh well, I guess I'll just have to deal with the bogus errors.

Thanks.