DCERouter Absorbing All Resources

[archived]

There might be a very simple answer to this question but being new.....

Fresh install of hybrid setup on an older 1GHZ PIII with 512MB RAM, 160GB HD, standard audio/video, no PVR cards or other input cards other than the network card.

Install runs flawlessly until I reboot for the first time after dropping through the wizard checklist.

After this point, when monitoring the server with TOP, DCERouter (us) and sy absorb 100% of the systems resources, slowly utilizing all of the memory except for approx. 4 MB, then it starts absorbing the swap space unitl it hits about 90%.

No external orbiters or MD are running or accessing the system and there is no work being done on the MD side of the hybrid, such as ripping a DVD, MYTHTV, *, etc.

The DCERouter log file grows faster than I can download it over scp, but I was still able to read a partial download. The log file grows at a monsterous rate, it grew to over 300MB within the first 15 minutes after the reboot when DCERouter took over the system.

Here are the repeating lines that show in log, there is nothing else other than these line repeated infinitely:

01   06/18/05 11:46:47.248      Interval timer  has no time: 
10   06/18/05 11:46:47.248      Timer: next event is  in -1119109607 seconds
10   06/18/05 11:46:47.248      Timer:  firing command group 2566
01   06/18/05 11:46:47.248      Interval timer  has no time: 
10   06/18/05 11:46:47.248      Timer: next event is  in -1119109607 seconds
10   06/18/05 11:46:47.248      Timer:  firing command group 2566


Thanks for any help in advance. I'm sure this is something silly I've done. I have looked for a event/timer/command group called "2566", but being so new to the system, and the extremely slow response of the Admin Web server, I haven't gotten anywhere.

-Lou

[archived]

O.K.,

I figured it out.

Under Advanced | Events there was an "interval" event setup.

I never set this up, so I'm not sure how it got added to the fresh install.

I deleted this event and kill -9'd DCERouter and that seems to have straightened everything out so far.

-Lou

[archived]

Aha, I see the problem  Yeah, an interval timer with no interval specified, at this moment, means a continuously executed event.  Ooops.  We'll fix to log a critical error and ignore it.