My /var filesystem run out of space earlier so I've grown it form 2Gb to 3Gb (I can grow it further if needed). Looking in /var/log the three logs debug, syslog and zimbra.log are massive (over 650Mb each) and full of slapd log line sequences like:
Code:
Feb 7 22:58:04 z5 slapd[2921]: conn=8004 op=5132 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15303 SRCH base="" scope=2 deref=0 filter="(&(zimbraDomainName=editeddomain.com.tw)(zimbraDomainType=alias)(zimbraMailStatus=enabled))"
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15303 SRCH attr=zimbraDomainName
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15303 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15304 SRCH base="" scope=2 deref=0 filter="(&(zimbraDomainName=editeddomain.com.tw)(zimbraDomainType=local)(zimbraMailStatus=enabled))"
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15304 SRCH attr=zimbraDomainName
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15304 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15305 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=linhr.tw@editeddomain.com.tw)(zimbraDomainName=linhr.tw@editeddomain.com.tw))(zimbraMailStatus=enabled))"
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15305 SRCH attr=zimbraMailTransport
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15305 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15306 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=editeddomain.com.tw)(zimbraDomainName=editeddomain.com.tw))(zimbraMailStatus=enabled))"
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15306 SRCH attr=zimbraMailTransport
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15306 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15307 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=.com.tw)(zimbraDomainName=.com.tw))(zimbraMailStatus=enabled))"
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15307 SRCH attr=zimbraMailTransport
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15307 SEARCH RESULT tag=101 err=0 nentries=0 text=
Feb 7 22:58:04 z5 slapd[2921]: conn=7975 op=15308 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=.tw)(zimbraDomainName=.tw))(zimbraMailStatus=enabled))"
(I've edited the domain name being referenced in those lines)
I'm guessing that these lines are emminiating from the processing that happens when mail, in this case junk as there is no reason I can think of for .tw addresses to be contacting this server, comes in.
The log file size isn't due to log rotation failing (which is usually the problem in such cases) as the content of the 650+Mb zimbra.log file only covers the last 18 hours.
Is there a safe/easy way to make slapd be less "chatty", or should I just find room to further grow the logical volume that holds /var? This may just be a "on off" anomaly due to an influx of junk, as the previous zimbra.log currently zimbra.log.0) is only 22M large.