CentOS 6.6; java 7: libjli.so cannot be found












0















Background



I have written a Java program to capture network packets. The code uses a wrapper API around libpcap and works nicely - as long as I run the program via sudo.



I am now trying to figure out how to set up things so that I can run the program as a "regular" user. Ultimately, it will be run on a system where I do not have sudo privilege.



After some investigation, a possible solution has been found that involves setting capabilities that provide privileged access in a specific way. Part of this involves setting the capabilities CAP_NET_RAW and CAP_NET_ADMIN to ei (e.g. sudo setcap 'CAP_NET_RAW=ei CAP_NET_ADMIN=ei' program).



The Problem



So, I have done this for the java command on my system. Unfortunately, this has created a problem (which has been asked about by many in various forums) where when java is invoked, the following message is displayed:




java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory




This library does indeed exist and shows up in the list of libraries for the java command.




$ sudo find / -name libjli.so -print
/opt/jdk1.7.0_79/lib/amd64/jli/libjli.so
/opt/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
/usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so
/usr/java/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/lib/amd64/jli/libjli.so
/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/jli/libjli.so



$ which java
/usr/bin/java



$ ls -l /usr/bin/java
lrwxrwxrwx. 1 root root 22 Jun 22 2015 /usr/bin/java -> /etc/alternatives/java



$ ls -l /etc/alternatives/java
lrwxrwxrwx. 1 root root 25 Jun 22 2015 /etc/alternatives/java -> /opt/jdk1.7.0_79/bin/java



$ ls -l /opt/jdk1.7.0_79/bin/java
-rwxr-xr-x. 1 uucp 143 7718 Apr 10 2015 /opt/jdk1.7.0_79/bin/java



$ ldd /usr/bin/java
linux-vdso.so.1 => (0x00007fff3f3fa000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003150c00000)
libjli.so => /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so (0x00007ff56d563000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003151000000)
libc.so.6 => /lib64/libc.so.6 (0x0000003150800000)
/lib64/ld-linux-x86-64.so.2 (0x0000003150400000)




BTW, I am using the Java 7 JDK, not the OpenJDK.



So, what's wrong here? Everything seems to be in place, yet it can't find what it needs. Does the fact that there are two versions of Java on the machine have anything to do it? Is there some other weird situation?



Based on my searches, this problem has been encountered by many, but I couldn't seem to find a reason, nor a solution.



Can anyone help with this?



UPDATE #1



Well, after a little more investigating, it appears that the problem is due to a "feature" in Java. The link below includes another link that gets to heart of the matter.



https://unix.stackexchange.com/a/16670/291340 with the embedded link http://blog.tinola.com/?e=7.



Based upon what I read in these, it would seem that running java with specific capabilities enabled is not allowed. Perhaps that will change at some point, with an improvement to Java security.



If anyone knows about this, or more importantly, knows that a solution has been provided, please comment.










