
New Member
•
2 Messages
5268AC errors in system log
In the system log of the 5268AC gateway are these messages that appear every 30 seconds.
Anything I should be concerned about?
Thanks,
Neal
err | Apr 25 18:28:07 | daemon: ustatsd[1923]: Parsing failed for fields [device info] at [ 8659 206110906 296 403796 206110906 800e src=173.194.54.71 dst=xxx.xxx.xxx.xxx sport=443 dport=44018 src=xxx.xxx.xxx.xxx dst=173.194.54.71 sport=44018 dport=443 ] on file: /proc/net/conntrack_dpi |
err | Apr 25 18:27:37 | daemon: ustatsd[1923]: Parsing failed for fields [device info] at [ 8659 206080692 296 403796 206080692 800e src=173.194.54.71 dst=xxx.xxx.xxx.xxx sport=443 dport=44018 src=xxx.xxx.xxx.xxx dst=173.194.54.71 sport=44018 dport=443 ] on file: /proc/net/conntrack_dpi |
err | Apr 25 18:27:07 | daemon: ustatsd[1923]: Parsing failed for fields [device info] at [ 8659 206050688 296 403796 206050688 800e src=173.194.54.71 dst=xxx.xxx.xxx.xxx sport=443 dport=44018 src=xxx.xxx.xxx.xxx dst=173.194.54.71 sport=44018 dport=443 ] on file: /proc/net/conntrack_dpi |
ATTHelp
Community Support
•
221.2K Messages
5 months ago
Hey there @nas135. We'd be happy to help you with your entries in your system log for your 5268AC gateway.
Just to confirm, have you been experiencing any intermittent internet service when you receive these entries? From the logs that you provided it doesn't look like your service is being attacked, but instead it looks like your system could be trying to access a website or server, but it's being blocked.
It doesn't seem to be anything that you should be concerned about as the log isn't showing that your service isn't being attacked.
Please let us know if you have any further questions.
Robert, AT&T Community Specialist
0
0
nas135
New Member
•
2 Messages
5 months ago
It does not appear to cause any connectivity issues.
Based on the name of the daemon (ustatsd), I'm guessing it is gathering statistics every 30 seconds and it is failing.
Thanks,
Neal
0
0
ATTHelp
Community Support
•
221.2K Messages
5 months ago
Thanks for sharing that information with us @nas135.
Please reach back out to us if you ever have any future questions. Thanks for contacting the AT&T Community Forums.
Robert, AT&T Community Specialist
0
0