Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[Kay Schenk]

On Mon, Jul 13, 2020, 02:35 José María Terry Jiménez 
wrote:

> El 13/7/20 a las 0:50, Kay Schenk escribió:
> >>   With your current setup in mind, do you know the modem internal
> >> IP? With that, set your computer's IP to be in the same network,
> >> verify the default route, and see if you can reach out to the modem.
> >>
> > I did this with a new network profile and activated it, but no good. I
> need
> > some info/tools on examining my "network" I think.
> >
> >
> >> Personally I would have the router between the two, but that is
> >> changing the problem instead of helping you fix yours.
> >>
> > Actually the router WAS between the modem and my desktop until I took
> > things apart and the router Was not part of the equation. I wanted to
> > verify the setup I had with JUST the modem, but I am at a loss on how to
> > get CentOS7 to access a "local" url on the same local network without
> > getting the "no network" business.
> >
> > Thank you for your suggestions.
> >
> > Regards,
> > Kay
> >
> As Mauricio said you must be in the same network that the DSL modem:
>
> Some considerations:
>
> I assume this is an Ethernet one and not USB one, right?
>
> Which IP are you trying to access?
>
> What is the computer IP and netmask?
>
> Did you tried to connect the MODEM directly to computer and set the IP
> to DHCP? Then look the IP you got and the gateway ( ip address show |
> grep -i "inet\ " **OR** ifconfig |grep -i "inet\ " ) and the default
> gateway ( ip route show | grep -i default )
>
> The "usual" would be you try to access the MODEM in your gateway
> address, but may be other.
>
> The maker and model of MODEM would be great
>
> Good luck
>
> Best!
>

Well I thought I had made some progress yesterday and was actually able to
ping my computer AND the old DSL modem. Unfortunately, I think my network
card has actually died now. 

Switched back to an old Ethernet cable and same result.

Thanks for all the help. My research led me to all sorts of useful
information on network naming schemes.

Regards,

Kay


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

Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[José María Terry Jiménez]

El 13/7/20 a las 0:50, Kay Schenk escribió:
>>   With your current setup in mind, do you know the modem internal
>> IP? With that, set your computer's IP to be in the same network,
>> verify the default route, and see if you can reach out to the modem.
>>
> I did this with a new network profile and activated it, but no good. I need
> some info/tools on examining my "network" I think.
>
>
>> Personally I would have the router between the two, but that is
>> changing the problem instead of helping you fix yours.
>>
> Actually the router WAS between the modem and my desktop until I took
> things apart and the router Was not part of the equation. I wanted to
> verify the setup I had with JUST the modem, but I am at a loss on how to
> get CentOS7 to access a "local" url on the same local network without
> getting the "no network" business.
>
> Thank you for your suggestions.
>
> Regards,
> Kay
>
As Mauricio said you must be in the same network that the DSL modem:

Some considerations:

I assume this is an Ethernet one and not USB one, right?

Which IP are you trying to access?

What is the computer IP and netmask?

Did you tried to connect the MODEM directly to computer and set the IP
to DHCP? Then look the IP you got and the gateway ( ip address show |
grep -i "inet\ " **OR** ifconfig |grep -i "inet\ " ) and the default
gateway ( ip route show | grep -i default )

The "usual" would be you try to access the MODEM in your gateway
address, but may be other.

The maker and model of MODEM would be great

Good luck

Best!


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

Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[Kay Schenk]

See inline...

On Sun, Jul 12, 2020, 12:47 Mauricio Tavares  wrote:

> On Sun, Jul 12, 2020 at 3:39 PM Kay Schenk  wrote:
> >
> > On Sun, Jul 12, 2020, 12:31 Mauricio Tavares 
> wrote:
> >
> > > On Sun, Jul 12, 2020 at 3:15 PM Kay Schenk 
> wrote:
> > > >
> > > > Hello all--
> > > > I'm in a bind trying to reset an older Nether DSL modem. I did a
> manual
> > > > reset on it. It was set up as "pass thru" by me and I want to "undo"
> > > that.
> > > > When I boot now, the joys of Network Manager!, I can not just enter
> the
> > > > modem manager IP address because I keep getting "network not
> accessible"
> > > .
> > > > HELP!
> > > >
> > >   Dumb question: is the modem directly connected to computer or
> > > attached to a router?
> > >
> >
> > Currently the modem is only attached to my computer. The modem WAS
> attached
> > to a router in pass thru mode. I did a reset on the modem which should
> have
> > gotten it back to "normal" modem mode. Now it's directly connected to my
> > desktop -- no router. Once upon a time I could directly access the modem
> > interface through my browser, now I can not.
> >
>   With your current setup in mind, do you know the modem internal
> IP? With that, set your computer's IP to be in the same network,
> verify the default route, and see if you can reach out to the modem.
>

I did this with a new network profile and activated it, but no good. I need
some info/tools on examining my "network" I think.


> Personally I would have the router between the two, but that is
> changing the problem instead of helping you fix yours.
>

Actually the router WAS between the modem and my desktop until I took
things apart and the router Was not part of the equation. I wanted to
verify the setup I had with JUST the modem, but I am at a loss on how to
get CentOS7 to access a "local" url on the same local network without
getting the "no network" business.

Thank you for your suggestions.

Regards,
Kay


> > > ___
> > > > Sent from MzK's phone.
> > > > ___
> > > > CentOS mailing list
> > > > CentOS@centos.org
> > > > https://lists.centos.org/mailman/listinfo/centos
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos
> > >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
Sent from MzK's phone.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[Mauricio Tavares]

On Sun, Jul 12, 2020 at 3:39 PM Kay Schenk  wrote:
>
> On Sun, Jul 12, 2020, 12:31 Mauricio Tavares  wrote:
>
> > On Sun, Jul 12, 2020 at 3:15 PM Kay Schenk  wrote:
> > >
> > > Hello all--
> > > I'm in a bind trying to reset an older Nether DSL modem. I did a manual
> > > reset on it. It was set up as "pass thru" by me and I want to "undo"
> > that.
> > > When I boot now, the joys of Network Manager!, I can not just enter the
> > > modem manager IP address because I keep getting "network not accessible"
> > .
> > > HELP!
> > >
> >   Dumb question: is the modem directly connected to computer or
> > attached to a router?
> >
>
> Currently the modem is only attached to my computer. The modem WAS attached
> to a router in pass thru mode. I did a reset on the modem which should have
> gotten it back to "normal" modem mode. Now it's directly connected to my
> desktop -- no router. Once upon a time I could directly access the modem
> interface through my browser, now I can not.
>
  With your current setup in mind, do you know the modem internal
IP? With that, set your computer's IP to be in the same network,
verify the default route, and see if you can reach out to the modem.

Personally I would have the router between the two, but that is
changing the problem instead of helping you fix yours.

> > ___
> > > Sent from MzK's phone.
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://lists.centos.org/mailman/listinfo/centos
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[Kay Schenk]

On Sun, Jul 12, 2020, 12:31 Mauricio Tavares  wrote:

> On Sun, Jul 12, 2020 at 3:15 PM Kay Schenk  wrote:
> >
> > Hello all--
> > I'm in a bind trying to reset an older Nether DSL modem. I did a manual
> > reset on it. It was set up as "pass thru" by me and I want to "undo"
> that.
> > When I boot now, the joys of Network Manager!, I can not just enter the
> > modem manager IP address because I keep getting "network not accessible"
> .
> > HELP!
> >
>   Dumb question: is the modem directly connected to computer or
> attached to a router?
>

Currently the modem is only attached to my computer. The modem WAS attached
to a router in pass thru mode. I did a reset on the modem which should have
gotten it back to "normal" modem mode. Now it's directly connected to my
desktop -- no router. Once upon a time I could directly access the modem
interface through my browser, now I can not.

> ___
> > Sent from MzK's phone.
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need HELP with old DSL modem setup on CentOS 7

[Mauricio Tavares]

On Sun, Jul 12, 2020 at 3:15 PM Kay Schenk  wrote:
>
> Hello all--
> I'm in a bind trying to reset an older Nether DSL modem. I did a manual
> reset on it. It was set up as "pass thru" by me and I want to "undo" that.
> When I boot now, the joys of Network Manager!, I can not just enter the
> modem manager IP address because I keep getting "network not accessible" .
> HELP!
>
  Dumb question: is the modem directly connected to computer or
attached to a router?
> ___
> Sent from MzK's phone.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Need HELP with old DSL modem setup on CentOS 7

[Kay Schenk]

Hello all--
I'm in a bind trying to reset an older Nether DSL modem. I did a manual
reset on it. It was set up as "pass thru" by me and I want to "undo" that.
When I boot now, the joys of Network Manager!, I can not just enter the
modem manager IP address because I keep getting "network not accessible" .
HELP!

___
Sent from MzK's phone.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help to fix bug in rsync

[Simon Matter via CentOS]

> I appreciate the reply - it keeps me from wondering "is there something I
> should be concerned about?".  We use a co-location facility where we pay
> for bandwidth utilization so it's still an issue.

Hi,

You are right, bandwidth always costs, always.

Who pays for it can differ a lot, but there is always someone who pays.

It can be an individual, a company, the tax payer, whoever, but bandwidth
is never free.

Thanks,
Simon

>
> 
> From: CentOS  on behalf of Pete Biggs
> 
> Sent: Wednesday, March 25, 2020 1:32 PM
> To: centos@centos.org 
> Subject: [EXTERNAL] Re: [CentOS] Need help to fix bug in rsync
>
>
> Harriscomputer
>
> Leroy Tennison
> Network Information/Cyber Security Specialist
> E: le...@datavoiceint.com
>
>
> [cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]
>
>
> 2220 Bush Dr
> McKinney, Texas
> 75070
> www.datavoiceint.com<http://www..com>
>
>
> This message has been sent on behalf of a company that is part of the
> Harris Operating Group of Constellation Software Inc.
>
> If you prefer not to be contacted by Harris Operating Group please notify
> us<http://subscribe.harriscomputer.com/>.
>
>
>
> This message is intended exclusively for the individual or entity to which
> it is addressed. This communication may contain information that is
> proprietary, privileged or confidential or otherwise legally exempt from
> disclosure. If you are not the named addressee, you are not authorized to
> read, print, retain, copy or disseminate this message or any part of it.
> If you have received this message in error, please notify the sender
> immediately by e-mail and delete all copies of the message.
>
>
>
>
>
> On Wed, 2020-03-25 at 19:15 +0100, Simon Matter via CentOS wrote:
>> > On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
>> > > Since you state that using -z is almost always a bad idea, could you
>> > > provide the rationale for that?  I must be missing something.
>> > >
>> > I think the "rationale" is that at some point the
>> > compression/decompression takes longer than the time reduction from
>> > sending a compressed file.  It depends on the relative speeds of the
>> > machines and the network.
>> >
>> > You have most to gain from compressing large files, but if they are
>> > already compressed, then you have nothing to gain from just doing
>> small
>> > files.
>> >
>> > It obviously depends on your network speed and if you have a metered
>> > connection, but does anyone really have such an ancient network
>> > connection still these days - I mean if you have fast enough machines
>> > at both ends to do rapid compression/decompression, it seems unlikely
>> > that you will have a damp piece of string connecting them.
>>
>> I really don't understand the discussion here. What is wrong with using
>> -z
>> with rsync? We're using rsync with -z for backups and just don't want to
>> waste bandwidth for nothing. We have better use for our bandwidth and it
>> makes quite a difference when backing up terabytes of data.
>
> I don't really care if you use -z, but you asked for the rationale, and
> I gave you it. I'm not telling you what you should do.
>
> I'll try and make it simpler - if rsync takes 1 second to compress the
> file, then 1 second to decompress the file, and the whole transfer of
> the file takes 11 seconds uncompressed vs 10 seconds compressed, then
> dealing with file takes overall 12 seconds compressed, vs 11 seconds
> uncompressed. It's not worth it.
>
> But as I said it depends on your network and your machine speeds.  It's
> up to you to decide what is best in your own situation.
>
> P.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


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

Re: [CentOS] Need help to fix bug in rsync

[Simon Matter via CentOS]

> On Wed, Mar 25, 2020 at 02:49:24PM +0100, Simon Matter via CentOS wrote:
>> Hi,
>>
>> I've discovered a bug in rsync which leads to increased CPU usage and
>> slower transfers in many situations.
>>
>> When syncing with compression (-z), certain file types should not be
>> compressed during the transfer because they are already compressed. The
>> file types which are not to be compressed can be seen in the man page
>> section --skip-compress.
>>
>> Unfortunately skipping the default file types doesn't work and all
>> transferred data is being compressed during the transfer. This is true
>> for
>> all versions since 3.1.0.
>>
>> Steps to Reproduce:
>> 1. run 'rm -f Z ; rsync -azv alpha:z.gz Z'
>>
>> Actual results, transferred data was compressed during the transfer:
>> sent 43 bytes  received 63,873 bytes  25,566.40 bytes/sec
>> total size is 628,952  speedup is 9.84
>>
>> Expected results:
>> No compression should happen for .gz file.
>>
>> Additional info:
>> Note that the source file 'z.gz' was an ascii text file to show clearly
>> that compression took place.
>
> That may invalidate your testing.
>
> rsync may not depend upon the filename extension
> but instead check the magic numbers within the file
> to determine whether to compress or not.

One could think so but it's not the case, rsync just uses the file suffix
to decide which files to compress. It even lower cases them, leaving good
old UNIX .Z file behind... Also a bug IMHO but not so important.

Simon

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

Re: [CentOS] Need help to fix bug in rsync

[Jon LaBadie]

On Wed, Mar 25, 2020 at 02:49:24PM +0100, Simon Matter via CentOS wrote:
> Hi,
> 
> I've discovered a bug in rsync which leads to increased CPU usage and
> slower transfers in many situations.
> 
> When syncing with compression (-z), certain file types should not be
> compressed during the transfer because they are already compressed. The
> file types which are not to be compressed can be seen in the man page
> section --skip-compress.
> 
> Unfortunately skipping the default file types doesn't work and all
> transferred data is being compressed during the transfer. This is true for
> all versions since 3.1.0.
> 
> Steps to Reproduce:
> 1. run 'rm -f Z ; rsync -azv alpha:z.gz Z'
> 
> Actual results, transferred data was compressed during the transfer:
> sent 43 bytes  received 63,873 bytes  25,566.40 bytes/sec
> total size is 628,952  speedup is 9.84
> 
> Expected results:
> No compression should happen for .gz file.
> 
> Additional info:
> Note that the source file 'z.gz' was an ascii text file to show clearly
> that compression took place.

That may invalidate your testing.

rsync may not depend upon the filename extension
but instead check the magic numbers within the file
to determine whether to compress or not.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help to fix bug in rsync

[Leon Fauster via CentOS]

Am 25.03.20 um 19:15 schrieb Simon Matter via CentOS:

On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:

Since you state that using -z is almost always a bad idea, could you
provide the rationale for that?  I must be missing something.


I think the "rationale" is that at some point the
compression/decompression takes longer than the time reduction from
sending a compressed file.  It depends on the relative speeds of the
machines and the network.

You have most to gain from compressing large files, but if they are
already compressed, then you have nothing to gain from just doing small
files.

It obviously depends on your network speed and if you have a metered
connection, but does anyone really have such an ancient network
connection still these days - I mean if you have fast enough machines
at both ends to do rapid compression/decompression, it seems unlikely
that you will have a damp piece of string connecting them.


I really don't understand the discussion here. What is wrong with using -z
with rsync? We're using rsync with -z for backups and just don't want to
waste bandwidth for nothing. We have better use for our bandwidth and it
makes quite a difference when backing up terabytes of data.

The only reason why I asked for help is because we don't want to double
compress data which is already compressed. This is what currently is
broken in rsync without manually specifying a skip-compress list. Fixing
it would help all those who don't know it's broken now.



Until this is fixed; as a workaround I would do a two-pass transfer with
filters via ".rsync-filter" file and then using rsync -azvF for
everything with high compression ratio and rsync -av for all, including
compressed data.
So, ".rsync-filter" includes the exclude statements for compressed
formats. This all makes only sense if the compression ratio is higher
then the meta data transfer of the second run ...

--
Leon


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

Re: [CentOS] Need help to fix bug in rsync

[Leroy Tennison]

I appreciate the reply - it keeps me from wondering "is there something I 
should be concerned about?".  We use a co-location facility where we pay for 
bandwidth utilization so it's still an issue.


From: CentOS  on behalf of Pete Biggs 

Sent: Wednesday, March 25, 2020 1:32 PM
To: centos@centos.org 
Subject: [EXTERNAL] Re: [CentOS] Need help to fix bug in rsync


Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com


[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]


2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>


This message has been sent on behalf of a company that is part of the Harris 
Operating Group of Constellation Software Inc.

If you prefer not to be contacted by Harris Operating Group please notify 
us<http://subscribe.harriscomputer.com/>.



This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential or otherwise legally exempt from disclosure. If you 
are not the named addressee, you are not authorized to read, print, retain, 
copy or disseminate this message or any part of it. If you have received this 
message in error, please notify the sender immediately by e-mail and delete all 
copies of the message.





