[CentOS] Virtualisation, guests cached memory and density

[Nux!]

Hello,

We all know linux distros will use most of the free memory available 
for caching stuff, I/O buffers etc (hence sites like linuxatemyram.com).
In many virt scenarios we have some sort of memory deduplication 
mechanisms, such as KSM on KVM (don't know how it's called in Vmware).

My situation is one where I need to cram up as many virtual machines as 
I can on a single hypervisor and I believe KSM does not work for the 
memory used as cache/buffers.
How could I work around this? Any other pointers for achieving higher 
density welcome (don't suggest container technology please).

-- 
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 96, Issue 4

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2013:0241 Moderate CentOS 5 xen Update (Johnny Hughes)


--

Message: 1
Date: Thu, 7 Feb 2013 21:02:50 +
From: Johnny Hughes 
Subject: [CentOS-announce] CESA-2013:0241 Moderate CentOS 5 xen Update
To: centos-annou...@centos.org
Message-ID: <20130207210250.ga19...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2013:0241 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-0241.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
a363cecbfc4b2f919cbfefa64e8b12ef940a6cf3c13d6597be02683741b0dcc6  
xen-3.0.3-142.el5_9.1.i386.rpm
f800b13367a728fae846bdc9605188a169f42e724f7c2049dcf75dcdaea00223  
xen-devel-3.0.3-142.el5_9.1.i386.rpm
99ca3b4e067348d95b20642ddb076fc7235cb0e46c8f72dce037db9e79d45297  
xen-libs-3.0.3-142.el5_9.1.i386.rpm

x86_64:
5e34b850232ecc759ab4ca1565a4235100f4c519a45df8cc4c58e3045aec295b  
xen-3.0.3-142.el5_9.1.x86_64.rpm
f800b13367a728fae846bdc9605188a169f42e724f7c2049dcf75dcdaea00223  
xen-devel-3.0.3-142.el5_9.1.i386.rpm
57cba1f271e3ed9219c83f4b8e8c9b10acc0fe63ea2f8d707a933c037e434628  
xen-devel-3.0.3-142.el5_9.1.x86_64.rpm
99ca3b4e067348d95b20642ddb076fc7235cb0e46c8f72dce037db9e79d45297  
xen-libs-3.0.3-142.el5_9.1.i386.rpm
93b3d760b5b508b947b0f384411a917eb30adc2c86ca4a03b20c2d8449f91f50  
xen-libs-3.0.3-142.el5_9.1.x86_64.rpm

Source:
c0bb9a713b50ba9db753a105c6e098d2f27042db57df5b2d110b7d0dda0dfed8  
xen-3.0.3-142.el5_9.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

___
CentOS-announce mailing list
centos-annou...@centos.org
http://lists.centos.org/mailman/listinfo/centos-announce


End of CentOS-announce Digest, Vol 96, Issue 4
**
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] apcupsd, odd behavior

[m . roth]

As we have every day, we had a power blip overnight. one, at least, of the
servers connected to a SmartUPS via cable, announced that "power
exhausted, initiating shutdown" (which I've disabled).

The thing is, I know the servers on that UPS draw a ridiculous amount of
power, but I don't see that on the others... and this was three seconds,
not minutes, after it announced there was a power outage.

Has anyone else seen this behavior?

mark

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

[CentOS] routing problem?

[Natxo Asenjo]

hi,

at home I have setup a kvm virtualization lab. I have a layer 3
switch, a host with 3 nics and centos 6.3.

In the layer 3 switch I have setup a couple of vlans: vlan 1
(default), 5 (quarantaine) and 10 (out-of-band-management).

nic0 is configured in the switch as a trunk interface that sees all
vlans. nic2 is an access port on vlan 5 and nic1 is not yet in the
picture ;-)

eth0 is bridged to br0. It also has the host default gateway. I have
also created eth0.5, br0.5, eth0.10 and br0.10 interfaces to add vm's
to vlan 5 and 10 and that works, I can successfully create vms and
assign them to br0.5 or br0.10 and they get ip's from a dchp server in
the correct network and their traffic is correctly routed in the
switch (inter vlan routing works). I can access the vms from my
workstation on on vlan 1.

Now I configure eth2 with an ip address in the range of vlan 5 (in the
switch it is an access port in vlan 5). This is the ifcfg-eth2 file:

