Re: [CentOS] SNMP oddity

2017-03-23 Thread Bruce Ferrell

On 03/23/2017 10:20 PM, Digimer wrote:

Hi all,

   Not sure if this is on topic or not.

   I'm trying to query an SNMP value from centos 6 and I get a bad
response if I don't specify the MIB to use:

   0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public -m
/home/digimer/Downloads/APC/AP7900/MIB/powernet421.mib 10.255.2.1
.1.3.6.1.2.1.2.2.1.6.2
RFC1213-MIB::ifPhysAddress.2 = Hex-STRING: 00 C0 B7 5F 8A 85

   0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public 10.255.2.1
.1.3.6.1.2.1.2.2.1.6.2
IF-MIB::ifPhysAddress.2 = STRING: 0:c0:b7:5f:8a:85

Note the second reply is not returning the first character (should be
'00:', returning '0:'.

Trying to request Hex doesn't seem to help, either:

   0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public -Ox
10.255.2.1 .1.3.6.1.2.1.2.2.1.6.2
IF-MIB::ifPhysAddress.2 = STRING: 0:c0:b7:5f:8a:85

   Any SNMP folks know what I might be doing wrong?

Thanks!


use

   net-snmp-config --default-mibdirs

to locate where the mib file can be dropped so that snmp can use them.  copy 
the mib file to one of the paths returned.  mine usually end up in:

/usr/share/snmp/mibs


  net-snmp-config --snmpconfpath

To find the snmp config files

Add the mib to the snmp.conf file.  Mine looks  like this:

mibs +ALL
mibs +ASTERISK-MIB
mibs /usr/share/snmp/mibs/powernet419.mib

you can simplify the line by looking at the mib file for this:

PowerNet-MIB DEFINITIONS ::= BEGIN

and then the config file can be this:

mibs +ALL
mibs +ASTERISK-MIB
mibs +PowerNet-MIB

To use the form above, the file has to be like this

/usr/share/snmp/mibs/powernet419-mib.txt

You can also use the MIBS environment variable to specify things:

 MIBS=+CISCO-RHINO-MIB:SOME-OTHER-SPIFFY-MIB
 export MIBS



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] SNMP oddity

2017-03-23 Thread Digimer
Hi all,

  Not sure if this is on topic or not.

  I'm trying to query an SNMP value from centos 6 and I get a bad
response if I don't specify the MIB to use:

  0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public -m
/home/digimer/Downloads/APC/AP7900/MIB/powernet421.mib 10.255.2.1
.1.3.6.1.2.1.2.2.1.6.2
RFC1213-MIB::ifPhysAddress.2 = Hex-STRING: 00 C0 B7 5F 8A 85

  0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public 10.255.2.1
.1.3.6.1.2.1.2.2.1.6.2
IF-MIB::ifPhysAddress.2 = STRING: 0:c0:b7:5f:8a:85

Note the second reply is not returning the first character (should be
'00:', returning '0:'.

Trying to request Hex doesn't seem to help, either:

  0 digimer@pulsar:~/anvil/striker$ snmpget -v2c -c public -Ox
10.255.2.1 .1.3.6.1.2.1.2.2.1.6.2
IF-MIB::ifPhysAddress.2 = STRING: 0:c0:b7:5f:8a:85

  Any SNMP folks know what I might be doing wrong?

Thanks!

-- 
Digimer
Papers and Projects: https://alteeve.com/w/
"I am, somehow, less interested in the weight and convolutions of
Einstein’s brain than in the near certainty that people of equal talent
have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] RHEL 6.9 is out

2017-03-23 Thread Earl A Ramirez
>
>
> OK .. current status on CentOS-6.9 testing:
>
> We have a CR tree (see this link if you don't know what CR is
> http://bit.ly/2mWkdq7 )
>
> We have been testing this tree for several hours in QA and have made
> some corrections.
>
> If we don't find any deal breaking errors, the plan is to push the CR
> repo to 6.8 tree tomorrow at 1600 UTC .. it will take a couple hours to
> get to all of mirror.centos.org.
>
> So expect some announcements on the CR-Annoucne list tomorrow:
>
> https://lists.centos.org/mailman/listinfo/centos-cr-announce
>
> Thanks,
> Johnny Hughes
>
>

Thanks Johnny and the CentOS team for all your hard work, commitment and
dedication to this community.

Thanks again


-- 
Kind Regards
Earl Ramirez
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] RHEL 6.9 is out

