Error found in monitor logs

[RICK L. PRITCHETT]

We are seeing the below error in the monitor daemon logs.  Curious if anyone else has come across this in their logs and if they were able to find the reason why.

Invalid command length (>= 8192).  Closing connection 0x2d034b0.

Topic

[RICK L. PRITCHETT]

We are seeing the below error in the monitor daemon logs.  Curious if anyone else has come across this in their logs and if they were able to find the reason why.

Invalid command length (>= 8192).  Closing connection 0x2d034b0.

Cloverleaf 6.2

OS Linux 3.10

[RICK L. PRITCHETT]

We are seeing the below error in the monitor daemon logs.  Curious if anyone else has come across this in their logs and if they were able to find the reason why.

Invalid command length (>= 8192).  Closing connection 0x2d034b0.

Cloverleaf 6.2

OS Linux Centos 7 kernel 3.10

[Paul Stein]

What is the ulimit associated to the hci user in Linux?

Command to use: ulimit -u

[RICK L. PRITCHETT]

When I get that command I get 4096.

[RICK L. PRITCHETT]

RICK L. PRITCHETT wrote:

When I run that command I get 4096.

[Paul Stein]

Never mind – 8192 is typically a value set for ulimit thresholds, but irrelevant in this case.

8192 is also a message priority in the engine. Any custom procs that control message priority or perhaps a resend that was done from the GUI where an incorrect message priority was set?

[Charlie Bursell]

8192 is the maximum line limit in Windows.  I don’t if that would have any meaning here.  Are there any surrounding entries in the log?

[RICK L. PRITCHETT]

HI Charlie. Here is as it appears in the log.

[cmd :cmd :ERR /0:_hcimonitord_:01/11/2023 16:10:01] Invalid command length (>= 8192).  Closing connection 0x2d02000.

[cmd :cmd :WARN/0:_hcimonitord_:01/11/2023 16:25:25] alerts client 0x2bd6fe0

[cmd :cmd :WARN/0:_hcimonitord_:01/11/2023 16:25:25] eonotify client 0x2bd6fe0

[aler:aler:WARN/0:_hcimonitord_:01/11/2023 16:25:25] All fields in WINDOW key are taken as ‘*’

[cmd :cmd :WARN/0:_hcimonitord_:01/11/2023 16:25:25] mdstatus client 0x2bd6fe0

[aler:aler:WARN/0:_hcimonitord_:01/11/2023 16:25:27] Sending client 0x2bd6fe0 mdstatus: mdstatus 0

[cmd :cmd :ERR /0:_hcimonitord_:01/11/2023 16:50:01] Invalid command length (>= 8192).  Closing connection 0x2d0ba70.

[cmd :cmd :ERR /0:_hcimonitord_:01/11/2023 16:50:02] Invalid command length (>= 8192).  Closing connection 0x2d31590.

[RICK L. PRITCHETT]

More from the main daemon log.

[aler:aler:INFO/0:_hcimonitord_:11/17/2022 11:23:11] New alert ID: #20

[aler:aler:INFO/0:_hcimonitord_:11/17/2022 11:23:11] New alert def:

[aler:aler:INFO/0:_hcimonitord_:–/–/—- –:–:–] {VALUE mdstatus} {SOURCE {notify}} {MODE actual} {WITH -1} {COMP none} {FOR once} {ACTION cascade} {WINDOW {* * * * * *}}

[cmd :cmd :WARN/0:_hcimonitord_:11/17/2022 11:23:11] mdstatus client 0x2d01690

[dbi :dbi :WARN/0:_hcimonitord_:11/17/2022 11:23:12] Double allocation of DTD

[aler:aler:WARN/0:_hcimonitord_:11/17/2022 11:23:12] Sending client 0x2d01690 mdstatus: mdstatus 0

[cmd :cmd :INFO/0:_hcimonitord_:11/17/2022 11:27:29] Received command: ” on connection 0x2d034c0

[cmd :cmd :INFO/0:_hcimonitord_:11/17/2022 11:27:29] Cmd null in ”

[cmd :cmd :ERR /0:_hcimonitord_:11/17/2022 11:27:29] Invalid command length (>= 8192).  Closing connection 0x2d034c0.

[aler:aler:INFO/0:_hcimonitord_:11/17/2022 11:27:29] Removing alerts and wants for connection 0x2d034c0

[cmd :cmd :INFO/0:_hcimonitord_:11/17/2022 11:27:29] Received command: ” on connection 0x2d034c0

[cmd :cmd :INFO/0:_hcimonitord_:11/17/2022 11:27:29] Cmd null in ”

[cmd :cmd :ERR /0:_hcimonitord_:11/17/2022 11:27:29] Invalid command length (>= 8192).  Closing connection 0x2d034c0.

[aler:aler:INFO/0:_hcimonitord_:11/17/2022 11:27:29] Removing alerts and wants for connection 0x2d034c0

[cmd :cmd :INFO/0:_hcimonitord_:11/17/2022 11:27:38] Received command: ” on connection 0x2d034c0

 

[Charlie Bursell]

Looks like something wrong in Alerts or Netconfig.    Try this:

Temporarily replace your Alerts file with an empty one and try it.  If you still have the error try replacing the NetConfig with an empty one and try it.  Maybe you can pin point which file and go from there.

Be sure to keep backups of your files so you can put back as before.  You can find empty Alerts and NetConfig files to copy  in $HCIROOT/siteProto directory.

[Author]

Replies