Re: [CentOS] centos 6.3

[Fabian Arrotin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 02/12/14 08:29, Hadi Motamedi wrote:
> Dear All I want to put my stuff on centos 6.3 but some colleagues
> warned that it is not wise to use it at now for some bugs reported.
> Can you please confirm if this is true and which vulnerability can
> be risked for ? Thank you

"There is no 6.3" ..
One thing you have to realize is that there is only CentOS 6, and
minor releases that combine security/bugfixes at a "certain point in
time".
So take whatever CentOS 6.x distro, do a "yum update" on it and it
will automatically jump to $actual_version (so 6.6+packages updated
post 6.6 release)

Of course, one can argue that he can just "stick" with a particular
release (by modifying yum or even not running yum update at all) but
then it's another game, as it means no security update[s] at all, with
all the possible consequences ..

- -- 

Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlR9a4IACgkQnVkHo1a+xU6TgwCcCQ1RDLGS31pmmySDTtaIIH/J
esgAnRPOgfloAuyZfvwGEA2SWylPGk5U
=4DQK
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] centos 6.3

[Digimer]

On 02/12/14 02:29 AM, Hadi Motamedi wrote:

Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?
Thank you


The heartbleed and shellshock bugs are worth upgrading for themselves. 
In any case, there really is no reason to stay on 6.3, it's quite old now.


--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without 
access to education?

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

Re: [CentOS] centos 6.3

[Mihamina Rakotomandimby]

On 12/02/2014 10:29 AM, Hadi Motamedi wrote:

Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?



It is generally unsafe to run a outdated operating system.
Whatever it is.
What are your constraints not to upgrade to the latests 6.6?

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

[CentOS] centos 6.3

[Hadi Motamedi]

Dear All
I want to put my stuff on centos 6.3 but some colleagues warned that
it is not wise to use it at now for some bugs reported. Can you please
confirm if this is true and which vulnerability can be risked for ?
Thank you
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NetworkManager fights with DHCP-only backup NIC

[Rob Kampen]

On 12/02/2014 10:35 AM, Warren Young wrote:

We ship servers to remote sites, which are rarely staffed with techs familiar 
with Linux.  We have them tell us the static IP configuration for the box 
before we ship it, then we set it up for them here and ship it out to the site, 
where they just plug it in, turn it on, and walk away.

That’s the ideal, anyway.

What often happens in reality is either:

1. They give us incorrect static IP info, so the box arrives and won’t connect 
to the Internet, which means we often have to arrange to get someone clueful 
on-site to fix it.

2. The site is in the middle of some major deployment, a small piece of which is our server, so the 
LAN isn’t ready, but they demand the box be shipped early anyway for some handwavy business reason. 
 "No, we can’t tell you what static IP to use," they say.  "Just configure it 
on-site," they say.  Sigh.

Since these systems have 2+ Ethernet ports and we really only need one in 
normal operations, we’ve taken to configuring the second one for DHCP, so that 
they can just move the cable from the primary port to the secondary.

This works fine in CentOS 5: DHCP comes up and takes over, giving us the access 
we need to fix/configure the static IP on the primary port.

What happens in CentOS 7 depends on whether you plug in one cable or two:

1. If you plug in only one cable, NetworkManager sees that the static interface 
is unplugged, so it *helpfully* moves that IP to the secondary NIC, apparently 
on the assumption that static is always better than DHCP.  This is of no use to 
us, since all it does is move the problem to the other NIC.

2. If you plug both cables in, both interfaces come up configured as you’d 
expect, but since both configurations provided a gateway address, you still 
can’t get out to the Internet since the static one came up first, and it’s 
pointing at an unreachable box.

I think all we need to do to fix this is convince NetworkManager not to be 
clever about moving the static IP to the second NIC.  Alas, there is no 
checkbox in the NM GUI labeled “This is a 4U server, dummy, not a laptop.”

Anyone know how to convince NM to obey the MAC binding in the ifcfg-* file, to 
prevent NM from moving the broken static IP info to the second NIC?

Have you put
NM_CONTROLLED="no"
in the ifcfg-eth0 script?


Yes, we know we can still disable NetworkManager and edit 
network-scripts/ifcfg-* directly.  We’d just prefer not to fight the OS.  Also, 
unlike EL6, disabling NM on EL7 breaks the network GUI, which we’ve 
occasionally found helpful, as when we have a semi-clueful tech at the remote 
site.
___
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] NetworkManager fights with DHCP-only backup NIC

[Les Mikesell]

On Mon, Dec 1, 2014 at 6:56 PM, Nathan Duehr  wrote:
>
>>
>>> We ship servers to remote sites, which are rarely staffed with techs 
>>> familiar with Linux.  We have them tell us the static IP configuration for 
>>> the box before we ship it, then we set it up for them here and ship it out 
>>> to the site, where they just plug it in, turn it on, and walk away.
>>>
>>> That’s the ideal, anyway.
>>>
>>
>> Is there anyone who has more than a few boxes at more than one
>> location who _doesn't_ have this issue?  I'd like to see a FAQ or
>> something by whoever designed the network configuration system about
>> how they planned for it to work (with and without GUI availability).
>> Likewise for what is supposed to happen when you restore a backup onto
>> different hardware.
>
> Most of the time, I end up nuking HWADDR from orbit on most boxes.  It just 
> causes more trouble than it fixes.

Sure, but the interface names will be different in the 'restore backup
case' - especially on servers that have several.

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

Re: [CentOS] System Hangs At Anaconda Detecting Hardware (SOLVED)

[Mark LaPierre]

