VMware Cloud Community
Katie2
Contributor
Contributor

ReportVob() missing 1 required positional argument: 'vobfmt'"

Looked up this error 'Dropping messages due to log stress (qsize = 25000)' but the solution isn't applicable to me. Not sure why I would be getting this issue. I'm running VMware ESXi, 6.5.0, Build 17167537 with vCenter 6.7 Build 17137327. This problem is happening on all 8 of my blades it appears. In VeeamOne the error is "Log daemon has failed for an unexpected reason: ReportVob() missing 1 required positional argument: 'vobfmt'"

Noticed this error in /var/log/.vmsyslogd.err 'Errno 16' but it doesn't make sense to me. I have VMs on this volume and I don't have any issues. /vmfs/volumes/5f6a6fed-93c79f99-74ad-74e6e2a7afe1 is DATASTORE_1 and it has 920GB free out of 2TB and 1.4TB is provisioned.

[Errno 16] Device or resource busy: '/vmfs/volumes/5f6a6fed-93c79f99-74ad-74e6e2a7afe1/scratch/log/syslog.log'

Any thoughts on this before I open a ticket with vmware? Nothing seems to be broken besides this logging. Hoping someone has a quick solution to this issue.


Partial: /var/log/.vmsyslogd.err

TypeError: ReportVob() missing 1 required positional argument: 'vobfmt'
2021-01-28T18:30:41.171Z vmsyslog : CRITICAL] vmsyslogd daemon starting (559129)
2021-01-28T18:30:41.746Z vmsyslog.main : CRITICAL] Dropping messages due to log stress (qsize = 25000)
2021-01-28T18:30:45.223Z vmsyslog.config : CRITICAL] Failed to enable logging of dropped messages
2021-01-28T18:30:49.307Z vmsyslog.loggers.file : ERROR ] Failed to create file logger </vmfs/volumes/5f6a6fed-93c79f99-74ad-74e6e2a7afe1/scratch/log
Traceback (most recent call last):
File "/build/mts/release/bora-17167537/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmsyslog/loggers/file.py", line 68, in __i
File "/build/mts/release/bora-17167537/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmsyslog/vmos/vmkernel.py", line 87, in Op
File "/build/mts/release/bora-17167537/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmsyslog/vmos/vmkernel.py", line 103, in _
File "/build/mts/release/bora-17167537/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/site-packages/vmsyslog/vmos/base.py", line 195, in __ini
OSError: [Errno 16] Device or resource busy: '/vmfs/volumes/5f6a6fed-93c79f99-74ad-74e6e2a7afe1/scratch/log/syslog.log'
2021-01-28T18:30:49.309Z vmsyslog.loggers.file : ERROR ] <syslog> failed to write log, disabling
2021-01-28T18:30:49.310Z vmsyslog : ERROR ] Unhandled exception!

2 Replies
dtceh5
Contributor
Contributor

I am experiencing the exact same issue utilizing the same ESXi version and Build.  No issues with the VMs themselves.  Curious as to what is causing this error.

Reply
0 Kudos
Katie2
Contributor
Contributor

Unfortunately I've not had the time to really invest in troubleshooting it. Since I'm not having any noticeable issues at the moment it's difficult to justify spending time on it. Got put on some very lengthy and time consuming projects.

 

Reply
0 Kudos