"Invalid Header" Filling Up Log

[Brosif_My_Nif]

Code:

Sep 20 22:47:01 freenas afpd[3188]: dsi_tcp_open: invalid header
Sep 20 22:52:01 freenas afpd[3253]: dsi_tcp_open: invalid header
Sep 20 22:57:01 freenas afpd[3380]: dsi_tcp_open: invalid header
Sep 20 23:02:01 freenas afpd[3547]: dsi_tcp_open: invalid header

The messages above are filling up my Log. I have researched these forums and the web for a while now, and have yet to come to an answer.

Is this a bug in 8.3.0? I don't remember exactly when it started but I would like to fix this problem. Possibly when I moved from 8.2.0 to 8.3.0 BETA1? I really am not sure. I do know that if I turn off AFP in my control services, these messages will not generate, but I have a mixture of MAC's and Windows machines on my network so I would like to keep AFP available.

I have upgraded my pools to v28 and I am currently running 8.3.0 BETA3.

Any help someone can offer, would be greatly appreciated. Thank you for your time.

 

[ben]

Disclaimer: There is no official BETA3 at this time, so you're running one of two pre-BETA3 releases. That said, none of the known bugs in those versions pertain to AFP directly, but watch out for NFS issues, and update immediately when BETA3 actually comes out.

FYI OSX supports SMB/CIFS as well, so if you have a heterogeneous network that's a good choice.

As for troubleshooting... perhaps one device on the network is the source of this problem? Can you temporarily disconnect your AFP clients one at a time and see if one of them makes the problem go away?

 

[Brosif_My_Nif]

Ben,

Thanks for replying. I will make sure to upgrade to the official BETA 3 when it is officially announced.

To test your theory, I shut down every computer on my network except my Windows 7 machine. I am still receiving the "Invalid Header". Are there any other recommendations you can think of trying to diagnose this problem?

Thank you for your time.

 

[ben]

Sorry, that a was a total shot in the dark. I don't use AFP, personally. The typical thing to do would be roll back to a saved config from before the problem happened, but since you don't know... not sure what to say. You could factory-reset the box, but that's obviously not an optimal solution. And the last possible answer is to abandon AFP for CIFS or NFS - is there something binding you to AFP in particular?

 

[Brosif_My_Nif]

Last night I did a complete re-install using an ISO of 8.3.0 BETA2. After auto-importing the pools and re-creating the shares, the same problem cropped up again. This was never a problem until I made the jump from 8.0.4 to 8.3.0.

I then installed two blank, spare hard drives to create a "Test" pool that I could mess around with. Created share, copied a few files onto it, and bam, "invalid header".

The only thing I can think of trying to do is re-install OSX on one of the MAC's, wipe out my FreeNAS box, create a new "Test" pool and see if the problem comes back again. If it comes back after doing all that, I will just give up on AFP.

The only thing that was keeping me tied to AFP was that it seemed to be a little faster on the MAC's when transferring files than CIFS did. I may just toss out AFP and switch over to CIFS or NFS. The trouble isn't worth it.

 

[ben]

The fact that it came up in 8.3.0 is troubling, but I don't know how to diagnose it further, since you can't roll back to 8.2.0 with an upgraded zpool. Unless you want to use those spare drives of yours to make absolutely sure that the version upgrade caused it. If you can do that, this is probably worth filing as a bug, otherwise there are still too many variables (some network configuration could have changed concurrently, for example.)

 

[yaneurabeya]

tcpdump it. Might be a configuration issue or another random software bug. Too bad OSX seems to be a second tier client platform..

 

[Brosif_My_Nif]

I hate to resurrect this old thread, but I am still experiencing this problem for almost a year and a half. I'm currently running the newest version (FreeNAS-9.2.0-RELEASE-x64). Has anyone been able to discover the root cause of AFP's "Invalid Header" error? If I turn off the AFP service, this error will not appear. Any assistance anyone can offer would be greatly appreciated.

 

[dlavigne]

You could create a ticket at bugs.freenas.org to see if the issue is resolvable. If you do, post the issue number here.

 

[Yatti420]

Have you tried a clean setup of FreeNAS with clean configuration? Is one of the mac clients sending invalid headers?

 

[Brosif_My_Nif]

I will do a clean install of 9.2.0 and then try it with a couple new Mac's to see what happens and report back.

Sent from my SCH-I535 using Tapatalk

 

[harlan]

https://bugs.freenas.org/issues/6238