Re: [CentOS] 7.2 kernel panic on boot

[Duncan Brown]

On 06/12/2015 01:12, Marcelo Ricardo Leitner wrote:

Em 05-12-2015 05:35, Duncan Brown escreveu:

On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote:

Em 03-12-2015 14:46, Duncan Brown escreveu:

Here is a couple of pictures,

http://i.imgur.com/Vqvqn1H.jpg
http://i.imgur.com/WQaz1j9.png

Any use?


Of some. It's failing on ftrace initialization while allocating
memory, but can't know the real reason. It can be just lack of memory
or any other bug.

Probably by that stage of the boot, framebuffer is already loaded. Use
vga=0x317 boot option to get a bigger resolution and more lines on it,
then send another pic.

I hope it fits this time. If not, pick 0x31A, if your monitor allows.

(kernel src, Documentation/fb/vesafb.txt)
| 640x480  800x600  1024x768 1280x1024
+-
256 |  0x3010x3030x3050x307
32k |  0x3100x3130x3160x319
64k |  0x3110x3140x3170x31A
16M |  0x3120x3150x3180x31B

  Marcelo

___

Hi Marcelo

Thanks for the suggestion

I've worked through a decent selection and cant get any to show a higher
resolution than it's currently at, in fact most just leave me with a
blank screen

Note I can change the resolution all I want if I boot via the previous
kernel