On Wed, 2020-03-25 at 19:15 +0100, Simon Matter via CentOS wrote:
> > On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
> > > Since you state that using -z is almost always a bad idea, could you
> > > provide the rationale for that?  I must be missing something.
> > >
> > I think the "rationale" is that at some point the
> > compression/decompression takes longer than the time reduction from
> > sending a compressed file.  It depends on the relative speeds of the
> > machines and the network.
> >
> > You have most to gain from compressing large files, but if they are
> > already compressed, then you have nothing to gain from just doing small
> > files.
> >
> > It obviously depends on your network speed and if you have a metered
> > connection, but does anyone really have such an ancient network
> > connection still these days - I mean if you have fast enough machines
> > at both ends to do rapid compression/decompression, it seems unlikely
> > that you will have a damp piece of string connecting them.
>
> I really don't understand the discussion here. What is wrong with using -z
> with rsync? We're using rsync with -z for backups and just don't want to
> waste bandwidth for nothing. We have better use for our bandwidth and it
> makes quite a difference when backing up terabytes of data.

I don't really care if you use -z, but you asked for the rationale, and
I gave you it. I'm not telling you what you should do.

I'll try and make it simpler - if rsync takes 1 second to compress the
file, then 1 second to decompress the file, and the whole transfer of
the file takes 11 seconds uncompressed vs 10 seconds compressed, then
dealing with file takes overall 12 seconds compressed, vs 11 seconds
uncompressed. It's not worth it.

But as I said it depends on your network and your machine speeds.  It's
up to you to decide what is best in your own situation.

P.


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

Re: [CentOS] Need help to fix bug in rsync

[Leroy Tennison]

That's why I asked, I wanted to know if there was something inherently bad with 
"-z".  I had a situation where Postgresql was replicating 16M files every few 
minutes ("log shipping") on approximately 10 systems, got behind which resulted 
in almost continuous file transfer (of mostly null 16M files) and saturated the 
common link.  Specifying compression with file transfer cut transmission time 
by 5-10x resolving the problem.


From: CentOS  on behalf of Simon Matter via CentOS 

Sent: Wednesday, March 25, 2020 1:15 PM
To: CentOS mailing list 
Subject: [EXTERNAL] Re: [CentOS] Need help to fix bug in rsync



Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com


[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]


2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>


This message has been sent on behalf of a company that is part of the Harris 
Operating Group of Constellation Software Inc.

If you prefer not to be contacted by Harris Operating Group please notify 
us<http://subscribe.harriscomputer.com/>.



This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential or otherwise legally exempt from disclosure. If you 
are not the named addressee, you are not authorized to read, print, retain, 
copy or disseminate this message or any part of it. If you have received this 
message in error, please notify the sender immediately by e-mail and delete all 
copies of the message.





t; On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
>> Since you state that using -z is almost always a bad idea, could you
>> provide the rationale for that?  I must be missing something.
>>
> I think the "rationale" is that at some point the
> compression/decompression takes longer than the time reduction from
> sending a compressed file.  It depends on the relative speeds of the
> machines and the network.
>
> You have most to gain from compressing large files, but if they are
> already compressed, then you have nothing to gain from just doing small
> files.
>
> It obviously depends on your network speed and if you have a metered
> connection, but does anyone really have such an ancient network
> connection still these days - I mean if you have fast enough machines
> at both ends to do rapid compression/decompression, it seems unlikely
> that you will have a damp piece of string connecting them.

I really don't understand the discussion here. What is wrong with using -z
with rsync? We're using rsync with -z for backups and just don't want to
waste bandwidth for nothing. We have better use for our bandwidth and it
makes quite a difference when backing up terabytes of data.

The only reason why I asked for help is because we don't want to double
compress data which is already compressed. This is what currently is
broken in rsync without manually specifying a skip-compress list. Fixing
it would help all those who don't know it's broken now.

Thanks,
Simon

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

Re: [CentOS] Need help to fix bug in rsync

[Pete Biggs]

On Wed, 2020-03-25 at 19:15 +0100, Simon Matter via CentOS wrote:
> > On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
> > > Since you state that using -z is almost always a bad idea, could you
> > > provide the rationale for that?  I must be missing something.
> > > 
> > I think the "rationale" is that at some point the
> > compression/decompression takes longer than the time reduction from
> > sending a compressed file.  It depends on the relative speeds of the
> > machines and the network.
> > 
> > You have most to gain from compressing large files, but if they are
> > already compressed, then you have nothing to gain from just doing small
> > files.
> > 
> > It obviously depends on your network speed and if you have a metered
> > connection, but does anyone really have such an ancient network
> > connection still these days - I mean if you have fast enough machines
> > at both ends to do rapid compression/decompression, it seems unlikely
> > that you will have a damp piece of string connecting them.
> 
> I really don't understand the discussion here. What is wrong with using -z
> with rsync? We're using rsync with -z for backups and just don't want to
> waste bandwidth for nothing. We have better use for our bandwidth and it
> makes quite a difference when backing up terabytes of data.

I don't really care if you use -z, but you asked for the rationale, and
I gave you it. I'm not telling you what you should do.

I'll try and make it simpler - if rsync takes 1 second to compress the
file, then 1 second to decompress the file, and the whole transfer of
the file takes 11 seconds uncompressed vs 10 seconds compressed, then
dealing with file takes overall 12 seconds compressed, vs 11 seconds
uncompressed. It's not worth it. 

But as I said it depends on your network and your machine speeds.  It's
up to you to decide what is best in your own situation.

P.


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

Re: [CentOS] Need help to fix bug in rsync

[Simon Matter via CentOS]

> On Wed, 25 Mar 2020, Leroy Tennison wrote:
>
>> Since you state that using -z is almost always a bad idea, could you
>> provide the rationale for that?  I must be missing something.
>
> I can't speak to that, but the obvious workaround is to use ssh's
> compression instead of rsync's:
>
> rsync -av -e 'ssh -C' remotehost:remote.file local.file

>From what I understand that's not really the same as having compression
inside rsync makes rsync transfers even better than only compressing the
transport.

Thanks,
Simon

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

Re: [CentOS] Need help to fix bug in rsync

[Simon Matter via CentOS]

> On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
>> Since you state that using -z is almost always a bad idea, could you
>> provide the rationale for that?  I must be missing something.
>>
> I think the "rationale" is that at some point the
> compression/decompression takes longer than the time reduction from
> sending a compressed file.  It depends on the relative speeds of the
> machines and the network.
>
> You have most to gain from compressing large files, but if they are
> already compressed, then you have nothing to gain from just doing small
> files.
>
> It obviously depends on your network speed and if you have a metered
> connection, but does anyone really have such an ancient network
> connection still these days - I mean if you have fast enough machines
> at both ends to do rapid compression/decompression, it seems unlikely
> that you will have a damp piece of string connecting them.

I really don't understand the discussion here. What is wrong with using -z
with rsync? We're using rsync with -z for backups and just don't want to
waste bandwidth for nothing. We have better use for our bandwidth and it
makes quite a difference when backing up terabytes of data.

The only reason why I asked for help is because we don't want to double
compress data which is already compressed. This is what currently is
broken in rsync without manually specifying a skip-compress list. Fixing
it would help all those who don't know it's broken now.

Thanks,
Simon

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

Re: [CentOS] Need help to fix bug in rsync

[Paul Heinlein]

On Wed, 25 Mar 2020, Leroy Tennison wrote:

Since you state that using -z is almost always a bad idea, could you 
provide the rationale for that?  I must be missing something.


I can't speak to that, but the obvious workaround is to use ssh's
compression instead of rsync's:

rsync -av -e 'ssh -C' remotehost:remote.file local.file

--
Paul Heinlein
heinl...@madboa.com
45°38' N, 122°6' W
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help to fix bug in rsync

[Pete Biggs]

On Wed, 2020-03-25 at 14:39 +, Leroy Tennison wrote:
> Since you state that using -z is almost always a bad idea, could you
> provide the rationale for that?  I must be missing something.
> 
I think the "rationale" is that at some point the
compression/decompression takes longer than the time reduction from
sending a compressed file.  It depends on the relative speeds of the
machines and the network.

You have most to gain from compressing large files, but if they are
already compressed, then you have nothing to gain from just doing small
files.

It obviously depends on your network speed and if you have a metered
connection, but does anyone really have such an ancient network
connection still these days - I mean if you have fast enough machines
at both ends to do rapid compression/decompression, it seems unlikely
that you will have a damp piece of string connecting them.

P.

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

Re: [CentOS] Need help to fix bug in rsync

[Leroy Tennison]

Since you state that using -z is almost always a bad idea, could you provide 
the rationale for that?  I must be missing something.


From: CentOS  on behalf of Peter Kjellström 

Sent: Wednesday, March 25, 2020 9:34 AM
To: Simon Matter 
Cc: centos@centos.org 
Subject: [EXTERNAL] Re: [CentOS] Need help to fix bug in rsync

On Wed, 25 Mar 2020 14:49:24 +0100
Simon Matter via CentOS  wrote:

> Hi,
>
> I've discovered a bug in rsync which leads to increased CPU usage and
> slower transfers in many situations.
>
> When syncing with compression (-z)

Tbh, using -z with rsync is almost always a bad idea (unless you're on
some pre-historic type of network link..).

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

Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com


[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]


2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>


This message has been sent on behalf of a company that is part of the Harris 
Operating Group of Constellation Software Inc.

If you prefer not to be contacted by Harris Operating Group please notify 
us<http://subscribe.harriscomputer.com/>.



This message is intended exclusively for the individual or entity to which it 
is addressed. This communication may contain information that is proprietary, 
privileged or confidential or otherwise legally exempt from disclosure. If you 
are not the named addressee, you are not authorized to read, print, retain, 
copy or disseminate this message or any part of it. If you have received this 
message in error, please notify the sender immediately by e-mail and delete all 
copies of the message.




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

Re: [CentOS] Need help to fix bug in rsync

[Peter Kjellström]

On Wed, 25 Mar 2020 14:49:24 +0100
Simon Matter via CentOS  wrote:

> Hi,
> 
> I've discovered a bug in rsync which leads to increased CPU usage and
> slower transfers in many situations.
> 
> When syncing with compression (-z)

Tbh, using -z with rsync is almost always a bad idea (unless you're on
some pre-historic type of network link..).

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

[CentOS] Need help to fix bug in rsync

[Simon Matter via CentOS]

Hi,

I've discovered a bug in rsync which leads to increased CPU usage and
slower transfers in many situations.

When syncing with compression (-z), certain file types should not be
compressed during the transfer because they are already compressed. The
file types which are not to be compressed can be seen in the man page
section --skip-compress.

Unfortunately skipping the default file types doesn't work and all
transferred data is being compressed during the transfer. This is true for
all versions since 3.1.0.

Steps to Reproduce:
1. run 'rm -f Z ; rsync -azv alpha:z.gz Z'

Actual results, transferred data was compressed during the transfer:
sent 43 bytes  received 63,873 bytes  25,566.40 bytes/sec
total size is 628,952  speedup is 9.84

Expected results:
No compression should happen for .gz file.

Additional info:
Note that the source file 'z.gz' was an ascii text file to show clearly
that compression took place.

Please the following BZ for more info:
https://bugzilla.samba.org/show_bug.cgi?id=14323
https://bugzilla.redhat.com/show_bug.cgi?id=1816528

I tried to locate the bug in the code but failed. That said I'm not a C
developer and therefore need some help from someone who understands C
better than me. Any help is much appreciated!

Thanks and kind regards,
Simon

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

Re: [CentOS] Need help modding src.rpms to generate complete SAMBA AD DC binary RPMs for CentOS 8

[Stephen John Smoogen]

On Sat, 9 Nov 2019 at 01:13, Robert G (Doc) Savage via CentOS
 wrote:
>
> When RHEL8 and CentOS8 were released, I was looking forward to setting
> up SAMBA as a AD DC server for CentOS8. But when I lifed the hood on
> the samba.spec file I found the option to build the samba-dc binary rpm
> has been disabled for rhel family builds.
>
> Apparently Red Hat does not want to support a unified SAMBA AD DC
> environment. I believe we have all of the componentns needed to set up
> a fully up-to-date samba-dc binary. But it's been decades since I last
> rolled up my sleeves with my hardbound copy of "Maximum RPM" and built
> custom binary rpms.
>

You need Heimdal which neither CentOS or RHEL ship but as others have
said, (and other threads in lists have been going on) Nico Kadell has
a set of RPMS with everything you need
https://github.com/nkadel/samba4repo

> Has anyone already done this as a COPR or similar project? Failing
> that, I'm willing to work with anyone with more up-to-date rpmbuild
> tools to create and document the process.
>
> --Doc Savage
>   Fairview Heights, IL
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos



-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help modding src.rpms to generate complete SAMBA AD DC binary RPMs for CentOS 8

[me]

On Sat, 9 Nov 2019, Robert G (Doc) Savage via CentOS wrote:


When RHEL8 and CentOS8 were released, I was looking forward to setting
up SAMBA as a AD DC server for CentOS8. But when I lifed the hood on
the samba.spec file I found the option to build the samba-dc binary rpm
has been disabled for rhel family builds.

Apparently Red Hat does not want to support a unified SAMBA AD DC
environment. I believe we have all of the componentns needed to set up
a fully up-to-date samba-dc binary. But it's been decades since I last
rolled up my sleeves with my hardbound copy of "Maximum RPM" and built
custom binary rpms.

Has anyone already done this as a COPR or similar project? Failing
that, I'm willing to work with anyone with more up-to-date rpmbuild
tools to create and document the process.


You might want to take a look at https://github.com/nkadel/samba4repo

In addition, you might want to join the samba list over at samba.org.

There are a few other doing rpms for centos also. I do not use them
but maybe it will help.

Regards,

--
Tom m...@tdiehl.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Need help modding src.rpms to generate complete SAMBA AD DC binary RPMs for CentOS 8

[Robert G (Doc) Savage via CentOS]

When RHEL8 and CentOS8 were released, I was looking forward to setting
up SAMBA as a AD DC server for CentOS8. But when I lifed the hood on
the samba.spec file I found the option to build the samba-dc binary rpm
has been disabled for rhel family builds.

Apparently Red Hat does not want to support a unified SAMBA AD DC
environment. I believe we have all of the componentns needed to set up
a fully up-to-date samba-dc binary. But it's been decades since I last
rolled up my sleeves with my hardbound copy of "Maximum RPM" and built
custom binary rpms.

Has anyone already done this as a COPR or similar project? Failing
that, I'm willing to work with anyone with more up-to-date rpmbuild
tools to create and document the process.

--Doc Savage
  Fairview Heights, IL

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

Re: [CentOS] Need help with Linux networking interfaces and NIC bonding

[Gordon Messmer]

On 10/3/18 10:44 PM, Sean Son wrote:

1) Whenever I ping any of the devices on our network, from this server, the
traffic goes out from the management port. I do not want the traffic to go
out of the management port. I want it to go out through the active port of
the NIC bond.  How do I configure the networking so that all primary
network traffic flows to and from the NIC bonded interfaces?  I only want
the management port to be used for SSH purposes and well, management of the
server.



First:  You never mentioned updating /etc/iproute2/rt_tables. Did you 
create an entry there for table "t1"?  If you haven't done that, then 
your alternate routing table and your rules aren't loading.  Run "ip 
route show" and "ip route show table t1" to make sure they both exist.


Second: I agree with Anand.  You should remove the default route from 
your management interface ifcfg file, and add one to the primary 
device.  Use the rules and alternate route tables for the management 
interface *if* it needs a default route at all.  If it's only supposed 
to communicate with other devices in the management network (which is 
typical, in the systems I've managed), then it shouldn't need a default 
route at all.


Third: When you are multi-homed, you should be selecting a specific 
interface with "ping -I ".  Don't rely on its automatic 
detection of the appropriate interface.




2) I have configured the NIC bond in active-backup mode. I notice that when
I used another computer to do a continuous ping to the NIC bond, and then I
disable one of the slave interfaces of the bond, the ping drops and it does
not failover to the backup slave interface and turn  into the active one.



Can you define "disable" more specifically?

The up side of active-backup is that it should work with generic 
switches, without any specific support on their end.  The down side of 
active-backup is that your switches may remember the association between 
MAC address and port number for pretty much as long as they like, and 
some switches will take a *really* long time to update.




Should I even use active-backup mode with the NIC bond



That depends on what component you think might fail, and what redundancy 
exists outside the system.  In my opinion: active-backup only makes 
sense if you have separate switches, since those fail more often than 
NICs.  And it only makes sense if everything behaves well when you pull 
power from one of the switches.  If you turn off one of your switches 
and the network stops working, then you shouldn't use active-backup.




3) Ive tested the networking, by changing  the VLAN of the NIC bonded
ports, on the switch, to a different VLAN, and it caused the management
port to stop responding to ping. Why is this and how do I fix that if I
decide to one day use two different VLANs for Management and the NIC bond
ports?



Best guess: set arp_filter to "1" and wait for your switches to update 
their MAC/port mapping


https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt


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

[CentOS] Need help with Linux networking interfaces and NIC bonding

[Leroy Tennison]

I don't know if this is your situation or not but I have found in my bonding 
testing that failover can take what I consider to be an inordinate amount of 
time (as in up to 50 seconds).  Were you "patient" (possibly using an altered 
definition of the term) to see if ping would eventually reply.


