- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: NFS message "FIler owner is not an IDENTIFIER"
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2014 09:37 PM
01-30-2014 09:37 PM
NFS message "FIler owner is not an IDENTIFIER"
Hello all, what is the reason for subject? NFS server throws this message every second and trashes the OPERATOR.LOG. I searched the mounted filesystems and found no obvious culprits (assuming "FIler owner" actually is the "file owner"). It became a bit annoying.
- Tags:
- NFS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2014 10:57 AM
01-31-2014 10:57 AM
Re: NFS message "FIler owner is not an IDENTIFIER"
> [...] NFS server throws this message [...]
Which version of _which_ NFS server?
tcpip show version ! Or whatever is appropriate...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2014 09:35 PM
02-02-2014 09:35 PM
Re: NFS message "FIler owner is not an IDENTIFIER"
Oh, sorry.
HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 4
on an HP rx2800 i2 (1.60GHz/5.0MB) running OpenVMS V8.4
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2014 12:04 PM
05-05-2014 12:04 PM
Re: NFS message "FIler owner is not an IDENTIFIER"
We are experiencing this same issue. Our system disks are filling up because the operator.log files are being flooded with OPCOM messages from NFS, all saying "FIler owner is not an IDENTIFIER.". The system then grinds to a halt.
Our research indicates that "Identifier based access" is a new feature in TCP/IP ECO4. We do not use this feature, and do not have the logicial defined mentioned in the release notes:
---------------------------------------------------------------------------
New Features for ECO 4 Updates
---------------------------------------------------------------------------
This section describes the new features of HP TCP/IP Services for
OpenVMS V5.7 ECO 4.
For information about installing and configuring TCP/IP Services,
see the HP TCP/IP Services for OpenVMS Installation and Configuration
guide.
1.1 Network File System Server - Identifier based access
.......
1. When the logical is defined:
$ DEFINE/SYSTEM TCPIP$UCP_LOAD_RESOURCE_ID_PROXY 1
We believe the opcom messages are related to this feature. How can we get rid of them?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2014 11:46 PM
05-05-2014 11:46 PM
Re: NFS message "FIler owner is not an IDENTIFIER"
Gary,
could you post a complete example NFS OPCOM message for this problem ?
Could there be files in the NFS export directories on this system, which are owned by a UIC without an associated identifier, i.e. $ DIR/OWN showing just: filename [x,y]
If so, can you create an identifier name for those UICs ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 05:31 AM
05-06-2014 05:31 AM
Re: NFS message "FIler owner is not an IDENTIFIER"
Hello Volker,
As long as Garry is not here yet, and we have the same problem, I'll try to reply.
The complete message is "FIler owner is not an IDENTIFIER" exactly (leaving out "%%% OPCOM .... Message from user NFS Server on NODEx" header). Mounted directories do not have files owned by the UIC ([x,y]) identifiers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 06:15 AM
05-06-2014 06:15 AM
Re: NFS message "FIler owner is not an IDENTIFIER"
Valentin,
this seems to be a known problem without a solution. Log a request with HP and reference QXCR1001350044
What kind of NFS client systems are accessing this OpenVMS NFS server ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 06:25 AM
05-06-2014 06:25 AM
Re: NFS message "FIler owner is not an IDENTIFIER"
Thank you, Volker. Client system is Suse Linux Enterprise (V11 or so, linux guys are already out to clarify)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 11:46 AM
05-06-2014 11:46 AM
Re: NFS message "FIler owner is not an IDENTIFIER"
Hello,
I am in US Pacific time zone, and been busy on other things this morning.
This is our exact message;
%%%%%%%%%%% OPCOM 6-MAY-2014 14:14:59.14 %%%%%%%%%%% (from node <NODE> at 6-MAY-2014 14:14:59.14)
Message from user NFS Server on <NODE>
FIler owner is not an IDENTIFIER.
What we have done is verify that TCPIP 5.7 ECO 2 does not have this issue, but we don't want to use that version.
I am not sure what you mean by;
If so, can you create an identifier name for those UICs ?
All of our files and directories are owned by accounts that have valid proxies, and the UID/GID's match those on the OEL5 Linux nodes we are using to access the systems. <OEL = Oracle Enterprise Linux >
Thank you, I will follow up with HP.