[CentOS] CentOS-announce Digest, Vol 97, Issue 10

[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. CEBA-2013:0651  CentOS 6 ghostscript Update (Johnny Hughes)
   2. CEEA-2013:0655  CentOS 6 pcs Update (Johnny Hughes)
   3. CEBA-2013:0654  CentOS 6 spice-vdagent Update (Johnny Hughes)
   4. CEBA-2013:0653  CentOS 6 initscripts Update (Johnny Hughes)
   5. CESA-2013:0656 Moderate CentOS 6 krb5 Update (Johnny Hughes)
   6. CEBA-2013:0659  CentOS 6 autofs Update (Johnny Hughes)
   7. CEBA-2013:0660  CentOS 5 ypserv Update (Johnny Hughes)


--

Message: 1
Date: Mon, 18 Mar 2013 15:44:26 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEBA-2013:0651  CentOS 6 ghostscript Update
To: centos-annou...@centos.org
Message-ID: <20130318154426.ga9...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2013:0651 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0651.html

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

i386:
3d76404119d85b0879012f8e412c34dfbc1d4712b1541ee06411d5ba8a57dbeb  
ghostscript-8.70-15.el6_4.1.i686.rpm
c726f8673493c73b8aa812059c10922aaad0dfc1fd3ebe0e958519bef38b32b3  
ghostscript-devel-8.70-15.el6_4.1.i686.rpm
440e1ca8dc8c5b7520c6cf7bab9913dfbd1466a5130f97ad3822fa0c73551d91  
ghostscript-doc-8.70-15.el6_4.1.i686.rpm
9b4027f8f697e0b0a888549278a646ce0dc8b3c53242936b117403639614babc  
ghostscript-gtk-8.70-15.el6_4.1.i686.rpm

x86_64:
3d76404119d85b0879012f8e412c34dfbc1d4712b1541ee06411d5ba8a57dbeb  
ghostscript-8.70-15.el6_4.1.i686.rpm
a17aa797a21eb7a5a18b9a3a0dde9ab8e7f6333865d2daddc91e61ab869f2033  
ghostscript-8.70-15.el6_4.1.x86_64.rpm
c726f8673493c73b8aa812059c10922aaad0dfc1fd3ebe0e958519bef38b32b3  
ghostscript-devel-8.70-15.el6_4.1.i686.rpm
4ac53afb615c7320b7cebd66e590f98b3be7d4759f8fb53884b2e3141e0e1722  
ghostscript-devel-8.70-15.el6_4.1.x86_64.rpm
eede1f3cb491278bc007a39eba5f91e081d1180c74a7b72b4a9add607baf1f1f  
ghostscript-doc-8.70-15.el6_4.1.x86_64.rpm
4f2bfc177c4ee3322735d643086a3625c948c60f292da24dcdd17b04eeb6fd5f  
ghostscript-gtk-8.70-15.el6_4.1.x86_64.rpm

Source:
d7b7538f7069a79a722d62ad0d1ba77ff93ad5a601d694113de1230ad344  
ghostscript-8.70-15.el6_4.1.src.rpm



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



--

Message: 2
Date: Mon, 18 Mar 2013 15:44:41 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEEA-2013:0655  CentOS 6 pcs Update
To: centos-annou...@centos.org
Message-ID: <20130318154441.ga9...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Enhancement Advisory 2013:0655 

Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-0655.html

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

i386:
21aad532e94cf76a4ea8ecd919d5b345c89a2371d45dd4991462c4d98a729635  
pcs-0.9.26-10.el6_4.1.noarch.rpm

x86_64:
21aad532e94cf76a4ea8ecd919d5b345c89a2371d45dd4991462c4d98a729635  
pcs-0.9.26-10.el6_4.1.noarch.rpm

Source:
3710243fa210fa0902c4d2d7d25c429ce7bae3f0df8626e510a7b5547529f0cf  
pcs-0.9.26-10.el6_4.1.src.rpm



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



--

Message: 3
Date: Mon, 18 Mar 2013 15:45:29 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEBA-2013:0654  CentOS 6 spice-vdagent
Update
To: centos-annou...@centos.org
Message-ID: <20130318154529.ga9...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2013:0654 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0654.html

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

i386:
af9f278f843c6e0722c96016d07954b073d8a2ea2a6d064fecbd33327126d3dc  
spice-vdagent-0.12.0-4.el6_4.1.i686.rpm

x86_64:
ded05774d067fd64d5a8abe50414596272e4a7ff7b41ed584b925735329d7c1e  
spice-vdagent-0.12.0-4.el6_4.1.x86_64.rpm

Source:
af2ded8623f21daa0f93f3fbd30e4eda7d56614671e3f4585466c38714975641  
spice-vdagent-0.12.0-4.el6_4.1.src.rpm



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



--

Message: 4
Date: Mon, 18 Mar 2013 15:45:42 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEBA-2013:0653  CentOS 6 initscript

Re: [CentOS] Making a clone of an LVM-based EL5 install

[Mike Burger]

Mondo?

http://www.mondorescue.org
-- 
Mike Burger
http://www.bubbanfriends.org

"It's always suicide-mission this, save-the-planet that. No one ever just
stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1


> Does anybody here have any idea how to make an exact copy of a drive
> that has LVM partitions? I'm having trouble using dd to do this for an
> EL5 server.
>
> We're trying to diagnose a software problem of some kind and would like
> an exact, perfect copy of the software running so that we can see
> exactly what the problem is without disturbing our production copy. It's
> been admin practice to set up a single server with the ideal image as
> desired, and then use DD to replicate that image to multiple hosts.
> We've done this a large number of times. The exact procedure followed is:
>
> -) Perform typical file-level backups with rsync
> -) Install additional HDD (hereafter sdb) as least a big as the HDD to
> be duplicated.
> -) Boot off a CentOS install DVD with "linux rescue"
> -) Where /dev/sda is the original drive and /dev/sdb is the new drive,
> run:
>  dd bs=8192 if=/dev/sda of=/dev/sdb;
> -) shutdown the server upon completion of the previous command and
> remove 2nd drive.
>
> Hereafter, using systems NOT running lvm, we have a bootable drive that
> can be installed into a 2nd machine and generally expect things to "just
> work" after sorting out a few driver issues. (EG: /dev/eth#s change)
> Following this exact procedure with partitions on LVM does NOT result in
> a booting system!
>
> -) When booting from the newly imaged drive, it starts the boot just
> fine but quits at:
> 
> Activating logical volumes
>Volume group "VolGroup00" not found
> Trying to resume from /dev/VolGroup00/LogVol01
> Unable to access resume device (/dev/VolGroup00/LogVol01)
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> --SNIP--
> switchroot: mount failed: no such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> 
>
>
> -) Running Linux rescue, at the shell:
> 
> # pvscan
> PV /dev/sda2VG VolGroup00   lvm2 [153.28 GiB / 0 free]
> Total: 1 [153.28 GiB] / inuse: 1 [153.28 GiB] / in no VG: [0  ]
> # vgscan
>Reading all physical volums. This may take a while...
>Found volume group "VolGroup00" using metadata type lvm2
> # lvscan
>inactive'/dev/VolGroup00/LogVol00' [151.31 GiB] inherit
>inactive'/dev/VolGroup00/LogVol01' [1.97 GiB] inherit
> 
>
> -) Running the EL5 installer with the "Find distro" option on mounts the
> install at /tmp/sysimage without issue.
>
> What am I missing?!?!
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

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

