[Bro-Dev] [JIRA] (BIT-1099) ./build/bro-git-20131129/lib/broctl/plugins/lb_myricom.py

[tyler.schoenke (JIRA)]

tyler.schoenke created BIT-1099:
-----------------------------------

             Summary: ./build/bro-git-20131129/lib/broctl/plugins/lb_myricom.py
                 Key: BIT-1099
                 URL: https://bro-tracker.atlassian.net/browse/BIT-1099
             Project: Bro Issue Tracker
          Issue Type: Problem
          Components: BroControl
    Affects Versions: git/master
         Environment: RHEL6
Myricom 10G
            Reporter: tyler.schoenke


Hi All,

First, unrelated, thanks for fixing whatever was wrong with PktSrc.cc:222.  I was core dumping on that with the Myricom 10G until I upgraded to the latest git version of Bro.

I had been running with my Myricom environment variables configured in .bash_profile, but decided to move them to etc/node.cfg because that feature is now available in Bro 2.2.  

When I tried to start the workers, they failed and I got the message to run diag.  When I ran diag, I noticed it showed the following.  

28366 snf.0.-1 P (environ)        SNF_DATARING_SIZE = 2147483648 (0x80000000) (2048.0 MiB)
28366 snf.0.-1 P (default)        SNF_DESCRING_SIZE = 536870912 (0x20000000) (512.0 MiB)
28366 snf.0.-1 P (userset)                SNF_FLAGS = 257 (0x101)
28366 snf.0.-1 P (environ)           SNF_DEBUG_MASK = 3 (0x3)
28366 snf.0.-1 P (default)       SNF_DEBUG_FILENAME = stderr

Everything looks great except for SNF_FLAGS.  Myricom defaults it to 0x1, and that was working when I ran bro from the command line.

I found it was getting set in ./build/bro-git-20131129/lib/broctl/plugins/lb_myricom.py

According to /opt/snf/include/snf.h, the only  valid values for SNF_FLAGS are 0x1, 0x2, and 0x300.  No possible combination of those will add up to 0x101.   I'm guessing that is a typo.  If not, please explain why it is defaulted to that, otherwise you may want to default to 0x1.  

Thanks,
Tyler





--
This message was sent by Atlassian JIRA
(v6.2-OD-03#6206)