I am new to TrueNAS. Just got it all set up and it works great. But the server I have it installed on is showing the following error messages on the monitor connected to the server. The error appears continually, with a few of them appearing every couple of minutes.
Google is a very easy way to find previous problems and then hopefully those lead to a solution.
I am not trying to be mean to you, I am trying to teach you to fish. It is much better if I can teach you how to find solutions quickly vice waiting on someone to read your posting.
Good luck and I hope you solve the issue quickly as it does get annoying when the log fills up with the same message non-stop.
Thanks, I meant to post the version but forgot…tired. Core TrueNAS-13.0-U6.7
I searched Google for a couple of hours but have been unable to determine how to fix it. Being new to TrueNAS (and FreeBSD in general), this is all new territory. I typically live in Windows. Usually when I venture into Linux and such I end up spending hours Googling issues. I just don’t have enough experience there.
If I can’t figure it out I may just ignore it since the NAS seems to be working fine otherwise.
An easy way to search Google is to use unique key words:
“truenas” is good to start with but if the problem is more Linux specific or FreeBSD specific, they you would need to use those as well.
Next add portions of your error message, in your case I used “truenas.local avahi-daemon 1353 - - avahi_normalize_name() failed” and since truenas was already part of the error message, I didn’t need to add it again.
Sometimes it takes a few tries but doing an internet search for anything is better if you can seach on unique words where possible.
If you have given your searching a good try (I typically take 2 days of on/off searching) then ask for help. If it is something you consider urgent, do it sooner. The folks here are very willing to help you out. I wish I could answer your question about the error message, I know I had it for a period of time years ago but I ignored it as it eventually was fixed without my intervention. Nad maybe someone will chime in and toss you some help.
I hear you, same for me when I started. I’ve been doing windows since version 1.0 (brother-in-law worked for Microsoft as a DOS/Windows Tech Support Hotline) so that should tell you that I’m old as dirt. Christopher Columbus and I were running mates. Yea, old.
Yes, I read the link. The issue is I was not understanding what I was reading. Your hint regarding it being another system sending and avahi simply responding was VERY helpful! Thank you! That has helped me to begin understanding better and I will now embark in a different direction to figure this out, starting with looking at my network and the other devices as you suggest. In fact, I have a theory as to what it might be. I really appreciate you.
I isolated the two devices I suspected could be the cause, but they were not the culprit. I plan to do more testing this evening. Question: Do you know if these errors, if they continue to accrue, are eventually going to cause issues …like will the log eventually get so big it causes issues? Or is it benign as far as TrueNAS is concerned? This NAS is going to end up at a completely different location on a completely different network eventually, so I suspect the issue will go away since the offending device won’t be present.
Have not tried that yet…but will this evening. I really appreciate your responses. They gave me enough clue to begin understanding what may be happening.
Liking TrueNAS so far. I decommissioned a HP Micro Server a while back and the little guy was just begging for a new life. Great little box for a NAS.
Yup, that did it. Disabling mDNS solved the issue…or at least stopped the reporting. I will enable it again when the NAS gets to its new home. Thanks again.
