OD error message every 10 minutes

Every ten minutes we get the following error for our base server in the od.log:

2010-05-06 13:10:02 IWDeploySock::ReadLineWithLength ERROR: Failed to read length of data buffer from socket.
2010-05-06 13:10:02 IWDeploySock::ReadLine ERROR: Failed to read (-1) bytes of data from socket.
2010-05-06 13:10:02 IWDeploySock::ReadLongLine ERROR: No response data from remote.

I'm sure that it's some bad configuration somewhere but I read through the manual to find something that happened every 10 minutes and couldn't figure it out.

All of the connections to the receivers seem to be up and running.

Any ideas?

Find more posts tagged with

Comments

nipper

run iwodserverstatus

anything of interest ?

Have you restarted OD ? Does the error show before any deployments are invoked ?

ewan

Well I tried to run iwodserverstatus in a loop at around the same time it was dumping the error message. I have received this every time:

OpenDeploy server host: localhost, RMI registry port: 9173
OpenDeploy server is alive.
0 deployments are currently active.

Yes, we have restarted OD multiple times.

If I grep for the error message in the od.log it looks like I have had a few occurrences of this in the past but it started reporting the error every 10 minutes as of 2009-12-03 at 9PM. Hmmm, got to remember what I did ... that might be a problem!

3ChartsAcross.rptdesign

Adam Stoller

Did you do anything with the OD Reporting DB or Scheduling DB?
Are any log files (or .db files) significantly large?

Untitled.png

ewan

To be honest I don't have a clue what happened that day. I tried looking through old emails but didn't find anything useful.

I have turned off event reporting in the odbase.xml file and it made no difference. I didn't make any changes to the scheduling DB that I know and it is still configured to use HypersonicSQL. I don't see any scheduled deployments if I use the admin UI.

We use the -inst parameter on most of our OD deployments so we don't have many large files but we do have a lot (3,922). Our largest log file is just over 37MB.