Join us
at the 2018 Momentum User Conference!
Register
here
Leroy Tennison
Network Information/Cyber Security Specialist
E: le...@datavoiceint.com
2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com
TThis message has been sent on behalf
of a company that is part of the Harris Operating Group of
Constellation Software Inc. These companies are listed
here
.
If you prefer not to be contacted by Harris
Operating Group
please notify us
.
This message is intended exclusively for the
individual or entity to which it is addressed. This communication
may contain information that is proprietary, privileged or
confidential or otherwise legally exempt from disclosure. If you are
not the named addressee, you are not authorized to read, print,
retain, copy or disseminate this message or any part of it. If you
have received this message in error, please notify the sender
immediately by e-mail and delete all copies of the
message.


From: CentOS  on behalf of Sean Son 

Sent: Thursday, October 4, 2018 12:44 AM
To: CentOS mailing list
Subject: [EXTERNAL] [CentOS] Need help with Linux networking interfaces and NIC 
bonding

Hello everyone

I am running into some strange issues when configuring networking
interfaces on my physical server running Centos 7.5. Let me give you an
overview of what's going on:

We have a physical server, running CentOS 7.5. This server has one 4 port
NIC and one 2 port NIC and a Dell IDRAC port.  The first port of the 4 port
NIC, em1, is used for Management traffic. The first port of the 2 port NIC,
is used for the second port in the  NIC bond, device p6p2.  The second
port on the 4 port NIC, device em2 is the first, port on the NIC bond.

These interfaces are using Static IPs.

Here is my /etc/sysconfig/network-scripts/ifcfg-em1 file. Please keep in
mind that I have changed the IPs and MAC addresses in the files for
security reasons:

ifcfg-em1:

TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="em1"
UUID="bbb2f9c2-141b-4a99-ab1e-328551aae612"
DEVICE="em1"
ONBOOT="yes"
IPADDR="192.168.56.50"
PREFIX="24"
GATEWAY="192.168.56.1"
DNS1="192.168.126.10"
DNS2="192.168.220.10"
IPV6_PRIVACY="no"
NM_CONTROLLED=no

as for the ifcfg-bond0 (the configuration file for the NIC bond, which is
bond0):

DEVICE=bond0
NAME=bond0
TYPE=Bond
ONBOOT=yes
BOOTPROTO=none
IPADDR=192.168.56.70
PREFIX=24
BONDING_MASTER=yes
BONDING_OPT="mode=1 miimon=100"
TYPE=Ethernet

and the ifcfg-slave1 configuration file, which is the first slave port for
the NIC bond, this corresponds to em2:

DEVICE=em2
HWADDR="c8:2f:87:fg:2a:31"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
MASTER=bond0
SLAVE=yes

and the ifcfg-slave2 configuration file , which corresponds to the second
slave port for the NIC bond, which is interface p6p2:

DEVICE=p6p2
HWADDR="00:6a:d7:7c:e8:09"
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
MASTER=bond0
SLAVE=yes

I created a custom routing policy for the NIC bond, bond0. Here is the
configuration for the routing  policy:

route-bond0:


192.168.56.0/24 dev bond0 src 192.168.56.70 table t1
default via 192.168.56.1 dev bond0 table t1

and the rule-bond0 file:

table t1 from 192.168.56.70

as for the routing table:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0192.168.56.10.0.0.0 UG0  00 bond0
192.168.56.00.0.0.0 255.255.255.0   U 0  00
bond0
192.168.56.00.0.0.0 255.255.255.0   U 0  00 em1
169.254.0.0 0.0.0.0 255.255.0.0 U 1002   00 em1
169.254.0.0 0.0.0.0 255.255.0.0 U 1008   00
bond0



now here is the scenario I am dealing with:

This linux server is used for monitoring purposes. We have Nagios, Cacti
and other tools installed on it. There are a few things I have noticed and
I want help on:

1) Whenever I ping any of the devices on our network, from this server, the
traffic goes out from the management port. I do not want the traffic to go
out of the management port. I want it to go out through the active port of
the NIC bond.  How do I configure the networking so that all primary
network traffic flows to and from the NIC bonded interfaces?  I only wan

Re: [CentOS] Need help with Linux networking interfaces and NIC bonding

[Anand Buddhdev]

On 04/10/2018 07:44, Sean Son wrote:

Hi Sean,

[snip]

> 1) Whenever I ping any of the devices on our network, from this server, the
> traffic goes out from the management port. I do not want the traffic to go
> out of the management port. I want it to go out through the active port of
> the NIC bond.  How do I configure the networking so that all primary
> network traffic flows to and from the NIC bonded interfaces?  I only want
> the management port to be used for SSH purposes and well, management of the
> server.

When the server *originates* traffic, it will use the main routing
table, and that's why traffic goes out of em1. There's no rule telling
the server that when the traffic is initiated by the server, it must
consult a different routing table, t1.

One way to ensure that all the monitoring traffic goes through bond0, is
to configure every service with an explicit source address. However,
some services allow this, and some don't, so this quickly becomes
cumbersome.

What you probably want to do is to invert your rules and routes, so that
the bond0 interface is in the main table, and you put your management
interface, em1, into another table (t1). Then, when you ssh into the
server, it will use em1, but all other traffic will use bond0 by default.

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

[CentOS] Need help with Linux networking interfaces and NIC bonding

[Sean Son]

Hello everyone

I am running into some strange issues when configuring networking
interfaces on my physical server running Centos 7.5. Let me give you an
overview of what's going on:

We have a physical server, running CentOS 7.5. This server has one 4 port
NIC and one 2 port NIC and a Dell IDRAC port.  The first port of the 4 port
NIC, em1, is used for Management traffic. The first port of the 2 port NIC,
is used for the second port in the  NIC bond, device p6p2.  The second
port on the 4 port NIC, device em2 is the first, port on the NIC bond.

These interfaces are using Static IPs.

Here is my /etc/sysconfig/network-scripts/ifcfg-em1 file. Please keep in
mind that I have changed the IPs and MAC addresses in the files for
security reasons:

ifcfg-em1:

TYPE="Ethernet"
PROXY_METHOD="none"
BROWSER_ONLY="no"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
IPV6_ADDR_GEN_MODE="stable-privacy"
NAME="em1"
UUID="bbb2f9c2-141b-4a99-ab1e-328551aae612"
DEVICE="em1"
ONBOOT="yes"
IPADDR="192.168.56.50"
PREFIX="24"
GATEWAY="192.168.56.1"
DNS1="192.168.126.10"
DNS2="192.168.220.10"
IPV6_PRIVACY="no"
NM_CONTROLLED=no

as for the ifcfg-bond0 (the configuration file for the NIC bond, which is
bond0):

DEVICE=bond0
NAME=bond0
TYPE=Bond
ONBOOT=yes
BOOTPROTO=none
IPADDR=192.168.56.70
PREFIX=24
BONDING_MASTER=yes
BONDING_OPT="mode=1 miimon=100"
TYPE=Ethernet

and the ifcfg-slave1 configuration file, which is the first slave port for
the NIC bond, this corresponds to em2:

DEVICE=em2
HWADDR="c8:2f:87:fg:2a:31"
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
MASTER=bond0
SLAVE=yes

and the ifcfg-slave2 configuration file , which corresponds to the second
slave port for the NIC bond, which is interface p6p2:

DEVICE=p6p2
HWADDR="00:6a:d7:7c:e8:09"
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
MASTER=bond0
SLAVE=yes

I created a custom routing policy for the NIC bond, bond0. Here is the
configuration for the routing  policy:

route-bond0:


192.168.56.0/24 dev bond0 src 192.168.56.70 table t1
default via 192.168.56.1 dev bond0 table t1

and the rule-bond0 file:

table t1 from 192.168.56.70

as for the routing table:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0192.168.56.10.0.0.0 UG0  00 bond0
192.168.56.00.0.0.0 255.255.255.0   U 0  00
bond0
192.168.56.00.0.0.0 255.255.255.0   U 0  00 em1
169.254.0.0 0.0.0.0 255.255.0.0 U 1002   00 em1
169.254.0.0 0.0.0.0 255.255.0.0 U 1008   00
bond0



now here is the scenario I am dealing with:

This linux server is used for monitoring purposes. We have Nagios, Cacti
and other tools installed on it. There are a few things I have noticed and
I want help on:

1) Whenever I ping any of the devices on our network, from this server, the
traffic goes out from the management port. I do not want the traffic to go
out of the management port. I want it to go out through the active port of
the NIC bond.  How do I configure the networking so that all primary
network traffic flows to and from the NIC bonded interfaces?  I only want
the management port to be used for SSH purposes and well, management of the
server.

2) I have configured the NIC bond in active-backup mode. I notice that when
I used another computer to do a continuous ping to the NIC bond, and then I
disable one of the slave interfaces of the bond, the ping drops and it does
not failover to the backup slave interface and turn  into the active one.
It also causes any pings to the management  port to drop as well.  Then
when I disable slave2, and enable slave1, the traffic does not fail over to
slave1 and the ping  continuously fails.  It is only when I enable both
slave interfaces and then either restart the networking  using systemctl
restart network, or reboot the server, the networking resumes and the pings
succeed again.  What steps should I take to fix this issue?  Should I even
use active-backup mode with the NIC bond or is there a better mode I should
use?

3) Ive tested the networking, by changing  the VLAN of the NIC bonded
ports, on the switch, to a different VLAN, and it caused the management
port to stop responding to ping. Why is this and how do I fix that if I
decide to one day use two different VLANs for Management and the NIC bond
ports?


Thank you for all of your help in advance!

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

Re: [CentOS] Need help to understand about some lines which are printing on console

[(RS) Tyler Schroder]

Shagun, 

More details would be appreciated to help you out. Centos Version #, VMware 
version, VMWare tools version. 

From the forum post that Jonathan linked (copied what seemed to be the answer 
below), seems to be a RabbitMQ or VMWare tools issue. If it comes down to it, " 
narendramadanapalli" claims " CAF can be disabled without disabling VGAuth. 
Disabling CAF will not cause any functional breach in VMTools." Most likely not 
ideal though 

answer ENABLE_VGAUTH no

answer ENABLE_CAF no

 

to /etc/vmware-tools/locations, you can use the --defaults option and it works 
provided that a previous version of VMware-tools was installed successfully

..RSTS

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Jonathan Billings
Sent: Wednesday, May 30, 2018 6:18 PM
To: CentOS mailing list 
Subject: Re: [CentOS] Need help to understand about some lines which are 
printing on console

Lmgtfy returns:

https://communities.vmware.com/thread/532962

Something to do with VMware’s agent?

--
Jonathan Billings

> On May 30, 2018, at 11:38, Maheshwari, Shagun  
> wrote:
> 
> Hi,
> 
> Some lines are printing on console:
> [CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] 
> CAppConfig:: getString() Required config parameter [amqp_password] is missing 
> from section [c ommunication_amqp]
> 
> Can you help me to understand why we are getting these lines on console?
> How we can remove these lines from the console?
> 
> Please suggest.
> 
> Thanks & Regards,
> Shagun
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help to understand about some lines which are printing on console

[Jonathan Billings]

Lmgtfy returns:

https://communities.vmware.com/thread/532962

Something to do with VMware’s agent?

--
Jonathan Billings

> On May 30, 2018, at 11:38, Maheshwari, Shagun  
> wrote:
> 
> Hi,
> 
> Some lines are printing on console:
> [CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] 
> CAppConfig:: getString() Required config parameter [amqp_password] is missing 
> from section [c ommunication_amqp]
> 
> Can you help me to understand why we are getting these lines on console?
> How we can remove these lines from the console?
> 
> Please suggest.
> 
> Thanks & Regards,
> Shagun
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Need help to understand about some lines which are printing on console

[Maheshwari, Shagun]

Hi,

Some lines are printing on console:
[CCafException] CAppConf@[1711]: CommAmqpListener: [CCafException] CAppConfig:: 
getString() Required config parameter [amqp_password] is missing from section 
[c ommunication_amqp]

Can you help me to understand why we are getting these lines on console?
How we can remove these lines from the console?

Please suggest.

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

Re: [CentOS] Need help: I219-v driver issue in centos 7 installation

[dibyendukoley1]

Sir, Thank you for your help. After kernel update network card start
working. Thank you for your help....

On Sat, 28 Apr 2018, 22:15 Phil Perry,  wrote:

> On 28/04/18 16:21, dibyendukoley1 wrote:
> > Sir,
> > This are the output.
> > [root@localhost ~]# lspci -nn| grep -i Ethernet
> > 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection
> > (7) I219-V [8086:15bc] (rev 10)
> >
>
> Support for your device has been added to the el7.5 kernel.
>
> grep -i 8086 /lib/modules/*/modules.alias | grep -i 15bc
> /lib/modules/3.10.0-862.el7.x86_64/modules.alias:alias
> pci:v8086d15BCsv*sd*bc*sc*i* e1000e
>
>
> > [root@localhost ~]# rpm -qa kernel
> > kernel-3.10.0-693.el7.x86_64
> >
> > [root@localhost ~]# uname -a
> > Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22
> > 21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> >
>
>
> Once you update to the el7.5 kernel (kernel-3.10.0-862.el7.x86_64), your
> device will be natively supported.
>
> >
> >
> >
> >
> > On Fri, Apr 27, 2018 at 3:02 AM, Phil Perry  wrote:
> >
> >> On 26/04/18 21:49, Phil Perry wrote:
> >>
> >>> On 26/04/18 17:03, dibyendukoley1 wrote:
> >>>
>  Sir,
>  Can any one please help me to install I219-V driver.
>  The driver that is provided by intel that is for freebsd only. I have
>  tried
>  of installing e1000e driver but no luck Please help
>  Looking forward to you.
> 
> >>>
> >>>
> >>> Please show the output from:
> >>>
> >>> lspci -nn | grep -i Ethernet
> >>>
> >>>
> >> Looking at this further, the kernel e1000e driver should support your
> >> hardware as it is the latest driver available for your device, but the
> >> output above will enable us to confirm this.
> >>
> >> Are you installing the latest available version of CentOS? Please
> confirm
> >> your kernel version:
> >>
> >> rpm -qa kernel
> >> uname -a
> >>
> >> Thanks
> >>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help: I219-v driver issue in centos 7 installation

[Phil Perry]

On 28/04/18 16:21, dibyendukoley1 wrote:

Sir,
This are the output.
[root@localhost ~]# lspci -nn| grep -i Ethernet
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection
(7) I219-V [8086:15bc] (rev 10)



Support for your device has been added to the el7.5 kernel.

grep -i 8086 /lib/modules/*/modules.alias | grep -i 15bc
/lib/modules/3.10.0-862.el7.x86_64/modules.alias:alias 
pci:v8086d15BCsv*sd*bc*sc*i* e1000e




[root@localhost ~]# rpm -qa kernel
kernel-3.10.0-693.el7.x86_64

[root@localhost ~]# uname -a
Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22
21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux




Once you update to the el7.5 kernel (kernel-3.10.0-862.el7.x86_64), your 
device will be natively supported.







On Fri, Apr 27, 2018 at 3:02 AM, Phil Perry  wrote:


On 26/04/18 21:49, Phil Perry wrote:


On 26/04/18 17:03, dibyendukoley1 wrote:


Sir,
Can any one please help me to install I219-V driver.
The driver that is provided by intel that is for freebsd only. I have
tried
of installing e1000e driver but no luck Please help
Looking forward to you.




Please show the output from:

lspci -nn | grep -i Ethernet



Looking at this further, the kernel e1000e driver should support your
hardware as it is the latest driver available for your device, but the
output above will enable us to confirm this.

Are you installing the latest available version of CentOS? Please confirm
your kernel version:

rpm -qa kernel
uname -a

Thanks


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

Re: [CentOS] Need help: I219-v driver issue in centos 7 installation

[dibyendukoley1]

Sir,
This are the output.
[root@localhost ~]# lspci -nn| grep -i Ethernet
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection
(7) I219-V [8086:15bc] (rev 10)

[root@localhost ~]# rpm -qa kernel
kernel-3.10.0-693.el7.x86_64

[root@localhost ~]# uname -a
Linux localhost.localdomain 3.10.0-693.el7.x86_64 #1 SMP Tue Aug 22
21:09:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux





On Fri, Apr 27, 2018 at 3:02 AM, Phil Perry  wrote:

> On 26/04/18 21:49, Phil Perry wrote:
>
>> On 26/04/18 17:03, dibyendukoley1 wrote:
>>
>>> Sir,
>>> Can any one please help me to install I219-V driver.
>>> The driver that is provided by intel that is for freebsd only. I have
>>> tried
>>> of installing e1000e driver but no luck Please help
>>> Looking forward to you.
>>>
>>
>>
>> Please show the output from:
>>
>> lspci -nn | grep -i Ethernet
>>
>>
> Looking at this further, the kernel e1000e driver should support your
> hardware as it is the latest driver available for your device, but the
> output above will enable us to confirm this.
>
> Are you installing the latest available version of CentOS? Please confirm
> your kernel version:
>
> rpm -qa kernel
> uname -a
>
> Thanks
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help: I219-v driver issue in centos 7 installation

