extra info for packet_exceeds_max_size about vernemq

[ioolkos]

@nirfr Thanks, I see your point. We probably should get the session state here and get the subscriber_id for logging.

vernemq/apps/vmq_server/src/vmq_ranch.erl

Line 187 in de87dad

lager:warning("session stopped abnormally due to '~p'", [Reason])

Right now, if you cannot conclude state information from one of the logs (console.log/error.log/crash.log) the client information is lost. You can maybe check for this in your log files, but I'll label this as an enhancement.

---

👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

[nirfr]

Thanks
I see this behavior in other logs too. Example:
session stopped abnormally due to '{error,unexpected_message,{error,'no_#_allowed_in_publish'}}'

I'm working in Kubernetes and only have stdout. Are there other logs I can get the client information from?

[mths1]

Here is a patch I wrote some time ago to fix this
https://github.com/mths1/vernemq/tree/feature/print-subscriber-on-log

unfortunately, I did not yet test it to the end...