DEVICE="eth2"
HWADDR="00:15:17:51:B8:AB"
IPV6INIT="no"
BOOTPROTO=none
MTU="1500"
NM_CONTROLLED="no"
ONBOOT="yes"
IPADDR=192.168.5.10
NETMASK=255.255.255.0
# GATEWAY=192.168.5.254

The GATEWAY parameter is now commented out, but it does not matter.

The interface on the virtualization host comes up all right. But I
cannot access it from my workstation on vlan 1 when accessing it to
vlan 5.

>From the virtualization host I can reach the switch vlan 5 interface
which is its gateway. From the switch I can also ping the interface
eth2.

The routing table on the virt host:

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
192.168.5.0 0.0.0.0 255.255.255.0   U 0  00 eth2
192.168.0.0 0.0.0.0 255.255.255.0   U 0  00 br0
169.254.0.0 0.0.0.0 255.255.0.0 U 1003   00 eth2
169.254.0.0 0.0.0.0 255.255.0.0 U 1016   00 br0
169.254.0.0 0.0.0.0 255.255.0.0 U 1018   00 br_v10
169.254.0.0 0.0.0.0 255.255.0.0 U 1020   00 br_v5
0.0.0.0 192.168.0.254   0.0.0.0 UG0  00 br0

Do you have any tips on how to reach vlan 5 on the virt host from vlan 1?
--
Groeten,
natxo
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apcupsd, odd behavior

[Les Mikesell]

On Fri, Feb 8, 2013 at 8:23 AM,   wrote:
> As we have every day, we had a power blip overnight. one, at least, of the
> servers connected to a SmartUPS via cable, announced that "power
> exhausted, initiating shutdown" (which I've disabled).
>
> The thing is, I know the servers on that UPS draw a ridiculous amount of
> power, but I don't see that on the others... and this was three seconds,
> not minutes, after it announced there was a power outage.
>
> Has anyone else seen this behavior?

You mean UPS's behaving badly?  Yes, they break like everything else,
especially the batteries.

-- 
   Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Les Mikesell wrote:
> On Fri, Feb 8, 2013 at 8:23 AM,   wrote:
>> As we have every day, we had a power blip overnight. one, at least, of
>> the servers connected to a SmartUPS via cable, announced that "power
>> exhausted, initiating shutdown" (which I've disabled).
>>
>> The thing is, I know the servers on that UPS draw a ridiculous amount of
>> power, but I don't see that on the others... and this was three seconds,
>> not minutes, after it announced there was a power outage.
>>
>> Has anyone else seen this behavior?
>
> You mean UPS's behaving badly?  Yes, they break like everything else,
> especially the batteries.

Nah, I think it's something with apcupsd.

   mark

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

Re: [CentOS] apcupsd, odd behavior

[Les Mikesell]

On Fri, Feb 8, 2013 at 9:54 AM,   wrote:
>
>>> As we have every day, we had a power blip overnight. one, at least, of
>>> the servers connected to a SmartUPS via cable, announced that "power
>>> exhausted, initiating shutdown" (which I've disabled).
>>>
>>> The thing is, I know the servers on that UPS draw a ridiculous amount of
>>> power, but I don't see that on the others... and this was three seconds,
>>> not minutes, after it announced there was a power outage.
>>>
>>> Has anyone else seen this behavior?
>>
>> You mean UPS's behaving badly?  Yes, they break like everything else,
>> especially the batteries.
>
> Nah, I think it's something with apcupsd.

Doesn't it log the message as received from the UPS?  It if has a
network interface you should be get messages via syslog, email, snmp,
etc., and there is probably a web interface with status showing
expected battery capacity at the current load.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Pulseaudio pauses when switching virtual terminal?

[James Pearson]

When using CentOS6/Gnome any audio playback will pause if I switch to 
other virtual terminals - and resume when I switch back to X

Does anyone know if it is possible to configure pulseaudio (or some 
other means?) to allow audio to continue playing when switching virtual 
terminals?

Thanks

James Pearson
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Pulseaudio pauses when switching virtual terminal?

[James Pearson]

