I see that your ASA configures a DHCP pool beginning at 192.168.0.2. And your syslog server is at 192.168.0.3. Is it possible that the ASA has assigned 192.168.0.3 to some device not your syslog server? What happens if you change the configuration of the DHCP pool to begin on some higher address?
That's not really recommended 'cause you may run into high cpu issues. Debug level is only recommended when it is sent to a syslog server or just for troubleshooting purposes.
Anyway, if the issue continues, you can verify the IP address stuff that Rick just mentioned. And if everything is ok but the issue continues, you'd have to run traffic captures to verify if the ASA's sending the logs to the server in question. You can refer to the following link for more info on captures:
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...