Interesting observation when using MySQL

General
1

I’m running Orthanc in a Docker container, alongside a MySSQL container that Orthanc is configured to use. I have NOT used the MySQL storage option, so the only information that’s stored in the database is the study metadata etc, not the binaries themselves (they reside on disk, within a volume).

Observing my MySQL container, I see a large number of the following:
[Note] Aborted connection xxxxxx to db (orthancdb), user (orthancuser), host (localhost) : (Got a packet bigger than 'max_allowed_packet' bytes)

Now I know MySQL has a max_allowed_packet, but I find it hard to believe that all of a sudden Orthanc is sending such large packet sizes (the value is set to the default of 4194304).

I would expect this if I were storing the binaries into the database, but I’m not …

Thoughts?

2

Hi Dave,

This is clearly weird. Indeed, the largest data Orthanc is storing is metadata and they should not be that large.

I would advise you to compare the Orthanc logs in verbose mode with the MySQL logs to try to determine what Orthanc actions triggers these messages.

HTH,

Alain.

3

Alain,
I wonder if it’s related to my latest post : Odd MySQL processlist results

Thoughts?

4

It does not seem related …

5

Alain,
From the config (using containers), I can’t see how to set the logging to verbose mode?

6

Hi Dave,

If you are using osimis/orthanc images, simply define VERBOSE_ENABLED=true.

Reference doc.

Best regards,

Alain

7

Just for clarity and prosperity: the use of the API /tools/log-level* is really useful too - the ability to change the logging on the fly is awesome