On 12/01/14 05:30, Ashish Yadav wrote:
> Hi,
> 
> On Mon, Dec 1, 2014 at 8:58 AM, Mark LaPierre  wrote:
> 
>> Hey All,
>>
>> I just assembled a new machine.
>>
>> Mother Board:   Gigabyte 78LMT-USB3
>> Processor:  AMD FX8350
>> Memory: Corsair CMZ16GX3M2A1600C10 2x8 GB
>> Video:  BFG Tech Nvidia GeForce 9600 GT
>>
>> I tried the 6.6 x86_64 netinstall disk.
>> I tried the 6.6 x86_64 install DVD
>>
>> Both fail at the same place:
>>
>> Anaconda installer init version 13.21.229 starting
>> mounting /proc filesystem... done
>> creating /dev filesystem... done
>> starting udev...udev[175]: error setting /sys/class/firmware/timeout: No
>> such file or directory
>> done
>>
>> mounting /dev/pts (unix98 pty) filesystem... done
>> mouning /sys filesystem... done
>> trying to remount root fiesystem read write... done
>> mounting /tmp as tmpfs... done
>> running install...
>> running /sbin/loader
>> detecting hardware...
>>
>> That's all she wrote!
>>
>> The BIOS detects the 500 GB hard drive, the CD/DVD drive, 16 GB of RAM,
>> all eight cores on the CPU, and boots from the CD/DVD.  Then it just
>> hangs at detecting hardware.
>>
>>
>> http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.6#head-aa1d1d1c4e306596f8ae129e016ef1f95fc7c36e
>>
>> Says:
>> "The netinstall isos do not work with UEFI installs, but the minimal or
>> DVD isos do work with UEFI. No versions of CentOS-6.6 will work with
>> Secure Boot turned on. Secure Boot must be disabled to install CentOS-6.6."
>>
>> I see nothing in the MB documentation about "Secure Boot" enabled or
>> disabled.  Also not a word about UEFI.
>>
>> Any suggestions anyone?
>>
> 
> Please make sure that your BIOS firmware is up to date. Have you checked
> that?
> 
> 
>>
>> --
>> _
>>°v°
>>   /(_)\
>>^ ^  Mark LaPierre
>> Registered Linux user No #267004
>> https://linuxcounter.net/
>> 
>> ___
>> 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
> 

I was using my TV on the S-Video Out.  It wasn't happy.  I connected my
monitor to one of the DVI ports and the world became a happy place.  I
got the install done from the DVD install disk.

Now the configuration battle starts.  First I have to install the Nvidia
drivers so that my Folding At Home application will use the 64 CUDA
cores on my video card.  Then I have to figure out how to get all the
applications I have on my 32 bit CentOS 6.6 system to run on the new 64
bit CentOS 6.6 platform.  I know it should be easy but past experience
has shown that it probably won't be.

-- 
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/

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

Re: [CentOS] NetworkManager fights with DHCP-only backup NIC

[Nathan Duehr]

> On Dec 1, 2014, at 14:48, Les Mikesell  wrote:
> 
> On Mon, Dec 1, 2014 at 3:35 PM, Warren Young  wrote:
> 
>> We ship servers to remote sites, which are rarely staffed with techs 
>> familiar with Linux.  We have them tell us the static IP configuration for 
>> the box before we ship it, then we set it up for them here and ship it out 
>> to the site, where they just plug it in, turn it on, and walk away.
>> 
>> That’s the ideal, anyway.
>> 
> 
> Is there anyone who has more than a few boxes at more than one
> location who _doesn't_ have this issue?  I'd like to see a FAQ or
> something by whoever designed the network configuration system about
> how they planned for it to work (with and without GUI availability).
> Likewise for what is supposed to happen when you restore a backup onto
> different hardware.

Most of the time, I end up nuking HWADDR from orbit on most boxes.  It just 
causes more trouble than it fixes.

--
Nate Duehr
denverpi...@me.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NetworkManager fights with DHCP-only backup NIC

[Les Mikesell]

On Mon, Dec 1, 2014 at 3:35 PM, Warren Young  wrote:

> We ship servers to remote sites, which are rarely staffed with techs familiar 
> with Linux.  We have them tell us the static IP configuration for the box 
> before we ship it, then we set it up for them here and ship it out to the 
> site, where they just plug it in, turn it on, and walk away.
>
> That’s the ideal, anyway.
>

Is there anyone who has more than a few boxes at more than one
location who _doesn't_ have this issue?  I'd like to see a FAQ or
something by whoever designed the network configuration system about
how they planned for it to work (with and without GUI availability).
Likewise for what is supposed to happen when you restore a backup onto
different hardware.

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

[CentOS] NetworkManager fights with DHCP-only backup NIC

[Warren Young]

We ship servers to remote sites, which are rarely staffed with techs familiar 
with Linux.  We have them tell us the static IP configuration for the box 
before we ship it, then we set it up for them here and ship it out to the site, 
where they just plug it in, turn it on, and walk away.

That’s the ideal, anyway.

What often happens in reality is either:

1. They give us incorrect static IP info, so the box arrives and won’t connect 
to the Internet, which means we often have to arrange to get someone clueful 
on-site to fix it.

2. The site is in the middle of some major deployment, a small piece of which 
is our server, so the LAN isn’t ready, but they demand the box be shipped early 
anyway for some handwavy business reason.  "No, we can’t tell you what static 
IP to use," they say.  "Just configure it on-site," they say.  Sigh.

Since these systems have 2+ Ethernet ports and we really only need one in 
normal operations, we’ve taken to configuring the second one for DHCP, so that 
they can just move the cable from the primary port to the secondary.

This works fine in CentOS 5: DHCP comes up and takes over, giving us the access 
we need to fix/configure the static IP on the primary port.

What happens in CentOS 7 depends on whether you plug in one cable or two:

1. If you plug in only one cable, NetworkManager sees that the static interface 
is unplugged, so it *helpfully* moves that IP to the secondary NIC, apparently 
on the assumption that static is always better than DHCP.  This is of no use to 
us, since all it does is move the problem to the other NIC.

2. If you plug both cables in, both interfaces come up configured as you’d 
expect, but since both configurations provided a gateway address, you still 
can’t get out to the Internet since the static one came up first, and it’s 
pointing at an unreachable box.

I think all we need to do to fix this is convince NetworkManager not to be 
clever about moving the static IP to the second NIC.  Alas, there is no 
checkbox in the NM GUI labeled “This is a 4U server, dummy, not a laptop.”

Anyone know how to convince NM to obey the MAC binding in the ifcfg-* file, to 
prevent NM from moving the broken static IP info to the second NIC?

Yes, we know we can still disable NetworkManager and edit 
network-scripts/ifcfg-* directly.  We’d just prefer not to fight the OS.  Also, 
unlike EL6, disabling NM on EL7 breaks the network GUI, which we’ve 
occasionally found helpful, as when we have a semi-clueful tech at the remote 
site.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] A gmane mystery

[Timothy Murphy]

On Monday 01 December 2014 16:00:44 m.r...@5-cent.us wrote:

