SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 55985: The error "Too many files are open" is logged when you have clustered SAS® Metadata Servers

DetailsHotfixAboutRate It

When a clustered metadata server node encounters communication errors, it disconnects from the master node. When it attempts to rejoin the cluster, the node can run out of file handles.

If you encounter this issue, the following message is returned in the SASMetadataServer*.log files:

2015-04-21T22:02:41,591 ERROR [00000015] :sas The TCP/IP tcpSockAccept support routine failed with error 24 
(Too many files are open.)

and/or 

2015-04-05T16:23:14,479 INFO  [01331883] 63135:sas- INTERNAL ERROR: Connecting node SASMeta -
Metadata Server has no pIface.

To work around this issue, complete the following steps:

  1. Ensure that the network is functioning and has no errors.
  2. Stop and start the metadata server node that is offline. Use the following command to control the SAS Metadata Server:
    SAS-configuration-directory/Lev1/SASMeta/MetadataServer/MetadataServer.sh options
  3. Use SAS® Management Console to review the state of the cluster:
    • Expand the Metadata Manager folder.
    • Right-click Active Server Properties.
    • Click the Cluster tab.

      Note: If this tab is not visible, you do not have a metadata server cluster.

    • If everything is running well, the tab should display the following:
      State: QUORUM
      Defined nodes=3
      Current nodes=3
    • If any nodes are not running, review the SASMetadataServer*.log files and resolve the issue that is preventing them from running.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Metadata ServerMicrosoft® Windows® for x649.49.49.4 TS1M3
Microsoft Windows 8 Enterprise 32-bit9.49.49.4 TS1M3
Microsoft Windows 8 Enterprise x649.49.49.4 TS1M3
Microsoft Windows 8 Pro 32-bit9.49.49.4 TS1M3
Microsoft Windows 8 Pro x649.49.49.4 TS1M3
Microsoft Windows 8.1 Enterprise 32-bit9.49.49.4 TS1M3
Microsoft Windows 8.1 Enterprise x649.49.49.4 TS1M3
Microsoft Windows 8.1 Pro9.49.49.4 TS1M3
Microsoft Windows 8.1 Pro 32-bit9.49.49.4 TS1M3
Microsoft Windows 95/989.4
Microsoft Windows 2000 Advanced Server9.4
Microsoft Windows 2000 Datacenter Server9.4
Microsoft Windows 2000 Server9.4
Microsoft Windows 2000 Professional9.4
Microsoft Windows NT Workstation9.4
Microsoft Windows Server 2003 Datacenter Edition9.4
Microsoft Windows Server 2003 Enterprise Edition9.4
Microsoft Windows Server 2003 Standard Edition9.4
Microsoft Windows Server 2003 for x649.4
Microsoft Windows Server 20089.49.49.4 TS1M3
Microsoft Windows Server 2008 R29.49.49.4 TS1M3
Microsoft Windows Server 2008 for x649.49.49.4 TS1M3
Microsoft Windows Server 2012 Datacenter9.49.49.4 TS1M3
Microsoft Windows Server 2012 R2 Datacenter9.49.49.4 TS1M3
Microsoft Windows Server 2012 R2 Std9.49.49.4 TS1M3
Microsoft Windows Server 2012 Std9.49.49.4 TS1M3
Microsoft Windows XP Professional9.4
Windows 7 Enterprise 32 bit9.49.49.4 TS1M3
Windows 7 Enterprise x649.49.49.4 TS1M3
Windows 7 Home Premium 32 bit9.49.49.4 TS1M3
Windows 7 Home Premium x649.49.49.4 TS1M3
Windows 7 Professional 32 bit9.49.49.4 TS1M3
Windows 7 Professional x649.49.49.4 TS1M3
Windows 7 Ultimate 32 bit9.49.49.4 TS1M3
Windows 7 Ultimate x649.49.49.4 TS1M3
Windows Millennium Edition (Me)9.4
Windows Vista9.4
Windows Vista for x649.4
64-bit Enabled AIX9.49.49.4 TS1M3
64-bit Enabled Solaris9.49.49.4 TS1M3
HP-UX IPF9.49.49.4 TS1M3
Linux for x649.49.49.4 TS1M3
Solaris for x649.49.49.4 TS1M3
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.