+ Post New Thread
Results 1 to 3 of 3
  1. #1
    Newbie level 1
    Points: 15, Level: 1

    Join Date
    Nov 2019
    Posts
    1
    Helped
    0 / 0
    Points
    15
    Level
    1

    How to fix Too many open files or Segmentation Fault.

    Here is my situation, while I run a simulation with Virtuoso IC6.1.7-b500.22, the virtuoso would suddenly quit by promoting error in terminal:

    Error while loading shared libraries: libc.so.6: cannot open shared object file: Error 23

    QEventDispatcherUNIXPrivate(): Unable to create thread pipe: Too many open files in system

    Segmentation Fault
    I've tried to modified the linux ulimits, not work for me.
    Could anyone encounter this problem? And is there some solutions to fix this? Or it's just limited by the hardware.
    PS. My server's system is redhat 6.7, and the server is DELL R740.

    •   AltAdvertisement

        
       

  2. #2
    Newbie level 2
    Points: 23, Level: 1

    Join Date
    Nov 2019
    Posts
    2
    Helped
    1 / 1
    Points
    23
    Level
    1

    Re: How to fix Too many open files or Segmentation Fault.

    Quote Originally Posted by yuqi View Post
    Error while loading shared libraries: libc.so.6: cannot open shared object file: Error 23
    This indicates that the system you're trying to run on is very different (different version of the C library) from the one you're trying to run it on. Make sure that whatever software you've downloaded is for your system (RedHat 6.7, it seems?) and not generally for Linux/another version of RedHat.



    •   AltAdvertisement

        
       

  3. #3
    Advanced Member level 5
    Points: 17,798, Level: 32
    Achievements:
    7 years registered

    Join Date
    Nov 2012
    Posts
    3,251
    Helped
    808 / 808
    Points
    17,798
    Level
    32

    Re: How to fix Too many open files or Segmentation Fault.

    I've tried to modified the linux ulimits, not work for me.
    In general, earlier errors are more user-friendly than subsequent errors.

    One single error often produces a cascade; usually the first reported error needs the greatest attention.

    Sometimes if is often useful to see errors in linkers and warnings in compilers.

    Just a general guide.



--[[ ]]--