Overloading logs with INFO level Header(type:b'MSG', chunk_type:b'F', body_size:62, channel:2612142770)

[pavlo-yashchuk]

I create opc client which connects to differents server and after connection if logs turn on I has too much INFO logs like this

and these messages when stopped client

What is it? And how can it be solved?

[AndreasHeine]

what logginglevel do you use?

[pavlo-yashchuk]

But its not solve that)
Or that its normal?

[pavlo-yashchuk]

Hmm

[pavlo-yashchuk]

I see, then I have to give up information logs
:(

[pavlo-yashchuk]

Thanks!

[swamper123]

Well, just because some stuff was logged, it doesn't mean it is a problem or sth. wasn't working (in that case, it would be a log on WARNING or ERROR level). But it is normal, that the INFO level has ... many infos. On DEBUG level you even got more of them.

If you want to know, what happens on INFO-Level on the server, you have to live with it (or fork it and make your own, logger-less version of python-opcua). This is what loggers are made for.

I am not familiar with handling multiple loggers in python (so far), but I bet there are posibilities to turn them off (on own risk of course) or set their levels.

[pavlo-yashchuk]

Thanks!

[oroulet]

ualogger = logging.getLoger("asyncua")
ualogger.setLevel(logging.CRITICAL)

That would make only the ua part of logger silent

[pavlo-yashchuk]

Thanks)