Author Topic: Motion keeps dieing - dcerouter keeps reloading  (Read 509 times)

pw44

  • Addicted
  • *
  • Posts: 653
    • View Profile
Motion keeps dieing - dcerouter keeps reloading
« on: August 26, 2010, 02:22:49 pm »
Hia,
i'm getting troubles with motion wrapper.
Cameras works fine accessed from the browser, but everytime they are added to motion wrapper, the hell starts, with dcerouter reloading, and motion dieing. /etc/init.d/motion restart brings it back to life, but for a short time. dcerouter reloads and motion dies.
I'm not figuring out what is happening. Could someone pass the eyes on this log and tell me what could be wrong?

Code: [Select]
Thu Aug 26 09:12:49 BRT 2010 Restart
========== NEW LOG SECTION ==========
1 08/26/10 09:12:57 264 (spawning-device) Starting... 2
1 08/26/10 09:12:57 264 (spawning-device) Found /usr/pluto/bin/Motion_Wrapper
05 08/26/10 9:12:57.399 Creating child 265 <0xb71ee6c0>
05 08/26/10 9:12:57.399 Note: Device manager has attached a device of type 1916 that this has no custom event handler for.  It will not fire events. <0xb71ee6c0>
05 08/26/10 9:12:57.399 Note: Device manager has attached a device of type 1916 that this has no custom handler for.  This is normal for IR. <0xb71ee6c0>
05 08/26/10 9:12:57.399 Creating child 266 <0xb71ee6c0>
05 08/26/10 9:12:57.399 Note: Device manager has attached a device of type 1916 that this has no custom event handler for.  It will not fire events. <0xb71ee6c0>
05 08/26/10 9:12:57.400 Note: Device manager has attached a device of type 1916 that this has no custom handler for.  This is normal for IR. <0xb71ee6c0>
05 08/26/10 9:12:57.400 Creating child 267 <0xb71ee6c0>
05 08/26/10 9:12:57.400 Note: Device manager has attached a device of type 1916 that this has no custom event handler for.  It will not fire events. <0xb71ee6c0>
05 08/26/10 9:12:57.400 Note: Device manager has attached a device of type 1916 that this has no custom handler for.  This is normal for IR. <0xb71ee6c0>
05 08/26/10 9:12:57.400 Creating child 268 <0xb71ee6c0>
05 08/26/10 9:12:57.400 Note: Device manager has attached a device of type 1916 that this has no custom event handler for.  It will not fire events. <0xb71ee6c0>
05 08/26/10 9:12:57.400 Note: Device manager has attached a device of type 1916 that this has no custom handler for.  This is normal for IR. <0xb71ee6c0>
05 08/26/10 9:13:32.204 Socket::ReceiveData 0x88dd368 failed, bytes left -1 start: 100000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 7 Command_Impl1 Dev #264 <0xb59eab90>
05 08/26/10 9:13:32.205 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #264 <0xb59eab90>
01 08/26/10 9:13:32.205 Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #264 <0xb59eab90>
05 08/26/10 9:13:32.205 Dumping 3 locks <0xb59eab90>
05 08/26/10 9:13:32.205 finished check for exceptions <0xb59eab90>
05 08/26/10 9:13:32.205 finished check for exceptions <0xb59eab90>
05 08/26/10 9:13:32.205 finished check for exceptions <0xb59eab90>
05 08/26/10 9:13:32.205 OL: (0x88dd4b4) (>186) MessageQueue Command_Impl.cpp l:822 time: 9:00:00p (1282824812 s) thread: 3055467408 Rel: Y Got: Y <0xb59eab90>

TIA,

Paulo