AlfrescoLabs / alfresco-environment-validation

Automatically exported from code.google.com/p/alfresco-environment-validation
2 stars 2 forks source link

liblibsigar-x86_64-linux.so do not exist #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Running:

./evt.sh -vv -t oracle -h 192.168.1.1 -r 1521 -d alfrdb -l alfresco -p alfresco

Not work and error display:

----

1 [main] DEBUG Sigar  - liblibsigar-x86_64-linux.so: 
liblibsigar-x86_64-linux.so: no se puede abrir el fichero del objeto 
compartido: No existe el fichero o el directorio
org.hyperic.sigar.SigarException: liblibsigar-x86_64-linux.so: 
liblibsigar-x86_64-linux.so: no se puede abrir el fichero del objeto 
compartido: No existe el fichero o el directorio
   at org.hyperic.sigar.Sigar.loadLibrary(Sigar.java:172)
   at org.hyperic.sigar.Sigar.<clinit>(Sigar.java:100)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at org.alfresco.extension.environment.validation.AbstractValidator.<clinit>(AbstractValidator.java:76)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at org.alfresco.extension.environment.validation.validators.AllValidators.<clinit>(AllValidators.java:43)
   at java.lang.Class.initializeClass(libgcj.so.7rh)
   at EVT.main(EVT.java:107)

[...]

Validating Operating System
  OS                    : Linux .......................................PASS
  Distribution          : SuSE 5 ......................................WARN!
    Reason              : Unsupported SuSE version
    Ramification        : Alfresco may function sufficiently well for development purposes but must not be used for production
    Remedy              : Install SuSE 11
    For more information: http://www.novell.com/linux/

  OS Architecture       : Exception in thread "main" java.lang.UnsatisfiedLinkError: gather
   at org.hyperic.sigar.OperatingSystem.getInstance(OperatingSystem.java:92)
   at org.alfresco.extension.environment.validation.validators.OSValidator.validateArchitecture(OSValidator.java:294)
   at org.alfresco.extension.environment.validation.validators.OSValidator.validate(OSValidator.java:100)
   at org.alfresco.extension.environment.validation.validators.AllValidators.validate(AllValidators.java:59)
   at EVT.main(EVT.java:107)

----

More information:

cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

uname -a
Linux griddm01 2.6.18-238.9.1.el5 #1 SMP Fri Mar 18 12:42:39 EDT 2011 x86_64 
x86_64 x86_64 GNU/Linux

ls lib/
alfresco33-environment-validation-0.9.jar  libsigar-pa-hpux-11.sl       
libsigar-universal64-macosx.dylib   ojdbc5-11.2.0.2.0.jar
db2jcc-9.7FP3a.jar                         libsigar-ppc64-aix-5.so      
libsigar-universal-macosx.dylib     postgresql-8.4-701.jdbc4.jar
jtds-1.2.4.jar                             libsigar-ppc64-linux.so      
libsigar-x86-freebsd-5.so           sigar-amd64-winnt.dll
libsigar-amd64-freebsd-6.so                libsigar-ppc-aix-5.so        
libsigar-x86-freebsd-6.so           sigar.jar
libsigar-amd64-linux.so                    libsigar-ppc-linux.so        
libsigar-x86-linux.so               sigar-x86-winnt.dll
libsigar-amd64-solaris.so                  libsigar-s390x-linux.so      
libsigar-x86-solaris.so             sigar-x86-winnt.lib
libsigar-ia64-hpux-11.sl                   libsigar-sparc64-solaris.so  
log4j.jar
libsigar-ia64-linux.so                     libsigar-sparc-solaris.so    
mysql-connector-java-5.1.7-bin.jar

...the liblibsigar-x86_64-linux.so do not exist.

Original issue reported on code.google.com by fegor@fegor.com on 1 Jun 2011 at 3:56

GoogleCodeExporter commented 9 years ago
This appears to be a defect in Hyperic SIGAR - see 
http://forums.hyperic.com/jiveforums/thread.jspa?messageID=37069, for example.

Original comment by pmo...@gmail.com on 1 Jun 2011 at 7:05

GoogleCodeExporter commented 9 years ago
I have the same problem with 
RHEL 5.6 x86_64
Websphere 7.0.0.11 SR7 (IBM JDK 1.6.0)
Alfresco Enterprise 3.4.1

Also the tool is not able to find the real JDK I'm using, it would be grear to 
have a --java-home to especify it.

Original comment by mikel.a...@gmail.com on 28 Jun 2011 at 8:30

GoogleCodeExporter commented 9 years ago
Mikel, you can control which JDK the tool uses via the standard mechanisms 
(i.e. set JAVA_HOME and update the PATH).

Original comment by pmo...@gmail.com on 11 Jul 2011 at 10:12

GoogleCodeExporter commented 9 years ago
This issue was closed by revision eefffd7f006c.

Original comment by op.b...@gmail.com on 15 Feb 2012 at 9:39