2017-03-23 Thread Johnny Hughes
On 03/22/2017 05:11 PM, Digimer wrote:
> On 22/03/17 05:31 PM, Johnny Hughes wrote:
>> On 03/22/2017 08:27 AM, Phelps, Matthew wrote:
>>> On Wed, Mar 22, 2017 at 9:16 AM, Valeri Galtsev 
>>> wrote:
>>>

 On Wed, March 22, 2017 7:46 am, Phelps, Matthew wrote:
> Red Hat released RHEL 6.9 yesterday.
>
> Why isn't CentOS 6.9 out yet? :)
>
 Somebody has to do a hard work, I'm sure. Thanks, guys for the great work
 you are doing!

 Or you as sysadmin know that and just being ironic?

 Valeri

>>>
>>> To be clear, I was being ironic. Hence the smiley face.
>>>
>>> I just wanted to start a thread for future updates to appear in.
>>>
>>
>> There are 270 SRPMs that need to be built .. of those 18 require
>> modification for branding.  All the mods have been applied and a build
>> consisting of those 270 SRPMs has been queued.
>>
>> As of right now (time of writing this mail), we are still building in
>> pass 1 .. so far 236 of the 270 SRPMs have tried to build, 15 have had
>> some sort of failure and the rest have built fine.
>>
>> Working right now to figure out the failures and will resubmit those
>> once the first pass of all 270 completes.
>>
> 
> Sending a digital $drink... :)
> 


OK .. current status on CentOS-6.9 testing:

We have a CR tree (see this link if you don't know what CR is
http://bit.ly/2mWkdq7 )

We have been testing this tree for several hours in QA and have made
some corrections.

If we don't find any deal breaking errors, the plan is to push the CR
repo to 6.8 tree tomorrow at 1600 UTC .. it will take a couple hours to
get to all of mirror.centos.org.

So expect some announcements on the CR-Annoucne list tomorrow:

https://lists.centos.org/mailman/listinfo/centos-cr-announce

Thanks,
Johnny Hughes



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Python 3.x on Centos 7

2017-03-23 Thread Christian, Mark
On Thu, 2017-03-23 at 23:27 +, Christian, Mark wrote:
> On Thu, 2017-03-23 at 18:16 -0500, Matt wrote:
> > 
> > Is there a way to install Python 3.x on Centos 7.x without breaking
> > anything that depends on an older version of Python? 
> Yes.
> # yum install python34
I should have mentioned that python34 comes from the epel repo.

which can be installed from:
https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Python 3.x on Centos 7

2017-03-23 Thread Paul Heinlein

On Thu, 23 Mar 2017, Matt wrote:


Is there a way to install Python 3.x on Centos 7.x without breaking
anything that depends on an older version of Python?  This server is a
minimal Centos 7 install that primarily runs a simple LAMP setup.


yum install centos-release-scl
yum search rh-python35

Install what you need, then you have a couple choices about how to use 
the SCL for Python 3.5. For your choices, see


https://www.madboa.com/blog/2016/08/29/scl-intro/

--
Paul Heinlein <> heinl...@madboa.com <> http://www.madboa.com/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Python 3.x on Centos 7

2017-03-23 Thread Christian, Mark
On Thu, 2017-03-23 at 18:16 -0500, Matt wrote:
> Is there a way to install Python 3.x on Centos 7.x without breaking
> anything that depends on an older version of Python?  This server is a
> minimal Centos 7 install that primarily runs a simple LAMP setup.
Yes.
# yum install python34


> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Python 3.x on Centos 7

2017-03-23 Thread Hal Wigoda
Yes.  Just don't delete 2.x version

(Sent from iPhone, so please accept my apologies in advance for any spelling or 
grammatical errors.)

> On Mar 23, 2017, at 6:16 PM, Matt  wrote:
> 
> Is there a way to install Python 3.x on Centos 7.x without breaking
> anything that depends on an older version of Python?  This server is a
> minimal Centos 7 install that primarily runs a simple LAMP setup.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Python 3.x on Centos 7

2017-03-23 Thread Matt
Is there a way to install Python 3.x on Centos 7.x without breaking
anything that depends on an older version of Python?  This server is a
minimal Centos 7 install that primarily runs a simple LAMP setup.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] kerberized-nfs - any experts out there?

