silly issue about logs size on my server

[linfant]

hello!
Can you please give me an idea about my silly issue? Sorry to bother you about this but i just struggling on this way to long:

i use zabbix 5.4 with mariadb on bulleye debian virtual server (esxi)
my logs just used to get fatter till they stop the database.
It's something like 25Go of plain text in 10 hours.

this is the solutions i unsuccesfully tried:
- I fixed this variable with max_log inside on 1Go
- i looked at the logs to find a periodic error i could fix (but it just looks like it's on verbose mode)

someone please have already see this problem or have an idea for me?
thanks a lot for reading

[linfant]

most of logs on /var/log/zabbix are like:
1289:20211226:175529.344 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.2'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.x.x.x.x.x.4'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.x.4'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.1.x.x.x.x.x.x.3'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1x.x.x.x.x.6.3'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.1.x.x.x.x.x.x.4'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.x..4'

is there a way to put zabbix off the verbose mode ? It just seems to looks like me and i hate this.

[linfant]

most of logs on /var/log/zabbix are like:
1289:20211226:175529.344 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.2'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.x.x.x.x.x.4'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.x.4'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.1.x.x.x.x.x.x.3'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1x.x.x.x.x.6.3'
1289:20211226:175529.345 In zbx_snmp_translate() OID:'.1.x.x.x.x.x.x.4'
1289:20211226:175529.345 End of zbx_snmp_translate() oid_translated:'.1.x.x.x.x.x..4'

is there a way to put zabbix off the verbose mode ? It just seems to looks like me and i hate this.

[ISiroshtan]

Hey mate

First of all you can try to change the debug level in Zabbix server config file. Default is 'DebugLevel=3' which is '3 - warnings'.

Also, if you use logrotate to rotate Zabbix log files, you can modify it to set a maximum limit on file size and number of rotated files system would keep.

Hope it helps.

[linfant]

it sounds great to me: where can i set the DebugLevel parameter? is it something i can fix on the web interface or do i have to put it on command line on mysql please?

[ISiroshtan]

It's actually in Zabbix server configuration file. Usually at /etc/zabbix/zabbix_server.conf

If you have not heavily modified it, search for a section

### Option: DebugLevel
# Specifies debug level:
# 0 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
# 5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=3

And add 'DebugLevel=3' line after the block with level of logging you want to try.

If you have modified the config file then check if said directive already exists. If not - just add at the end of file. Should work.

P.S. dont forger to restart Zabbix server daemon for changes to take the effect.

[linfant]

oh yeah. You just point it right )
It was like DebugLevel=5
I think i can guess who did it and when we forgot about it hahaha
no matter: you find it, thank you a lot

The fact is i just reboot cause the /dev/sda1 was 98% full, no matter how many file i delete (files locked even if i stop services^^)
I will tell you final result

[linfant]

really works fine now, thank you a lot !!!