Highlighted
Absent Member.
Absent Member.
2941 views

AFP OES2 Linux Locking errors

Hello,

after using the new AFP server on Linux for a month now, I think there are some bungs about file locking.

First thing is that if I enable the CROSS_PROTOCOL_LOCKS setting, I'm unable to read any file or folders with brackets [] in their names. The mac says that the already in use an cannot be accessed. The afptcp.log says the afp-deamon is unable to communicate with the ncp server. So I disabled this.

But shortly users complained about accessing some files. And it's true that some files in some folders are unaccessible from the mac. The error seems to be on the folder, cause if one is affected it's impossible to read any file in it. If I try to copy a file from a affected folder, the mac reports error -50 unknown. The afp server log reports:

Jan 25 11:34:44 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:46 obelix afptcpd[12018]:
Jan 25 11:34:46 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:46 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:46 obelix afptcpd[12018]:
Jan 25 11:34:46 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:47 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:47 obelix afptcpd[12018]:
Jan 25 11:34:47 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:47 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:47 obelix afptcpd[12018]:
Jan 25 11:34:47 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:48 obelix afptcpd[12018]:
Jan 25 11:34:48 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:48 obelix afptcpd[12018]:
Jan 25 11:34:48 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork

Any ideas? Are there any error free Linux AFP servers out there?

Quirin Pasquay
Labels (1)
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Re: AFP OES2 Linux Locking errors

Quirin Pasquay;1722184 wrote:
Hello,

after using the new AFP server on Linux for a month now, I think there are some bungs about file locking.

First thing is that if I enable the CROSS_PROTOCOL_LOCKS setting, I'm unable to read any file or folders with brackets [] in their names. The mac says that the already in use an cannot be accessed. The afptcp.log says the afp-deamon is unable to communicate with the ncp server. So I disabled this.

But shortly users complained about accessing some files. And it's true that some files in some folders are unaccessible from the mac. The error seems to be on the folder, cause if one is affected it's impossible to read any file in it. If I try to copy a file from a affected folder, the mac reports error -50 unknown. The afp server log reports:

Jan 25 11:34:44 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: FPEnumerate returning ERROR (4FB7) at 5
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:45 obelix afptcpd[12018]:
Jan 25 11:34:45 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:45 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:46 obelix afptcpd[12018]:
Jan 25 11:34:46 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:46 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:46 obelix afptcpd[12018]:
Jan 25 11:34:46 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:47 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:47 obelix afptcpd[12018]:
Jan 25 11:34:47 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:47 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:47 obelix afptcpd[12018]:
Jan 25 11:34:47 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:48 obelix afptcpd[12018]:
Jan 25 11:34:48 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork
Jan 25 11:34:48 obelix afptcpd[12018]:
Jan 25 11:34:48 obelix afptcpd[12018]: [ERROR] Failed to open fork
Jan 25 11:34:48 obelix afptcpd[12018]: From FPOpenFork

Any ideas? Are there any error free Linux AFP servers out there?

Quirin Pasquay


Similar kind of problem will come if the file/directory has '+' or '-' symbol in its name. A bug(bug 460142) is raised on this issue.This has been fixed from NCP side. As part of this fix they have removed the extra validation, which will now allow these characters to be part of file/folder.But this is patch is yet to be released.Mean while you can download this patch from bugzilla for your testing.

Incase of CPL disable case, I would prefer you to 'restart' the afp service and start fresh copying the new files/folders instead of 'reloading' the service and working on intermediatery files/folders which are created during CPL enabled. I have done this fresh testing with CPL disabled. Its working fine and there are no access issues.

Try to install the patch incase if you want to work with CPL enabled. This will defenitely address the problem that you are facing now.

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: AFP OES2 Linux Locking errors

Hi,

kthemantha wrote:
> But this is patch is yet to be released.Mean while you can
> download this patch from bugzilla for your testing.


Customers cannot access OES bugs in bugzilla.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: AFP OES2 Linux Locking errors

Hello,

I've found a way to make the affected folders working for the mac:
1. Rename the folder to a temporary name
2. Restart the afp service
3. Rename the folder to its original name

I'm unsure, if the affected folders where created before the CPL was disabled.

Is there a chance to get a beta release of the patch?

Quirin Pasquay
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: AFP OES2 Linux Locking errors

Hi,

Quirin Pasquay wrote:
>
> Hello,
>
> I've found a way to make the affected folders working for the mac:
> 1. Rename the folder to a temporary name
> 2. Restart the afp service
> 3. Rename the folder to its original name
>
> I'm unsure, if the affected folders where created before the CPL was disabled.
>
> Is there a chance to get a beta release of the patch?


Assuming you're on maintenance, the official way is to open a SR with
Novel directly, and cite the bugzilla number kthemantha mentioned, and
ask if you can get the patch.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: AFP OES2 Linux Locking errors

I opened an SR and requested bug fix 460142. I have CPL turned on and I can now save, open and delete files and folders with + - [ and ] in the names. Still can't use / or \ (yes our mac users put these in file/folder names on Netware.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.