> >> I've been collecting redhat.fedora from gmane for several years,
> >> but about a week ago I found that while I could read gmane newsgroups
> >> I was unable to post to them - that is, my posts did not appear.
> > 
> > To be honest, this was a test post,
> > to see if I could post directly to this newsgroup
> > (rather than sending email to the mailing list).
> > 
> > I found that I can indeed post to the centos newsgroup.
> > But for some reason I cannot post directly
> > to the corresponding Fedora newsgroup,
> > gmane.linux.redhat.fedora.general,
> > though I can send email the corresponding mailing list,
> > us...@lists.fedoraproject.org .
> > 
> > Why can I post to one gmane newsgroup, and not to the other?
> > I am subscribed to both mailing lists,
> > and everything is exactly the same in the two cases.
> > 
> > If anyone can cast light on this phenomenon, I should be very grateful.
> 
> This is the CentOS mailing list. You have to subscribe to it, and it's
> moderated (by someone who currently seems to have a personal issue with
> me, so I can't post to it). It's not a newsgroup.

Evidently you are not familiar with gmane.
This is a newsgroup server that mirrors various mailing lists

including this mailing list, to which I am subscribed,
and which is mirrored in the newsgroup .

> Is the CentOS newsgroup you're talking about a real usenet newsgroup? If
> so, what's the name, comp.os.centos, or some such?

I posted my query to the gmane newsgroup described above,
and it thereupon found its way to the CentOS mailing list,
where you presumably read it.


-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin

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

Re: [CentOS] A gmane mystery

[Timothy Murphy]

Timothy Murphy wrote:

> I found that I can indeed post to the centos newsgroup.
> But for some reason I cannot post directly
> to the corresponding Fedora newsgroup,
> gmane.linux.redhat.fedora.general,
> though I can send email to the corresponding mailing list,
> us...@lists.fedoraproject.org .

Sorry, that should of course be us...@lists.fedoraproject.org .

> Why can I post to one gmane newsgroup, and not to the other?
> I am subscribed to both mailing lists,
> and everything is exactly the same in the two cases.
 
> If anyone can cast light on this phenomenon, I should be very grateful.

-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


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

Re: [CentOS] Fix for RHEL BZ#771868 in CentOS?

[Ned Slider]

On 01/12/14 20:48, Ned Slider wrote:
> On 01/12/14 20:33, Jeff Hammerbacher wrote:
>> Hey,
>>
>> We are blocked on a bug fixed by RHEL in
>> https://rhn.redhat.com/errata/RHBA-2012-0362.html. Specifically, the splice
>> code in sendfile() incorrectly updating the offset position on the write
>> side, Red Hat BZ#771868.
>>
>> I have not been able to figure out if this bugfix is included in any CentOS
>> releases. If you are better at reading release notes than me, could you
>> please help me out and let me know if there's a CentOS release that
>> includes this bugfix?
>>
>> Thanks,
>> Jeff
> 
> Hi Jeff,
> 
> It looks like it's fixed in the current kernel.
> 
> Hint: try grepping the package changelog:
> 
> $ rpm -q --changelog kernel-2.6.32-504.el6.x86_64 | grep sendfile
> - [fs] Fix sendfile write-side file position (Steven Whitehouse) [770023]
> - [fs] sendfile(): check f_op.splice_write() rather than f_op.sendpage()
> (Lukas Czerner) [689426]
> 
> Those entries seem to match the bug description in the errata you list
> so I'd guess it's fixed.
> 

Further googling finds that it was fixed in the 6.2 kernel release, as
documented in the Technical Notes for 6.2:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Technical_Notes/kernel.html

^^ Search for "sendfile" and you will find it.


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

Re: [CentOS] A gmane mystery

[Timothy Murphy]

Timothy Murphy wrote:

> I've been collecting redhat.fedora from gmane for several years,
> but about a week ago I found that while I could read gmane newsgroups
> I was unable to post to them - that is, my posts did not appear.

To be honest, this was a test post,
to see if I could post directly to this newsgroup
(rather than sending email to the mailing list).

I found that I can indeed post to the centos newsgroup.
But for some reason I cannot post directly 
to the corresponding Fedora newsgroup,
gmane.linux.redhat.fedora.general,
though I can send email the corresponding mailing list,
us...@lists.fedoraproject.org .

Why can I post to one gmane newsgroup, and not to the other?
I am subscribed to both mailing lists,
and everything is exactly the same in the two cases.

If anyone can cast light on this phenomenon, I should be very grateful.


-- 
Timothy Murphy  
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin


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

Re: [CentOS] Fix for RHEL BZ#771868 in CentOS?

[Ned Slider]

On 01/12/14 20:33, Jeff Hammerbacher wrote:
> Hey,
> 
> We are blocked on a bug fixed by RHEL in
> https://rhn.redhat.com/errata/RHBA-2012-0362.html. Specifically, the splice
> code in sendfile() incorrectly updating the offset position on the write
> side, Red Hat BZ#771868.
> 
> I have not been able to figure out if this bugfix is included in any CentOS
> releases. If you are better at reading release notes than me, could you
> please help me out and let me know if there's a CentOS release that
> includes this bugfix?
> 
> Thanks,
> Jeff

Hi Jeff,

It looks like it's fixed in the current kernel.

Hint: try grepping the package changelog:

$ rpm -q --changelog kernel-2.6.32-504.el6.x86_64 | grep sendfile
- [fs] Fix sendfile write-side file position (Steven Whitehouse) [770023]
- [fs] sendfile(): check f_op.splice_write() rather than f_op.sendpage()
(Lukas Czerner) [689426]

Those entries seem to match the bug description in the errata you list
so I'd guess it's fixed.


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

[CentOS] Fix for RHEL BZ#771868 in CentOS?

[Jeff Hammerbacher]

Hey,

We are blocked on a bug fixed by RHEL in
https://rhn.redhat.com/errata/RHBA-2012-0362.html. Specifically, the splice
code in sendfile() incorrectly updating the offset position on the write
side, Red Hat BZ#771868.

I have not been able to figure out if this bugfix is included in any CentOS
releases. If you are better at reading release notes than me, could you
please help me out and let me know if there's a CentOS release that
includes this bugfix?

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

Re: [CentOS] ssh connections not closing when Qt application is opened?

[Michael Lampe]

Dave Johansen wrote:


https://bugzilla.redhat.com/show_bug.cgi?id=1086971
I have been able to reproduce the above issue on my home network and at
work, but RedHat is claiming it is not a bug, so can some people on this
list give it a try and see if they can reproduce it?


If you connect with '-vvv' you can see multiple x11 connections being open:

debug3: channel 1: status: The following connections are open:
  #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cfd -1)
  #1 x11 (t4 r2 i3/0 o3/0 fd 7/7 cfd -1)
  #2 x11 (t4 r3 i0/0 o0/0 fd 8/8 cfd -1)
  #3 x11 (t4 r4 i0/0 o0/0 fd 9/9 cfd -1)

The additional x11 connections are from automatically launched dbus 
stuff. On exit they don't get closed, therefore the hang. This happens 
on C6 and C7 with GTK+ 2/3 or Qt4/5 but not with GTK+ 1, Qt3 or legacy 
apps and it's nothing new. It just never gets fixed. (I think it's a 
dbus bug.)


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