2017-03-23 Thread Matt Garman
On Wed, Mar 22, 2017 at 6:11 PM, John Jasen  wrote:
> On 03/22/2017 03:26 PM, Matt Garman wrote:
>> Is anyone on the list using kerberized-nfs on any kind of scale?
>
> Not for a good many years.
>
> Are you using v3 or v4 NFS?

v4.  I think you can only do kerberized NFS with v4.


> Also, you can probably stuff the rpc.gss* and idmapd services into
> verbose mode, which may give you a better ideas as to whats going on.

I do that.  The logs are verbose, but generally too cryptic for me to
make sense of.  Web searches on the errors yield results at best 50%
of the time, and the hits almost never have a solution.

> And yes, the kernel does some kerberos caching. I think 10 to 15 minutes.

To me it looks like it's more on the order of an hour.  For example, a
simple test I've done is to do a "fresh" login on a server.  The
server has just been rebooted, and with the reboot, all the
/tmp/krb5cc* files were deleted.

I login via ssh, which implicitly establishes my Kerberos tickets.  I
deliberately do a "kdestroy".  Then I have a simple shell loop like
this:

while [ 1 ] ; do date ; ls ; sleep 30s ; done

Which is just doing an ls on my home directory, which is a kerberized
NFS mount.  Despite having done a kdestroy, this works, presumably
from cached credentials.  And it continues to work for *about* an
hour, and then I start getting permission denied.  I emphasized
"about" because it's not precisely one hour, but seems to range from
maybe 55 to 65 minutes.

But, that's a super-simple, controlled test.  What happens when you
add screen multiplexers (tmux, gnu screen) into the mix.  What if you
login "fresh" via password versus having your gss (kerberos)
credentials forwarded?  What if you're logged in multiple times on the
same machine by via different methods?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] kerberized-nfs - any experts out there?

2017-03-23 Thread Matt Garman
On Wed, Mar 22, 2017 at 3:19 PM,   wrote:
> Matt Garman wrote:
>> (2) Permission denied issues.  I have user Kerberos tickets
>> configured for 70 days.  But there is clearly some kind of
>> undocumented kernel caching going on.  Looking at the Kerberos server
>> logs, it looks like it "could" be a performance issue, as I see 100s
>> of ticket requests within the same second when someone tries to launch
>> a lot of jobs.  Many of these will fail with "permission denied" but
>> if they immediately re-try, it works.  Related to this, I have been
>> unable to figure out what creates and deletes the
>> /tmp/krb5cc_uid_random files.
>
> Are they asking for *new* credentials each time? They should only be doing
> one kinit.

Well, that's what I don't understand.  In practice, I don't believe a
user should ever have to explicitly do kinit, as their
credentials/tickets are implicitly created (and forwarded) via ssh.
Despite that, I see the /tmp/krb5cc_uid files accumulating over time.
But I've tried testing this, and I haven't been able to determine
exactly what creates those files.  And I don't understand why new
krb5cc_uid files are created when there is an existing, valid file
already.  Clearly some programs ignore existing files, and some create
new ones.

> And there's nothing in the logs, correct? Have you tried attaching strace
> to one of those, and see if you can get a clue as to what's happening?

Actually, I get this in the log:

Mar 22 13:25:09 daemon.err lnxdev108 rpc.gssd[19329]: WARNING:
handle_gssd_upcall: failed to find uid in upcall string 'mech=krb5'

Thanks,
Matt
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos