Author Topic: "Badly formed message" - how to track where does it come from ?  (Read 857 times)

bulek

  • Administrator
  • wants to work for LinuxMCE
  • *****
  • Posts: 889
  • Living with LMCE
    • View Profile
Hi,

I get occasionally these in DCERouter.log. I assume this is empty message, but would like to track from where does it come from ....

Quote
07      03/20/09 19:51:36.661           Received Message from 27 (Bluetooth Dongle / Living Room/Family Room) to -1001 (unknown / ), type 2 id 4 Event:Mobile orbiter detected, retry none, parameters: <0x741c5b90>
07      03/20/09 19:51:36.661             Parameter 5(Mac Address): 00:16:4E:DA:12:03 <0x741c5b90>
07      03/20/09 19:51:36.661             Parameter 6(Signal Strength): 0 <0x741c5b90>
07      03/20/09 19:51:36.661             Parameter 7(ID): Nokia N70 robi <0x741c5b90>
07      03/20/09 19:51:36.983           Event #65 has no handlers <0xae437b90>
07      03/20/09 19:51:36.983           Received Message from 16 (HAL / Living Room/Family Room) to -1001 (unknown / ), type 2 id 65 Event:Device Detected, retry none, parameters: <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 5(Mac Address):  <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 13(Text):  <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 28(IP Address):  <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 49(PK_DeviceTemplate): 0 <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 51(VendorModelID): ffffffff <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 52(PK_CommMethod): 4 <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 53(PK_PnpProtocol): 0 <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 54(PNP Serial Number): /org/freedesktop/Hal/devices/usb_device_a12_1_noserial_if0 <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 55(DeviceData):  <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 56(Category): bluetooth_hci <0xae437b90>
07      03/20/09 19:51:36.983             Parameter 59(Signature): 16,HAL <0xae437b90>
08      03/20/09 19:51:37.919           Received Message from 16 (HAL / Living Room/Family Room) to Main OnScreen Orbiter(20),Cisco 7970 Orbiter(62),Cisco 7970 Orbiter(722),Cisco 7970 Orbiter(761), type 1 id  809 Command:Display Alert, retry none, parameters: <0x965fab90>
08      03/20/09 19:51:37.919             Parameter 9(Text): 492784 Done with new device bluetooth_hci Added: Bluetooth Dongle <0x965fab90>
08      03/20/09 19:51:37.919             Parameter 70(Tokens): pnp_492784 <0x965fab90>
08      03/20/09 19:51:37.919             Parameter 182(Timeout): 2 <0x965fab90>
08      03/20/09 19:51:37.919             Parameter 251(Interruption): 2 <0x965fab90>
01      03/20/09 19:51:38.011           Badly formed message <0x7e9dab90>
01      03/20/09 19:51:38.012           **** dwStart: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_From: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Group_ID_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwID: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPriority: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwMessage_Type: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Category_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Template: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_bIncludeChildren: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eBroadcastLevel: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eRetry: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_bRelativeToSender: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eExpectedResponse: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           Badly formed message <0x7e9dab90>
01      03/20/09 19:51:38.012           **** dwEnd: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_From: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Group_ID_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwID: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPriority: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwMessage_Type: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Category_To: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_dwPK_Device_Template: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_bIncludeChildren: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eBroadcastLevel: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eRetry: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_bRelativeToSender: 0 <0x7e9dab90>
01      03/20/09 19:51:38.012           **** m_eExpectedResponse: 0 <0x7e9dab90>
07      03/20/09 19:51:41.855           Event #25 has no handlers <0x7e9dab90>
01      03/20/09 19:51:41.855           Climate_Plugin: EVENT_Temperature_Changed_CONST ! <0x7e9dab90>
07      03/20/09 19:51:43.171           Event #66 has no handlers <0xae437b90>

Any advice how to track this one ?

Thanks in advance,

regards,

Bulek.
Thanks in advance,

regards,

Bulek.