[Phil Perry]

On 26/04/18 21:49, Phil Perry wrote:

On 26/04/18 17:03, dibyendukoley1 wrote:

Sir,
Can any one please help me to install I219-V driver.
The driver that is provided by intel that is for freebsd only. I have 
tried

of installing e1000e driver but no luck Please help
Looking forward to you.



Please show the output from:

lspci -nn | grep -i Ethernet



Looking at this further, the kernel e1000e driver should support your 
hardware as it is the latest driver available for your device, but the 
output above will enable us to confirm this.


Are you installing the latest available version of CentOS? Please 
confirm your kernel version:


rpm -qa kernel
uname -a

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

Re: [CentOS] Need help: I219-v driver issue in centos 7 installation

[Phil Perry]

On 26/04/18 17:03, dibyendukoley1 wrote:

Sir,
Can any one please help me to install I219-V driver.
The driver that is provided by intel that is for freebsd only. I have tried
of installing e1000e driver but no luck Please help
Looking forward to you.



Please show the output from:

lspci -nn | grep -i Ethernet

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

[CentOS] Need help: I219-v driver issue in centos 7 installation

[dibyendukoley1]

Sir,
Can any one please help me to install I219-V driver.
The driver that is provided by intel that is for freebsd only. I have tried
of installing e1000e driver but no luck Please help
Looking forward to you.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Keith Keller]

On 2017-03-20, Styma, Robert (Nokia - US)  wrote:
> I am also using CentOS, but to get a bug fixed, you have to go upstream to 
> RedHat.   I think John Pierce is right, I had to change my run level to get 
> the alternate consoles to work.  I still have the machine at run level 3 
> hoping that a bug fix lets me go back to run level 5.   Other machines work 
> fine, just the 2 with the MACH64 video on the motherboard will no longer run 
> X.

In previous versions of CentOS, runlevel 5 put a virtual console on
console 7, so ctrl-alt-F7 to switch to that console might work if changing
the default runlevel is not feasible.  Note that if X is trying to do
something and not letting go of the virtual console, then you need ctrl
in addition to alt-FN because X will intercept a plain alt-FN.  (I
usually set my servers to runlevel 3 by default, so I haven't tried this
on CentOS in a while.  My Ubuntu laptop does put a console on F7 even in
runlevel 5.)

--keith

-- 
kkel...@wombat.san-francisco.ca.us


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

Re: [CentOS] Need help

[Shoshana Rosenthal]

Sent from my iPad

> On Mar 20, 2017, at 6:21 PM, Styma, Robert (Nokia - US) 
> <robert.st...@nokia.com> wrote:
> 
> I am also using CentOS, but to get a bug fixed, you have to go upstream to 
> RedHat.   I think John Pierce is right, I had to change my run level to get 
> the alternate consoles to work.  I still have the machine at run level 3 
> hoping that a bug fix lets me go back to run level 5.   Other machines work 
> fine, just the 2 with the MACH64 video on the motherboard will no longer run 
> X.
> 
> Bob S.
> 
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Rosenthal, 
> Shoshana
> Sent: Monday, March 20, 2017 2:24 PM
> To: CentOS mailing list <centos@centos.org>
> Subject: Re: [CentOS] Need help
> 
> I did try other console  and it did not work.
> I did go from 6.7 to 6.8 but with centos not redhat.
> 
> 
> On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) <
> robert.st...@nokia.com> wrote:
> 
>> Try another console like ALT-F2.  See if you have a black screen login
>> prompt.  I opened a bug with RedHat for a system that when I went from 6.7
>> to 6.8 booted but would not start the X server.  Problem was in the MACH64
>> driver.  It is missing an external symbol that the X server requires.
>> 
>> -Original Message-
>> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Leroy
>> Tennison
>> Sent: Monday, March 20, 2017 1:35 PM
>> To: centos <centos@centos.org>
>> Subject: Re: [CentOS] Need help
>> 
>> This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS
>> but the symptoms are identical.  Try 'systemctl enable
>> console-getty.service' then 'systemctl start console-getty.service' or, if
>> it is headless (serial console only), 'systemctl enable
>> serial-getty@ttyS0.service' then 'systemctl start
>> serial-getty@ttyS0.service' assuming it's ttyS0).  For VMs (specifically
>> kvm/qemu) neither of these "solutions" worked.
>> 
>> - Original Message -
>> From: "Rosenthal, Shoshana" <srosent...@cfa.harvard.edu>
>> To: "centos" <centos@centos.org>
>> Sent: Monday, March 20, 2017 3:25:06 PM
>> Subject: Re: [CentOS] Need help
>> 
>> I figured out that the system boots OK and it is possible
>> to login remotely. However the monitor does not start up.
>> 
>> Do you know how to fix it?
>> 
>> 
>> On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
>> srosent...@cfa.harvard.edu> wrote:
>> 
>>> You are right it is a Dell PowerEdge. However as I said it stops in the
>>> middle of booting with no message.
>>> 
>>> 
>>> 
>>> On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pie...@hogranch.com>
>>> wrote:
>>> 
>>>>> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>>>>> 
>>>>> I am running centos 6.8
>>>>>> The system went down when we try to reboot it we get the
>>>>>> message ST:3P7Y9Y1
>>>>>> Do you know what the problem might be.
>>>>>> 
>>>>> I'm guessing you mean the message on the front panel, which is the
>>>>> service
>>>>> tag number.
>>>>> 
>>>> 
>>>> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
>>>> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
>>>> originally running RHEL 6.5
>>>> 
>>>> indeed, you need to connect a monitor to it to determine what stage of
>>>> the boot is failing and why.
>>>> 
>>>> 
>>>> --
>>>> john r pierce, recycling bits in santa cruz
>>>> 
>>>> 
>>>> ___
>>>> CentOS mailing list
>>>> CentOS@centos.org
>>>> https://lists.centos.org/mailman/listinfo/centos
>>>> 
>>> 
>>> 
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Shoshana Rosenthal]

Yes I did try another working  console did not work

Sent from my iPad

> On Mar 20, 2017, at 5:45 PM, Richard  
> wrote:
> 
> 
> 
> 
>> Date: Monday, March 20, 2017 17:24:02 -0400
>> From: "Rosenthal, Shoshana" 
>> 
>> I did try other console  and it did not work.
>> I did go from 6.7 to 6.8 but with centos not redhat.
>> 
>> 
> 
> Did you try another monitor -- one that you know works, and that
> turns on when plugged into the outlet near the machine in question?
> Also, some monitors go to sleep, so even an otherwise working monitor
> may require a couple of taps on the attached keyboard to wake them up.
> 
> 
> 
> 
> 
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Styma, Robert (Nokia - US)]

I am also using CentOS, but to get a bug fixed, you have to go upstream to 
RedHat.   I think John Pierce is right, I had to change my run level to get the 
alternate consoles to work.  I still have the machine at run level 3 hoping 
that a bug fix lets me go back to run level 5.   Other machines work fine, just 
the 2 with the MACH64 video on the motherboard will no longer run X.

Bob S.

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Rosenthal, Shoshana
Sent: Monday, March 20, 2017 2:24 PM
To: CentOS mailing list <centos@centos.org>
Subject: Re: [CentOS] Need help

I did try other console  and it did not work.
I did go from 6.7 to 6.8 but with centos not redhat.


On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) <
robert.st...@nokia.com> wrote:

> Try another console like ALT-F2.  See if you have a black screen login
> prompt.  I opened a bug with RedHat for a system that when I went from 6.7
> to 6.8 booted but would not start the X server.  Problem was in the MACH64
> driver.  It is missing an external symbol that the X server requires.
>
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Leroy
> Tennison
> Sent: Monday, March 20, 2017 1:35 PM
> To: centos <centos@centos.org>
> Subject: Re: [CentOS] Need help
>
> This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS
> but the symptoms are identical.  Try 'systemctl enable
> console-getty.service' then 'systemctl start console-getty.service' or, if
> it is headless (serial console only), 'systemctl enable
> serial-getty@ttyS0.service' then 'systemctl start
> serial-getty@ttyS0.service' assuming it's ttyS0).  For VMs (specifically
> kvm/qemu) neither of these "solutions" worked.
>
> - Original Message -
> From: "Rosenthal, Shoshana" <srosent...@cfa.harvard.edu>
> To: "centos" <centos@centos.org>
> Sent: Monday, March 20, 2017 3:25:06 PM
> Subject: Re: [CentOS] Need help
>
> I figured out that the system boots OK and it is possible
> to login remotely. However the monitor does not start up.
>
> Do you know how to fix it?
>
>
> On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
> srosent...@cfa.harvard.edu> wrote:
>
> > You are right it is a Dell PowerEdge. However as I said it stops in the
> > middle of booting with no message.
> >
> >
> >
> > On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pie...@hogranch.com>
> > wrote:
> >
> >> On 3/20/2017 11:54 AM, Scott Robbins wrote:
> >>
> >>> I am running centos 6.8
> >>>> The system went down when we try to reboot it we get the
> >>>> message ST:3P7Y9Y1
> >>>> Do you know what the problem might be.
> >>>>
> >>> I'm guessing you mean the message on the front panel, which is the
> >>> service
> >>> tag number.
> >>>
> >>
> >> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
> >> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
> >> originally running RHEL 6.5
> >>
> >> indeed, you need to connect a monitor to it to determine what stage of
> >> the boot is failing and why.
> >>
> >>
> >> --
> >> john r pierce, recycling bits in santa cruz
> >>
> >>
> >> ___
> >> CentOS mailing list
> >> CentOS@centos.org
> >> https://lists.centos.org/mailman/listinfo/centos
> >>
> >
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Richard]

> Date: Monday, March 20, 2017 17:24:02 -0400
> From: "Rosenthal, Shoshana" 
>
> I did try other console  and it did not work.
> I did go from 6.7 to 6.8 but with centos not redhat.
> 
> 

Did you try another monitor -- one that you know works, and that
turns on when plugged into the outlet near the machine in question?
Also, some monitors go to sleep, so even an otherwise working monitor
may require a couple of taps on the attached keyboard to wake them up.






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

Re: [CentOS] Need help

[John R Pierce]

On 3/20/2017 1:25 PM, Rosenthal, Shoshana wrote:

I figured out that the system boots OK and it is possible
to login remotely. However the monitor does not start up.


set the system to boot into init state 3 (non-graphical) instead of 
state 5 (full GUI).   to do this, edit /etc/inittab, and change the one 
non-commented line in that file to read...


id:3:initdefault:

(its probably set to id:5: now), then reboot, and you should come up 
with a text console.   Virtually ALL my servers run with text consoles 
as they are headless, but if you really need X support, its easier to 
debug it starting from text ...


--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] Need help

[Rosenthal, Shoshana]

I did try other console  and it did not work.
I did go from 6.7 to 6.8 but with centos not redhat.


On Mon, Mar 20, 2017 at 4:59 PM, Styma, Robert (Nokia - US) <
robert.st...@nokia.com> wrote:

> Try another console like ALT-F2.  See if you have a black screen login
> prompt.  I opened a bug with RedHat for a system that when I went from 6.7
> to 6.8 booted but would not start the X server.  Problem was in the MACH64
> driver.  It is missing an external symbol that the X server requires.
>
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Leroy
> Tennison
> Sent: Monday, March 20, 2017 1:35 PM
> To: centos <centos@centos.org>
> Subject: Re: [CentOS] Need help
>
> This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS
> but the symptoms are identical.  Try 'systemctl enable
> console-getty.service' then 'systemctl start console-getty.service' or, if
> it is headless (serial console only), 'systemctl enable
> serial-getty@ttyS0.service' then 'systemctl start
> serial-getty@ttyS0.service' assuming it's ttyS0).  For VMs (specifically
> kvm/qemu) neither of these "solutions" worked.
>
> - Original Message -
> From: "Rosenthal, Shoshana" <srosent...@cfa.harvard.edu>
> To: "centos" <centos@centos.org>
> Sent: Monday, March 20, 2017 3:25:06 PM
> Subject: Re: [CentOS] Need help
>
> I figured out that the system boots OK and it is possible
> to login remotely. However the monitor does not start up.
>
> Do you know how to fix it?
>
>
> On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
> srosent...@cfa.harvard.edu> wrote:
>
> > You are right it is a Dell PowerEdge. However as I said it stops in the
> > middle of booting with no message.
> >
> >
> >
> > On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pie...@hogranch.com>
> > wrote:
> >
> >> On 3/20/2017 11:54 AM, Scott Robbins wrote:
> >>
> >>> I am running centos 6.8
> >>>> The system went down when we try to reboot it we get the
> >>>> message ST:3P7Y9Y1
> >>>> Do you know what the problem might be.
> >>>>
> >>> I'm guessing you mean the message on the front panel, which is the
> >>> service
> >>> tag number.
> >>>
> >>
> >> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
> >> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
> >> originally running RHEL 6.5
> >>
> >> indeed, you need to connect a monitor to it to determine what stage of
> >> the boot is failing and why.
> >>
> >>
> >> --
> >> john r pierce, recycling bits in santa cruz
> >>
> >>
> >> ___
> >> CentOS mailing list
> >> CentOS@centos.org
> >> https://lists.centos.org/mailman/listinfo/centos
> >>
> >
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Styma, Robert (Nokia - US)]

Try another console like ALT-F2.  See if you have a black screen login prompt.  
I opened a bug with RedHat for a system that when I went from 6.7 to 6.8 booted 
but would not start the X server.  Problem was in the MACH64 driver.  It is 
missing an external symbol that the X server requires.

-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Leroy Tennison
Sent: Monday, March 20, 2017 1:35 PM
To: centos <centos@centos.org>
Subject: Re: [CentOS] Need help

This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS but 
the symptoms are identical.  Try 'systemctl enable console-getty.service' then 
'systemctl start console-getty.service' or, if it is headless (serial console 
only), 'systemctl enable serial-getty@ttyS0.service' then 'systemctl start 
serial-getty@ttyS0.service' assuming it's ttyS0).  For VMs (specifically 
kvm/qemu) neither of these "solutions" worked.

- Original Message -
From: "Rosenthal, Shoshana" <srosent...@cfa.harvard.edu>
To: "centos" <centos@centos.org>
Sent: Monday, March 20, 2017 3:25:06 PM
Subject: Re: [CentOS] Need help

I figured out that the system boots OK and it is possible
to login remotely. However the monitor does not start up.

Do you know how to fix it?


On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
srosent...@cfa.harvard.edu> wrote:

> You are right it is a Dell PowerEdge. However as I said it stops in the
> middle of booting with no message.
>
>
>
> On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pie...@hogranch.com>
> wrote:
>
>> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>>
>>> I am running centos 6.8
>>>> The system went down when we try to reboot it we get the
>>>> message ST:3P7Y9Y1
>>>> Do you know what the problem might be.
>>>>
>>> I'm guessing you mean the message on the front panel, which is the
>>> service
>>> tag number.
>>>
>>
>> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
>> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
>> originally running RHEL 6.5
>>
>> indeed, you need to connect a monitor to it to determine what stage of
>> the boot is failing and why.
>>
>>
>> --
>> john r pierce, recycling bits in santa cruz
>>
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Leroy Tennison]

This is a wild guess since the problem I had occurred on Ubuntu 16.04 LTS but 
the symptoms are identical.  Try 'systemctl enable console-getty.service' then 
'systemctl start console-getty.service' or, if it is headless (serial console 
only), 'systemctl enable serial-getty@ttyS0.service' then 'systemctl start 
serial-getty@ttyS0.service' assuming it's ttyS0).  For VMs (specifically 
kvm/qemu) neither of these "solutions" worked.

- Original Message -
From: "Rosenthal, Shoshana" <srosent...@cfa.harvard.edu>
To: "centos" <centos@centos.org>
Sent: Monday, March 20, 2017 3:25:06 PM
Subject: Re: [CentOS] Need help

I figured out that the system boots OK and it is possible
to login remotely. However the monitor does not start up.

Do you know how to fix it?


On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
srosent...@cfa.harvard.edu> wrote:

> You are right it is a Dell PowerEdge. However as I said it stops in the
> middle of booting with no message.
>
>
>
> On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce <pie...@hogranch.com>
> wrote:
>
>> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>>
>>> I am running centos 6.8
>>>> The system went down when we try to reboot it we get the
>>>> message ST:3P7Y9Y1
>>>> Do you know what the problem might be.
>>>>
>>> I'm guessing you mean the message on the front panel, which is the
>>> service
>>> tag number.
>>>
>>
>> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
>> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
>> originally running RHEL 6.5
>>
>> indeed, you need to connect a monitor to it to determine what stage of
>> the boot is failing and why.
>>
>>
>> --
>> john r pierce, recycling bits in santa cruz
>>
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Rosenthal, Shoshana]

I figured out that the system boots OK and it is possible
to login remotely. However the monitor does not start up.

Do you know how to fix it?


On Mon, Mar 20, 2017 at 3:15 PM, Rosenthal, Shoshana <
srosent...@cfa.harvard.edu> wrote:

> You are right it is a Dell PowerEdge. However as I said it stops in the
> middle of booting with no message.
>
>
>
> On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce 
> wrote:
>
>> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>>
>>> I am running centos 6.8
 The system went down when we try to reboot it we get the
 message ST:3P7Y9Y1
 Do you know what the problem might be.