Re: [CentOS] Making a clone of an LVM-based EL5 install

[Antonio da Silva Martins Junior]

- "Lists"  escreveu:

> De: "Lists" 
> Para: "CentOS mailing list" 
> Enviadas: Segunda-feira, 18 de Março de 2013 19:36:41 (GMT-0300) Auto-Detected
> Assunto: [CentOS] Making a clone of an LVM-based EL5 install
>
> Does anybody here have any idea how to make an exact copy of a drive 
> that has LVM partitions? I'm having trouble using dd to do this for an
> 

Hi, 

  What about Clonezilla (www.clonezilla.org) or Mondo (www.mondorescue.org) ??

  But, I do it with dd too, and it works fine with LVM.

  Att.,

 Antonio.

-- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Antonio S. Martins Jr. - Support Analyst | "Only The Shadow Knows |
| Universidade Estadual de Maringá - Brasil|   what evil lurks in the   |
| NPD - Núcleo de Processamento de Dados   |   Heart of Men!"   |
| E-Mail: asmart...@uem.br / sha...@uem.br | !!! Linux User: 52392 !!!  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 "Real Programmers don’t need comments — the code is obvious."

-- 
Esta mensagem foi verificada pelo sistema de antivirus e
 acredita-se estar livre de perigo.

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

[CentOS] Policy kit issue on new install of 6.4

[Emmett Culley]

Twice I've done a fresh install of a "Development" machine.  In both cases 
pkexec as a normal user always returns "Error executing command as another 
user: No authentication agent was found."  This keeps me from getting a root 
command line and prevents yumex from starting from the launcher.

I've googled and found nothing accept some references to installing virtual 
box.  Checking the man pages for polkit was no help either.

Since this only happens when I install the "Development" group I must assume 
that some package is missing, and I am at a loss as to where to look.

Any clues?

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

Re: [CentOS] Policy kit issue on new install of 6.4

[m . roth]

Emmett Culley wrote:
> Twice I've done a fresh install of a "Development" machine.  In both cases
> pkexec as a normal user always returns "Error executing command as another
> user: No authentication agent was found."  This keeps me from getting a
> root command line and prevents yumex from starting from the launcher.
>
> I've googled and found nothing accept some references to installing
> virtual box.  Checking the man pages for polkit was no help either.
>
> Since this only happens when I install the "Development" group I must
> assume that some package is missing, and I am at a loss as to where to
> look.
>
> Any clues?

Completely unfamiliar with pkexec, but it sounds as though no
authentication agent is running. Is something like ssh-agent running, and
have you added credentials (e.g. ssh-add)?

mark

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

Re: [CentOS] Policy kit issue on new install of 6.4

[Emmett Culley]

On 03/19/2013 07:25 AM, m.r...@5-cent.us wrote:
> Emmett Culley wrote:
>> Twice I've done a fresh install of a "Development" machine.  In both cases
>> pkexec as a normal user always returns "Error executing command as another
>> user: No authentication agent was found."  This keeps me from getting a
>> root command line and prevents yumex from starting from the launcher.
>>
>> I've googled and found nothing accept some references to installing
>> virtual box.  Checking the man pages for polkit was no help either.
>>
>> Since this only happens when I install the "Development" group I must
>> assume that some package is missing, and I am at a loss as to where to
>> look.
>>
>> Any clues?
> 
> Completely unfamiliar with pkexec, but it sounds as though no
> authentication agent is running. Is something like ssh-agent running, and
> have you added credentials (e.g. ssh-add)?
> 
>  mark

Kwallet is running and working as I get prompted, as expected, for my private 
key passwords when appropriate.

I didn't know anything about pkexec either, until now.  I only found out about 
it by googling for the error quoted above.  I have, in the past, run into 
issues starting a root terminal from the launcher (KDE), but it has always 
returned to normal after a restart or re-login.  This is the first time it has 
been persistent and consistent.

All the searches seem to indicate that the polkit daemon is not configured 
correctly, but in no case is there any suggestions on how to configure it.

I'll keep looking for documentation.

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

Re: [CentOS] Policy kit issue on new install of 6.4

[m . roth]

Emmett Culley wrote:
> On 03/19/2013 07:25 AM, m.r...@5-cent.us wrote:
>> Emmett Culley wrote:
>>> Twice I've done a fresh install of a "Development" machine.  In both
>>> cases pkexec as a normal user always returns "Error executing command as
>>> another user: No authentication agent was found."  This keeps me from
getting a
>>> root command line and prevents yumex from starting from the launcher.
>>>
>>> I've googled and found nothing accept some references to installing
>>> virtual box.  Checking the man pages for polkit was no help either.
>>>
>>> Since this only happens when I install the "Development" group I must
>>> assume that some package is missing, and I am at a loss as to where to
>>> look.
>>>
>>> Any clues?
>>
>> Completely unfamiliar with pkexec, but it sounds as though no
>> authentication agent is running. Is something like ssh-agent running,
>> and have you added credentials (e.g. ssh-add)?
>
> Kwallet is running and working as I get prompted, as expected, for my
> private key passwords when appropriate.
>
> I didn't know anything about pkexec either, until now.  I only found out
> about it by googling for the error quoted above.  I have, in the past, run
> into issues starting a root terminal from the launcher (KDE), but it has
> always returned to normal after a restart or re-login.  This is the first
> time it has been persistent and consistent.
>
> All the searches seem to indicate that the polkit daemon is not configured
> correctly, but in no case is there any suggestions on how to configure it.
>
> I'll keep looking for documentation.

Have you read the man page? I just did, and I've got a really good guess
as to why it says that: it appears to want to work like sudo  -
someotheruser

  mark

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

[CentOS] kickstart bonding

[Artifex Maximus]

Hello!

I would like to use the new bonding feature of kickstart in release 6.4.

My setup is one bonding interface (bond0) with two (eth0, eth1)
ethernet cards. I am using two VLANs on bonding interface so I have no
IP for bond0 but have IPs for bond0.1 and bond0.2. If I create config
by hand it works.

Now I would like to convert my kickstart file using the new bonding
feature. The kickstart file has:

network --onboot=yes --noipv6 --device=eth0  --bootproto=static
network --onboot=yes --noipv6 --device=eth1  --bootproto=static
network --onboot=yes --noipv6 --device=bond0 --bootproto=static
--bondslaves=eth0,eth1 --bondopts=...

Kickstart gives an error to the bond0 line saying "The provided
network interface bond0 does not exist". Why? Then I put a 'modprobe
bonding' line to my %pre section. Now same error in the following
line:

network --onboot=yes --noipv6 --device=bond0 --vlanid=1
--bootproto=static --ip=192.168.1.1 --netmask=255.255.255.0

It is clear as I do not have bond0.1 but why should I have at setup
time. I do not want to use at setup time only in my final
installation.

I am lost that point so I turned to the list. I do not really
understand why kickstart use interface bond0 and others at the setup
time. Is it just parameters for making config file to my installation.

Any idea what is the problem or a good tutorial on this new feature?

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

[CentOS] 2 questions re UPS management

[Fred Smith]

Hi, trying to figure out how the system manages UPS connections. On both
Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
to appear in the top panel, and (at least on 5.9, haven't yet tested
this in 6.4) when the UPS suffers a power failure the system notices
and after a bit does a clean shutdown.