Reindl Harald wrote:
> 
> Am 08.02.2013 17:20, schrieb James Pearson:
> 
>>When using CentOS6/Gnome any audio playback will pause if I switch to 
>>other virtual terminals - and resume when I switch back to X
>>
>>Does anyone know if it is possible to configure pulseaudio (or some 
>>other means?) to allow audio to continue playing when switching virtual 
>>terminals?
> 
> 
> system-wide is what you need for google
> 
> pulse 1082  0.6  0.0 525320 13256 ?S /usr/bin/pulseaudio --daemonize=true --system=true
> --log-level=0 --log-target=stderr --disallow-module-loading=true 
> --disallow-exit=true --exit-idle-time=0
> --disable-shm=true --no-cpu-limit=false --use-pid-file=false 
> --resample-method=src-sinc-best-quality

Thanks - however, google brings me to 


which seems to suggest that it is not a good idea ... do you know if 
there is a way to do what I would like - but not using system-wide ?

Thanks

James Pearson

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

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Les Mikesell wrote:
> On Fri, Feb 8, 2013 at 9:54 AM,   wrote:
>>
 As we have every day, we had a power blip overnight. one, at least, of
 the servers connected to a SmartUPS via cable, announced that "power
 exhausted, initiating shutdown" (which I've disabled).

 The thing is, I know the servers on that UPS draw a ridiculous amount
 of power, but I don't see that on the others... and this was three
 seconds, not minutes, after it announced there was a power outage.

 Has anyone else seen this behavior?
>>>
>>> You mean UPS's behaving badly?  Yes, they break like everything else,
>>> especially the batteries.
>>
>> Nah, I think it's something with apcupsd.
>
> Doesn't it log the message as received from the UPS?  It if has a
> network interface you should be get messages via syslog, email, snmp,
> etc., and there is probably a web interface with status showing
> expected battery capacity at the current load.

The entire contents of that incident. I see nothing in messages.

2013-02-07 17:38:19 -0500  Power failure.
2013-02-07 17:38:21 -0500  Battery power exhausted.
2013-02-07 17:38:21 -0500  Initiating system shutdown!
2013-02-07 17:38:21 -0500  User logins prohibited
2013-02-07 17:38:23 -0500  Power is back. UPS running on mains.
2013-02-07 17:38:23 -0500  Allowing logins

Two seconds?

  mark

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

Re: [CentOS] apcupsd, odd behavior

[Craig White]

service apcupsd status

(or cat /var/log/apcupsd.events)

Craig

On Feb 8, 2013, at 9:54 AM, m.r...@5-cent.us wrote:

> Les Mikesell wrote:
>> On Fri, Feb 8, 2013 at 9:54 AM,   wrote:
>>> 
> As we have every day, we had a power blip overnight. one, at least, of
> the servers connected to a SmartUPS via cable, announced that "power
> exhausted, initiating shutdown" (which I've disabled).
> 
> The thing is, I know the servers on that UPS draw a ridiculous amount
> of power, but I don't see that on the others... and this was three
> seconds, not minutes, after it announced there was a power outage.
> 
> Has anyone else seen this behavior?
 
 You mean UPS's behaving badly?  Yes, they break like everything else,
 especially the batteries.
>>> 
>>> Nah, I think it's something with apcupsd.
>> 
>> Doesn't it log the message as received from the UPS?  It if has a
>> network interface you should be get messages via syslog, email, snmp,
>> etc., and there is probably a web interface with status showing
>> expected battery capacity at the current load.
> 
> The entire contents of that incident. I see nothing in messages.
> 
> 2013-02-07 17:38:19 -0500  Power failure.
> 2013-02-07 17:38:21 -0500  Battery power exhausted.
> 2013-02-07 17:38:21 -0500  Initiating system shutdown!
> 2013-02-07 17:38:21 -0500  User logins prohibited
> 2013-02-07 17:38:23 -0500  Power is back. UPS running on mains.
> 2013-02-07 17:38:23 -0500  Allowing logins
> 
> Two seconds?
> 
>  mark
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

-- 
Craig White ~ craig.wh...@ttiltd.com
1.800.869.6908 ~~ www.ttiassessments.com 

Improving Productivity and Communication in the Workplace Webinar 
https://www4.gotomeeting.com/register/353378831

February 21, 2013, 11am EST

Enhanced productivity begins with effective communication -- providing clear 
information, 
communicating honestly, listening, asking questions, letting others talk, and 
bringing a positive approach when engaging in difficult conversations.

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

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Craig White wrote:
> service apcupsd status
>
> (or cat /var/log/apcupsd.events)
>
Already posted the latter; the former, hey, neat results, excerpted here:
MODEL: Smart-UPS 3000 RM
STATUS   : SHUTTING DOWN
LINEV: 118.0 Volts
LOADPCT  :  55.9 Percent Load Capacity
BCHARGE  : 100.0 Percent
TIMELEFT :  10.0 Minutes
<...>
TONBATT  : 0 seconds
CUMONBATT: 27 seconds

Now, the "shutting down" annoys me, since it *appears* that by creating
the script that it calls that returns, per the documentation, a -99, it
sets a flag *somewhere*, that's never, ever changed. Just for grins, I
restarted apcupsd, it's all fine, online, and the battery light is not
telling me it needs to be changed, but it still reads "SHUTTING DOWN".

   mark

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

[CentOS] DNS caching is not working on CentOS

[Ed Morrison]

Hi All:

For whatever reason I can not get dns caching to work on any of my 
centos boxes.  Running Centos 5 and 6.  Any thoughts on why these will 
not run?  The services start fine but when telling to perform a dig 
using itself as the resolver the queries fail (See below).

Any help would be appreciated.

Thanks,
Ed

[root@qmail ~]# ps -aux | grep pdns-recursor
Warning: bad syntax, perhaps a bogus '-'? See 
/usr/share/doc/procps-3.2.7/FAQ
root  7908  0.0  0.1  61208   568 pts/2R+   11:07   0:00 grep 
pdns-recursor
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]# dig mx blm.gov @127.0.0.1

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> mx blm.gov @127.0.0.1
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4634
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;blm.gov.   IN  MX

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Feb  8 11:08:04 2013
;; MSG SIZE  rcvd: 25
[root@qmail ~]# service pdns-recursor stop
Stopping pdns-recursor: [  OK  ]
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]# service named start
Starting named: [  OK  ]
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]#
[root@qmail ~]# dig mx teichert.com @127.0.0.1

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> mx teichert.com 
@127.0.0.1
;; global options:  printcmd
;; connection timed out; no servers could be reached
[root@qmail ~]# *
*[root@qmail ~]# dig mx teichert.com @192.168.1.6

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> mx teichert.com 
@192.168.1.6
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28537
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;teichert.com.  IN  MX

;; ANSWER SECTION:
teichert.com.   3600IN  MX  10 mailgw4.ppt.questsys.com.
teichert.com.   3600IN  MX  10 mailgw1.ppt.questsys.com.
teichert.com.   3600IN  MX  10 mailgw2.ppt.questsys.com.
teichert.com.   3600IN  MX  10 mailgw3.ppt.questsys.com.

;; ADDITIONAL SECTION:
mailgw4.ppt.questsys.com. 3600  IN  A   208.67.178.51

;; Query time: 125 msec
;; SERVER: 192.168.1.6#53(192.168.1.6)
;; WHEN: Fri Feb  8 11:12:20 2013
;; MSG SIZE  rcvd: 155
[root@qmail ~]#
[root@qmail ~]# dig mx blm.gov @192.168.1.6

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> mx blm.gov @192.168.1.6
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63254
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 8

;; QUESTION SECTION:
;blm.gov.   IN  MX

;; ANSWER SECTION:
blm.gov.300 IN  MX  5 mail4.blm.gov.
blm.gov.300 IN  MX  5 mail5.blm.gov.

;; AUTHORITY SECTION:
blm.gov.86400   IN  NS  blmdns2.blm.gov.
blm.gov.86400   IN  NS  blmdns1.blm.gov.

;; ADDITIONAL SECTION:
mail4.blm.gov.  600 IN  A   204.124.92.27
mail4.blm.gov.  600 IN   2001:49c8:8004:20fc::92:27
mail5.blm.gov.  600 IN  A   204.124.92.28
mail5.blm.gov.  600 IN   2001:49c8:8004:20fc::92:28
blmdns1.blm.gov.86400   IN  A   204.124.92.8
blmdns1.blm.gov.86400   IN   2001:49c8:8004:20fc::92:8
blmdns2.blm.gov.86400   IN  A   204.124.93.8
blmdns2.blm.gov.86400   IN   2001:49c8:8004:20fc::93:8

;; Query time: 78 msec
;; SERVER: 192.168.1.6#53(192.168.1.6)
;; WHEN: Fri Feb  8 11:13:01 2013
;; MSG SIZE  rcvd: 289*



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

Re: [CentOS] apcupsd, odd behavior

[Toby Bluhm]

On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
> Craig White wrote:
>> service apcupsd status
>>
>> (or cat /var/log/apcupsd.events)
>>
> Already posted the latter; the former, hey, neat results, excerpted here:
> MODEL: Smart-UPS 3000 RM
> STATUS   : SHUTTING DOWN
> LINEV: 118.0 Volts
> LOADPCT  :  55.9 Percent Load Capacity
> BCHARGE  : 100.0 Percent
> TIMELEFT :  10.0 Minutes
> <...>
> TONBATT  : 0 seconds
> CUMONBATT: 27 seconds
>

You can specify in the conf file that shutdown occurs when it hits X 
minutes of runtime left - "MINUTES" should be the parameter. You're at 
10.0 minutes left & if you have it set to something 10.0 or greater, 
it's probably gonna want to shutdown immediately at any AC power loss.



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

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Toby Bluhm wrote:
> On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
>> Craig White wrote:
>>> service apcupsd status
>>>
>>> (or cat /var/log/apcupsd.events)
>>>
>> Already posted the latter; the former, hey, neat results, excerpted
>> here:
>> MODEL: Smart-UPS 3000 RM
>> STATUS   : SHUTTING DOWN
>> LINEV: 118.0 Volts
>> LOADPCT  :  55.9 Percent Load Capacity
>> BCHARGE  : 100.0 Percent
>> TIMELEFT :  10.0 Minutes
>> <...>
>> TONBATT  : 0 seconds
>> CUMONBATT: 27 seconds
>>
>
> You can specify in the conf file that shutdown occurs when it hits X
> minutes of runtime left - "MINUTES" should be the parameter. You're at
> 10.0 minutes left & if you have it set to something 10.0 or greater,
> it's probably gonna want to shutdown immediately at any AC power loss.

I'm afraid you've missed the whole beginning of this thread - I suggest
you read it. I know what you were saying; it's the response of apcupsd to
a power blip this morning that's the issue: as much as these servers draw,
there's no way that the UPS is out of power in 3 seconds.

   mark

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

Re: [CentOS] apcupsd, odd behavior

[Toby Bluhm]

On 2/8/2013 2:26 PM, m.r...@5-cent.us wrote:
> Toby Bluhm wrote:
>> On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
>>> Craig White wrote:
 service apcupsd status

 (or cat /var/log/apcupsd.events)

>>> Already posted the latter; the former, hey, neat results, excerpted
>>> here:
>>> MODEL: Smart-UPS 3000 RM
>>> STATUS   : SHUTTING DOWN
>>> LINEV: 118.0 Volts
>>> LOADPCT  :  55.9 Percent Load Capacity
>>> BCHARGE  : 100.0 Percent
>>> TIMELEFT :  10.0 Minutes
>>> <...>
>>> TONBATT  : 0 seconds
>>> CUMONBATT: 27 seconds
>>>
>>
>> You can specify in the conf file that shutdown occurs when it hits X
>> minutes of runtime left - "MINUTES" should be the parameter. You're at
>> 10.0 minutes left & if you have it set to something 10.0 or greater,
>> it's probably gonna want to shutdown immediately at any AC power loss.
>
> I'm afraid you've missed the whole beginning of this thread - I suggest
> you read it. I know what you were saying; it's the response of apcupsd to
> a power blip this morning that's the issue: as much as these servers draw,
> there's no way that the UPS is out of power in 3 seconds.
>

I'm not saying it's out of battery power. I'm saying you may be telling 
it to shutdown when it has, by it's own calculations, 10 minutes of 
battery run time left. I believe the default is 3 or 5 in apcupsd.conf.

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

Re: [CentOS] apcupsd, odd behavior

[Craig White]

On Feb 8, 2013, at 12:26 PM, m.r...@5-cent.us wrote:

> Toby Bluhm wrote:
>> On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
>>> Craig White wrote:
 service apcupsd status
 
 (or cat /var/log/apcupsd.events)
 
>>> Already posted the latter; the former, hey, neat results, excerpted
>>> here:
>>> MODEL: Smart-UPS 3000 RM
>>> STATUS   : SHUTTING DOWN
>>> LINEV: 118.0 Volts
>>> LOADPCT  :  55.9 Percent Load Capacity
>>> BCHARGE  : 100.0 Percent
>>> TIMELEFT :  10.0 Minutes
>>> <...>
>>> TONBATT  : 0 seconds
>>> CUMONBATT: 27 seconds
>>> 
>> 
>> You can specify in the conf file that shutdown occurs when it hits X
>> minutes of runtime left - "MINUTES" should be the parameter. You're at
>> 10.0 minutes left & if you have it set to something 10.0 or greater,
>> it's probably gonna want to shutdown immediately at any AC power loss.
> 
> I'm afraid you've missed the whole beginning of this thread - I suggest
> you read it. I know what you were saying; it's the response of apcupsd to
> a power blip this morning that's the issue: as much as these servers draw,
> there's no way that the UPS is out of power in 3 seconds.

You can configure the anticipation of how many minutes are necessary for 
powering down because it's definitely not instantaneous and in fact, powering 
down is likely to cause an increase of power consumption.

That said, 55% load capacity is very high and obviously fits into the 
calculation that APCUPSD is making when it instructs connected server(s) to 
shut down.

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

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Toby Bluhm wrote:
> On 2/8/2013 2:26 PM, m.r...@5-cent.us wrote:
>> Toby Bluhm wrote:
>>> On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
 Craig White wrote:
> service apcupsd status
>
> (or cat /var/log/apcupsd.events)
>
 Already posted the latter; the former, hey, neat results, excerpted
 here:
 MODEL: Smart-UPS 3000 RM
 STATUS   : SHUTTING DOWN
 LINEV: 118.0 Volts
 LOADPCT  :  55.9 Percent Load Capacity
 BCHARGE  : 100.0 Percent
 TIMELEFT :  10.0 Minutes
 <...>
 TONBATT  : 0 seconds
 CUMONBATT: 27 seconds

>>>
>>> You can specify in the conf file that shutdown occurs when it hits X
>>> minutes of runtime left - "MINUTES" should be the parameter. You're at
>>> 10.0 minutes left & if you have it set to something 10.0 or greater,
>>> it's probably gonna want to shutdown immediately at any AC power loss.
>>
>> I'm afraid you've missed the whole beginning of this thread - I suggest
>> you read it. I know what you were saying; it's the response of apcupsd
>> to a power blip this morning that's the issue: as much as these servers
>> draw,there's no way that the UPS is out of power in 3 seconds.
>
> I'm not saying it's out of battery power. I'm saying you may be telling
> it to shutdown when it has, by it's own calculations, 10 minutes of
> battery run time left. I believe the default is 3 or 5 in apcupsd.conf.

Oh, sorry, you weren't clear. Nope, apcupsd.conf is at its default of
MINUTES 3.

   mark

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

Re: [CentOS] apcupsd, odd behavior

[m . roth]

Craig White wrote:
> On Feb 8, 2013, at 12:26 PM, m.r...@5-cent.us wrote:
>> Toby Bluhm wrote:
>>> On 2/8/2013 1:23 PM, m.r...@5-cent.us wrote:
 Craig White wrote:
> service apcupsd status
>
> (or cat /var/log/apcupsd.events)
>
 Already posted the latter; the former, hey, neat results, excerpted
 here:
 MODEL: Smart-UPS 3000 RM
 STATUS   : SHUTTING DOWN
 LINEV: 118.0 Volts
 LOADPCT  :  55.9 Percent Load Capacity
 BCHARGE  : 100.0 Percent
 TIMELEFT :  10.0 Minutes
 <...>
 TONBATT  : 0 seconds
 CUMONBATT: 27 seconds

>
> That said, 55% load capacity is very high and obviously fits into the
> calculation that APCUPSD is making when it instructs connected server(s)
> to shut down.

Heh. You think 55% is bad? with the 48 core servers, and esp. with the 64
core ones, when someone's running a job on the cluster, under no
circumstances can I have more than three servers plugged into a 3000...
and even then, I've seen it around 90%. I still don't believe that it
would be run dry in 2-3 seconds.

And I'm still perturbed about it still telling me it's shutting down.
Haven't figured out how to tell that to stop.

   mark

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

[CentOS] rpmbuild for different architecture [OT?]

[Steve]