share|improve this question





























    0















    Background



    I have written a Java program to capture network packets. The code uses a wrapper API around libpcap and works nicely - as long as I run the program via sudo.



    I am now trying to figure out how to set up things so that I can run the program as a "regular" user. Ultimately, it will be run on a system where I do not have sudo privilege.



    After some investigation, a possible solution has been found that involves setting capabilities that provide privileged access in a specific way. Part of this involves setting the capabilities CAP_NET_RAW and CAP_NET_ADMIN to ei (e.g. sudo setcap 'CAP_NET_RAW=ei CAP_NET_ADMIN=ei' program).



    The Problem



    So, I have done this for the java command on my system. Unfortunately, this has created a problem (which has been asked about by many in various forums) where when java is invoked, the following message is displayed:




    java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory




    This library does indeed exist and shows up in the list of libraries for the java command.




    $ sudo find / -name libjli.so -print
    /opt/jdk1.7.0_79/lib/amd64/jli/libjli.so
    /opt/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
    /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so
    /usr/java/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
    /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/lib/amd64/jli/libjli.so
    /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/jli/libjli.so



    $ which java
    /usr/bin/java



    $ ls -l /usr/bin/java
    lrwxrwxrwx. 1 root root 22 Jun 22 2015 /usr/bin/java -> /etc/alternatives/java



    $ ls -l /etc/alternatives/java
    lrwxrwxrwx. 1 root root 25 Jun 22 2015 /etc/alternatives/java -> /opt/jdk1.7.0_79/bin/java



    $ ls -l /opt/jdk1.7.0_79/bin/java
    -rwxr-xr-x. 1 uucp 143 7718 Apr 10 2015 /opt/jdk1.7.0_79/bin/java



    $ ldd /usr/bin/java
    linux-vdso.so.1 => (0x00007fff3f3fa000)
    libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003150c00000)
    libjli.so => /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so (0x00007ff56d563000)
    libdl.so.2 => /lib64/libdl.so.2 (0x0000003151000000)
    libc.so.6 => /lib64/libc.so.6 (0x0000003150800000)
    /lib64/ld-linux-x86-64.so.2 (0x0000003150400000)




    BTW, I am using the Java 7 JDK, not the OpenJDK.



    So, what's wrong here? Everything seems to be in place, yet it can't find what it needs. Does the fact that there are two versions of Java on the machine have anything to do it? Is there some other weird situation?



    Based on my searches, this problem has been encountered by many, but I couldn't seem to find a reason, nor a solution.



    Can anyone help with this?



    UPDATE #1



    Well, after a little more investigating, it appears that the problem is due to a "feature" in Java. The link below includes another link that gets to heart of the matter.



    https://unix.stackexchange.com/a/16670/291340 with the embedded link http://blog.tinola.com/?e=7.



    Based upon what I read in these, it would seem that running java with specific capabilities enabled is not allowed. Perhaps that will change at some point, with an improvement to Java security.



    If anyone knows about this, or more importantly, knows that a solution has been provided, please comment.










    share|improve this question



























      0












      0








      0








      Background



      I have written a Java program to capture network packets. The code uses a wrapper API around libpcap and works nicely - as long as I run the program via sudo.



      I am now trying to figure out how to set up things so that I can run the program as a "regular" user. Ultimately, it will be run on a system where I do not have sudo privilege.



      After some investigation, a possible solution has been found that involves setting capabilities that provide privileged access in a specific way. Part of this involves setting the capabilities CAP_NET_RAW and CAP_NET_ADMIN to ei (e.g. sudo setcap 'CAP_NET_RAW=ei CAP_NET_ADMIN=ei' program).



      The Problem



      So, I have done this for the java command on my system. Unfortunately, this has created a problem (which has been asked about by many in various forums) where when java is invoked, the following message is displayed:




      java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory




      This library does indeed exist and shows up in the list of libraries for the java command.




      $ sudo find / -name libjli.so -print
      /opt/jdk1.7.0_79/lib/amd64/jli/libjli.so
      /opt/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
      /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so
      /usr/java/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
      /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/lib/amd64/jli/libjli.so
      /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/jli/libjli.so



      $ which java
      /usr/bin/java



      $ ls -l /usr/bin/java
      lrwxrwxrwx. 1 root root 22 Jun 22 2015 /usr/bin/java -> /etc/alternatives/java



      $ ls -l /etc/alternatives/java
      lrwxrwxrwx. 1 root root 25 Jun 22 2015 /etc/alternatives/java -> /opt/jdk1.7.0_79/bin/java



      $ ls -l /opt/jdk1.7.0_79/bin/java
      -rwxr-xr-x. 1 uucp 143 7718 Apr 10 2015 /opt/jdk1.7.0_79/bin/java



      $ ldd /usr/bin/java
      linux-vdso.so.1 => (0x00007fff3f3fa000)
      libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003150c00000)
      libjli.so => /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so (0x00007ff56d563000)
      libdl.so.2 => /lib64/libdl.so.2 (0x0000003151000000)
      libc.so.6 => /lib64/libc.so.6 (0x0000003150800000)
      /lib64/ld-linux-x86-64.so.2 (0x0000003150400000)




      BTW, I am using the Java 7 JDK, not the OpenJDK.



      So, what's wrong here? Everything seems to be in place, yet it can't find what it needs. Does the fact that there are two versions of Java on the machine have anything to do it? Is there some other weird situation?



      Based on my searches, this problem has been encountered by many, but I couldn't seem to find a reason, nor a solution.



      Can anyone help with this?



      UPDATE #1



      Well, after a little more investigating, it appears that the problem is due to a "feature" in Java. The link below includes another link that gets to heart of the matter.



      https://unix.stackexchange.com/a/16670/291340 with the embedded link http://blog.tinola.com/?e=7.



      Based upon what I read in these, it would seem that running java with specific capabilities enabled is not allowed. Perhaps that will change at some point, with an improvement to Java security.



      If anyone knows about this, or more importantly, knows that a solution has been provided, please comment.










      share|improve this question
















      Background



      I have written a Java program to capture network packets. The code uses a wrapper API around libpcap and works nicely - as long as I run the program via sudo.



      I am now trying to figure out how to set up things so that I can run the program as a "regular" user. Ultimately, it will be run on a system where I do not have sudo privilege.



      After some investigation, a possible solution has been found that involves setting capabilities that provide privileged access in a specific way. Part of this involves setting the capabilities CAP_NET_RAW and CAP_NET_ADMIN to ei (e.g. sudo setcap 'CAP_NET_RAW=ei CAP_NET_ADMIN=ei' program).



      The Problem



      So, I have done this for the java command on my system. Unfortunately, this has created a problem (which has been asked about by many in various forums) where when java is invoked, the following message is displayed:




      java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory




      This library does indeed exist and shows up in the list of libraries for the java command.




      $ sudo find / -name libjli.so -print
      /opt/jdk1.7.0_79/lib/amd64/jli/libjli.so
      /opt/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
      /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so
      /usr/java/jdk1.7.0_79/jre/lib/amd64/jli/libjli.so
      /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/lib/amd64/jli/libjli.so
      /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.35.x86_64/jre/lib/amd64/jli/libjli.so



      $ which java
      /usr/bin/java



      $ ls -l /usr/bin/java
      lrwxrwxrwx. 1 root root 22 Jun 22 2015 /usr/bin/java -> /etc/alternatives/java



      $ ls -l /etc/alternatives/java
      lrwxrwxrwx. 1 root root 25 Jun 22 2015 /etc/alternatives/java -> /opt/jdk1.7.0_79/bin/java



      $ ls -l /opt/jdk1.7.0_79/bin/java
      -rwxr-xr-x. 1 uucp 143 7718 Apr 10 2015 /opt/jdk1.7.0_79/bin/java



      $ ldd /usr/bin/java
      linux-vdso.so.1 => (0x00007fff3f3fa000)
      libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003150c00000)
      libjli.so => /usr/java/jdk1.7.0_79/lib/amd64/jli/libjli.so (0x00007ff56d563000)
      libdl.so.2 => /lib64/libdl.so.2 (0x0000003151000000)
      libc.so.6 => /lib64/libc.so.6 (0x0000003150800000)
      /lib64/ld-linux-x86-64.so.2 (0x0000003150400000)




      BTW, I am using the Java 7 JDK, not the OpenJDK.



      So, what's wrong here? Everything seems to be in place, yet it can't find what it needs. Does the fact that there are two versions of Java on the machine have anything to do it? Is there some other weird situation?



      Based on my searches, this problem has been encountered by many, but I couldn't seem to find a reason, nor a solution.



      Can anyone help with this?



      UPDATE #1



      Well, after a little more investigating, it appears that the problem is due to a "feature" in Java. The link below includes another link that gets to heart of the matter.



      https://unix.stackexchange.com/a/16670/291340 with the embedded link http://blog.tinola.com/?e=7.



      Based upon what I read in these, it would seem that running java with specific capabilities enabled is not allowed. Perhaps that will change at some point, with an improvement to Java security.



      If anyone knows about this, or more importantly, knows that a solution has been provided, please comment.







      centos java






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 17 '18 at 18:24









      slm

      255k71538687




      255k71538687










      asked May 17 '18 at 14:10









      Joseph GagnonJoseph Gagnon

      12




      12






















          1 Answer
          1






          active

          oldest

          votes


















          0














          if you are in a chroot environment you need to mount /proc to make java work.



          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so



          Best regards!






          share|improve this answer


























          • Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

            – JigglyNaga
            Sep 26 '18 at 19:02






          • 1





            If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

            – Abraham Macias Paredes
            Sep 28 '18 at 6:18













          • OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

            – JigglyNaga
            Sep 28 '18 at 6:46











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444382%2fcentos-6-6-java-7-libjli-so-cannot-be-found%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          if you are in a chroot environment you need to mount /proc to make java work.



          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so



          Best regards!






          share|improve this answer


























          • Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

            – JigglyNaga
            Sep 26 '18 at 19:02






          • 1





            If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

            – Abraham Macias Paredes
            Sep 28 '18 at 6:18













          • OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

            – JigglyNaga
            Sep 28 '18 at 6:46
















          0














          if you are in a chroot environment you need to mount /proc to make java work.



          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so



          Best regards!






          share|improve this answer


























          • Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

            – JigglyNaga
            Sep 26 '18 at 19:02






          • 1





            If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

            – Abraham Macias Paredes
            Sep 28 '18 at 6:18













          • OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

            – JigglyNaga
            Sep 28 '18 at 6:46














          0












          0








          0







          if you are in a chroot environment you need to mount /proc to make java work.



          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so



          Best regards!






          share|improve this answer















          if you are in a chroot environment you need to mount /proc to make java work.



          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so



          Best regards!







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 1 '18 at 6:18

























          answered Sep 26 '18 at 15:09









          Abraham Macias ParedesAbraham Macias Paredes

          111




          111













          • Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

            – JigglyNaga
            Sep 26 '18 at 19:02






          • 1





            If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

            – Abraham Macias Paredes
            Sep 28 '18 at 6:18













          • OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

            – JigglyNaga
            Sep 28 '18 at 6:46



















          • Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

            – JigglyNaga
            Sep 26 '18 at 19:02






          • 1





            If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

            – Abraham Macias Paredes
            Sep 28 '18 at 6:18













          • OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

            – JigglyNaga
            Sep 28 '18 at 6:46

















          Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

          – JigglyNaga
          Sep 26 '18 at 19:02





          Welcome to U&L! The OP doesn't mention a chroot environment, and mounting /proc shouldn't make a difference to either permissions or locating libraries.

          – JigglyNaga
          Sep 26 '18 at 19:02




          1




          1





          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

          – Abraham Macias Paredes
          Sep 28 '18 at 6:18







          If you use "strace" you will see something like this: readlink("/proc/self/exe", "/usr/lib/jvm/java-8-openjdk-amd6"..., 4096) That means that Java first look at "/proc/self/exe" to know where to look for /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/../lib/amd64/jli/libjli.so. So if there is no /proc it can't find libjli.so. The OP doesn't mention it, but "chroot" is the only reason I know to not finding /proc.

          – Abraham Macias Paredes
          Sep 28 '18 at 6:18















          OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

          – JigglyNaga
          Sep 28 '18 at 6:46





          OK - that explanation would be more useful included as part of your answer (use the edit link), but it still doesn't seem relevant given that the OP already found the cause of the problem (see under "Update").

          – JigglyNaga
          Sep 28 '18 at 6:46


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444382%2fcentos-6-6-java-7-libjli-so-cannot-be-found%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to make a Squid Proxy server?

          第一次世界大戦

          Touch on Surface Book