All this without installing ANYTHING extra.

one of the UPSes I'm using is a tripplite (now on 6.4 x86_64, but formerly
on the same machine with 5.9 i686), the other is a CyberPower UPS on
a different 5.9 machine.

question #1:
in 5.9 there are two entries in /etc/inittab, one for power fail and
the other for power restoration. The default setting for the powerfail
entry has it doing a shutdown in 2 minutes.

So, I need to tweak it a bit: that UPS powers two computers, the Centos 5.9
box and a Windows XP box. A little googling showed me how to use Samba
tools to tell XP to do a shutdown. That works fine.

but if I add the command for that into the inittab entry I get an error
message (when power fails) about the line being too long. So, I created
a shellscript that runs both the command to tell XP to go down, followed
by the shutdown command that tells Centos to shut down. I changed the
two minute time to 5 minutes to make sure Windoze is all the way down
even if it's busy.

When I run this script from the commandline it works just fine. but when
I turn off input power to the UPS it starts the  XP shutdown then within
without waiting the specified length of time, initiates the shutdown
of Linux. Once the shutdown is done, the UPS powers off, thereby killing
the not-yet-shutdown windoze box.

#!/bin/sh
#
# invoked by the poweroff clause in /etc/inittab instead of the command
# originally in that place. This one also shuts down the Windoze box.


net rpc SHUTDOWN -C "System shutting down NOW due to power failure" -f 
-I 172.19.23.120 -U %
/sbin/shutdown -f -h +5 "Power Failure; System Shutting Down"

and here's the entry from inittab:

pf::powerfail:/etc/powerfail

The shellscript does contain "#!/bin/sh" as its first line, but it is
currently being invoked simply by the path to the script. when I get
back to the office I'll try changing it to "/bin/bash /etc/powerfail"
to see if that makes a difference, but I kinda don't expect it to.

So, I'm wondering how the underlying mechanism works, AND if anyone knows
how (or even IF) it's possible to hand inittab a script to run instead of
burying the necessary commands directly into the inittab entry.

Question #2:
On the Centos 6.4 box at home, I haven't yet tried turning off power to
the UPS to see if it actually shuts doown, but given that a UPS icon
appears in the panel, and there are settings for what should happen 
when power fails, I expect it will.

The question here is: how does this magic all work? We no longer have
any entries in inittab to manage this, apparently we now use upstart
to  manage the same things, and I've spent some time digging for man
pages and looking around for upstart file(s) to find out how such
events are handled, and so far I've not found anything specifically
for a "powerfail" event.

Clues appreciated, thanks all!

Fred
-- 
---
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
 --Roger Ebert, December, 1996
- The Boulder Pledge -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[m . roth]

Fred Smith wrote:
> Hi, trying to figure out how the system manages UPS connections. On both
> Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
> to appear in the top panel, and (at least on 5.9, haven't yet tested
> this in 6.4) when the UPS suffers a power failure the system notices
> and after a bit does a clean shutdown.

Interesting I haven't observed this behavior; certainly not on
headless servers, though most are on UPSes; nor, when I had a working UPS
for my workstation, have I seen it. Are you running gnome or KDE?
>
> All this without installing ANYTHING extra.
>
You mean, like apcupsd?

> question #1:
> in 5.9 there are two entries in /etc/inittab, one for power fail and
> the other for power restoration. The default setting for the powerfail
> entry has it doing a shutdown in 2 minutes.

> message (when power fails) about the line being too long. So, I created
> a shellscript that runs both the command to tell XP to go down, followed

> When I run this script from the commandline it works just fine. but when
> I turn off input power to the UPS it starts the  XP shutdown then within
> without waiting the specified length of time, initiates the shutdown
> of Linux. Once the shutdown is done, the UPS powers off, thereby killing
> the not-yet-shutdown windoze box.

Thinking about this as I write, I'd guess that it expects the machine
*receiving* the shutdown to respect the five minute wait. What you might
want to do is a sleep 300 before sending the command.


 mark

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

[CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

[Woehrle Hartmut SBB CFF FFS (Extern)]

Hello Mailing List

I got a severe network error message at a HP DL360 Server.
The kernel log says:

--- /var/log/messages 
-
Mar 19 15:45:06 server kernel: do_IRQ: 2.168 No irq handler for vector (irq -1)
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: intr_sem[0] 
PCI_CMD[00100446]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: PCI_PM[19002108] 
PCI_MISC_CFG[9288]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
EMAC_TX_STATUS[0008] EMAC_RX_STATUS[0006]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
RPM_MGMT_PKT_CTRL[4088]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
HC_STATS_INTERRUPT_STATUS[017f0080]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: PBA[]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: <--- start MCP states 
dump --->
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
MCP_STATE_P0[0003610e] MCP_STATE_P1[0003610e]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: MCP 
mode[b880] state[80008000] evt_mask[0500]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: pc[0800adec] 
pc[0800aeb0] instr[8fb10014]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: shmem states:
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: drv_mb[0103000f] 
fw_mb[000f] link_status[006f] drv_pulse_mb[432b]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 
dev_info_signature[44564903] reset_type[01005254] condition[0003610e]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03cc: 
   0a3c
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03dc: 
0ffe   
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 03ec: 
   0002
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: DEBUG: 0x3fc[]
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: <--- end MCP states 
dump --->
Mar 19 15:45:17 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is Down
Mar 19 15:45:20 server kernel: bnx2 :02:00.1: eth1: NIC Copper Link is Up, 
1000 Mbps full duplex
---

Does anyone know that problem?

System is Centos 6.3 Kernel 
Linux server 2.6.32-279.5.2.el6.centos.plus.x86_64 #1 SMP Fri Aug 24 00:25:34 
UTC 2012 x86_64 x86_64 x86_64 GNU/Linux


Thanks
Hartmut

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

Re: [CentOS] Making a clone of an LVM-based EL5 install

[Gordon Messmer]

On 03/18/2013 03:36 PM, Lists wrote:
> -) When booting from the newly imaged drive, it starts the boot just
> fine but quits at:
> 
> Activating logical volumes
> Volume group "VolGroup00" not found

The only reason that I can think of that would cause this is an initrd 
that doesn't contain the driver for the whatever adapter the disk is 
attached to.

Boot the rescue image and identify the adapter module.  When you've 
identified it, go back to the live system and make a new initrd using 
"--with ".  Don't replace the existing initrd, just 
create a new one in /boot.  If you then clone the disk, you should be 
able to boot the cloned disk to grub.  Edit the kernel definition and 
change the path to the initrd, selecting the one you've created for the 
new system.  It should boot properly, at which point you can replace the 
standard initrd path or fix grub's configuration file.

...and if you don't want to clone the system again, you can just boot 
the rescue environment, chroot to the sysimage, and make the initrd there.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Making a clone of an LVM-based EL5 install

[m . roth]

Gordon Messmer wrote:
> On 03/18/2013 03:36 PM, Lists wrote:
>> -) When booting from the newly imaged drive, it starts the boot just
>> fine but quits at:
>> 
>> Activating logical volumes
>> Volume group "VolGroup00" not found
>
> The only reason that I can think of that would cause this is an initrd
> that doesn't contain the driver for the whatever adapter the disk is
> attached to.

> ...and if you don't want to clone the system again, you can just boot
> the rescue environment, chroot to the sysimage, and make the initrd there.

This latter is what I'd recommend doing.

mark

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

