Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Socket error running on Solaris 11

Description

During standalone installer execution I get 2 errors:

First one is during core:

chmod a+x /usr/local/OpenNMS/lib/bin/karaf-client.jar

=> file seems to be not present

Second one during configuration step:

bash-3.00# ./install -dis
/usr/local/OpenNMS/bin/runjava: local: not found
/usr/jdk/instances/jdk1.7.0/jre/bin/java
==============================================================================
OpenNMS Installer
==============================================================================

Configures PostgreSQL tables, users, and other miscellaneous settings.

WARNING: unable to load XXX_TOKENIZE_ME_XXX/etc/opennms.properties
WARNING: unable to load XXX_TOKENIZE_ME_XXX/etc/model-importer.properties
Exception in thread "main" java.lang.Exception: property "importer.requisition.dir" not set from bundled installer.properties file
at org.opennms.install.Installer.fetchProperty(Installer.java:430)
at org.opennms.install.Installer.loadProperties(Installer.java:390)
at org.opennms.install.Installer.install(Installer.java:148)
at org.opennms.install.Installer.main(Installer.java:949)

Environment

Solaris 10 sparc

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Matt Brozowski September 11, 2014 at 2:27 PM

The client.jar fil will occur in 1.14

Mike Jacobi January 13, 2014 at 12:11 AM

The first issue mentioned (karat-client.jar) still exists.

Benjamin Reed October 11, 2013 at 11:24 AM

Forked syslog4j and fixed its JNA usage. Fixed in 1.12.2 with a new syslog4j dependency.

Benjamin Reed September 25, 2013 at 9:50 AM

This appears to be a different issue than the original one, if it's the syslog northbounder with issues. https://github.com/twall/jna/issues/227 seems to imply it's a problem with syslog4j.

If you're not using the syslog northbounder, you can just delete the jar.

Nicklas Björk September 24, 2013 at 5:45 AM

What is the current status of this issue? We are running OpenNMS on Solaris as well, and experience problems with OpenNMS 1.12.1 and java not being able to find socket. Have upgraded to jicmp 1.4.2 and jicmp6 1.2.2 but it does not seem to make any difference.

Part of the output.log quoted below. Does this error message imply that the problem is related to opennms-alarm-northbounder-syslog-1.12.1.jar or is my interpretation of the java error way out there?

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daemonContext' defined in URL [jar:file:/opt/opennms/lib/org.opennms.core.daemon-1.12.1.jar!/beanRefContext.xml]: Cannot resolve reference to bean 'daoContext' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoContext' defined in URL [jar:file:/opt/opennms/lib/opennms-dao-1.12.1.jar!/beanRefContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: *Error creating bean with name 'syslogNorthbounderManager' defined in URL [jar:file:/opt/opennms/lib/opennms-alarm-northbounder-syslog-1.12.1.jar!/META-INF/opennms/component-dao.xml]: Invocation of init method failed; nested exception is java.lang.UnsatisfiedLinkError: Error looking up function 'socket': ld.so.1: java: fatal: socket: can't find symbol*

Fixed

Details

Assignee

Reporter

Labels

Due date

Components

Fix versions

Affects versions

Priority

PagerDuty

Created September 5, 2013 at 4:04 AM
Updated January 27, 2017 at 4:21 PM
Resolved September 11, 2014 at 2:27 PM

Flag notifications