>>> I'm guessing you mean the message on the front panel, which is the
>>> service
>>> tag number.
>>>
>>
>> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
>> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
>> originally running RHEL 6.5
>>
>> indeed, you need to connect a monitor to it to determine what stage of
>> the boot is failing and why.
>>
>>
>> --
>> john r pierce, recycling bits in santa cruz
>>
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[John R Pierce]

On 3/20/2017 12:15 PM, Rosenthal, Shoshana wrote:

You are right it is a Dell PowerEdge. However as I said it stops in the
middle of booting with no message.


there may be some status LEDs on the mainboard inside the server that 
show power on self test results.


But, its a 4-5 year old Dell, most likely its power supply has 
failed.or the main board.  For sure its a hardware problem, as if it 
was a CentOS specific software problem, you'd see the BIOS self test, 
setup messages, then grub boot, etcetc.


standard PC server hardware trouble shooting applies...   if its on 
service contract, call your support provider.   if not, and your time is 
worth less than a replacement server, open it up, unplug everything 
extra, reseat all the remaining connectors, see if it passes 
power-on-self-test.  if not, swap PSU with an identical server, try 
again. If it DOES pass POST w/ everything unplugged, plug back in a 
minimum amount of stuff, repeat   etc etc etc.




--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] Need help

[Styma, Robert (Nokia - US)]

> You are right it is a Dell PowerEdge. However as I said it stops in the
 > middle of booting with no message.
When it behaves weird like that, starting to boot and then quitting and it is a 
Dell, open the case and look at the motherboard.  Look for failed electrolytic 
capacitors.  They usually have scribe marks on the top in the form of an "X" or 
a "K".  The failed ones will be bulging up or actually split.  

If it is a corporate machine under maintenance, make Dell fix it.  If it is 
your machine or not under warrantee and you want to fix it, it is not that 
hard.  Capacitors are available on Amazon.  You can read the value off the side 
of the capacitor.

Bob S.

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

Re: [CentOS] Need help

[m . roth]

I'm sending to you, directly, because manitu is again blocking my ISP

Rosenthal, Shoshana wrote:
> You are right it is a Dell PowerEdge. However as I said it stops in the
middle of booting with no message.
>
> On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce  wrote:
>
>> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>>
>>> I am running centos 6.8
 The system went down when we try to reboot it we get the
 message ST:3P7Y9Y1
 Do you know what the problem might be.


You say "in the middle of booting" - please define.
1. Did it finish POST?
2. Did you see the kernel it was about to boot, displayed by grub?

If the latter, *sigh*, hit "e" when you see the kernel, then edit the
kernel line, and DELETE rhgb quiet, then boot.

   mark



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

Re: [CentOS] Need help

[Rosenthal, Shoshana]

You are right it is a Dell PowerEdge. However as I said it stops in the
middle of booting with no message.



On Mon, Mar 20, 2017 at 3:11 PM, John R Pierce  wrote:

> On 3/20/2017 11:54 AM, Scott Robbins wrote:
>
>> I am running centos 6.8
>>> The system went down when we try to reboot it we get the
>>> message ST:3P7Y9Y1
>>> Do you know what the problem might be.
>>>
>> I'm guessing you mean the message on the front panel, which is the service
>> tag number.
>>
>
> indeed, thats the service tag for a Dell PowerEdge T620, shipped in
> September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives,
> originally running RHEL 6.5
>
> indeed, you need to connect a monitor to it to determine what stage of the
> boot is failing and why.
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[Rosenthal, Shoshana]

There is a monitor attached, but the computer does not boot up.
It stops before ending the boot. With no message on the monitor.

Yes, you are right the message is on the front panel. I thought the
service tag was a different number.

Thanks for responding.

Shoshana



On Mon, Mar 20, 2017 at 2:54 PM, Scott Robbins  wrote:

> On Mon, Mar 20, 2017 at 02:49:11PM -0400, Rosenthal, Shoshana wrote:
> > I am running centos 6.8
> > The system went down when we try to reboot it we get the
> > message ST:3P7Y9Y1
> > Do you know what the problem might be.
>
> I'm guessing you mean the message on the front panel, which is the service
> tag number.
>
> There should be more helpful information if you attach a monitor to the
> machine and boot it up.
>
>
> --
> Scott Robbins
> PGP keyID EB3467D6
> ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
> gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help

[John R Pierce]

On 3/20/2017 11:54 AM, Scott Robbins wrote:

I am running centos 6.8
The system went down when we try to reboot it we get the
message ST:3P7Y9Y1
Do you know what the problem might be.

I'm guessing you mean the message on the front panel, which is the service
tag number.


indeed, thats the service tag for a Dell PowerEdge T620, shipped in 
September 2013, with dual Xeon E5-X2667, 48GB ram, and 10 3TB drives, 
originally running RHEL 6.5


indeed, you need to connect a monitor to it to determine what stage of 
the boot is failing and why.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] Need help

[Scott Robbins]

On Mon, Mar 20, 2017 at 02:49:11PM -0400, Rosenthal, Shoshana wrote:
> I am running centos 6.8
> The system went down when we try to reboot it we get the
> message ST:3P7Y9Y1
> Do you know what the problem might be.

I'm guessing you mean the message on the front panel, which is the service
tag number.  

There should be more helpful information if you attach a monitor to the
machine and boot it up. 


-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

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

[CentOS] Need help

[Rosenthal, Shoshana]

I am running centos 6.8
The system went down when we try to reboot it we get the
message ST:3P7Y9Y1
Do you know what the problem might be.

Thanks
shosh...@cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Gordon Messmer]

On 11/16/2016 07:33 AM, Sean Son wrote:

No matter how many times I
restart the NetworkManager-dispatcher service, if I reboot the system, and
run a systemctl status NetworkManager-dispatcher.service, the service shows
as Inactive (Dead) even though it has been enabled.


That's normal.  It's a dbus-invoked service.  You don't need to manually 
enable it.  It runs a command when it's invoked, and then terminates.  
There isn't a daemon process associated with the service.



Also whenever I
reboot the VM, after logging into the GUI, I get a pop up that says failed
to activate network connection , yet I still have network connectivity.
Any ideas on what I can do to fix these things?


Not really.  The log might tell you why it thinks an interface wasn't 
successfully enabled.



   Also overall, because I am
using a static IP config for both NICs, is it better to just disable
NetworkManager and use network scripts instead?


Not generally.  If you find the old network service works better for 
your use case, it's available.  I use it on a small number of hosts 
where NM bugs interfere with normal operation, but I'm waiting for the 
7.3 updates (where NM has been rebased to a newer version) to see if I 
can stop doing that.

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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Sean Son]

On Tue, Nov 15, 2016 at 10:55 AM, Gordon Messmer 
wrote:

> On 11/15/2016 06:07 AM, Sean Son wrote:
>
>> I have no network connectivity even
>> when I restart the network service.  Should I reenable NetworkManager now?
>>
>
>
> Yeah, the switch is just a test to see if the problem is specific to
> NetworkManager.  It seems that you have other problems as well.
>
> Before you do that, post the output of the following:
>
> ip route show
>
> ip route show table 300
>
> ip route show table 301
>
> ip rule show
>
> cat /etc/sysconfig/network-scripts/ifcfg-eth0
>
> cat /etc/sysconfig/network-scripts/route-eth0
>
> cat /etc/sysconfig/network-scripts/rule-eth0
>
> cat /etc/sysconfig/network-scripts/ifcfg-eth1
>
> cat /etc/sysconfig/network-scripts/route-eth1
>
> cat /etc/sysconfig/network-scripts/rule-eth1
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


Hello

I think i figured it out.   I had forgotten to install
NetworkManager-config-routing-rules and then enable and start the
NetworkManager-dispatcher service.   I tried that on a different test
machine and I am able to ping both of the IPs from another machine just
fine. Only a few things I have noticed:   No matter how many times I
restart the NetworkManager-dispatcher service, if I reboot the system, and
run a systemctl status NetworkManager-dispatcher.service, the service shows
as Inactive (Dead) even though it has been enabled.   Also whenever I
reboot the VM, after logging into the GUI, I get a pop up that says failed
to activate network connection , yet I still have network connectivity.
Any ideas on what I can do to fix these things?  Also overall, because I am
using a static IP config for both NICs, is it better to just disable
NetworkManager and use network scripts instead?



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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Gordon Messmer]

On 11/15/2016 06:07 AM, Sean Son wrote:

I have no network connectivity even
when I restart the network service.  Should I reenable NetworkManager now?



Yeah, the switch is just a test to see if the problem is specific to 
NetworkManager.  It seems that you have other problems as well.


Before you do that, post the output of the following:

ip route show

ip route show table 300

ip route show table 301

ip rule show

cat /etc/sysconfig/network-scripts/ifcfg-eth0

cat /etc/sysconfig/network-scripts/route-eth0

cat /etc/sysconfig/network-scripts/rule-eth0

cat /etc/sysconfig/network-scripts/ifcfg-eth1

cat /etc/sysconfig/network-scripts/route-eth1

cat /etc/sysconfig/network-scripts/rule-eth1


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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Sean Son]

On Mon, Nov 14, 2016 at 5:30 PM, Gordon Messmer 
wrote:

> On 11/14/2016 12:47 PM, Sean Son wrote:
>
>> Any ideas on what
>> I am doing wrong here?
>>
>
>
> Nothing obvious.  Since your interfaces have static configurations, I'd
> suggest turning off NetworkManager and turning on the "network" service to
> determine whether or not that works correctly after a reboot.
>
> Assuming it does, fixing the issue might be as simple as getting
> NetworkManager to not rename one interface to "wired connection 1".
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


Hello Gordon

Thank you for your response.  I disabled NetworkManager and started the
network service, then I rebooted the VM and now 'ip rule show' has the
rules for both interfaces showing but I have no network connectivity even
when I restart the network service.  Should I reenable NetworkManager now?
How would I go about getting NetworkManager to stop creating new Interface
files and naming them Wired_connection-*?


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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Gordon Messmer]

On 11/14/2016 12:47 PM, Sean Son wrote:

Any ideas on what
I am doing wrong here?



Nothing obvious.  Since your interfaces have static configurations, I'd 
suggest turning off NetworkManager and turning on the "network" service 
to determine whether or not that works correctly after a reboot.


Assuming it does, fixing the issue might be as simple as getting 
NetworkManager to not rename one interface to "wired connection 1".


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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Sean Son]

On Tue, Nov 8, 2016 at 8:02 AM, Boris Epstein  wrote:

> Hello there,
>
> What is the hypervisor that hosts the VM? What does ifconfig show on it?
>
> Boris.
>
> On Mon, Nov 7, 2016 at 4:36 PM, Gordon Messmer 
> wrote:
>
> > On 11/06/2016 11:00 PM, Sean Son wrote:
> >
> >> How do I
> >> configure the networking so that both IPs are pingable and the VM is
> >> reachable via both IPs?
> >>
> >
> >
> > You need one rule file per interface, which directs traffic out the
> > appropriate interface based on the source address of the packet:
> >
> > https://blogs.oracle.com/networking/entry/advance_
> routing_for_multi_homed
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


Hello all

Thank you for the replies.  I ran into  some issues with the policy based
routing which I will explain in a few.  First off to answer each one of
your questions:

Digimer: No I didnt take a look at IPTables

Peter Brady: Thank you for the example, I tried that but it failed and I
will explain in a minute.

Frank Cox : That works but how do I make it persistent across reboots?

Boris Epstein:  I am using Hyper-V and its getting annoying lol


Ok so here is how I have set everything up:

my /etc/iproute2/rt_tables:


#
# reserved values
#
255 local
254 main
253 default
0   unspec
#
# local
#
#1  inr.ruhep
300 NIC1
310 NIC2

my /etc/sysconfig/network-scripts/route-eth0 file:

168.87.147.0/24 dev eth0 table 300
default via 168.87.147.1 dev eth0 table 300

/etc/sysconfig/network-scripts/route-eth1 file:

10.20.50.0/24 dev eth1 table 310
default via 10.20.50.1 dev eth1 table 310

My /etc/sysconfig/network-scripts/rule-eth0:

from 168.87.147.33/32 table 300
to 168.87.147.33 table 300

My /etc/sysconfig/network-scripts/rule-eth1:

from 10.20.50.90/32 table 310
to 10.20.50.90 table 310


now after implementing this and restarting NetworkManager,  when I run 'ip
rule list', I get the following:

0:  from all lookup local
32764:  from all to 10.20.50.90 lookup NIC2
32765:  from 10.20.50.90 lookup NIC2
32766:  from all lookup main
32767:  from all lookup default


and when i run 'ip route' , i get the following:

default via 168.87.147.1 dev eth0  proto static  metric 1024
10.20.50.0/24 dev eth1  proto kernel  scope link  src 10.20.50.90
168.87.147.0/24 dev eth0  proto kernel  scope link  src 168.87.147.33



yet when I try to ping from another server to 10.20.50.90 it will not ping
at all. Also, whenever I reboot the VM, eth1 switches over to DHCP and I
lose my IP configuration. After I reset the IP Configuration back to Manual
and reenter the IP, Centos creates a new interface file called
ifcfg-Wired_Connection-1 and places the IP configuration for the interface
into that file. Both virtual NICs are set to Static Mac Addresses, so I
dont know why it keeps creating another interface file.  Any ideas on what
I am doing wrong here? All help is greatly appreciated!


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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Boris Epstein]

Hello there,

What is the hypervisor that hosts the VM? What does ifconfig show on it?

Boris.

On Mon, Nov 7, 2016 at 4:36 PM, Gordon Messmer 
wrote:

> On 11/06/2016 11:00 PM, Sean Son wrote:
>
>> How do I
>> configure the networking so that both IPs are pingable and the VM is
>> reachable via both IPs?
>>
>
>
> You need one rule file per interface, which directs traffic out the
> appropriate interface based on the source address of the packet:
>
> https://blogs.oracle.com/networking/entry/advance_routing_for_multi_homed
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[lejeczek]

On 07/11/16 07:00, Sean Son wrote:

Hello all

Here is the scenario:  We have a mail server VM which currently has two
virtual NICs attached to it. One NIC is has an IP on a subnet with a
default gateway defined and the other NIC has an IP on a different subnet
with a different gateway on a different VLAN defined. Now when I activate
both NICs, and run an ifconfig -a, I see that both IP addresses are
showing. Now here is the problem. When I ping the VM, the first NIC's IP is
not pingable at all, but the second NIC's IP is pingable. How do I
configure the networking so that both IPs are pingable and the VM is
reachable via both IPs? Please let me know what I may be doing wrong!


Thank you!

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


policy based routing is useful concept but in my mind should 
be the very last resort.
It is the kernel's networking functions which are 
responsible for routing tables construction and if you can 
shed more details (like mentioned earlier) on what can(not) 
ping what(VM hosting box <-> VM guest / outside internal net 
<-> VM / etc.) centbuddies could share more concrete 
thoughts then.
Basically - with policy/source based routing you need to be 
very careful, test everything - best is to leave it to the 
kernel and only use main table, kernel should be the 
smartest, for more complex setups maybe think "routing daemons".

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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Gordon Messmer]

On 11/06/2016 11:00 PM, Sean Son wrote:

How do I
configure the networking so that both IPs are pingable and the VM is
reachable via both IPs?



You need one rule file per interface, which directs traffic out the 
appropriate interface based on the source address of the packet:


https://blogs.oracle.com/networking/entry/advance_routing_for_multi_homed

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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Peter Brady]

On 7/11/2016 6:00 PM, Sean Son wrote:
> Hello all
>
> Here is the scenario:  We have a mail server VM which currently has two
> virtual NICs attached to it. One NIC is has an IP on a subnet with a
> default gateway defined and the other NIC has an IP on a different subnet
> with a different gateway on a different VLAN defined. Now when I activate
> both NICs, and run an ifconfig -a, I see that both IP addresses are
> showing. Now here is the problem. When I ping the VM, the first NIC's IP is
> not pingable at all, but the second NIC's IP is pingable. How do I
> configure the networking so that both IPs are pingable and the VM is
> reachable via both IPs? Please let me know what I may be doing wrong!
>
I've done this recently on C7.  The key words for your Google Fu is
policy based routing.  That ensures the incoming packets come back out
the same interface they came in on.  Mind you, depending on the routers
in the way this may not be a problem.  CISCO ASAs get really picky but
otherwise there may be other problems to deal with as well.

If you're using Network Manager then the package:
NetworkManager-config-routing-rules will help.

After that you create the rules and routes files in
/etc/sysconfig/network-scripts

So in my case I have:

  * enp3s0: 192.168.20.253 (the default gateway on this subnet is
192.168.20.2)
  * vlan22@enp3s0: 192.168.22.253 (the default gateway on this subnet is
192.168.22.1)

[root@host network-scripts]# cat route-enp3s0
192.168.20.0/24 dev enp3s0 tab 20
default via 192.168.20.2 dev enp3s0 tab 20

[root@host network-scripts]# cat rule-enp3s0
from 192.168.20.0/24 tab 20 priority 20

[root@host network-scripts]# cat route-vlan22
192.168.22.0/24 dev vlan22 tab 22
default via 192.168.22.1 dev vlan22 tab 22

[root@host network-scripts]# cat rule-vlan22
from 192.168.22.0/24 tab 22 priority 22

Wireshark can be really helpful here as it can confirm that the
"unpingable" NIC is actually receiving the packets that you think it
is.  And hopefully in that case can also confirm if the echo packets are
going out the alternate NIC.  If there are no incoming packets then the
PBR is no real help at all and you'd need to look further upstream.

Hope that helps,
-pete




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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Frank Cox]

On Mon, 7 Nov 2016 02:00:24 -0500
Sean Son wrote:

>  When I ping the VM, the first NIC's IP is
> not pingable at all, but the second NIC's IP is pingable. How do I
> configure the networking so that both IPs are pingable and the VM is
> reachable via both IPs? 

The last time I did that I did it on Centos 5.  Here are my notes from back 
then.

First, add two lines to /etc/iproute2/rt_tables, so it looks like this:

#
# reserved values
#
255 local
254 main
253 default
0   unspec
#
# local
#
#1  inr.ruhep
50  access1
60  access2

Then add the following routes:

ip route add 1.2.3.0/24 dev eth1 table access1
ip route add default via 1.2.3.1 dev eth1 table access1
ip rule add from 1.2.3.178/32 lookup access1

ip route add 1.2.3.0/24 dev eth2 table access2
ip route add default via 1.2.3.1 dev eth2 table access2
ip rule add from 1.2.3.180/32 lookup access2

Of course, in this example 1.2.3.178 is the IP address of the first nic and 
1.2.3.180 is the address of the second nic.


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

Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Digimer]

On 07/11/16 02:00 AM, Sean Son wrote:
> Hello all
> 
> Here is the scenario:  We have a mail server VM which currently has two
> virtual NICs attached to it. One NIC is has an IP on a subnet with a
> default gateway defined and the other NIC has an IP on a different subnet
> with a different gateway on a different VLAN defined. Now when I activate
> both NICs, and run an ifconfig -a, I see that both IP addresses are
> showing. Now here is the problem. When I ping the VM, the first NIC's IP is
> not pingable at all, but the second NIC's IP is pingable. How do I
> configure the networking so that both IPs are pingable and the VM is
> reachable via both IPs? Please let me know what I may be doing wrong!

We're missing a lot of details, but to speak generally, I'd look at the
bridging on the host if you're confident that the interfaces are
configured properly inside the host.

Also, have you looked at iptables?

-- 
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
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Need help getting two NICs to work on CentOS 7

[Sean Son]

Hello all

Here is the scenario:  We have a mail server VM which currently has two
virtual NICs attached to it. One NIC is has an IP on a subnet with a
default gateway defined and the other NIC has an IP on a different subnet
with a different gateway on a different VLAN defined. Now when I activate
both NICs, and run an ifconfig -a, I see that both IP addresses are
showing. Now here is the problem. When I ping the VM, the first NIC's IP is
not pingable at all, but the second NIC's IP is pingable. How do I
configure the networking so that both IPs are pingable and the VM is
reachable via both IPs? Please let me know what I may be doing wrong!


Thank you!

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

[CentOS] Need help to Build entire CentOS distro

[kavitha bk]

Hi

I am aware of steps to build kernel and individual rpms

1.  git clone https://git.centos.org/git/rpms/kernel

2.  cd kernel

3.  git checkout c7

4.  get_sources.sh

You can get this script from below.

git clone  https://git.centos.org/git/centos-git-common.git

cp centos-git-common/get_sources.sh to kernel folder.

5.  git checkout c7

But I want to build entire CentOS distro.Please let me know the build
procedure?


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

[CentOS] Need help for write rpm spec

[Jegadeesh Kumar]

Hi

I am try to write  rpm spec for install tomcat on a linux machine.But while
build the rpm i found following error

+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id
/home/rpmbuild/BUILD/Install_tomcat-1.0
extracting debug info from
/home/rpmbuild/BUILDROOT/Install_tomcat-1.0-1.el6.x86_64/usr/local/jdk1.7.0_13/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so
*** ERROR: No build ID note found in
/home/rpmbuild/BUILDROOT/Install_tomcat-1.0-1.el6.x86_64/usr/local/jdk1.7.0_13/lib/visualvm/profiler/lib/deployed/jdk16/linux-amd64/libprofilerinterface.so
error: Bad exit status from /home/rpmbuild/tmp/rpm-tmp.n1saIQ (%install)


RPM build errors:
Bad exit status from /home/rpmbuild/tmp/rpm-tmp.n1saIQ (%install)


Below is my spec file

Name:   Install_tomcat
Version:1.0
Release:1%{?dist}
Summary:Tomcat installer

Group:  Application
License:BSOFT
Source0:Install_tomcat-1.0.tar.gz
BuildArch:  noarch
BuildRoot:  %(mktemp -ud
%{_tmppath}/%{name}-%{version}-%{release}-XX)


#BuildRequires:
#Requires:

%description
This RPM is used to install the tomcat application

%clean
rm -rf $RPM_BUILD_ROOT

%prep
%setup -q


%build


%install
rm -rf $RPM_BUILD_ROOT
install -d $RPM_BUILD_ROOT/usr/local
cd $RPM_BUILD_ROOT/usr/local
tar -xf   %{_topdir}/SOURCES/Install_tomcat-1.0.tar.gz --strip 1
tar -xf  jdk-7u13-linux-x64.gz
ln -s  jdk1.7.0_13/  $RPM_BUILD_ROOT/usr/local/java
echo export JAVA_HOME=/usr/local/java /etc/profile
echo PATH=\${JAVA_HOME}/bin:\${PATH} /etc/profile
source /etc/profile
java -version
tar -xf apache-tomcat-7.0.32.tar.gz
ln -s  apache-tomcat-7.0.32/  $RPM_BUILD_ROOT/usr/local/tomcat

%files
%dir /usr/local
%defattr(-,root,root,-)
%doc

%post
chmod 755 -R /usr/local

Please help me to solve the error

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

Re: [CentOS] Need help for write rpm spec

[Earl A Ramirez]

On Wed, 2015-03-18 at 13:16 -0400, m.r...@5-cent.us wrote:
 Jegadeesh Kumar wrote:
 
  I am try to write  rpm spec for install tomcat on a linux machine.But
  while build the rpm i found following error
 snip
 Why are you writing a new specfile, rather than just yum install tomcat,
 and you'll get the official working package installed via a working
 specfile?
 
 mark
 
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
Mark is 100% correct but I don't know your reasons behind the build,
therefore I have copied and paste the SPEC file from tomcat, maybe it
can serve as a guiding light for you to have the correct SPEC file.

# Copyright (c) 2000-2008, JPackage Project
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
#
# 1. Redistributions of source code must retain the above copyright
#notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
#notice, this list of conditions and the following disclaimer in the
#documentation and/or other materials provided with the
#distribution.
# 3. Neither the name of the JPackage Project nor the names of its
#contributors may be used to endorse or promote products derived
#from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
# AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#

%global jspspec 2.2
%global major_version 7
%global minor_version 0
%global micro_version 33
%global packdname apache-tomcat-%{version}-src
%global servletspec 3.0
%global elspec 2.2
%global tcuid 91

# FHS 2.3 compliant tree structure - http://www.pathname.com/fhs/2.3/
%global basedir %{_var}/lib/%{name}
%global appdir %{basedir}/webapps
%global homedir %{_datadir}/%{name}
%global bindir %{homedir}/bin
%global confdir %{_sysconfdir}/%{name}
%global libdir %{_javadir}/%{name}
%global logdir %{_var}/log/%{name}
%global cachedir %{_var}/cache/%{name}
%global tempdir %{cachedir}/temp
%global workdir %{cachedir}/work
%global _initrddir %{_sysconfdir}/init.d

Name:  tomcat
Epoch: 0
Version:   %{major_version}.%{minor_version}.%{micro_version}
Release:   4%{?dist}
Summary:   Apache Servlet/JSP Engine, RI for Servlet
%{servletspec}/JSP %{jspspec} API

Group: System Environment/Daemons
License:   ASL 2.0
URL:   http://tomcat.apache.org/
Source0:
http://archive.apache.org/dist/tomcat/tomcat-%{major_version}/v
%{version}/src/%{packdname}.tar.gz
Source1:   %{name}-%{major_version}.%{minor_version}.conf
Source2:   %{name}-%{major_version}.%{minor_version}.init
Source3:   %{name}-%{major_version}.%{minor_version}.sysconfig
Source4:   %{name}-%{major_version}.%{minor_version}.wrapper
Source5:   %{name}-%{major_version}.%{minor_version}.logrotate
Source6:   %{name}-%{major_version}.%{minor_version}-digest.script
Source7:
%{name}-%{major_version}.%{minor_version}-tool-wrapper.script
Source8:   servlet-api-OSGi-MANIFEST.MF
Source9:   jsp-api-OSGi-MANIFEST.MF
Source10:
%{name}-%{major_version}.%{minor_version}-log4j.properties
Source11:  el-api-OSGi-MANIFEST.MF
Source12:  jasper-el-OSGi-MANIFEST.MF
Source13:  jasper-OSGi-MANIFEST.MF
Source14:  tomcat-api-OSGi-MANIFEST.MF
Source15:  tomcat-juli-OSGi-MANIFEST.MF
Source16:  %{name}-%{major_version}.%{minor_version}-jsvc.wrapper

Patch0:
%{name}-%{major_version}.%{minor_version}-bootstrap-MANIFEST.MF.patch
Patch1:
%{name}-%{major_version}.%{minor_version}-tomcat-users-webapp.patch

BuildArch: noarch

ExcludeArch: ppc64

BuildRequires: ant
BuildRequires: ant-nodeps
BuildRequires: ant-trax
BuildRequires: ecj
BuildRequires: findutils
BuildRequires: jakarta-commons-collections
BuildRequires: jakarta-commons-daemon
BuildRequires: jakarta-commons-dbcp
BuildRequires: jakarta-commons-pool
BuildRequires: jakarta-taglibs-standard
BuildRequires: java-devel = 1:1.6.0
BuildRequires: jpackage-utils = 0:1.7.0
BuildRequires: junit
BuildRequires: log4j
BuildRequires: wsdl4j
Requires:  jakarta-commons-daemon
Requires:  

Re: [CentOS] Need help for write rpm spec

[m . roth]

Jegadeesh Kumar wrote:

 I am try to write  rpm spec for install tomcat on a linux machine.But
 while build the rpm i found following error
snip
Why are you writing a new specfile, rather than just yum install tomcat,
and you'll get the official working package installed via a working
specfile?

mark


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

[CentOS] Need help for issue with /etc/ppp/ip-down in Centos 6.4 64 bits

[nampt2]

Hi,
I have question about /etc/ppp/ip-down

What 's the script call this one when ppp interface down ?
Or how can i check it's working ?

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

Re: [CentOS] Need help for issue with /etc/ppp/ip-down in Centos 6.4 64 bits

[Alexander Farber]

Have you tried:

# fgrep -r ip-down /etc


On Mon, Sep 1, 2014 at 11:35 AM, nampt2 nam_phamt...@yahoo.com wrote:


 I have question about /etc/ppp/ip-down

 What 's the script call this one when ppp interface down ?
 Or how can i check it's working ?


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

Re: [CentOS] Need help for issue with /etc/ppp/ip-down in Centos 6.4 64 bits

[Alexander Dalloz]

Am 01.09.2014 um 11:35 schrieb nampt2:

Hi,
I have question about /etc/ppp/ip-down

What 's the script call this one when ppp interface down ?


The call of a script by that name is hardcoded in the pppd.


Or how can i check it's working ?


Create a script /etc/ppp/ip-down.local and let it write information into 
an output file under /tmp for example.


Why should it not work?


Thanks,
Nam.


If you are still running CentOS 6.4 as you say in the subject, then 
update ASAP.


Alexander

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[John Doe]

From: Alfred von Campe alf...@von-campe.com

 I have been using 32-bit CentOS since the 4.X days without a real need for 
 64-bit, but in preparation for CentOS 7, I have installed 64-bit CentOS 6 on 
 a 
 test system to qualify all our builds.  However, in order to build some of 
 our 
 current 32-bit applications, I had to install some i686 packages, including 
 glib.
 
 Now when I try to do a yum update on this test system, I get the 
 dreaded Error:  Multilib version problems found. issue.  I have 
 tried following the instructions from yum (--exclude=glib.i686, yum check, 
 etc.) 
 to resolve this to no avail.  What is the best way to proceed with the yum 
 update so that all (64-bit and 32-bit) packages are updated?

Maybe try 'protected_multilib' in yum.conf (see man).

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[Alfred von Campe]

On Feb 25, 2014, at 6:13, John Doe jd...@yahoo.com wrote:

 Maybe try 'protected_multilib' in yum.conf (see man).

Thanks for the hint.  Upon closer inspection, the issue was with glib from 
rpmforge, so doing a yum update --disablerepo=rpmforge\* makes it work.

Alfred

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[John Doe]

From: Alfred von Campe alf...@von-campe.com

 Thanks for the hint.  Upon closer inspection, the issue was with glib from 
 rpmforge, so doing a yum update --disablerepo=rpmforge\* makes 
 it work.

You Should set up repos priorities...

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

[CentOS] Need help resolving yum update issues on mixed architecture system

[Alfred von Campe]

I have been using 32-bit CentOS since the 4.X days without a real need for 
64-bit, but in preparation for CentOS 7, I have installed 64-bit CentOS 6 on a 
test system to qualify all our builds.  However, in order to build some of our 
current 32-bit applications, I had to install some i686 packages, including 
glib.

Now when I try to do a yum update on this test system, I get the dreaded 
Error:  Multilib version problems found. issue.  I have tried following the 
instructions from yum (--exclude=glib.i686, yum check, etc.) to resolve this to 
no avail.  What is the best way to proceed with the yum update so that all 
(64-bit and 32-bit) packages are updated?

Thanks,
Alfred

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[John R Pierce]

On 2/24/2014 3:18 PM, Alfred von Campe wrote:
 However, in order to build some of our current 32-bit applications, I had to 
 install some i686 packages, including glib.

how did you do these installs?  I've never had trouble doing it via 
yum, like:   yum install glibc.i686

but then, I've only done this on centos 6

-- 
john r pierce  37N 122W
somewhere on the middle of the left coast

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[Alfred von Campe]

On Feb 24, 2014, at 18:59, John R Pierce pie...@hogranch.com wrote:

 how did you do these installs?  I've never had trouble doing it via 
 yum, like:   yum install glibc.i686

That's exactly what I did, and it worked fine (I can compile our 32-bit apps), 
but I get the error when I try to do the yum update.

 but then, I've only done this on centos 6

So have I.  I only mentioned CentOS 7 because it was supposed to be 64-bit only 
(but now it seems that the CentOS team is working on an i686 release for CentOS 
7).

Alfred

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

Re: [CentOS] Need help resolving yum update issues on mixed architecture system

[dominicpg]

 What is the best way to proceed with the yum update so that all (64-bit
and 32-bit) packages are updated?

I usually check the dependency error and will install the missing 32bit
package alone ( one time task ), then will try yum update . I think,
rpm/repo compose file decides the dependency 32bit package.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Need help with kernel, modules and headers

[Patrick Begou]

Akemi Yagi wrote:
 On Mon, Jan 13, 2014 at 9:09 AM, Patrick Begou
 patrick.be...@legi.grenoble-inp.fr wrote:
 I need some help about kernels, modules and so on.

 I've installed CentOS6.5 (fresh install) on a DELL E7440 laptop. After all 
 the
 updates I get the latest kernel: kernel-2.6.32-431.

 But with this config I've a problem: If I close the screen on the keyboard, 
 the
 laptop hibernate. When I open it the system restart (I connect use ssh to 
 reach
 the laptop) but the screen remains black (Intel HD Graphics 4400).

 I've installed a more recent kernel from  elrepo-kernel
 (kernel-lt-3.10.26-1.el6.elrepo.x86_64) and it solves the black screen 
 problem.

 But now I have several errors about
 = kdump,
 Starting kdump: ÉCHOUÉ
 = vboxdrv
 Starting VirtualBox kernel modules  ÉCHOUÉ
 (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
 = dkms (requested for VirtualBox)
 Démarrage de dkms : Error!
 Your kernel headers for kernel 3.10.26-1.el6.elrepo.x86_64 cannot be found at
 /lib/modules/3.10.26-1.el6.elrepo.x86_64/build or
 /lib/modules/3.10.26-1.el6.elrepo.x86_64/source.

 but kernel-lt-headers cannot be installed (conflicting with the installed
 kernel-headers requested by many packages).
 You need the kernel-devel package (not -headers) that matches your
 running kernel.

 Akemi


Thanks Akemi.  Now, after a new fresh install of centos and this kernel, the 
laptop boot properly and when the laptop hibernate after closing the screen the 
restart is fast and efficient. I also notice a very faster network with these 
new drivers!

But I think I still have a problem with modules added by virtual box. If I 
install this application the problem come back as with previous kernel. Mays be 
hibernation it is not supported with virtualbox and the modules it adds...

Patrick

-- 
===
|  Equipe M.O.S.T. |  |
|  Patrick BEGOU   | mailto:patrick.be...@grenoble-inp.fr |
|  LEGI|  |
|  BP 53 X | Tel 04 76 82 51 35   |
|  38041 GRENOBLE CEDEX| Fax 04 76 82 52 71   |
===


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

[CentOS] Need help with kernel, modules and headers

[Patrick Begou]

I need some help about kernels, modules and so on.

I've installed CentOS6.5 (fresh install) on a DELL E7440 laptop. After all the 
updates I get the latest kernel: kernel-2.6.32-431.

But with this config I've a problem: If I close the screen on the keyboard, the 
laptop hibernate. When I open it the system restart (I connect use ssh to reach 
the laptop) but the screen remains black (Intel HD Graphics 4400).

I've installed a more recent kernel from  elrepo-kernel 
(kernel-lt-3.10.26-1.el6.elrepo.x86_64) and it solves the black screen problem.

But now I have several errors about
= kdump,
Starting kdump: ÉCHOUÉ
= vboxdrv
Starting VirtualBox kernel modules  ÉCHOUÉ
   (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
= dkms (requested for VirtualBox)
Démarrage de dkms : Error!
Your kernel headers for kernel 3.10.26-1.el6.elrepo.x86_64 cannot be found at
/lib/modules/3.10.26-1.el6.elrepo.x86_64/build or 
/lib/modules/3.10.26-1.el6.elrepo.x86_64/source.

but kernel-lt-headers cannot be installed (conflicting with the installed 
kernel-headers requested by many packages).


So what could you suggest me to solve this situation ?
- kernel-2.6.32-431 all is working but if the laptop hibernate it hangs
- kernel 3.10.26-1 video works fine but I get conflicts for some applications

Thanks for your advices

Patrick

-- 
===
|  Equipe M.O.S.T. |  |
|  Patrick BEGOU   | mailto:patrick.be...@grenoble-inp.fr |
|  LEGI|  |
|  BP 53 X | Tel 04 76 82 51 35   |
|  38041 GRENOBLE CEDEX| Fax 04 76 82 52 71   |
===


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

Re: [CentOS] Need help with kernel, modules and headers

[Akemi Yagi]

On Mon, Jan 13, 2014 at 9:09 AM, Patrick Begou
patrick.be...@legi.grenoble-inp.fr wrote:
 I need some help about kernels, modules and so on.

 I've installed CentOS6.5 (fresh install) on a DELL E7440 laptop. After all the
 updates I get the latest kernel: kernel-2.6.32-431.

 But with this config I've a problem: If I close the screen on the keyboard, 
 the
 laptop hibernate. When I open it the system restart (I connect use ssh to 
 reach
 the laptop) but the screen remains black (Intel HD Graphics 4400).

 I've installed a more recent kernel from  elrepo-kernel
 (kernel-lt-3.10.26-1.el6.elrepo.x86_64) and it solves the black screen 
 problem.

 But now I have several errors about
 = kdump,
 Starting kdump: ÉCHOUÉ
 = vboxdrv
 Starting VirtualBox kernel modules  ÉCHOUÉ
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)
 = dkms (requested for VirtualBox)
 Démarrage de dkms : Error!
 Your kernel headers for kernel 3.10.26-1.el6.elrepo.x86_64 cannot be found at
 /lib/modules/3.10.26-1.el6.elrepo.x86_64/build or
 /lib/modules/3.10.26-1.el6.elrepo.x86_64/source.

 but kernel-lt-headers cannot be installed (conflicting with the installed
 kernel-headers requested by many packages).

You need the kernel-devel package (not -headers) that matches your
running kernel.

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

Re: [CentOS] Need help with spec file for Apache-2.4.7

[Peter]

On 01/05/2014 08:28 PM, James B. Byrne wrote:
 
 RPM build errors:
 error: Installed (but unpackaged) file(s) found:
...
/usr/bin/apu-1-config

...

 %{_bindir}/apr-u-config

apu-l != apr-u


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

Re: [CentOS] Need help with spec file for Apache-2.4.7

[James B. Byrne]

On Sun, January 5, 2014 06:02, Peter wrote:
 On 01/05/2014 08:28 PM, James B. Byrne wrote:

 RPM build errors:
 error: Installed (but unpackaged) file(s) found:
 ...
/usr/bin/apu-1-config

 ...

 %{_bindir}/apr-u-config

 apu-l != apr-u


 Peter



Ahhh. Thank you. I suppose that eventually I might have noticed. Sigh...

Anyway, it is built and packaged now.  Next I will see if it runs.

Regards, and thanks.

-- 
***  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

Re: [CentOS] Need help with spec file for Apache-2.4.7

[James B. Byrne]

On Fri, January 3, 2014 20:29, Markus Falb wrote:

 On 03.Jan.2014, at 21:24, James B. Byrne wrote:


 Now, I added this in the Sources:

 Source0: http://www.apache.org/dist/httpd/httpd-%{version}.tar.bz2
 Source1: http://www.apache.org/dist/httpd/httpd-%{version}-deps.tar.bz2

 You have to extract Source1 into the BUILDDIR...
 You can verify if apr directory is present with

 $ rpmbuild -bp httpd.spec
 $ ls ../BUILD/httpd-2.4.7

 --- rpmbuild/SPECS/httpd.spec

 ...

 %prep
 %setup -q

 after that %setup macro your working directory should be
 rpmbuild/BUILD/httpd-2.4.7
 now something like

 %setup -D -q -b 1

 http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html#id853841

 --
 Markus


Thank you very much for that reference.  This got me past that roadblock.  I
have resolved many other difficulties but I have run into another problem for
which I am unable find any guidance.  Now I am getting this error in the
build:

RPM build errors:
File not found:
/builddir/build/BUILDROOT/httpd-2.4.7-1.x86_64/usr/lib64/httpd/modules/mod_session_crypto.so
Child return code was: 1
EXCEPTION: Command failed. See logs for output.
 # ['bash', '--login', '-c', 'rpmbuild -bb --target x86_64 --nodeps
builddir/build/SPECS/httpd.spec']

I cannot find anything in the spec file that refers to this module by name
other than the following:

%{_libdir}/httpd/modules/mod_session_crypto.so

Am I missing something obvious?  Is there an undeclared dependency?

Any assistance gratefully accepted.

-- 
***  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

Re: [CentOS] Need help with spec file for Apache-2.4.7

[James B. Byrne]

On Sat, January 4, 2014 22:14, James B. Byrne wrote:

 RPM build errors:
 File not found:
 /builddir/build/BUILDROOT/httpd-2.4.7-1.x86_64/usr/lib64/httpd/modules/mod_session_crypto.so
 Child return code was: 1
 EXCEPTION: Command failed. See logs for output.
  # ['bash', '--login', '-c', 'rpmbuild -bb --target x86_64 --nodeps
 builddir/build/SPECS/httpd.spec']

 I cannot find anything in the spec file that refers to this module by name
 other than the following:

 %{_libdir}/httpd/modules/mod_session_crypto.so

 Am I missing something obvious?  Is there an undeclared dependency?

 Any assistance gratefully accepted.


I have gotten this to compile to completion but now I am getting an error that
says:

RPM build errors:
error: Installed (but unpackaged) file(s) found:
   /usr/bin/apr-1-config
   /usr/bin/apu-1-config
Installed (but unpackaged) file(s) found:
   /usr/bin/apr-1-config
   /usr/bin/apu-1-config
Child return code was: 1

However, if I add this to the %files directive:

%files devel
%defattr(-,root,root)
.  .  .
# Adds in apr libs
%{_bindir}/apr-1-config
%{_bindir}/apr-u-config

The error becomes:

error: File not found:
/builddir/build/BUILDROOT/httpd-2.4.7-1.x86_64/usr/bin/apr-u-config
RPM build errors:
File not found:
/builddir/build/BUILDROOT/httpd-2.4.7-1.x86_64/usr/bin/apr-u-config

Where should the arp stuff go? Into its own package?

-- 
***  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] Need help with spec file for Apache-2.4.7

[James B. Byrne]

I am trying to build an RPM for Apache-2.4.7-1 on Centos-6.5-i86_64.  I am
using mock.

The are three build dependencies that I am trying to resolve.  One,
mod_socache_dc / distcache, I have simply removed from the spec file.  The
other two are arp and apr-utils.  Since httpd-2.4.7 needs arp = 1.4 I got the
two latter requirements from
http://www.apache.org/dist/httpd/httpd-2.4.7-deps.tar.bz2 and extracted them
into rpmbuild/SOURCES/httpd-2.4.7/srclib intending to use the
--with-included-arp configuration directive per
rpmbuild/SOURCES/httpd-2.4.7/INSTALL.

I also revised the spec file to remove requirements for the removed 
dependencies.

#BuildRequires: apr-devel = 1.4.0, apr-util-devel = 1.4.0
# Replaced by --with-included-apr
. . .
#Requires: apr-devel, apr-util-devel
# Replaced by --with-included-apr

and this little 'gotcha'

# forcibly prevent use of bundled apr, apr-util, pcre
# rm -rf srclib/{apr,apr-util,pcre}

removed this from %configure:

#--with-apr=%{_prefix} --with-apr-util=%{_prefix} \

and replaced it with this:

--with-included-apr \

and removed the reference to mod_socache_dc

#%files -n mod_socache_dc
#%defattr(-,root,root)
#%{_libdir}/httpd/modules/mod_socache_dc.so

However, the build dies saying that it cannot find arp/arp-utils:

configure: Configuring Apache Portable Runtime library...
configure:
configure: error: Bundled APR requested but not found at ./srclib/. Download
and unpack the corresponding apr and apr-util packages to ./srclib/.
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.pXoIWK (%build)
Bad exit status from /var/tmp/rpm-tmp.pXoIWK (%build)
Child return code was: 1

Now, I added this in the Sources:

Source0: http://www.apache.org/dist/httpd/httpd-%{version}.tar.bz2
Source1: http://www.apache.org/dist/httpd/httpd-%{version}-deps.tar.bz2

And I have confirmed that the srclib directory contains the files for arp and
arp-utils:

$ ll rpmbuild/SOURCES/httpd-2.4.7/srclib
total 12
drwxr-xr-x. 27 byrnejb byrnejb 4096 Jan  3 14:11 apr
drwxr-xr-x. 19 byrnejb byrnejb 4096 Nov 19 12:36 apr-util
-rw-r--r--.  1 byrnejb byrnejb  121 Feb 11  2005 Makefile.in


As this pretty much exhausts my small stock of knowledge respecting rpmbuild
it is evident that I need some help with the spec file to get past this
problem.  The spec is provided below and I would be grateful if anyone could
help me out with this. I am sure others would find the information useful as
well.

Thanks.


--- rpmbuild/SPECS/httpd.spec

%define contentdir /var/www
%define suexec_caller apache
%define mmn 20120211

Summary: Apache HTTP Server
Name: httpd
Version: 2.4.7
Release: 1
URL: http://httpd.apache.org/
Vendor: Apache Software Foundation
Source0: http://www.apache.org/dist/httpd/httpd-%{version}.tar.bz2
Source1: http://www.apache.org/dist/httpd/httpd-%{version}-deps.tar.bz2
License: Apache License, Version 2.0
Group: System Environment/Daemons
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
BuildRequires: autoconf, perl, pkgconfig, findutils
BuildRequires: zlib-devel, libselinux-devel, libuuid-devel
#BuildRequires: apr-devel = 1.4.0, apr-util-devel = 1.4.0
# using --with-included-apr instead
BuildRequires:  pcre-devel = 5.0
Requires: initscripts = 8.36, /etc/mime.types
Obsoletes: httpd-suexec
Requires(pre): /usr/sbin/useradd
Requires(post): chkconfig
Provides: webserver
Provides: mod_dav = %{version}-%{release}, httpd-suexec = %{version}-%{release}
Provides: httpd-mmn = %{mmn}

%description
Apache is a powerful, full-featured, efficient, and freely-available
Web server. Apache is also the most popular Web server on the
Internet.

%package devel
Group: Development/Libraries
Summary: Development tools for the Apache HTTP server.
Obsoletes: secureweb-devel, apache-devel
#Requires: apr-devel, apr-util-devel  # Replaced by --with-included-apr
Requires: pkgconfig, libtool
Requires: httpd = %{version}-%{release}

%description devel
The httpd-devel package contains the APXS binary and other files
that you need to build Dynamic Shared Objects (DSOs) for the
Apache HTTP Server.

If you are installing the Apache HTTP server and you want to be
able to compile or develop additional modules for Apache, you need
to install this package.

%package manual
Group: Documentation
Summary: Documentation for the Apache HTTP server.
Requires: httpd = :%{version}-%{release}
Obsoletes: secureweb-manual, apache-manual

%description manual
The httpd-manual package contains the complete manual and
reference guide for the Apache HTTP server. The information can
also be found at http://httpd.apache.org/docs/.

%package tools
Group: System Environment/Daemons
Summary: Tools for use with the Apache HTTP Server

%description tools
The httpd-tools package contains tools which can be used with
the Apache HTTP Server.

%package -n mod_authnz_ldap
Group: System Environment/Daemons
Summary: LDAP modules for the Apache HTTP server
BuildRequires: openldap-devel
Requires: httpd = %{version}-%{release}, 

Re: [CentOS] Need help with spec file for Apache-2.4.7

[Markus Falb]

On 03.Jan.2014, at 21:24, James B. Byrne wrote:

 I am trying to build an RPM for Apache-2.4.7-1 on Centos-6.5-i86_64.  I am
 using mock.
 
 The are three build dependencies that I am trying to resolve.  One,
 mod_socache_dc / distcache, I have simply removed from the spec file.  The
 other two are arp and apr-utils.  Since httpd-2.4.7 needs arp = 1.4 I got the
 two latter requirements from
 http://www.apache.org/dist/httpd/httpd-2.4.7-deps.tar.bz2 and extracted them
 into rpmbuild/SOURCES/httpd-2.4.7/srclib intending to use the
 --with-included-arp configuration directive per
 rpmbuild/SOURCES/httpd-2.4.7/INSTALL.

...

 However, the build dies saying that it cannot find arp/arp-utils:
 
 configure: Configuring Apache Portable Runtime library...
 configure:
 configure: error: Bundled APR requested but not found at ./srclib/. Download
 and unpack the corresponding apr and apr-util packages to ./srclib/.
 RPM build errors:
 error: Bad exit status from /var/tmp/rpm-tmp.pXoIWK (%build)
Bad exit status from /var/tmp/rpm-tmp.pXoIWK (%build)
 Child return code was: 1
 
 Now, I added this in the Sources:
 
 Source0: http://www.apache.org/dist/httpd/httpd-%{version}.tar.bz2
 Source1: http://www.apache.org/dist/httpd/httpd-%{version}-deps.tar.bz2

You have to extract Source1 into the BUILDDIR...
You can verify if apr directory is present with

$ rpmbuild -bp httpd.spec
$ ls ../BUILD/httpd-2.4.7

 --- rpmbuild/SPECS/httpd.spec

...

 %prep
 %setup -q

after that %setup macro your working directory should be 
rpmbuild/BUILD/httpd-2.4.7
now something like

%setup -D -q -b 1

http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html-single/RPM_Guide/index.html#id853841

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

[CentOS] Need help with gateways nd routing of 192.168.0.0/24 addresses

[James B. Byrne]

Arch = x86_64
OS = CentOS-6.4

Problem:
What is the correct gateway to specify for private IP addresses that
may pass thorough NAT?

Background:
Our gateway is configured thus:

#/etc/sysconfig/network-scripts/ificfg-eth1
BOOTPROTO=none
BROADCAST=
DEFROUTE=yes
DEVICE=eth1
DNS1=216.185.71.33
GATEWAY=216.185.64.53
IPADDR=216.185.71.1
IPV4_FAILURE_FATAL=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
MACADDR=
MTU=
NAME=LAN Link - eth1
NETMASK=
NETWORK=
NM_CONTROLLED=no
ONBOOT=yes
PREFIX=24
TYPE=Ethernet
USERCTL=no

and

#/etc/sysconfig/network-scripts/ificfg-eth1:192006
NAME=eth1:192006 internal
BOOTPROTO=none
MACADDR=
IPV6INIT=no
DEVICE=eth1:192006
NETMASK=255.255.255.0
MTU=
BROADCAST=192.168.6.255
ONPARENT=yes
IPADDR=192.168.6.1
NETWORK=192.168.6.0

On the gateway these are the routes present:

216.185.64.52/30 dev eth0  proto kernel  scope link  src 216.185.64.54
192.168.6.0/24 dev eth1  proto kernel  scope link  src 192.168.6.1
192.168.216.0/24 dev eth1  proto kernel  scope link  src 192.168.216.1
216.185.71.0/24 dev eth1  proto kernel  scope link  src 216.185.71.1
169.254.0.0/16 dev eth0  scope link  metric 1002
169.254.0.0/16 dev eth1  scope link  metric 1003
default via 216.185.64.53 dev eth0

Situation:
I have a device configured thus:

BOOTPROTO=none
BROADCAST=255.255.255.255
DEVICE=eth0
DNS1=216.185.71.33
GATEWAY=216.185.71.1
IPADDR=192.168.6.9
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
MACADDR=
MTU=
NAME=eth0
NETMASK=255.255.255.0
NETWORK=192.168.6.0
NM_CONTROLLED=no
ONBOOT=yes
PREFIX=24
TYPE=Ethernet

When I try and ping this device I see this:

PING 192.168.6.9 (192.168.6.9) 56(84) bytes of data.
From 216.185.71.1: icmp_seq=2 Redirect Host(New nexthop: 192.168.6.9)
From 216.185.71.1: icmp_seq=3 Redirect Host(New nexthop: 192.168.6.9)
From 216.185.71.1: icmp_seq=4 Redirect Host(New nexthop: 192.168.6.9)
From 216.185.71.1: icmp_seq=5 Redirect Host(New nexthop: 192.168.6.9)

If I down eth1:192006 on the gateway then all ping packets are simply
lost:

PING 192.168.6.9 (192.168.6.9) 56(84) bytes of data.
^C
--- 192.168.6.9 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8277ms


However, if leave eth1:192006 on the gateway up and I change the
gateway on 192.168 device to 192.168.6.1 the problem goes away.

I can see what works.  My question is really is this the way things
are supposed to be set up when one has private IP4 hosts on the same
network segments as public IP4 hosts?  Is there any way to configure
the gateway so that it only requires one internal address
[216.185.71.1] and can still route 192.168.6.0 addresses so that they
stay on the LAN segment?

-- 
***  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] need help with 6.3 install, kernel panic when os boots up

[Lewis]

Hi,

I am new to the community and look for some help for installing CentOS on
my Dell poweredge t420 server.

I am installing the CentOS on dual boot; already have the windows server
2008 installed via UEFI.
I installed the CentOS 6.3 via UEFI DVD boot too, and because my server
have the hardware RAID, so instead of the LVM, I use standard partition for
all my partitions.
The installation completed successfully and I let the installer write the
boot info into the EFI boot partition.
Reboot the machine after installation complete, but got kernel panic issue
when loading the OS.

I saw some message like this:

Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted blablba version

BTW, don't want to make thing complicated, but curious if the partition
might be a issue here(whether type, or the order of the partition)
The weird thing is before I installed the centOS using standard partition,
I by chance, chose use free space for create the partition to install the
OS once, and the system automatically help me create the LVM and OS was
working fine.
After that I format the harddisk and want to install it again using
standard partition, and it failed.

Thanks for any help. I could provide more debug info, just let me know how.

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

Re: [CentOS] Need help configuring wireless NIC

[Marko Vojinovic]

On Tuesday, 27. March 2012. 19.45.33 Ned Slider wrote:
 That ndiswrapper issue should hopefully be fixed now with the
 kmod-ndiswrapper-1.57-1.el6 release. It at least gives you that option
 should the native driver prove fruitless.

Indeed, the new ndiswrapper works perfectly! :-) The compat-wireless looks 
promising, but it still seems rough around the edges, and I needed a working 
solution asap, so... ;-)

Thanks for help!

Best, :-)
Marko


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

Re: [CentOS] Need help configuring wireless NIC

[Marko Vojinovic]

On Tuesday, 27. March 2012. 10.02.25 Arun Khan wrote:
 On Sat, Mar 24, 2012 at 10:05 PM, Marko Vojinovic vvma...@gmail.com wrote:
  Yesterday I managed to find a driver for my USB wireless dongle, and it is
  now correctly recognized by the kernel. However, I don't know how to
  configure it.
 How did you install the driver that you found?

Basically, I did this (following the advice of Ned Slider, from another 
thread):

# yum --enablerepo=elrepo-testing kmod-compat-wireless
# modprobe usb8xxx

Namely, on the http://elrepo.org/tiki/kmod-compat-wireless there is a list of 
drivers corresponding to various devices. My device is

# lsusb
Bus 001 Device 006: ID 1286:1fab Marvell Semiconductor, Inc. 88W8338 
[Libertas] 802.11g

so I did a search on the site for 1286 and found two relevant modules, 
usb8xxx and libertas. Modprobe-ing usb8xxx loads the following:

# lsmod 

Module  Size  Used by   
 
usb8xxx13926  0 
 
libertas  105931  1 usb8xxx
libertas_tf12514  0 
mac80211  234108  1 libertas_tf
cfg80211  164625  2 libertas,mac80211
rfkill 15242  1 cfg80211
compat 16607  2 mac80211,cfg80211
lib802114194  1 libertas

When I plug in the device, /var/log/messages says:

Mar 27 08:10:30 CicaMaca kernel: usb 1-2: new high speed USB device using 
ehci_hcd and address 7
Mar 27 08:10:31 CicaMaca kernel: usb 1-2: New USB device found, idVendor=1286, 
idProduct=1fab
Mar 27 08:10:31 CicaMaca kernel: usb 1-2: New USB device strings: Mfr=1, 
Product=2, SerialNumber=0
Mar 27 08:10:31 CicaMaca kernel: usb 1-2: Product: 54M USB Wireless NIC  
Mar 27 08:10:31 CicaMaca kernel: usb 1-2: Manufacturer: Tenda.. 
Mar 27 08:10:31 CicaMaca kernel: usb 1-2: configuration #1 chosen from 1 choice

which is basically the same information as found in dmesg. The device is 
correctly recognized, as far as it goes.

 What is the output of /sbin/ifconfig -a  does it list the wifi
 device i.e. wlan0 ?

No, ifconfig lists only my two wired ethernet devices (eth0, eth1), and the 
openvpn virtual ethernet device (tap0). No mention of anything wireless.

 Do ethtool --driver  ifaceto find the driver associated with
 your wifi network interface.

What should iface be? There isn't one associated to the wireless NIC, or I 
am unable to find it. I tried the following methods:

# ifconfig -a
# lshw -C network
# rfkill list
# iwconfig

None of these report anything except my three wired devices (if at all).

I vaguely understand that all these utilities are querrying the kernel for the 
info about hardware, but the kernel does not seem to be exposing it (or 
requires some non-automatic initialization). I tried looking at various places 
under /proc (to see if I can read something manually), but I found nothing, 
and TBH I don't quite know where to look.

 Usuall the NetworkManager detects all the active network interfaces
 and presents the devices.   In your case, I suspect the wifi device is
 not being initialized.

The NetworkManager does indeed give some indication that there is a wireless 
device, but it doesn't tell much. When I do a service NetworkManager 
restart, this is the only relevant thing I recognized about wireless from 
/var/log/messages:

Mar 27 08:24:24 CicaMaca NetworkManager[30454]: info WiFi enabled by radio 
killswitch; enabled by state file
Mar 27 08:24:24 CicaMaca NetworkManager[30454]: info WWAN enabled by radio 
killswitch; enabled by state file
Mar 27 08:24:24 CicaMaca NetworkManager[30454]: info WiMAX enabled by radio 
killswitch; enabled by state file
Mar 27 08:24:24 CicaMaca NetworkManager[30454]: info Networking is enabled 
by state file

Everything else is about eth0, eth1 and tap0 devices. I can provide full logs 
if you think I missed something.

I am almost out of patience with this, and I'm already considering buying 
another wireless card, or rather a wireless router which can act as a client 
to another wireless router, so that I can connect the computer via wired 
ethernet. I'd prefer not to waste any money on this, especially if it is just 
a software configuration issue, but I also need the damn thing to start working 
sooner than later.

Btw, the device is working properly under Windows, and it used to work 
properly under Linux with ndiswrapper. But current ndiswrapper fails to work 
(or even fails to compile) on current CentOS, so my only option is to try a 
native Linux driver from kmod-compat-wireless.

If there is any way to make this work without throwing money at the problem, 
I'd appreciate to know. Also, 

Re: [CentOS] Need help configuring wireless NIC

[anax]

Hi Marko
if your WLAN interface does not show up in ifconfig or in ls -l 
/sys/class/net/  then
- your system recognizes that it has to load the modules you mention 
when you plug in your WLAN interface
- but the modules are incapable to install the interface correctly

if you say you cannot bring to work ndiswrapper because its compilation 
fails, then you are in bad luck.

I once had a similar problem with a D-Link card (featuring the adx 
TI-chip). What I did: I waited until a new version of ndiswrapper was 
available, compiled this one, and off I went.

suomi

On 03/27/2012 08:46 AM, Marko Vojinovic wrote:
 On Tuesday, 27. March 2012. 10.02.25 Arun Khan wrote:
 On Sat, Mar 24, 2012 at 10:05 PM, Marko Vojinovicvvma...@gmail.com  wrote:
 Yesterday I managed to find a driver for my USB wireless dongle, and it is
 now correctly recognized by the kernel. However, I don't know how to
 configure it.
 How did you install the driver that you found?

 Basically, I did this (following the advice of Ned Slider, from another
 thread):

 # yum --enablerepo=elrepo-testing kmod-compat-wireless
 # modprobe usb8xxx

 Namely, on the http://elrepo.org/tiki/kmod-compat-wireless there is a list of
 drivers corresponding to various devices. My device is

 # lsusb
 Bus 001 Device 006: ID 1286:1fab Marvell Semiconductor, Inc. 88W8338
 [Libertas] 802.11g

 so I did a search on the site for 1286 and found two relevant modules,
 usb8xxx and libertas. Modprobe-ing usb8xxx loads the following:

 # lsmod
 Module  Size  Used by
 usb8xxx13926  0
 libertas  105931  1 usb8xxx
 libertas_tf12514  0
 mac80211  234108  1 libertas_tf
 cfg80211  164625  2 libertas,mac80211
 rfkill 15242  1 cfg80211
 compat 16607  2 mac80211,cfg80211
 lib802114194  1 libertas

 When I plug in the device, /var/log/messages says:

 Mar 27 08:10:30 CicaMaca kernel: usb 1-2: new high speed USB device using
 ehci_hcd and address 7
 Mar 27 08:10:31 CicaMaca kernel: usb 1-2: New USB device found, idVendor=1286,
 idProduct=1fab
 Mar 27 08:10:31 CicaMaca kernel: usb 1-2: New USB device strings: Mfr=1,
 Product=2, SerialNumber=0
 Mar 27 08:10:31 CicaMaca kernel: usb 1-2: Product: 54M USB Wireless NIC
 Mar 27 08:10:31 CicaMaca kernel: usb 1-2: Manufacturer: Tenda..
 Mar 27 08:10:31 CicaMaca kernel: usb 1-2: configuration #1 chosen from 1 
 choice

 which is basically the same information as found in dmesg. The device is
 correctly recognized, as far as it goes.

 What is the output of /sbin/ifconfig -a  does it list the wifi
 device i.e. wlan0 ?

 No, ifconfig lists only my two wired ethernet devices (eth0, eth1), and the
 openvpn virtual ethernet device (tap0). No mention of anything wireless.

 Do ethtool --driveriface to find the driver associated with
 your wifi network interface.

 What shouldiface  be? There isn't one associated to the wireless NIC, or I
 am unable to find it. I tried the following methods:

 # ifconfig -a
 # lshw -C network
 # rfkill list
 # iwconfig

 None of these report anything except my three wired devices (if at all).

 I vaguely understand that all these utilities are querrying the kernel for the
 info about hardware, but the kernel does not seem to be exposing it (or
 requires some non-automatic initialization). I tried looking at various places
 under /proc (to see if I can read something manually), but I found nothing,
 and TBH I don't quite know where to look.

 Usuall the NetworkManager detects all the active network interfaces
 and presents the devices.   In your case, I suspect the wifi device is
 not being initialized.

 The NetworkManager does indeed give some indication that there is a wireless
 device, but it doesn't tell much. When I do a service NetworkManager
 restart, this is the only relevant thing I recognized about wireless from
 /var/log/messages:

 Mar 27 08:24:24 CicaMaca NetworkManager[30454]:info  WiFi enabled by radio
 killswitch; enabled by state file
 Mar 27 08:24:24 CicaMaca NetworkManager[30454]:info  WWAN enabled by radio
 killswitch; enabled by state file
 Mar 27 08:24:24 CicaMaca NetworkManager[30454]:info  WiMAX enabled by radio
 killswitch; enabled by state file
 Mar 27 08:24:24 CicaMaca NetworkManager[30454]:info  Networking is enabled
 by state file

 Everything else is about eth0, eth1 and tap0 devices. I can provide full logs
 if you think I missed something.

 I am almost out of patience with this, and I'm already considering buying
 another wireless card, or rather a wireless router which can act as a client
 to another wireless router, so that I can connect the computer via wired
 ethernet. I'd prefer not to waste any money on this, especially if it is just
 a software configuration issue, but I also need the damn thing to start 
 working
 sooner than later.

 Btw, the device is working properly under Windows, and it used to work
 properly under Linux with ndiswrapper. 

Re: [CentOS] Need help configuring wireless NIC

[Ned Slider]

On 27/03/12 07:46, Marko Vojinovic wrote:


 Btw, the device is working properly under Windows, and it used to work
 properly under Linux with ndiswrapper. But current ndiswrapper fails to work
 (or even fails to compile) on current CentOS, so my only option is to try a
 native Linux driver from kmod-compat-wireless.


That ndiswrapper issue should hopefully be fixed now with the 
kmod-ndiswrapper-1.57-1.el6 release. It at least gives you that option 
should the native driver prove fruitless.



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

Re: [CentOS] Need help configuring wireless NIC

[Arun Khan]

On Sat, Mar 24, 2012 at 10:05 PM, Marko Vojinovic vvma...@gmail.com wrote:

 Hi everyone! :-)

 Yesterday I managed to find a driver for my USB wireless dongle, and it is now
 correctly recognized by the kernel. However, I don't know how to configure it.

How did you install the driver that you found?

What is the output of /sbin/ifconfig -a  does it list the wifi
device i.e. wlan0 ?

Do ethtool --driver  ifaceto find the driver associated with
your wifi network interface.

In my case I get the following output:

# ethtool --driver wlan0
driver: ath9k
version: 3.2.0-1-amd64
firmware-version: N/A
bus-info: :02:00.0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no

Usuall the NetworkManager detects all the active network interfaces
and presents the devices.   In your case, I suspect the wifi device is
not being initialized.

HTH,
-- Arun Khan
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Need help configuring wireless NIC

[Marko Vojinovic]

Hi everyone! :-)

Yesterday I managed to find a driver for my USB wireless dongle, and it is now 
correctly recognized by the kernel. However, I don't know how to configure it. 

The system-config-network opens up in text mode and is not very forthcoming (it 
lists ethernet, ISDN and modem as possibilities for configuring a new device). 
I don't know how to create an /etc/sysconfig/network-scripts/ifcfg-whatever 
manually for my wireless card. NetworkManager doesn't see the device since the 
ifcfg* script doesn't exist. What am I supposed to do? (Google also didn't 
help...).

The device is listed by lsusb as:

# lsusb | grep 802
Bus 001 Device 005: ID 1286:1fab Marvell Semiconductor, Inc. 88W8338 
[Libertas] 802.11g

The libertas kernel module is loaded:

# lsmod | grep liber
libertas  105931  0 
cfg80211  164625  1 libertas
lib802114194  1 libertas

How do I find out the name of the device, and how do I create the ifcfg script 
properly?

Best, :-)
Marko


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

[CentOS] need help to build livecd and create success iso file but it hang

[ha do]

Hi all

my environment:
  1/ windows 7 OS system
  2/ use virtual box install the host centos system


i try to make a centos livecd and i follow the step
1/ create  file: vi /etc/yum.repos.d/centos-livecd.repo and the content of file:
# Name: CentOS LiveCD repository
[livecd]
name = CentOS $releasever - LiveCD
baseurl = 
http://www.nanotechnologies.qc.ca/propos/linux/centos-live/$basearch/live
enabled=1
protect=0
gpgkey = http://www.nanotechnologies.qc.ca/propos/linux/RPM-GPG-KEY-PGuay2010
2/ yum install livecd-tools syslinux anaconda-runtime

3/ create file alochym.ks and content of file:
lang en_US.UTF-8
keyboard us
timezone US/Eastern
auth --useshadow --enablemd5
selinux --enforcing
firewall --disabled
repo --name=a-base
--baseurl=http://mirror-fpt-telecom.fpt.net/centos/5/os/$basearch
repo --name=a-updates 
--baseurl=http://mirror-fpt-telecom.fpt.net/centos/5/updates/$basearch
repo --name=a-extras  
--baseurl=http://mirror-fpt-telecom.fpt.net/centos/5/extras/$basearch
repo --name=a-live
--baseurl=http://www.nanotechnologies.qc.ca/propos/linux/centos-live/$basearch/live
%packages
bash
kernel
syslinux
passwd
policycoreutils
chkconfig
authconfig
rootfiles
comps-extras
xkeyboard-config
openssh

4/ run command : LANG=C livecd-creator --config=/mnt/alochym.ks 
--fslabel=CentOS-mini

5/ download the file CentOS-mini.iso to windows 7

6/ use virtual box create new virtual machine with CentOS-mini.iso as cdrom

the log of create livecd : http://pastebin.com/Z5BFASXa

the problem is when i use the CentOS-mini.iso with new virtual machine and the 
virtual manchine hang when automatic boot to 0 second

can somebody help me

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