Re: [CentOS] CentOs 7.0 and reboot failure

[Les Mikesell]

On Mon, Dec 1, 2014 at 12:59 PM, Frank Cox  wrote:
> On Mon, 01 Dec 2014 18:50:42 +
> Ned Slider wrote:
>
>> So the system will perform a cold reboot, but not a warm reboot. Sounds
>> like a hardware issue to me.
>
> I had a computer that did that a few years ago.  It would reboot about every 
> third time you started it up, otherwise it would hang.
>
> Didn't bother me too much since I rarely rebooted it.

I'd recommend checking to see if there are any firmware updates for
the system motherboard.

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

Re: [CentOS] CentOs 7.0 and reboot failure

[Frank Cox]

On Mon, 01 Dec 2014 18:50:42 +
Ned Slider wrote:

> So the system will perform a cold reboot, but not a warm reboot. Sounds
> like a hardware issue to me.

I had a computer that did that a few years ago.  It would reboot about every 
third time you started it up, otherwise it would hang.

Didn't bother me too much since I rarely rebooted it.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOs 7.0 and reboot failure

[Ned Slider]

On 01/12/14 18:36, Gregory P. Ennis wrote:
> On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
>> On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
>>> Date: Sun, 23 Nov 2014 13:50:17 -0600
>>>
>>> On Sun, 23 Nov 2014 13:07:47 -0600
>>> Gregory P. Ennis wrote:
>>>
 I also changed the boot level to 5.
>>>
>>> Do you mean the runlevel?  If so, are you sure that you changed it 
>>> correctly?
>>>
>>> Centos 7 doesn't use runlevels set in inittab like previous versions did.  
>>> I see that fact is actually noted in /etc/inittab, along with the expected 
>>> way to do it.
>>> -
>>>
>>> Frank,
>>>
>>> Yes, you are correct, I changed the run level and not boot level to 5
>>> and did so by using the command :
>>>
>>> ln -sf /lib/systemd/system/graphical.target 
>>> /etc/systemd/system/default.target
>>>
>>> Also, I appreciate everybody's input on this, but I am still at a loss
>>> as to how to fix this.  Without being able to reboot, it sure makes the
>>> set up difficult.
>>>
>>> Does anyone else have any ideas??
>>>
>>> Greg
>>>
>>
>> I have tried some additional changes that have not made a difference.
>>
>> I disabled selinux - that made no difference
>> I stopped and disabled firewalld  - that made no difference.
>>
>> I can boot this machine after I turn it off and then back on, but when I
>> try to do a shutdown now -r, the system hangs right after picking the OS
>> that is desired "CentOS Linux..".
>>
>> After the machine is turned off the boot process occurs normally after
>> this choice and I get two penguins in the upper left hand corner, and
>> the boot proceeds.  When I do a shutdown now -r, I do not get to the
>> penguins and the machine hangs forever until I either unplug it or press
>> the power button for 5 seconds.
>>
>> Any help would be appreciated!!!
>>
>> Greg 
>>
> ---
> 
> Everyone, 
> 
> I did not get much of a response on the list so I filed a bug report.  I
> wanted to document the bug report for anyone else that is having a
> reboot problem. 
> 
> https://bugs.centos.org/view.php?id=7949
> 
> 
> Greg Ennis
> 

Seems little point in filing a bug report when you have no idea what the
issue is. Bugs are not a means of troubleshooting nor a support forum.
However, you did get my attention so lets see if we can stimulate some
further interest in troubleshooting this.

So the system will perform a cold reboot, but not a warm reboot. Sounds
like a hardware issue to me.

Any clues in /var/log/messages ?

Tried updating the BIOS?

Any hardware firmwares being loaded?


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

Re: [CentOS] CentOs 7.0 and reboot failure

[Gregory P. Ennis]

On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
> On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
> > Date: Sun, 23 Nov 2014 13:50:17 -0600
> > 
> > On Sun, 23 Nov 2014 13:07:47 -0600
> > Gregory P. Ennis wrote:
> > 
> > > I also changed the boot level to 5.
> > 
> > Do you mean the runlevel?  If so, are you sure that you changed it 
> > correctly?
> > 
> > Centos 7 doesn't use runlevels set in inittab like previous versions did.  
> > I see that fact is actually noted in /etc/inittab, along with the expected 
> > way to do it.
> > -
> > 
> > Frank,
> > 
> > Yes, you are correct, I changed the run level and not boot level to 5
> > and did so by using the command :
> > 
> > ln -sf /lib/systemd/system/graphical.target 
> > /etc/systemd/system/default.target
> > 
> > Also, I appreciate everybody's input on this, but I am still at a loss
> > as to how to fix this.  Without being able to reboot, it sure makes the
> > set up difficult.
> > 
> > Does anyone else have any ideas??
> > 
> > Greg
> > 
> 
> I have tried some additional changes that have not made a difference.
> 
> I disabled selinux - that made no difference
> I stopped and disabled firewalld  - that made no difference.
> 
> I can boot this machine after I turn it off and then back on, but when I
> try to do a shutdown now -r, the system hangs right after picking the OS
> that is desired "CentOS Linux..".
> 
> After the machine is turned off the boot process occurs normally after
> this choice and I get two penguins in the upper left hand corner, and
> the boot proceeds.  When I do a shutdown now -r, I do not get to the
> penguins and the machine hangs forever until I either unplug it or press
> the power button for 5 seconds.
> 
> Any help would be appreciated!!!
> 
> Greg 
> 
---

Everyone, 

I did not get much of a response on the list so I filed a bug report.  I
wanted to document the bug report for anyone else that is having a
reboot problem. 

https://bugs.centos.org/view.php?id=7949


Greg Ennis


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

Re: [CentOS] OpenJDK 8 on CentOS 7

[Fernando Cassia]

On Mon, Dec 1, 2014 at 3:23 PM, Fernando Cassia  wrote:

> Two ideas:
>
> 1. OpenJDK 8 is available as a "technology preview" for CentOS 6.6, or so
> this article claims
>
> http://news.softpedia.com/news/CentOS-6-6-Features-OpenJDK-8-Support-463730.shtml
>
> 2. Since Oracle Linux is userland-binary compatible with RHEL and CentOS,
> I think you will eventually surely get a build by Oracle for OL7 that you
> can run in your CentOS if you want.
>
> Of course #2 is only wishful thinking on my part.
>

A third one: you can bug Henri Gomez to include CentOS 7 / OL 7 into his
OBuildFactory script.

