NL/ML Converter Errors normal?

3 replies

 

I'm troubleshooting some strange behavior in my NL streaming and am seeing an awful lot of these errors showing up in the logs of my NL/ML converters.

I suspect that one (or both) of the messages below could possibly be normal and could represent B&O servers failing to respond to the now end-of-life converters checking for updaters etc.

 

Feb 23 08:59:38 (none) BLC[4779]: [info]:Client disconnected. Message: Socket error. Error: Connection reset by peer, ErrorCode: 104 [Notifier.cpp:233]

Feb 23 08:59:38 (none) BLC[4779]: [info]:Dismissing HTTP Response due to errorState [Http.cpp:349]

 

Is anyone else seeing a lot of these or is this indicating a more serious condition? 

I can`t believe it`s normal, but same here:

- "Client disconnect..." ....(?!)

Otherwise BLC is running well (configured as A.slave)

Stefan

I, too, have noticed the numerous errors in the logs for all of my 7 converters. I even turned off the automatic firmware update searches, but the errors persist. It's been years since there has been an update to the firmware.

My converters all work well with the exception that some sources cannot be controlled by the app. For example the A.MEM SD card source of the BeoSound 4 does not show the NEXT or PREVIOUS arrow icons on the app. Strange. Still, control is as it should be with the B&O remotes.

or
BeoWorld Gold Membership card
Join BeoWorld

Register to access the forums, reference material, and exclusive member benefits — including our monthly prize draw.

Become a Member

December 2026 Prize Draw

Gold Members Only

As a Gold member you're automatically entered into our exclusive prize draw — your chance to win iconic Bang & Olufsen products. A unique benefit of BeoWorld Gold membership, every draw brings a new opportunity to win something special.