Damn :-(
Serial cable then? heh

Cheers,
Marcelo

Yeah I've got a nice little usb one I can hook directly into a raspberry 
pi on the way


I'm totally expecting this to get fixed in a kernel update before the 
thing even arrives, but it'll be a good learning experience and will 
probably be useful in the future!



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

Re: [CentOS-es] Cluster - Como empezar?

[A.Rubio]

igual te puede servir

http://www.cursovirtualizacion.es/


El vie, 04-12-2015 a las 22:49 -0300, Diego Sanchez escribió:
> Encontré el link que tenía en favoritos.
> Te dejo esto, nunca llegué a probarlo
> 
> http://blog.secaserver.com/2012/12/high-availability-cpanel-mysql-cluster/
> (En inglés)
> 
> El viernes, 4 de diciembre de 2015, Diego Sanchez 
> escribió:
> 
> > CPanel no soporta cluster para los sitios.
> > Si soporta DNS en cluster y algunas pocas configuraciones más por ahora.
> >
> > Tal vez sea posible, pero seguramente manoseando mucho cPanel...y no creo
> > que el soporte lo cubra
> >
> > PD; ando buscando lo mismo... desde hace 5 años..
> >
> >
> > El viernes, 4 de diciembre de 2015, Diego Valencia <
> > diegovalencia1...@gmail.com
> > > escribió:
> >
> >> Buen día,
> >>
> >> Actualmente cuento con 3 servidores Dell R710 con CentOs7, estos
> >> servidores
> >> los utilizo para el hosting de paginas de Internet, actualmente uso el
> >> sistema cPanel/WHM.
> >>
> >> Cada servidor tiene sistema Operativo y el software de cPanel de manera
> >> independiente, actualmente pago las 3 licencias, y me recomendaron
> >> realizar
> >> un Cluster con los 3 servidores para unificar mi sistema y hacerlo mas
> >> eficiente.
> >>
> >> Por lo que recurro a ustedes, que puedan ayudarme con algún tutorial,
> >> asesoría, curso, diagramas, etc... que me pueda ayudar a crear un Cluster
> >> con estos 3 servidores.
> >>
> >> De antemano agradezco su ayuda.
> >> ___
> >> CentOS-es mailing list
> >> CentOS-es@centos.org
> >> https://lists.centos.org/mailman/listinfo/centos-es
> >>
> >
> >
> > --
> > Diego - Yo no soy paranoico! (pero que me siguen, me siguen)
> >
> 
> 


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

Re: [CentOS] Centos 7 Yum conflict libicalss

[Earl Ramirez]

On Sat, 2015-12-05 at 17:39 -0800, david wrote:
> Folks
> 
> My Centos 7 systems are all failing to update because of
> 
> Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
> Requires: libicalss.so.0()(64bit)
> Removing: libical-0.48-6.el7.x86_64 (@base)
> libicalss.so.0()(64bit)
> Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>~libicalss.so.1()(64bit)
> Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
> Requires: libicalvcal.so.0()(64bit)
> Removing: libical-0.48-6.el7.x86_64 (@base)
> libicalvcal.so.0()(64bit)
> Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>~libicalvcal.so.1()(64bit)
> Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
> Requires: libical.so.0()(64bit)
> Removing: libical-0.48-6.el7.x86_64 (@base)
> libical.so.0()(64bit)
> Updated By: libical-1.0.1-1.el7.x86_64 (cr)
>~libical.so.1()(64bit)
>   You could try using --skip-broken to work around the problem
>   You could try running: rpm -Va --nofiles --nodigest
> 
> 
> Is there something I should (not) be doing?
> The command was:
>yum update
> 
> 
> 
> David
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

Hello David, 

The conflict is caused by 'orage' from epel, I am not to familiar with
that package, you can try and uninstall it and run 'yum clean all' and
try to update your box again. Or you can exclude it from epel repo. 


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

Re: [CentOS] 7.2 kernel panic on boot

[Johnny Hughes]

On 12/04/2015 12:46 PM, Greg Lindahl wrote:
> On Fri, Dec 04, 2015 at 12:06:14PM +, Karanbir Singh wrote:
> 
>> i dont see it being dropped, on my completely updated machine i still
>> see the fully qualified numbering in /etc/centos-release ( as an example ) ?
> 
> I know this is a big, confused thread, but the main complaint is that
> the website has dropped the fully qualified numbering:
> 
> https://www.google.com/#q=%227.1.1503%27+site:centos.org
> 
> vs
> 
> https://www.google.com/#q=%227+1503%27+site:centos.org
> 
> The first is "7.1.1503" and has 895 results, and they aren't html
> pages, they're things like directories containing that string.
> 
> The second is strings like "7 (1503)", and has 1,700+ results, and
> they are the html pages.
> 

Puppet, Chef, Ansible and the other CFG Management systems work with the
current numbering system like it is now, we have no intention of
changing it ever again.

Not only that, but all the cloud images that we produce for Google
Compute, Amazon AWS, OpenNebula, Vagrant, etc, work.

Our docker containers work and this works with the CentOS Atomic Host
within Project Atomic.  It works in OpenHPC.

People can still get and use CentOS-7, it is completely free and it also
works completely with every major public cloud and private onsite cloud
setup.

Our community build system for SIGs is functioning and producing
software in several SIGS (https://cbs.centos.org/).

In the Virt SIG we have Xen for CentOS-6 in production with
XenProject.org taking the lead on that (http://bit.ly/1jFYLUe) (there
are also testing RPMs for CentOS-7).  There are oVirt RPMs for the last
2 releases also in the Virt SIG (http://bit.ly/1XJJ2X4).

CentOS Atomic Host is available here:  (http://bit.ly/1XJIvEl)

The Software Collections SIG is producing RPMs as well
(http://bit.ly/1m3Jmid).  Both SCLs and the Dev Tool Sets.

In our AltArch SIG ee have a beta build of ppc64le and ppc64 in (with
IBM helping with that build) as well released i686 and AArch64 arches
(http://bit.ly/1OMOWyX). We will have an Arm32 release very soon as well.

There are RDO Packages being produced for both openstack-kilo and
openstack-liberty in the Cloud SIG (http://bit.ly/21FmFl6).

The Storage SIG has 2 releases of GlusterFS Packages
(http://bit.ly/1Q7cXUA).

The bottom line is, our numbering system works for us to be able to do
all those things.

This is much more complicated than just a name on an ISO and I don't
think that we really need to discuss it at every singe CentOS-7 point
release for the next 8 years.

The CentOS-7 Base OS is still there, it is free for anyone to use, it is
being maintained as always.  If you don't want to use it, great.  That
is your choice.

However, CentOS is more open and more community driven now that it ever
has been .. while still maintaining our Base OS trees.

Thanks,
Johnny Hughes




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

Re: [CentOS] 7.2 kernel panic on boot

[Always Learning]

I always admire Johnny's prose, passion for Centos and his calm approach
to everything.

He is right. We are stuck with the numbering system.

On Sat, 2015-12-05 at 12:46 -0600, Johnny Hughes wrote:

> The bottom line is, our numbering system works for us to be able to do
> all those things.
> 
> This is much more complicated than just a name on an ISO and I don't
> think that we really need to discuss it at every singe CentOS-7 point
> release for the next 8 years.

Once thing is for certain, Centos has expanded significantly and now
offers an increasing variety of exciting/interesting computer solutions.

Centos on Android tablets would be really nice.

Happy Christmas everyone and a successful and prosperous New Year


-- 

Paul.
England, EU.

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

Re: [CentOS] 7.2 kernel panic on boot

[Marcelo Ricardo Leitner]

Em 05-12-2015 05:35, Duncan Brown escreveu:

On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote:

Em 03-12-2015 14:46, Duncan Brown escreveu:

Here is a couple of pictures,

http://i.imgur.com/Vqvqn1H.jpg
http://i.imgur.com/WQaz1j9.png

Any use?


Of some. It's failing on ftrace initialization while allocating
memory, but can't know the real reason. It can be just lack of memory
or any other bug.

Probably by that stage of the boot, framebuffer is already loaded. Use
vga=0x317 boot option to get a bigger resolution and more lines on it,
then send another pic.

I hope it fits this time. If not, pick 0x31A, if your monitor allows.

(kernel src, Documentation/fb/vesafb.txt)
| 640x480  800x600  1024x768 1280x1024
+-
256 |  0x3010x3030x3050x307
32k |  0x3100x3130x3160x319
64k |  0x3110x3140x3170x31A
16M |  0x3120x3150x3180x31B

  Marcelo

___

Hi Marcelo

Thanks for the suggestion

I've worked through a decent selection and cant get any to show a higher
resolution than it's currently at, in fact most just leave me with a
blank screen

Note I can change the resolution all I want if I boot via the previous
kernel


Damn :-(
Serial cable then? heh

Cheers,
Marcelo

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

Re: [CentOS] 7.2 kernel panic on boot

[Greg Lindahl]

> > The first is "7.1.1503" and has 895 results, and they aren't html
> > pages, they're things like directories containing that string.
> > 
> > The second is strings like "7 (1503)", and has 1,700+ results, and
> > they are the html pages.
> > 
> 
> Puppet, Chef, Ansible and the other CFG Management systems work with the
> current numbering system like it is now, we have no intention of
> changing it ever again.

I'm suggesting that you use 7.1.1503 instead of 7 (1503) *on the
website*. I don't think that Puppet, Chef, Ansible, or any other
configuration management system parses webpages. They look at things
like /etc/centos-release, which is 7.1.1503, and I think that's fine.

I am not suggesting that you revert to 7.1.

> The CentOS-7 Base OS is still there, it is free for anyone to use, it is
> being maintained as always.  If you don't want to use it, great.  That
> is your choice.

CentOS: love it or leave it! My new employer uses Debian for their
large cluster.

-- greg

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

[CentOS] Centos 7 Yum conflict libicalss

[david]

Folks

My Centos 7 systems are all failing to update because of

Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
   Requires: libicalss.so.0()(64bit)
   Removing: libical-0.48-6.el7.x86_64 (@base)
   libicalss.so.0()(64bit)
   Updated By: libical-1.0.1-1.el7.x86_64 (cr)
  ~libicalss.so.1()(64bit)
Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
   Requires: libicalvcal.so.0()(64bit)
   Removing: libical-0.48-6.el7.x86_64 (@base)
   libicalvcal.so.0()(64bit)
   Updated By: libical-1.0.1-1.el7.x86_64 (cr)
  ~libicalvcal.so.1()(64bit)
Error: Package: orage-4.10.0-4.el7.x86_64 (@epel)
   Requires: libical.so.0()(64bit)
   Removing: libical-0.48-6.el7.x86_64 (@base)
   libical.so.0()(64bit)
   Updated By: libical-1.0.1-1.el7.x86_64 (cr)
  ~libical.so.1()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Is there something I should (not) be doing?
The command was:
  yum update



David

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