https://github.com/hgomez/obuildfactory

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

Re: [CentOS] OpenJDK 8 on CentOS 7

[Fernando Cassia]

On Sat, Nov 29, 2014 at 12:11 PM, Arun Gupta  wrote:

> Do you know the timelines by which it will be included in CentOS 7.0 ?
>
> Any place where a binary build can be downloaded ?
>

Two ideas:

1. OpenJDK 8 is available as a "technology preview" for CentOS 6.6, or so
this article claims
http://news.softpedia.com/news/CentOS-6-6-Features-OpenJDK-8-Support-463730.shtml

2. Since Oracle Linux is userland-binary compatible with RHEL and CentOS, I
think you will eventually surely get a build by Oracle for OL7 that you can
run in your CentOS if you want.

Of course #2 is only wishful thinking on my part.

Just my $0.02 of course.
FC
-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
- George Orwell
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SEtroubleshootd Crashing

[Daniel J Walsh]

On 12/01/2014 10:39 AM, Gary Smithson wrote:
> We are currently running libxml2-2.7.6-14.el6_5.2.x86_64
>
> How far back would you suggest we go? would libxml2-2.7.6-14.el6_5.1.x86_64 
> be sufficient
Ok might not be related.  One other suggestion would be to clear the
database out.  And see if there
was something in the database that was causing it problems.

Make sure there is no setroubleshootd running and

>/var/lib/setroubleshoot/setroubleshoot_database.xml
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf 
> Of Daniel J Walsh
> Sent: 01 December 2014 15:10
> To: CentOS mailing list
> Subject: Re: [CentOS] SEtroubleshootd Crashing
>
> I am not sure.  I was just seeing email on this today.  Could you try to 
> downgrade the latest version of libxml to see if the problem goes away.
>
> On 12/01/2014 10:01 AM, Gary Smithson wrote:
>> Thanks
>>
>> Could you please clarify, which version libxml is broken and has there been 
>> a newer version released that will fix it.
>>
>> -Original Message-
>> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
>> Behalf Of Daniel J Walsh
>> Sent: 01 December 2014 14:58
>> To: CentOS mailing list
>> Subject: Re: [CentOS] SEtroubleshootd Crashing
>>
>> This seems to be a problem with an updated version of libxml.
>> On 11/28/2014 09:04 AM, Gary Smithson wrote:
>>> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 
>>> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 
>>> x86_64 x86_64 GNU/Linux), with SELinux enabled in permissive mode we 
>>> receive a large number of entries in the audit.log and setroubleshootd 
>>> randomly crashes with the following error, We have resolved the selinux 
>>> alerts by following the troubleshooting steps recommend by running 
>>> sealert,However we are concerned by setroubleshootd crashing and are 
>>> concered that we may have masked the issue by fixing the entries in the 
>>> audit.log.
>>>
>>>
>>>
>>> abrt_version:   2.0.8
>>>
>>> cmdline:/usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
>>>
>>> executable: /usr/sbin/setroubleshootd
>>>
>>> kernel: 2.6.32-431.23.3.el6.x86_64
>>>
>>> last_occurrence: 1417101625
>>>
>>> time:   Thu 27 Nov 2014 03:20:25 PM UTC
>>>
>>> uid:0
>>>
>>> username:   root
>>>
>>>
>>>
>>> sosreport.tar.xz: Binary file, 3642240 bytes
>>>
>>>
>>>
>>> backtrace:
>>>
>>> :analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature
>>> not found
>>>
>>> :
>>>
>>> :Traceback (most recent call last):
>>>
>>> :  File
>>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>>> 401, in auto_save_callback
>>>
>>> :self.save()
>>>
>>> :  File
>>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>>> 377, in save
>>>
>>> :self.prune()
>>>
>>> :  File
>>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>>> 340, in prune
>>>
>>> :self.delete_signature(sig, prune=True)
>>>
>>> :  File
>>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>>> 471, in delete_signature
>>>
>>> :siginfo = self.lookup_signature(sig)
>>>
>>> :  File
>>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>>> 426, in lookup_signature
>>>
>>> :raise ProgramError(ERR_NO_SIGNATURE_MATCH)
>>>
>>> :ProgramError: [Errno 1001] signature not found
>>>
>>> :
>>>
>>> :Local variables in innermost frame:
>>>
>>> :matches: []
>>>
>>> :siginfo: None
>>>
>>> :self: >> 0x151d590>
>>>
>>> :sig: 
>>>
>>>
>>>
>>> We are running the following versions Passenger/htttpd/node
>>>
>>>
>>> passenger --version
>>>
>>> Phusion Passenger version 4.0.53
>>>
>>>
>>> httpd -v
>>> Server version: Apache/2.2.15 (Unix)
>>> Server built:   Jul 23 2014 14:17:29
>>>
>>>
>>> node -v
>>> v0.10.32
>>>
>>> This email is from the Press Association. For more information, see 
>>> www.pressassociation.com. This email may contain confidential information. 
>>> Only the addressee is permitted to read, copy, distribute or otherwise use 
>>> this email or any attachments. If you have received it in error, please 
>>> contact the sender immediately. Any opinion expressed in this email is 
>>> personal to the sender and may not reflect the opinion of the Press 
>>> Association. Any email reply to this address may be subject to interception 
>>> or monitoring for operational reasons or for lawful business practices.
>>> ___
>>> 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
>>
>> This email is from the Press Association. For more information, see 
>> www.pressassociation.com. This email may contain confidential information. 
>> Only the addressee is permitted to read, copy, distr

Re: [CentOS] SEtroubleshootd Crashing

[Gary Smithson]

We are currently running libxml2-2.7.6-14.el6_5.2.x86_64

How far back would you suggest we go? would libxml2-2.7.6-14.el6_5.1.x86_64 be 
sufficient

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Daniel J Walsh
Sent: 01 December 2014 15:10
To: CentOS mailing list
Subject: Re: [CentOS] SEtroubleshootd Crashing

I am not sure.  I was just seeing email on this today.  Could you try to 
downgrade the latest version of libxml to see if the problem goes away.

On 12/01/2014 10:01 AM, Gary Smithson wrote:
> Thanks
>
> Could you please clarify, which version libxml is broken and has there been a 
> newer version released that will fix it.
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Daniel J Walsh
> Sent: 01 December 2014 14:58
> To: CentOS mailing list
> Subject: Re: [CentOS] SEtroubleshootd Crashing
>
> This seems to be a problem with an updated version of libxml.
> On 11/28/2014 09:04 AM, Gary Smithson wrote:
>> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 
>> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 
>> x86_64 GNU/Linux), with SELinux enabled in permissive mode we receive a 
>> large number of entries in the audit.log and setroubleshootd randomly 
>> crashes with the following error, We have resolved the selinux alerts by 
>> following the troubleshooting steps recommend by running sealert,However we 
>> are concerned by setroubleshootd crashing and are concered that we may have 
>> masked the issue by fixing the entries in the audit.log.
>>
>>
>>
>> abrt_version:   2.0.8
>>
>> cmdline:/usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
>>
>> executable: /usr/sbin/setroubleshootd
>>
>> kernel: 2.6.32-431.23.3.el6.x86_64
>>
>> last_occurrence: 1417101625
>>
>> time:   Thu 27 Nov 2014 03:20:25 PM UTC
>>
>> uid:0
>>
>> username:   root
>>
>>
>>
>> sosreport.tar.xz: Binary file, 3642240 bytes
>>
>>
>>
>> backtrace:
>>
>> :analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature
>> not found
>>
>> :
>>
>> :Traceback (most recent call last):
>>
>> :  File
>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>> 401, in auto_save_callback
>>
>> :self.save()
>>
>> :  File
>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>> 377, in save
>>
>> :self.prune()
>>
>> :  File
>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>> 340, in prune
>>
>> :self.delete_signature(sig, prune=True)
>>
>> :  File
>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>> 471, in delete_signature
>>
>> :siginfo = self.lookup_signature(sig)
>>
>> :  File
>> "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line
>> 426, in lookup_signature
>>
>> :raise ProgramError(ERR_NO_SIGNATURE_MATCH)
>>
>> :ProgramError: [Errno 1001] signature not found
>>
>> :
>>
>> :Local variables in innermost frame:
>>
>> :matches: []
>>
>> :siginfo: None
>>
>> :self: > 0x151d590>
>>
>> :sig: 
>>
>>
>>
>> We are running the following versions Passenger/htttpd/node
>>
>>
>> passenger --version
>>
>> Phusion Passenger version 4.0.53
>>
>>
>> httpd -v
>> Server version: Apache/2.2.15 (Unix)
>> Server built:   Jul 23 2014 14:17:29
>>
>>
>> node -v
>> v0.10.32
>>
>> This email is from the Press Association. For more information, see 
>> www.pressassociation.com. This email may contain confidential information. 
>> Only the addressee is permitted to read, copy, distribute or otherwise use 
>> this email or any attachments. If you have received it in error, please 
>> contact the sender immediately. Any opinion expressed in this email is 
>> personal to the sender and may not reflect the opinion of the Press 
>> Association. Any email reply to this address may be subject to interception 
>> or monitoring for operational reasons or for lawful business practices.
>> ___
>> 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
>
> This email is from the Press Association. For more information, see 
> www.pressassociation.com. This email may contain confidential information. 
> Only the addressee is permitted to read, copy, distribute or otherwise use 
> this email or any attachments. If you have received it in error, please 
> contact the sender immediately. Any opinion expressed in this email is 
> personal to the sender and may not reflect the opinion of the Press 
> Association. Any email reply to this address may be subject to interception 
> or monitoring for operational reasons or for lawful business practices.
> ___
> CentOS mailing list
> CentOS@cent

[CentOS] [OT] Searching for SNetTerm author

[James B. Byrne]

Our firm is constrained by the requirements of an upstream VAN to use a
software package called SNetTerm; an MS-Windows based enhanced SSH
communications program.  SNetTerm is from a corporation called InterSoft
International, Inc.  This firm's web site was last accessible in June 2014 and
is now 'Under Construction' (in much the same way as restaurants are 'Under
Renovation' I suspect).  I have tried tracking down an email address but
everything to do with InterSoft International, Inc. appears out of date.  The
phone number I have has been disconnected.  So, I have little hope of getting
any response from the business.

However, the author of SNEtTerm is/was Kenneth Robinette.  I cannot seem track
him down on LinkedIn or FB (the one profile I found that appeared promising
has been locked from viewing). So, in desperation, I am asking if anyone has
any lead to contacting this person and can either provided it directly to me
or contact Mr. Robinette and have him contact me then I would be greatly
appreciative.

If anyone has any information respecting the fate of InterSoft International,
Inc. and their products then I would appreciate if you would sshare that as
well.

Sincerely,



-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

[CentOS] A gmane mystery

[Timothy Murphy]

I've been collecting redhat.fedora from gmane for several years,
but about a week ago I found that while I could read gmane newsgroups
I was unable to post to them - that is, my posts did not appear.

I was able to post to gmane.test, and could read these posts.
So I assume there is no problem with my From: or other headers.

I take it that the gmane.linux.centos.general is in fact
"mirroring" the mailman mailing list 

Assuming this is so, I don't know
whether the problem lies with the list or with the newsgroup?
I seem to be properly subscribed to the mailing list,
with my current email address.

Any enlightenment or advice gratefully received.

-- 
Timothy Murphy  
gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
School of Mathematics, Trinity College, Dublin


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

Re: [CentOS] SEtroubleshootd Crashing

[Daniel J Walsh]

I am not sure.  I was just seeing email on this today.  Could you try to
downgrade the latest version of libxml to see if the
problem goes away.

On 12/01/2014 10:01 AM, Gary Smithson wrote:
> Thanks
>
> Could you please clarify, which version libxml is broken and has there been a 
> newer version released that will fix it.
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf 
> Of Daniel J Walsh
> Sent: 01 December 2014 14:58
> To: CentOS mailing list
> Subject: Re: [CentOS] SEtroubleshootd Crashing
>
> This seems to be a problem with an updated version of libxml.
> On 11/28/2014 09:04 AM, Gary Smithson wrote:
>> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 
>> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 
>> x86_64 GNU/Linux), with SELinux enabled in permissive mode we receive a 
>> large number of entries in the audit.log and setroubleshootd randomly 
>> crashes with the following error, We have resolved the selinux alerts by 
>> following the troubleshooting steps recommend by running sealert,However we 
>> are concerned by setroubleshootd crashing and are concered that we may have 
>> masked the issue by fixing the entries in the audit.log.
>>
>>
>>
>> abrt_version:   2.0.8
>>
>> cmdline:/usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
>>
>> executable: /usr/sbin/setroubleshootd
>>
>> kernel: 2.6.32-431.23.3.el6.x86_64
>>
>> last_occurrence: 1417101625
>>
>> time:   Thu 27 Nov 2014 03:20:25 PM UTC
>>
>> uid:0
>>
>> username:   root
>>
>>
>>
>> sosreport.tar.xz: Binary file, 3642240 bytes
>>
>>
>>
>> backtrace:
>>
>> :analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature not 
>> found
>>
>> :
>>
>> :Traceback (most recent call last):
>>
>> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
>> 401, in auto_save_callback
>>
>> :self.save()
>>
>> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
>> 377, in save
>>
>> :self.prune()
>>
>> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
>> 340, in prune
>>
>> :self.delete_signature(sig, prune=True)
>>
>> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
>> 471, in delete_signature
>>
>> :siginfo = self.lookup_signature(sig)
>>
>> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
>> 426, in lookup_signature
>>
>> :raise ProgramError(ERR_NO_SIGNATURE_MATCH)
>>
>> :ProgramError: [Errno 1001] signature not found
>>
>> :
>>
>> :Local variables in innermost frame:
>>
>> :matches: []
>>
>> :siginfo: None
>>
>> :self: 
>>
>> :sig: 
>>
>>
>>
>> We are running the following versions Passenger/htttpd/node
>>
>>
>> passenger --version
>>
>> Phusion Passenger version 4.0.53
>>
>>
>> httpd -v
>> Server version: Apache/2.2.15 (Unix)
>> Server built:   Jul 23 2014 14:17:29
>>
>>
>> node -v
>> v0.10.32
>>
>> This email is from the Press Association. For more information, see 
>> www.pressassociation.com. This email may contain confidential information. 
>> Only the addressee is permitted to read, copy, distribute or otherwise use 
>> this email or any attachments. If you have received it in error, please 
>> contact the sender immediately. Any opinion expressed in this email is 
>> personal to the sender and may not reflect the opinion of the Press 
>> Association. Any email reply to this address may be subject to interception 
>> or monitoring for operational reasons or for lawful business practices.
>> ___
>> 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
>
> This email is from the Press Association. For more information, see 
> www.pressassociation.com. This email may contain confidential information. 
> Only the addressee is permitted to read, copy, distribute or otherwise use 
> this email or any attachments. If you have received it in error, please 
> contact the sender immediately. Any opinion expressed in this email is 
> personal to the sender and may not reflect the opinion of the Press 
> Association. Any email reply to this address may be subject to interception 
> or monitoring for operational reasons or for lawful business practices.
> ___
> 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] SEtroubleshootd Crashing

[Gary Smithson]

Thanks

Could you please clarify, which version libxml is broken and has there been a 
newer version released that will fix it.

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
Daniel J Walsh
Sent: 01 December 2014 14:58
To: CentOS mailing list
Subject: Re: [CentOS] SEtroubleshootd Crashing

This seems to be a problem with an updated version of libxml.
On 11/28/2014 09:04 AM, Gary Smithson wrote:
> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 
> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 
> x86_64 GNU/Linux), with SELinux enabled in permissive mode we receive a large 
> number of entries in the audit.log and setroubleshootd randomly crashes with 
> the following error, We have resolved the selinux alerts by following the 
> troubleshooting steps recommend by running sealert,However we are concerned 
> by setroubleshootd crashing and are concered that we may have masked the 
> issue by fixing the entries in the audit.log.
>
>
>
> abrt_version:   2.0.8
>
> cmdline:/usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
>
> executable: /usr/sbin/setroubleshootd
>
> kernel: 2.6.32-431.23.3.el6.x86_64
>
> last_occurrence: 1417101625
>
> time:   Thu 27 Nov 2014 03:20:25 PM UTC
>
> uid:0
>
> username:   root
>
>
>
> sosreport.tar.xz: Binary file, 3642240 bytes
>
>
>
> backtrace:
>
> :analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature not 
> found
>
> :
>
> :Traceback (most recent call last):
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 401, in auto_save_callback
>
> :self.save()
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 377, in save
>
> :self.prune()
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 340, in prune
>
> :self.delete_signature(sig, prune=True)
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 471, in delete_signature
>
> :siginfo = self.lookup_signature(sig)
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 426, in lookup_signature
>
> :raise ProgramError(ERR_NO_SIGNATURE_MATCH)
>
> :ProgramError: [Errno 1001] signature not found
>
> :
>
> :Local variables in innermost frame:
>
> :matches: []
>
> :siginfo: None
>
> :self: 
>
> :sig: 
>
>
>
> We are running the following versions Passenger/htttpd/node
>
>
> passenger --version
>
> Phusion Passenger version 4.0.53
>
>
> httpd -v
> Server version: Apache/2.2.15 (Unix)
> Server built:   Jul 23 2014 14:17:29
>
>
> node -v
> v0.10.32
>
> This email is from the Press Association. For more information, see 
> www.pressassociation.com. This email may contain confidential information. 
> Only the addressee is permitted to read, copy, distribute or otherwise use 
> this email or any attachments. If you have received it in error, please 
> contact the sender immediately. Any opinion expressed in this email is 
> personal to the sender and may not reflect the opinion of the Press 
> Association. Any email reply to this address may be subject to interception 
> or monitoring for operational reasons or for lawful business practices.
> ___
> 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

This email is from the Press Association. For more information, see 
www.pressassociation.com. This email may contain confidential information. Only 
the addressee is permitted to read, copy, distribute or otherwise use this 
email or any attachments. If you have received it in error, please contact the 
sender immediately. Any opinion expressed in this email is personal to the 
sender and may not reflect the opinion of the Press Association. Any email 
reply to this address may be subject to interception or monitoring for 
operational reasons or for lawful business practices.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SEtroubleshootd Crashing

[Daniel J Walsh]

This seems to be a problem with an updated version of libxml.
On 11/28/2014 09:04 AM, Gary Smithson wrote:
> When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 
> 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 
> x86_64 GNU/Linux), with SELinux enabled in permissive mode we receive a large 
> number of entries in the audit.log and setroubleshootd randomly crashes with 
> the following error, We have resolved the selinux alerts by following the 
> troubleshooting steps recommend by running sealert,However we are concerned 
> by setroubleshootd crashing and are concered that we may have masked the 
> issue by fixing the entries in the audit.log.
>
>
>
> abrt_version:   2.0.8
>
> cmdline:/usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
>
> executable: /usr/sbin/setroubleshootd
>
> kernel: 2.6.32-431.23.3.el6.x86_64
>
> last_occurrence: 1417101625
>
> time:   Thu 27 Nov 2014 03:20:25 PM UTC
>
> uid:0
>
> username:   root
>
>
>
> sosreport.tar.xz: Binary file, 3642240 bytes
>
>
>
> backtrace:
>
> :analyze.py:426:lookup_signature:ProgramError: [Errno 1001] signature not 
> found
>
> :
>
> :Traceback (most recent call last):
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 401, in auto_save_callback
>
> :self.save()
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 377, in save
>
> :self.prune()
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 340, in prune
>
> :self.delete_signature(sig, prune=True)
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 471, in delete_signature
>
> :siginfo = self.lookup_signature(sig)
>
> :  File "/usr/lib64/python2.6/site-packages/setroubleshoot/analyze.py", line 
> 426, in lookup_signature
>
> :raise ProgramError(ERR_NO_SIGNATURE_MATCH)
>
> :ProgramError: [Errno 1001] signature not found
>
> :
>
> :Local variables in innermost frame:
>
> :matches: []
>
> :siginfo: None
>
> :self: 
>
> :sig: 
>
>
>
> We are running the following versions Passenger/htttpd/node
>
>
> passenger --version
>
> Phusion Passenger version 4.0.53
>
>
> httpd -v
> Server version: Apache/2.2.15 (Unix)
> Server built:   Jul 23 2014 14:17:29
>
>
> node -v
> v0.10.32
>
> This email is from the Press Association. For more information, see 
> www.pressassociation.com. This email may contain confidential information. 
> Only the addressee is permitted to read, copy, distribute or otherwise use 
> this email or any attachments. If you have received it in error, please 
> contact the sender immediately. Any opinion expressed in this email is 
> personal to the sender and may not reflect the opinion of the Press 
> Association. Any email reply to this address may be subject to interception 
> or monitoring for operational reasons or for lawful business practices.
> ___
> 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] CentOS6 gvfs disk thrashing

[isdtor]

I believe I have found the problem. CentOS version in use here is 6.4,
and it seems 6.6 has the updated packages.

https://bugzilla.gnome.org/show_bug.cgi?id=637095
https://bugzilla.redhat.com/show_bug.cgi?id=561904
https://rhn.redhat.com/errata/RHBA-2014-1499.html

I have no access to BZ#902448, but there's some interesting reading in
those bug reports ...
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] System Hangs At Anaconda Detecting Hardware

[Ashish Yadav]

Hi,

On Mon, Dec 1, 2014 at 8:58 AM, Mark LaPierre  wrote:

> Hey All,
>
> I just assembled a new machine.
>
> Mother Board:   Gigabyte 78LMT-USB3
> Processor:  AMD FX8350
> Memory: Corsair CMZ16GX3M2A1600C10 2x8 GB
> Video:  BFG Tech Nvidia GeForce 9600 GT
>
> I tried the 6.6 x86_64 netinstall disk.
> I tried the 6.6 x86_64 install DVD
>
> Both fail at the same place:
>
> Anaconda installer init version 13.21.229 starting
> mounting /proc filesystem... done
> creating /dev filesystem... done
> starting udev...udev[175]: error setting /sys/class/firmware/timeout: No
> such file or directory
> done
>
> mounting /dev/pts (unix98 pty) filesystem... done
> mouning /sys filesystem... done
> trying to remount root fiesystem read write... done
> mounting /tmp as tmpfs... done
> running install...
> running /sbin/loader
> detecting hardware...
>
> That's all she wrote!
>
> The BIOS detects the 500 GB hard drive, the CD/DVD drive, 16 GB of RAM,
> all eight cores on the CPU, and boots from the CD/DVD.  Then it just
> hangs at detecting hardware.
>
>
> http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.6#head-aa1d1d1c4e306596f8ae129e016ef1f95fc7c36e
>
> Says:
> "The netinstall isos do not work with UEFI installs, but the minimal or
> DVD isos do work with UEFI. No versions of CentOS-6.6 will work with
> Secure Boot turned on. Secure Boot must be disabled to install CentOS-6.6."
>
> I see nothing in the MB documentation about "Secure Boot" enabled or
> disabled.  Also not a word about UEFI.
>
> Any suggestions anyone?
>

Please make sure that your BIOS firmware is up to date. Have you checked
that?


>
> --
> _
>°v°
>   /(_)\
>^ ^  Mark LaPierre
> Registered Linux user No #267004
> https://linuxcounter.net/
> 
> ___
> 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] CentOS6 gvfs disk thrashing

[isdtor]

On 25/11/2014, isdtor  wrote:
> We recently started upgrading users' workstations to CentOS6. Now
> we've come across an interesting issue:
> ~user/.local/share/gvfs-metadata is filling up with tons of files.
> Once there are around 69270 of them, no more are being created, and
> the NetApp filer the user's home is on logs:
>
> Directory /user/.local/share/gvfs-metadata/ reached the maxdirsize
> limit. Reduce the number of files or use the vol options command to
> increase this limit..
>
> Nearly all of the files are exactly 32k in size and they are named
> .openXX. All of them are being created within the same range of
> timestamps, with a time that's in the past. I.e. even when deleted,
> they are being recreated with these timestamps.
>
> drwx-- 2 user group 5353472 Nov 15 17:39 ./
> drwxr-xr-x 5 user group4096 Oct 29 11:05 ../
> -rw-r--r-- 25699 user group   32768 Nov 11 17:11 .open0018OX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open0019OX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open002EPX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open002GPX
> -rw-r--r-- 25699 user group   32768 Nov 11 17:11 .open002OPX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open0037OX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open003MPX
> -rw-r--r-- 42962 user group   32768 Nov 11 17:10 .open004NPX
> -rw-r--r-- 25699 user group   32768 Nov 11 17:11 .open0067OX
>
> According to lsof, the only processes operating in this directory are
> a few instances of nautilus and /usr/libexec/gvfsd-metadata. There's a
> whole bunch of gvfs* processes running
>
> user 21209 1  0 Nov11 ?00:00:00 /usr/libexec/gvfsd
> user 21549 1  0 Nov11 ?00:03:17
> /usr/libexec/gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
> user 21788 1  0 Nov11 ?00:00:06
> /usr/libexec/gvfs-gdu-volume-monitor
> user 21829 1  0 Nov11 ?00:00:00
> /usr/libexec/gvfs-gphoto2-volume-monitor
> user 21849 1  0 Nov11 ?00:00:25
> /usr/libexec/gvfs-afc-volume-monitor
> user 22150 1  0 Nov11 ?00:00:00 /usr/libexec/gvfsd-metadata
> user 22323 1  0 Nov11 ?00:00:00
> /usr/libexec/gvfsd-burn --spawner :1.2 /org/gtk/gvfs/exec_spaw/1
>
> Does anyone have an idea what's going on here? And how to stop it?

The more machines we're moving to CentOS6, the more urgent this
problems becomes. Is there any suggestion what could be causing this
behavior?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos