Bug 844235 - JON smnp modules generate a kernel warning
Summary: JON smnp modules generate a kernel warning
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- Apache
Version: JON 3.0.1
Hardware: x86_64
OS: Linux
Target Milestone: ER04
: JON 3.3.0
Assignee: Simeon Pinder
QA Contact: Garik Khachikyan
Depends On:
Blocks: 868423
TreeView+ depends on / blocked
Reported: 2012-07-30 05:08 UTC by Coty Sutherland
Modified: 2018-11-28 20:22 UTC (History)
8 users (show)

It was discovered that #ifdef macros were incorrectly included in C code for customers compiling SNMP modules. Unnecessary kernel warnings were randomly thrown, and appeared in the logs when running SNMP modules. The fix updates the C code provided for customers compiling SNMP modules to remove erroneous #ifdef lines. This prevents spurious kernel warnings, as originally reported.
Clone Of:
Last Closed: 2014-12-11 14:03:14 UTC
spinder: needinfo-

Attachments (Terms of Use)
Disable SO_BSDCOMPAT call (479 bytes, patch)
2012-10-23 12:45 UTC, Mladen Turk
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1127513 None None None Never

Internal Trackers: 1127513

Description Coty Sutherland 2012-07-30 05:08:11 UTC
Description of problem:
JON smnp modules generate a kernel warning. The following is seen in the messages log:
    <kern.warning> jbintstg2 kernel: process `httpd' is using obsolete setsockopt SO_BSDCOMPAT

The following is the load modules statements on the apache end:
    LoadModule snmpcommon_module modules/libsnmpcommon.so
    LoadModule snmpagt_module modules/libsnmpmonagt.so
    SNMPConf   conf
    SNMPVar    var

The issue seems to be coming from the following line in the JON mod_snmp module code:
    setsockopt(sd, SOL_SOCKET, SO_BSDCOMPAT, &one, sizeof(one));

Version-Release number of selected component (if applicable):
JON 3.0.1

How reproducible:
We were unable to reproduce the issue at will. It just seemed to be randomly occurring.

Steps to Reproduce:

Actual results:
The kernel warning is sometimes logged.

Expected results:
The modules should not generate a kernel warning.

Additional info:

Comment 1 Charles Crouch 2012-07-30 14:50:01 UTC
Other people with similar issue from 2005

Comment 2 Charles Crouch 2012-07-30 15:53:48 UTC
Triage: Setting priority to low, should fix if rebuilding snmp module for other issues.

Comment 3 mark yarborough 2012-09-24 20:24:51 UTC
Triage from 3.1.2 to 3.1.3 per ccrouch and loleary.

Comment 4 Larry O'Leary 2012-09-24 20:28:56 UTC
I recall seeing this in the errata rpm package test that was done on either the EC2 RPMs or JON 3.1 RPMs. I can't find the email thread that contained the report details but I recall seeing that the obsolete SO_BSDCOMPAT will be removed from Fedora within the Fedora 17 time frame. If that is the case, there is a chance that this call will fail in a future release of RHEL 6/7.

Comment 5 Charles Crouch 2012-10-19 19:33:22 UTC
Marizol has very kindly agreed to investigate whether this constant has/will disappeared.

Comment 6 Mladen Turk 2012-10-23 12:43:44 UTC
Looking at the kernel's net/core/sock.c with 2.6 and up SO_BSDCOMPAT just causes warning log message (as observed by this case).
There is no additional functionality provided, so if the mod_snmp works but the only problem is that kernel warning I have attached a trivial patch that would shut down kernel log reporting.

Comment 7 Mladen Turk 2012-10-23 12:45:11 UTC
Created attachment 632071 [details]
Disable SO_BSDCOMPAT call

Trivial fix for 2.6+ kernels.

Comment 8 Marizol Martinez 2012-10-25 00:37:48 UTC
Thank you for the update, Mladen, and the patch.

Charles -- If you agree with this change, your team should file BZs for the appropriate RHEL releases, to ensure this is considered/integrated into RHEL.

Comment 11 Jay Shaughnessy 2014-09-03 19:01:33 UTC
Master commit 48ea5d09bd54794d5168575f7dfa62c55119e041
Author: Jay Shaughnessy <jshaughn@redhat.com>
Date:   Wed Sep 3 14:55:18 2014 -0400

    [844235] JON smnp modules generate a kernel warning
    Applied the supplied patch for the issue.

Test Notes:  If standard SNMP stuff works then we're good, no way to specifically test this fix, just need to make sure it builds and functions normally.

Simeon, pleasre cherry-pick this to release branch.

Comment 13 Simeon Pinder 2014-09-22 15:02:25 UTC
Fixed with commit: b73a4b27ace97a jon.git

Moving to MODIFIED for testing in next brew build.

Comment 14 Simeon Pinder 2014-09-22 15:03:26 UTC
Fixing erroneous milestone.... ?

Comment 15 Simeon Pinder 2014-10-01 21:33:32 UTC
Moving to ON_QA as available for test with build:

Comment 17 Garik Khachikyan 2014-10-16 14:01:02 UTC
taking QA contact.

Comment 18 Garik Khachikyan 2014-10-16 14:17:30 UTC

no such entries in /var/log/messages after keeping server running for a while.

version under test:
10:16:49,333 INFO  [SystemInfoManager] (http-/ SystemInformation: ********
ALERT_PURGE: [2678400000]
AS config dir: [/home/hudson/jon-server-3.3.0.ER03/jbossas/standalone/configuration]
AS product name: [EAP]
AS product version: [6.3.0.GA]
AS version: [7.4.0.Final-redhat-19]
AlertCount: [0]
AlertDefinitionCount: [8]
BuildNumber: [4aefe39:44e33a4]
CAM_DATA_PURGE_1D: [31536000000]
CAM_DATA_PURGE_1H: [1209600000]
CAM_DATA_PURGE_6H: [2678400000]
CAM_HELP_PASSWORD: [- non null -]
CAM_LDAP_BASE_DN: [ou=Users,dc=jboss,dc=org]
CAM_LDAP_BIND_PW: [- non null -]
CAM_LDAP_NAMING_FACTORY_INITIAL: [com.sun.jndi.ldap.LdapCtxFactory]
CAM_LDAP_NAMING_PROVIDER_URL: [ldap://web.bc.jonqe.lab.eng.bos.redhat.com:10389]
DATABASE_CONNECTION_URL: [jdbc:postgresql://]
DATABASE_DRIVER_NAME: [PostgreSQL Native Driver]
DATABASE_DRIVER_VERSION: [PostgreSQL 9.2 JDBC4 (build 1002)]
DRIFT_FILE_PURGE: [2678400000]
EVENT_PURGE: [1209600000]
FullName: [JBoss Operations Network]
Name: [JBoss ON]
PlatformCount: [22]
RT_DATA_PURGE: [2678400000]
SERVER_HOME_DIR: [/home/hudson/jon-server-3.3.0.ER03/jbossas/standalone]
SERVER_IDENTITY: [qe-perf-three.bc.jonqe.lab.eng.bos.redhat.com]
SERVER_INSTALL_DIR: [/home/hudson/jon-server-3.3.0.ER03]
SERVER_LOCAL_TIME: [October 16, 2014 10:16:48 AM EDT]
SERVER_TIMEZONE: [Eastern Standard Time]
SchedulesPerMinute: [596]
ServerCount: [152]
ServiceCount: [11348]
Storage_Node qe-perf-three.bc.jonqe.lab.eng.bos.redhat.com: [storageNode.addresss=qe-perf-three.bc.jonqe.lab.eng.bos.redhat.com, hostname=qe-perf-three.bc.jonqe.lab.eng.bos.redhat.com, beginTime=1413440209234, beginTime=1413440209234, unackAlerts=0, heapUsed=null, heapPercentageUsed=Min: 0.036756581405311094, Max: 0.3438498048586552, Avg: 0.1751365582028845 (%), load=null, dataUsedPercentage=null, dataDiskUsed=null, tokens=null, actuallyOwns=null]
TRAIT_PURGE: [31536000000]
Version: [3.3.0.ER03]

Note You need to log in before you can comment on or make changes to this bug.