Re: [CentOS] Policy kit issue on new install of 6.4

[Emmett Culley]

On 03/19/2013 07:48 AM, m.r...@5-cent.us wrote:
> Emmett Culley wrote:
>> On 03/19/2013 07:25 AM, m.r...@5-cent.us wrote:
>>> Emmett Culley wrote:
 Twice I've done a fresh install of a "Development" machine.  In both
 cases pkexec as a normal user always returns "Error executing command as
 another user: No authentication agent was found."  This keeps me from
> getting a
 root command line and prevents yumex from starting from the launcher.

 I've googled and found nothing accept some references to installing
 virtual box.  Checking the man pages for polkit was no help either.

 Since this only happens when I install the "Development" group I must
 assume that some package is missing, and I am at a loss as to where to
 look.

 Any clues?
>>>
>>> Completely unfamiliar with pkexec, but it sounds as though no
>>> authentication agent is running. Is something like ssh-agent running,
>>> and have you added credentials (e.g. ssh-add)?
>>
>> Kwallet is running and working as I get prompted, as expected, for my
>> private key passwords when appropriate.
>>
>> I didn't know anything about pkexec either, until now.  I only found out
>> about it by googling for the error quoted above.  I have, in the past, run
>> into issues starting a root terminal from the launcher (KDE), but it has
>> always returned to normal after a restart or re-login.  This is the first
>> time it has been persistent and consistent.
>>
>> All the searches seem to indicate that the polkit daemon is not configured
>> correctly, but in no case is there any suggestions on how to configure it.
>>
>> I'll keep looking for documentation.
> 
> Have you read the man page? I just did, and I've got a really good guess
> as to why it says that: it appears to want to work like sudo  -
> someotheruser
> 
>mark
It turns out that every machine I've updated to 6.4 works like this.  Most of 
the others I only log into occasionally, and as root.

I suppose it is possible that they were like this before I upgraded to 6.4.  
I'll have to build a 6.3 machine and find out.

Emmett

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

Re: [CentOS] 2 questions re UPS management

[Markku Kolkka]

19.3.2013 16:55, Fred Smith kirjoitti:
> Hi, trying to figure out how the system manages UPS connections. On both
> Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
> to appear in the top panel, and (at least on 5.9, haven't yet tested
> this in 6.4) when the UPS suffers a power failure the system notices
> and after a bit does a clean shutdown.

If you are using the default GNOME desktop, then that's the GNOME Power
Manager: http://projects.gnome.org/gnome-power-manager/

> The question here is: how does this magic all work?

It uses DBus and the UPower service. See: http://upower.freedesktop.org/

-- 
Markku Kolkka
markku.kol...@iki.fi
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] unexpected 'reinitialize disk?' prompt form anaconda during kickstart with zerombr

[Duncan Hutty]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Anyone have any thoughts on why anaconda might be prompting me to
reinitialize the disk during the kickstart of a Centos6.4 install on
hyperV when
a) the kickstart file contains "zerombr" as referred to in the
installation guide[1]
b) installation proceeds with no prompt on KVM hypervisors and succeeds?

I have read the release notes[2]/tech notes[3] for 6.4 and noted lots
of changes concerned with virtualization in general and hyperv hosts
in particular, but I don't see anything that appears to be directly
pertinent.

I did try using the "clearpart --initlabel --all" approach (although
that appears to be removed from 6.4), but I get the prompt with that
as well.

[1]:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html
[2]:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.4_Release_Notes/index.html
[3]:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Technical_Notes/index.html
- -- 
Duncan Hutty
http://www.allgoodbits.org
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlFIkeoACgkQCFuTFybf1woVDQCbBUd7PRSa8pWNVo5aQ9V/x+lS
mo4AniIpKoK0HvoDxHl2i8IZVmMJLADJ
=HnVj
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 11:10:07AM -0400, m.r...@5-cent.us wrote:
> Fred Smith wrote:
> > Hi, trying to figure out how the system manages UPS connections. On both
> > Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
> > to appear in the top panel, and (at least on 5.9, haven't yet tested
> > this in 6.4) when the UPS suffers a power failure the system notices
> > and after a bit does a clean shutdown.
> 
> Interesting I haven't observed this behavior; certainly not on
> headless servers, though most are on UPSes; nor, when I had a working UPS
> for my workstation, have I seen it. Are you running gnome or KDE?
> >
> > All this without installing ANYTHING extra.
> >
> You mean, like apcupsd?

Yes, nor "nut" either.

> 
> > question #1:
> > in 5.9 there are two entries in /etc/inittab, one for power fail and
> > the other for power restoration. The default setting for the powerfail
> > entry has it doing a shutdown in 2 minutes.
> 
> > message (when power fails) about the line being too long. So, I created
> > a shellscript that runs both the command to tell XP to go down, followed
> 
> > When I run this script from the commandline it works just fine. but when
> > I turn off input power to the UPS it starts the  XP shutdown then within
> > without waiting the specified length of time, initiates the shutdown
> > of Linux. Once the shutdown is done, the UPS powers off, thereby killing
> > the not-yet-shutdown windoze box.
> 
> Thinking about this as I write, I'd guess that it expects the machine
> *receiving* the shutdown to respect the five minute wait. What you might
> want to do is a sleep 300 before sending the command.
> 

just to be sure I'm clear: the shutdown command appears to be sent
to windows, as I desire. then instead of honoring the "+5" in the 
local shutdown command it shuts down immediately.

but if I just run the identical script from a commandline it does
exactly what I think it should: (1) tells windows to shut down then (2)
waits 5 mins before shutting down Linux.

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
  "For him who is able to keep you from falling and to present you before his 
 glorious presence without fault and with great joy--to the only God our Savior
 be glory, majesty, power and authority, through Jesus Christ our Lord, before
 all ages, now and forevermore! Amen."
- Jude 1:24,25 (niv) -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] New locales on C6...

[John Doe]

Hi,

I am trying to add esperanto and a modified greek locales... but I am not sure 
I am doing it right...
On C5, a long time ago, I would:
 - grab eo_XX and el_GR from the net and put them in /usr/share/i18n/locales

 - localedef -c -i eo_XX -f UTF-8 /usr/share/locale/eo_XX.utf8
 - localedef -c -i el_GR -f UTF-8 /usr/share/locale/el_GR.utf8

The thing is in my archives, I would have locales in both:
  /usr/lib/locale/
  /usr/share/locale/
I do not remember if I just copied the share one in the llib one...
Now, on C6, I see only /usr/share/locale/ populated...
Does anybody have any experience with modifying/adding locales...?


Thx,
JD

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

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 12:44:37PM -0400, Fred Smith wrote:
> On Tue, Mar 19, 2013 at 11:10:07AM -0400, m.r...@5-cent.us wrote:
> > Fred Smith wrote:
> > > Hi, trying to figure out how the system manages UPS connections. On both
> > > Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
> > > to appear in the top panel, and (at least on 5.9, haven't yet tested
> > > this in 6.4) when the UPS suffers a power failure the system notices
> > > and after a bit does a clean shutdown.
> > 
> > Interesting I haven't observed this behavior; certainly not on
> > headless servers, though most are on UPSes; nor, when I had a working UPS
> > for my workstation, have I seen it. Are you running gnome or KDE?

sorry, I forgot to say: standard Centos-5 Gnome installation.

> > >
> > > All this without installing ANYTHING extra.
> > >
> > You mean, like apcupsd?
> 
> Yes, nor "nut" either.
> 
> > 
> > > question #1:
> > > in 5.9 there are two entries in /etc/inittab, one for power fail and
> > > the other for power restoration. The default setting for the powerfail
> > > entry has it doing a shutdown in 2 minutes.
> > 
> > > message (when power fails) about the line being too long. So, I created
> > > a shellscript that runs both the command to tell XP to go down, followed
> > 
> > > When I run this script from the commandline it works just fine. but when
> > > I turn off input power to the UPS it starts the  XP shutdown then within
> > > without waiting the specified length of time, initiates the shutdown
> > > of Linux. Once the shutdown is done, the UPS powers off, thereby killing
> > > the not-yet-shutdown windoze box.
> > 
> > Thinking about this as I write, I'd guess that it expects the machine
> > *receiving* the shutdown to respect the five minute wait. What you might
> > want to do is a sleep 300 before sending the command.
> > 
> 
> just to be sure I'm clear: the shutdown command appears to be sent
> to windows, as I desire. then instead of honoring the "+5" in the 
> local shutdown command it shuts down immediately.
> 
> but if I just run the identical script from a commandline it does
> exactly what I think it should: (1) tells windows to shut down then (2)
> waits 5 mins before shutting down Linux.
-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
The Lord is like a strong tower. 
 Those who do what is right can run to him for safety.
--- Proverbs 18:10 (niv) -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Making a clone of an LVM-based EL5 install

[Lists]

Thanks!

Your reply in conjunction with a google search that found the below 
website and resolved this completely!

http://wiki.centos.org/TipsAndTricks/CreateNewInitrd

The final line being something like
mkinitrd --with sata_nv initrd-2.6.18-194.32.1.el5.img 2.6.18-194.32.1.el5

-Ben

On 03/19/2013 08:37 AM, Gordon Messmer wrote:
> On 03/18/2013 03:36 PM, Lists wrote:
>> -) When booting from the newly imaged drive, it starts the boot just
>> fine but quits at:
>> 
>> Activating logical volumes
>>  Volume group "VolGroup00" not found
> The only reason that I can think of that would cause this is an initrd
> that doesn't contain the driver for the whatever adapter the disk is
> attached to.
>
> Boot the rescue image and identify the adapter module.  When you've
> identified it, go back to the live system and make a new initrd using
> "--with ".  Don't replace the existing initrd, just
> create a new one in /boot.  If you then clone the disk, you should be
> able to boot the cloned disk to grub.  Edit the kernel definition and
> change the path to the initrd, selecting the one you've created for the
> new system.  It should boot properly, at which point you can replace the
> standard initrd path or fix grub's configuration file.
>
> ...and if you don't want to clone the system again, you can just boot
> the rescue environment, chroot to the sysimage, and make the initrd there.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>

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

Re: [CentOS] unexpected 'reinitialize disk?' prompt form anaconda during kickstart with zerombr

[Clint Dilks]

Hi,

There has been a change since 6.3

"The 'clearpart --initlabel' option in a kickstart no longer initializes
drives in 6.3."

Try something like

zerombr
clearpart --all --initlabel



On Wed, Mar 20, 2013 at 5:27 AM, Duncan Hutty wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Anyone have any thoughts on why anaconda might be prompting me to
> reinitialize the disk during the kickstart of a Centos6.4 install on
> hyperV when
> a) the kickstart file contains "zerombr" as referred to in the
> installation guide[1]
> b) installation proceeds with no prompt on KVM hypervisors and succeeds?
>
> I have read the release notes[2]/tech notes[3] for 6.4 and noted lots
> of changes concerned with virtualization in general and hyperv hosts
> in particular, but I don't see anything that appears to be directly
> pertinent.
>
> I did try using the "clearpart --initlabel --all" approach (although
> that appears to be removed from 6.4), but I get the prompt with that
> as well.
>
> [1]:
>
> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-options.html
> [2]:
>
> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.4_Release_Notes/index.html
> [3]:
>
> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Technical_Notes/index.html
> - --
> Duncan Hutty
> http://www.allgoodbits.org
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlFIkeoACgkQCFuTFybf1woVDQCbBUd7PRSa8pWNVo5aQ9V/x+lS
> mo4AniIpKoK0HvoDxHl2i8IZVmMJLADJ
> =HnVj
> -END PGP SIGNATURE-
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Craig White]

On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:

> just to be sure I'm clear: the shutdown command appears to be sent
> to windows, as I desire. then instead of honoring the "+5" in the 
> local shutdown command it shuts down immediately.
> 
> but if I just run the identical script from a commandline it does
> exactly what I think it should: (1) tells windows to shut down then (2)
> waits 5 mins before shutting down Linux.

sounds as if there is another daemon that is processing the signal from the UPS 
system and initiating the power down rendering the 5 minute wait in your script 
moot.

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

Using Assessments to Create Agile Organizations Webinar
https://www4.gotomeeting.com/register/480934271

March 21, 2013, 12pm EDT 
Transform your company into a thriving, agile organization that is 
able to respond immediately to changing customer demands.


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

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 01:25:27PM -0700, Craig White wrote:
> On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:
> 
> > just to be sure I'm clear: the shutdown command appears to be sent
> > to windows, as I desire. then instead of honoring the "+5" in the 
> > local shutdown command it shuts down immediately.
> > 
> > but if I just run the identical script from a commandline it does
> > exactly what I think it should: (1) tells windows to shut down then (2)
> > waits 5 mins before shutting down Linux.
> 
> sounds as if there is another daemon that is processing the signal from the 
> UPS system and initiating the power down rendering the 5 minute wait in your 
> script moot.

Well, factor this in, then:
the original powerfail entry in inittab was the same as the shutdown
command in my script EXCEPT for the lengthy command that makes windows
shutdown.  It uses exactly the same "shutdown..." command, and as long
as that command is inside inittab, when powerfail occurs, the pause
also occurs.  only when I move it out to the external script does the
pause fail to happen.

-- 
---
 .Fred Smith   /  
( /__  ,__.   __   __ /  __   : / 
 //  /   /__) /  /  /__) .+'   Home: fre...@fcshome.stoneham.ma.us 
//  (__ (___ (__(_ (___ / :__ 781-438-5471 
 Jude 1:24,25 -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Craig White]

On Mar 19, 2013, at 1:31 PM, Fred Smith wrote:

> On Tue, Mar 19, 2013 at 01:25:27PM -0700, Craig White wrote:
>> On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:
>> 
>>> just to be sure I'm clear: the shutdown command appears to be sent
>>> to windows, as I desire. then instead of honoring the "+5" in the 
>>> local shutdown command it shuts down immediately.
>>> 
>>> but if I just run the identical script from a commandline it does
>>> exactly what I think it should: (1) tells windows to shut down then (2)
>>> waits 5 mins before shutting down Linux.
>> 
>> sounds as if there is another daemon that is processing the signal from the 
>> UPS system and initiating the power down rendering the 5 minute wait in your 
>> script moot.
> 
> Well, factor this in, then:
> the original powerfail entry in inittab was the same as the shutdown
> command in my script EXCEPT for the lengthy command that makes windows
> shutdown.  It uses exactly the same "shutdown..." command, and as long
> as that command is inside inittab, when powerfail occurs, the pause
> also occurs.  only when I move it out to the external script does the
> pause fail to happen.

having the commands in an external script would fork a new process outside of 
the inittab so if it were me, I would simply join the commands to run as one 
within the inittab i.e..

/usr/bin/net rpc SHUTDOWN -C \
  "System shutting down NOW due to power failure" \
  -f -I 172.19.23.120 \
  -U % && \
  /sbin/shutdown -f -h +5 \
  "Power Failure; System Shutting Down"

I can't see /bin/sh or /bin/bash making any difference in the outcome anyway.

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

Re: [CentOS] 2 questions re UPS management

[m . roth]

Fred Smith wrote:

  #!/bin/sh
#
# invoked by the poweroff clause in /etc/inittab instead of the
command
# originally in that place. This one also shuts down the Windoze box.


net rpc SHUTDOWN -C "System shutting down NOW due to power
failure" -f -I
172.19.23.120 -U %
/sbin/shutdown -f -h +5 "Power Failure; System Shutting Down"

Hoold on thar: I just had some thoughts, and went back to look at your
script... then the man page, then shutdown --help.

What's that undocumented -f do?

   mark

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

Re: [CentOS] 2 questions re UPS management

[m . roth]

Fred Smith wrote:
> On Tue, Mar 19, 2013 at 01:25:27PM -0700, Craig White wrote:
>> On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:
>>
>> > just to be sure I'm clear: the shutdown command appears to be sent
>> > to windows, as I desire. then instead of honoring the "+5" in the
>> > local shutdown command it shuts down immediately.
>> >
>> > but if I just run the identical script from a commandline it does
>> > exactly what I think it should: (1) tells windows to shut down then
>> > (2) waits 5 mins before shutting down Linux.
>> 
>> sounds as if there is another daemon that is processing the signal from
>> the UPS system and initiating the power down rendering the 5 minute wait
>> in your script moot.
>
> Well, factor this in, then:
> the original powerfail entry in inittab was the same as the shutdown
> command in my script EXCEPT for the lengthy command that makes windows
> shutdown.  It uses exactly the same "shutdown..." command, and as long
> as that command is inside inittab, when powerfail occurs, the pause
> also occurs.  only when I move it out to the external script does the
> pause fail to happen.
>
Dunno if this affects it, but I just found a piece about shutting your XP
system down from the command line, and a) he says order of switch matters,
and b) gives this as an example... with *no* + sign, it's just seconds.
shutdown -s -t 60

From


   mark


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

Re: [CentOS] Centos 6.3 Network bnx2 Problem on HP DL360

[Nathan Duehr]

On Mar 19, 2013, at 9:32 AM, Woehrle Hartmut SBB CFF FFS (Extern) 
 wrote:

> Hello Mailing List
> 
> I got a severe network error message at a HP DL360 Server.
> The kernel log says:

If that's a DL360 G7 server, make sure you've applied all of the latest 
firmware patches from HP on it.  The G7 version has been almost notorious for 
firmware issues with drive controllers, ethernet interfaces, etc.

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

Re: [CentOS] 2 questions re UPS management

[Craig White]

On Mar 19, 2013, at 2:25 PM, m.r...@5-cent.us wrote:

> Fred Smith wrote:
> 
>  #!/bin/sh
>#
># invoked by the poweroff clause in /etc/inittab instead of the
> command
># originally in that place. This one also shuts down the Windoze box.
> 
> 
>net rpc SHUTDOWN -C "System shutting down NOW due to power
> failure" -f -I
> 172.19.23.120 -U %
>/sbin/shutdown -f -h +5 "Power Failure; System Shutting Down"
> 
> Hoold on thar: I just had some thoughts, and went back to look at your
> script... then the man page, then shutdown --help.
> 
> What's that undocumented -f do?

it's well documented in the man page

-f Skip fsck on reboot.

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

[CentOS] Problem with Lisp-in-box installation

[Bruce Whealton]

Hello,
 I was reading the book Practical Common Lisp and wanted to use the same
setup to follow along.  Actually that might not be necessary as there are
other tutorials on Lisp, so I just need, Emacs, SLIME, which I guess this is
what provides the REPL, (it also had QuickLisp library manager - not sure
how that is used yet) and the Clozure Common Lisp compiler.  I tried a yum
on anything with lisp in the name and didn't find anything.  Perhaps I need
a new repo.
 Anyway, I downloaded the Linux version of Lisp-in-a-box from user
webadmin.  So, it put it in the webadmin/downloads directory. I just noticed
that the errors only show up if I run it from the bash shell.  It says that
some directories do not exist, specifically,
/tmp/lispbox-0.7/emacs-23.2/libexec/emacs/23.2/x86-64-unknown-linux-gnu 
So, maybe I either need a desktop, or I develop on a different system and if
I want to create web apps, I need to install lisp to run on the server.  
 Can anyone offer some advice, please?  I am wanting to install
WebProtege, which is a Semantic Web Ontology modeling application that runs
as a web app using Java.  And I want to run another Java based application
that runs not as a server app but a desktop app.  So, somehow I need to give
shell scripts or other apps the ability to create directories, such as tmp
directories that are needed.  Maybe that isn't an issue if you double click
on the icon.
Thanks in advance for any help and advice,
Bruce

___
Bruce Whealton - Web Design/Development/Programming
Future Wave Web Development:
http://futurewaveonline.com
Developing for the Desktop as well as for
Mobile Devices - Smartphones/Tablets
Call 919-636-5809
___


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

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 05:25:11PM -0400, m.r...@5-cent.us wrote:
> Fred Smith wrote:
> 
>   #!/bin/sh
> #
> # invoked by the poweroff clause in /etc/inittab instead of the
> command
> # originally in that place. This one also shuts down the Windoze box.
> 
> 
> net rpc SHUTDOWN -C "System shutting down NOW due to power
> failure" -f -I
> 172.19.23.120 -U %
> /sbin/shutdown -f -h +5 "Power Failure; System Shutting Down"
> 
> Hoold on thar: I just had some thoughts, and went back to look at your
> script... then the man page, then shutdown --help.
> 
> What's that undocumented -f do?

This is a Centos-5 system. here's an excerpt from its man page:


SYNOPSIS
   /sbin/shutdown [-t sec] [-arkhncfFHP] time [warning-message]

DESCRIPTION


OPTIONS

   -f Skip fsck on reboot.

   The -f flag means \u2018reboot fast\u2019.  This only creates an 
advisory file /fastboot which can be tested
   by  the  system  when  it  comes up again.  The boot rc file can test if 
this file is present, and
   decide not to run fsck(1) since the system has been shut down in the 
proper way.  After that,  the
   boot process should remove /fastboot.

-- 
---
 .Fred Smith   /  
( /__  ,__.   __   __ /  __   : / 
 //  /   /__) /  /  /__) .+'   Home: fre...@fcshome.stoneham.ma.us 
//  (__ (___ (__(_ (___ / :__ 781-438-5471 
 Jude 1:24,25 -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 05:14:45PM -0400, m.r...@5-cent.us wrote:
> Fred Smith wrote:
> > On Tue, Mar 19, 2013 at 01:25:27PM -0700, Craig White wrote:
> >> On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:
> >>
> >> > just to be sure I'm clear: the shutdown command appears to be sent
> >> > to windows, as I desire. then instead of honoring the "+5" in the
> >> > local shutdown command it shuts down immediately.
> >> >
> >> > but if I just run the identical script from a commandline it does
> >> > exactly what I think it should: (1) tells windows to shut down then
> >> > (2) waits 5 mins before shutting down Linux.
> >> 
> >> sounds as if there is another daemon that is processing the signal from
> >> the UPS system and initiating the power down rendering the 5 minute wait
> >> in your script moot.
> >
> > Well, factor this in, then:
> > the original powerfail entry in inittab was the same as the shutdown
> > command in my script EXCEPT for the lengthy command that makes windows
> > shutdown.  It uses exactly the same "shutdown..." command, and as long
> > as that command is inside inittab, when powerfail occurs, the pause
> > also occurs.  only when I move it out to the external script does the
> > pause fail to happen.
> >
> Dunno if this affects it, but I just found a piece about shutting your XP
> system down from the command line, and a) he says order of switch matters,
> and b) gives this as an example... with *no* + sign, it's just seconds.
> shutdown -s -t 60
> 
> From
> 
> 

the plus sign goes in the linux shutdown command. Sorry if I wasn't clear.


-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
  The eyes of the Lord are everywhere, 
keeping watch on the wicked and the good.
- Proverbs 15:3 (niv) -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 01:55:11PM -0700, Craig White wrote:
> 
> On Mar 19, 2013, at 1:31 PM, Fred Smith wrote:
> 
> > On Tue, Mar 19, 2013 at 01:25:27PM -0700, Craig White wrote:
> >> On Mar 19, 2013, at 9:44 AM, Fred Smith wrote:
> >> 
> >>> just to be sure I'm clear: the shutdown command appears to be sent
> >>> to windows, as I desire. then instead of honoring the "+5" in the 
> >>> local shutdown command it shuts down immediately.
> >>> 
> >>> but if I just run the identical script from a commandline it does
> >>> exactly what I think it should: (1) tells windows to shut down then (2)
> >>> waits 5 mins before shutting down Linux.
> >> 
> >> sounds as if there is another daemon that is processing the signal from 
> >> the UPS system and initiating the power down rendering the 5 minute wait 
> >> in your script moot.
> > 
> > Well, factor this in, then:
> > the original powerfail entry in inittab was the same as the shutdown
> > command in my script EXCEPT for the lengthy command that makes windows
> > shutdown.  It uses exactly the same "shutdown..." command, and as long
> > as that command is inside inittab, when powerfail occurs, the pause
> > also occurs.  only when I move it out to the external script does the
> > pause fail to happen.
> 
> having the commands in an external script would fork a new process outside of 
> the inittab so if it were me, I would simply join the commands to run as one 
> within the inittab i.e..
> 
> /usr/bin/net rpc SHUTDOWN -C \
>   "System shutting down NOW due to power failure" \
>   -f -I 172.19.23.120 \
>   -U % && \
>   /sbin/shutdown -f -h +5 \
>   "Power Failure; System Shutting Down"

I originally did that (I think my original posting mentioned that) without
the backslashes, but when run it got an error message about line too long
or something similar, so that's why I tried making it an external script.

Ah, I see you used "&&" whereas I just used a semicolon separator.
wonder if it would make any difference (I understand that the "&&"
causes the second command to be skipped if the first one fails, while
the semicolon keeps it as two independent commands.)

I don't expect to be back there til Monday, but I'll try some of these
variants when I get there. (I could VPN in and try it, but if something
goes haywire, then I'm scrod for remote access.)

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
The Lord is like a strong tower. 
 Those who do what is right can run to him for safety.
--- Proverbs 18:10 (niv) -
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] 2 questions re UPS management

[Gordon Messmer]

On 03/19/2013 07:55 AM, Fred Smith wrote:
> All this without installing ANYTHING extra.

GNOME features power management software that handles common battery 
support.  The same software manages laptops that operate on battery and 
desktop PCs with a UPS.

> When I run this script from the commandline it works just fine. but when
> I turn off input power to the UPS it starts the  XP shutdown then within
> without waiting the specified length of time, initiates the shutdown
> of Linux. Once the shutdown is done, the UPS powers off, thereby killing
> the not-yet-shutdown windoze box.

If you run the script manually, you should expect to see the Windows PC 
shut down, then the Linux machine after 5 minutes, and the UPS should 
shut down with the Linux host.  Is that what happens?

It sounds like you have the Linux host on the UPS "master" port, which 
typically has to be configured specifically to behave the way that you 
describe.  One option that you might have is to configure the UPS not to 
turn off along with the master port, particularly if you have more than 
one PC on it.  Master ports should only be used if the UPS is powering a 
single PC and its peripherals (external disks, etc).

If you're not using a master port, then it sounds like the UPS is simply 
draining too quickly.  If you have a 500Va UPS, it's probably not going 
to support two PCs for five minutes.  Without knowing more about the UPS 
capacity and its load, we can only speculate, but it may be that GNOME 
is firing off the system shutdown script on power loss, then firing 
another shutdown when the available power reaches a critically low 
threshold, and then everything shutting off when there's no longer juice 
to support it (especially if you're testing this without giving the UPS 
24 hours to fully charge up).

Try turning off the Windows host and then pulling the UPS off of line 
power.  See how everything behaves when only the Linux host is running 
on the UPS.

> The shellscript does contain "#!/bin/sh" as its first line, but it is
> currently being invoked simply by the path to the script. when I get
> back to the office I'll try changing it to "/bin/bash /etc/powerfail"
> to see if that makes a difference, but I kinda don't expect it to.

It won't.

> So, I'm wondering how the underlying mechanism works, AND if anyone knows
> how (or even IF) it's possible to hand inittab a script to run instead of
> burying the necessary commands directly into the inittab entry.

Yes, I believe you're doing it correctly.

If you want the systems to shut down whether or not you're logged in, 
you'd need to install NUT and configure it to manage the UPS, and 
configure GNOME to not do so.

> Question #2:
> On the Centos 6.4 box at home, I haven't yet tried turning off power to
> the UPS to see if it actually shuts doown, but given that a UPS icon
> appears in the panel, and there are settings for what should happen
> when power fails, I expect it will.

If you're logged in, yes.  If you're not logged in, nothing is 
monitoring the UPS.

> The question here is: how does this magic all work?

GNOME!  It "just works"!

> We no longer have
> any entries in inittab to manage this, apparently we now use upstart
> to  manage the same things, and I've spent some time digging for man
> pages and looking around for upstart file(s) to find out how such
> events are handled, and so far I've not found anything specifically
> for a "powerfail" event.

Yeah, if you want a system that you have more control over, use NUT 
rather than GNOME.  You'll gain the added benefit of UPS support when no 
user is logged in at the console.

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

Re: [CentOS] 2 questions re UPS management

[Gordon Messmer]

On 03/19/2013 01:55 PM, Craig White wrote:
> having the commands in an external script would fork a new process outside of 
> the inittab so if it were me, I would simply join the commands to run as one 
> within the inittab i.e..
>
> /usr/bin/net rpc SHUTDOWN -C \
>"System shutting down NOW due to power failure" \
>-f -I 172.19.23.120 \
>-U % && \
>/sbin/shutdown -f -h +5 \
>"Power Failure; System Shutting Down"

For the love of god, don't do that!  Using "&&," if the Windows host 
isn't available, and "net" exits with an error code, the local system 
won't be instructed to shut down.

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

Re: [CentOS] 2 questions re UPS management

[SilverTip257]

On Tue, Mar 19, 2013 at 12:44 PM, Fred Smith
wrote:

> On Tue, Mar 19, 2013 at 11:10:07AM -0400, m.r...@5-cent.us wrote:
> > Fred Smith wrote:
> > > Hi, trying to figure out how the system manages UPS connections. On
> both
> > > Centos 5.9 and 6.4, merely plugging in a USB UPS device causes an icon
> > > to appear in the top panel, and (at least on 5.9, haven't yet tested
> > > this in 6.4) when the UPS suffers a power failure the system notices
> > > and after a bit does a clean shutdown.
> >
> > Interesting I haven't observed this behavior; certainly not on
> > headless servers, though most are on UPSes; nor, when I had a working UPS
> > for my workstation, have I seen it. Are you running gnome or KDE?
> > >
> > > All this without installing ANYTHING extra.
> > >
> > You mean, like apcupsd?
>
> Yes, nor "nut" either.
>

http://www.networkupstools.org/

[ I had to look it up ... so hopefully this will help those other curious
people out there. ]


>
> >
> > > question #1:
> > > in 5.9 there are two entries in /etc/inittab, one for power fail and
> > > the other for power restoration. The default setting for the powerfail
> > > entry has it doing a shutdown in 2 minutes.
> > 
> > > message (when power fails) about the line being too long. So, I created
> > > a shellscript that runs both the command to tell XP to go down,
> followed
> > 
> > > When I run this script from the commandline it works just fine. but
> when
> > > I turn off input power to the UPS it starts the  XP shutdown then
> within
> > > without waiting the specified length of time, initiates the shutdown
> > > of Linux. Once the shutdown is done, the UPS powers off, thereby
> killing
> > > the not-yet-shutdown windoze box.
> >
> > Thinking about this as I write, I'd guess that it expects the machine
> > *receiving* the shutdown to respect the five minute wait. What you might
> > want to do is a sleep 300 before sending the command.
> > 
>
> just to be sure I'm clear: the shutdown command appears to be sent
> to windows, as I desire. then instead of honoring the "+5" in the
> local shutdown command it shuts down immediately.
>
> but if I just run the identical script from a commandline it does
> exactly what I think it should: (1) tells windows to shut down then (2)
> waits 5 mins before shutting down Linux.
>
> --
>  Fred Smith -- fre...@fcshome.stoneham.ma.us-
>   "For him who is able to keep you from falling and to present you before
> his
>  glorious presence without fault and with great joy--to the only God our
> Savior
>  be glory, majesty, power and authority, through Jesus Christ our Lord,
> before
>  all ages, now and forevermore! Amen."
> - Jude 1:24,25 (niv)
> -
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 6.4 on Dell R320 64 Bit.

[Kaushal Shriyan]

Hi,

I have installed CentOS 6.4 on Dell Server R320 64bit with UEFI BIOS. Do i
need both /boot and /boot/efi partitions. Please help me understand the
difference between these.

Regards,

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

Re: [CentOS] 2 questions re UPS management

[Fred Smith]

On Tue, Mar 19, 2013 at 03:36:45PM -0700, Gordon Messmer wrote:
> On 03/19/2013 07:55 AM, Fred Smith wrote:
> > All this without installing ANYTHING extra.
> 
> GNOME features power management software that handles common battery 
> support.  The same software manages laptops that operate on battery and 
> desktop PCs with a UPS.
> 
> > When I run this script from the commandline it works just fine. but when
> > I turn off input power to the UPS it starts the  XP shutdown then within
> > without waiting the specified length of time, initiates the shutdown
> > of Linux. Once the shutdown is done, the UPS powers off, thereby killing
> > the not-yet-shutdown windoze box.
> 
> If you run the script manually, you should expect to see the Windows PC 
> shut down, then the Linux machine after 5 minutes, and the UPS should 
> shut down with the Linux host.  Is that what happens?

Yes. exactly that.

And, if I use the original inittab entry (which is just the shutdown
command for linux, with a "+3" in it) it waits 3 minutes then shuts
down.
 
> It sounds like you have the Linux host on the UPS "master" port, which 
> typically has to be configured specifically to behave the way that you 
> describe.  One option that you might have is to configure the UPS not to 
> turn off along with the master port, particularly if you have more than 
> one PC on it.  Master ports should only be used if the UPS is powering a 
> single PC and its peripherals (external disks, etc).

I dunno what a "master port" is,... there's only one place to connect
the USB cable to the UPS.

> 
> If you're not using a master port, then it sounds like the UPS is simply 
> draining too quickly.  If you have a 500Va UPS, it's probably not going 
> to support two PCs for five minutes.  Without knowing more about the UPS 
> capacity and its load, we can only speculate, but it may be that GNOME 
> is firing off the system shutdown script on power loss, then firing 
> another shutdown when the available power reaches a critically low 
> threshold, and then everything shutting off when there's no longer juice 
> to support it (especially if you're testing this without giving the UPS 
> 24 hours to fully charge up).

No, it's a 1500VA (900 W) ups. it powers two PCs, one monitor and one
teeny little network switch. normal load is between 190-200 watts.
It's got plenty of oomph to power both systems for at least 15 minutes.

> Try turning off the Windows host and then pulling the UPS off of line 
> power.  See how everything behaves when only the Linux host is running 
> on the UPS.
> 
> > The shellscript does contain "#!/bin/sh" as its first line, but it is
> > currently being invoked simply by the path to the script. when I get
> > back to the office I'll try changing it to "/bin/bash /etc/powerfail"
> > to see if that makes a difference, but I kinda don't expect it to.
> 
> It won't.
> 
> > So, I'm wondering how the underlying mechanism works, AND if anyone knows
> > how (or even IF) it's possible to hand inittab a script to run instead of
> > burying the necessary commands directly into the inittab entry.
> 
> Yes, I believe you're doing it correctly.

so my puzzle remains: why does shutdown not honor the "+5" when it's
part of a separate script, but does when it's not?

> 
> If you want the systems to shut down whether or not you're logged in, 
> you'd need to install NUT and configure it to manage the UPS, and 
> configure GNOME to not do so.

You think this mechanism only works when logged in? (I have no idea,
I'm not doubting you, it's simply a thought I hadn't had--yet).

but that's probably not a problem, I'm logged in there pretty much
24 hours a day.

> > Question #2:
> > On the Centos 6.4 box at home, I haven't yet tried turning off power to
> > the UPS to see if it actually shuts doown, but given that a UPS icon
> > appears in the panel, and there are settings for what should happen
> > when power fails, I expect it will.
> 
> If you're logged in, yes.  If you're not logged in, nothing is 
> monitoring the UPS.
> 
> > The question here is: how does this magic all work?
> 
> GNOME!  It "just works"!
> 
> > We no longer have
> > any entries in inittab to manage this, apparently we now use upstart
> > to  manage the same things, and I've spent some time digging for man
> > pages and looking around for upstart file(s) to find out how such
> > events are handled, and so far I've not found anything specifically
> > for a "powerfail" event.
> 
> Yeah, if you want a system that you have more control over, use NUT 
> rather than GNOME.  You'll gain the added benefit of UPS support when no 
> user is logged in at the console.

the C6 system is a personal desktop, at home, and it too is logged in
most of the time. Last time I looked at nut, I found too many things
I had to know in order to configure it that I didn't know, like it wasn't
clear which nut device driver was correct for the tripplite UPS I had
at the time, and some of the configurations (as f