As far as I can tell, the rpm-list went defunct circa 2008 so I'm asking here. 
No doubt someone will let me know if this is not OK.

I'm trying to build an RPM on a CentOS VM targeted to run on an ARM 
architecture machine.

I have a test program, prime, that I cross compiled on my VM and when I copy it 
onto 
my target machine it runs correctly. Now I want to package it in an RPM.

On my target machine, I run
$ uname -m
armv71

so on the VM I wrote my spec file and ran
$ rpmbuild -ba --target armv71 prime.spec
...
processing files: prime-1.0-1.armv71
unknown, 0: Warning using regular magic file '/etc/magic'
Requires(rpmlib): rpmlib(payloadFilesHavePrefix) <= 4.0-1 
rpmlib(CompressedFileNames) <= 3.0.4-1
...
Wrote /home/steve/rpmbuild/RPMS/armv71/prime-1.0-1.armv71.rpm
...

So it seems that some parts of rpm realize that I've cross compiled and some 
parts don't. 
Any ideas on how to get rid of these warning messages? I tried putting 
'Autoreq: 0' in the spec file but that didn't help.

A second problem is that when I go to install the rpm on the target machine, I 
get an error saying that the architecture doesn't match.
I had to use --ignorarch to get it to install. What does rpm use to determine 
what the architecture is if not uname?

With the --ignorearch option, the RPM installs and the program runs as expected.

Thanks,
Steve

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

Re: [CentOS] OT - odd behavior of Cisco switch

[m . roth]

I know y'all have been waiting with baited breath to hear the latest: the
group that handles it has agreed that one of the pair is bad. My manager
tells me that depending on when they look at it, they get anomalous
results, such as an increment-only timer going *down*.

They have a case opened with Cisco.

   mark

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

Re: [CentOS] DNS caching is not working on CentOS

[Leon Fauster]

Am 08.02.2013 um 20:09 schrieb Ed Morrison :
> For whatever reason I can not get dns caching to work on any of my 
> centos boxes.  Running Centos 5 and 6.  Any thoughts on why these will 
> not run?  The services start fine but when telling to perform a dig 
> using itself as the resolver the queries fail (See below).
> 
> Any help would be appreciated.
> 
...
> [root@qmail ~]# dig mx teichert.com @127.0.0.1
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 <<>> mx teichert.com 
> @127.0.0.1
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached



how does your named.conf looks like?

is there some firewall filtering outgoing dns request?

--
LF
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Is this right? -- Centos 6 and RHEL 6 infrastrure for continuous update/upgrade

[Gelen James]

Hi all,

Both RHEL 6 and CentOS 6 can be installed from any minor releases DVDs: 6.0, 
6.1, 6.2, 6.3, etc. And then got continuous upgrade/update with command 'yum -y 
upgrade' if repos are setup correct.

But the repos infrastructure is different between the two. CentOS uses two 
repos:

    /centos/6/os/... repo and .../centos/6/updates/...

The updates/ repo contains ONLY updated RPMs between minor releases. currently 
the updates/ contains updates after 6.3. and the /centos/6/os/ points to 
6.3Base.

Question #1: 


supposed I installed with Centos 6.2 last year, and let's say Centos 6.4 comes 
out two months later and I have not updated a single package since initial 
installation until Centos 6.4 comes out (I am way too lazy :) ), then How can I 
setup my yum config to not miss any updated packages?

Should I put all three repos inside yum config?

        centos-6.2-kickstart-os
        centos-6-os
        centos-6-updates
    
  or the centos-6.2-kickstart-os is not needed at all -- the centos-6-os and 
cnetos-6-updates together contains all latest RPMS since 6.0 -- ? The first way 
may render yum to report warning of 'duplicate RPM group definitions' or 
similar.


Questions #2:


I've heard that RHEL 6 uses a different path, they seems to have only one big 
continuously updated base os/ repository. all the RPMs updated since 6.0 
(include RPMs at the published day of RHEL 6.0) are contained in the repo. So 
only the one repo is in need to upgrade systems at any time. Is this true? and 
if so, any benefits go with it?

Thanks.

--Robinson
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Virtualisation, guests cached memory and density

[Joseph L. Casale]

> How could I work around this? Any other pointers for achieving higher 

> density welcome (don't suggest container technology please).

See memory ballooning.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos