CentOS-6.6
We have a host that has multiple IPv4 addresses aliased to eth0. The
primary address is 216.185.71.x and the alias is 192.168.6.x.
This host connects to devices on both netblocks without problems.
Only default routing is used and it looks like this:
#ip route
192.168.6.0/24 dev eth0 proto kernel scope link src 192.168.6.x
216.185.71.0/24 dev eth0 proto kernel scope link src 216.185.71.x
169.254.0.0/16 dev eth0 scope link metric 1002
default via 192.168.6.1 dev eth0 src 192.168.6.x
default via 216.185.71.1 dev eth0
When the system connects to internal systems via ssh it uses the src
216.185.71.x for devices on that netblock and 192.168.6.x for devices
on the other.
The problem is that when we try to establish an ssh connection
off-site to another netblock altogether the host uses 192.168.6.x as
the source and the destination gets the public side IP address of our
gateway router as the point of origin due to masquerading.
I have solved this by explicitly binding ssh to the public ipv4 when
connecting using the --bind=216.185.71.x parameter. But I have two
questions I would like to find answers for
1. Why is ssh using the private IP in preference to the public IP when
connecting to off-site addresses?
2. How does one configure the routing table on network startup to
specifically detail the route particular addresses are supposed to
take?
For diagnosis here are the ifcfg scripts used for both interfaces:
DEVICE="eth0"
BOOTPROTO="static"
BROADCAST="216.185.71.255"
DNS1="216.185.71.33"
GATEWAY="216.185.71.1"
HWADDR="38:60:77:D5:AC:D8"
IPADDR="216.185.71.x"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
NETMASK="255.255.255.0"
NM_CONTROLLED="no"
ONBOOT="yes"
TYPE="Ethernet"
UUID="0202e615-ce93-4fe1-833a-c11259afb850"
DEVICE="eth0:192"
BOOTPROTO="static"
BROADCAST="192.168.6.255"
GATEWAY="192.168.6.1"
IPADDR="192.168.6.x"
NETMASK="255.255.255.0"
NM_CONTROLLED="no"
ONPARENT="yes"
TYPE="Ethernet"
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@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
Are there any tools to help assemble libraries and debuginfo to
examine core dumps that happened on another host where the versions
don't match? Something like mock but build-version specific and with
the debuginfo packages pulled in?
--
Les Mikesell
lesmikesell(a)gmail.com
On Tue, February 17, 2015 15:20, Les Mikesell wrote:
> Are there any tools to help assemble libraries and debuginfo to
> examine core dumps that happened on another host where the versions
> don't match? Something like mock but build-version specific and with
> the debuginfo packages pulled in?
>
I am not sure that I understand your question so if this answer is
totally irrelevant then please forgive me.
But, in case this might help, you can configure mock to use locally
provided repos and different architectures via the --configdir
parameter. You provide an architecture specific config file like
epel-6-x86_64.cfg in the specified directory and alter it to require
packages to suit a specific build requirement.
One of mine looks like this:
config_opts['root'] = 'epel-6-x86_64'
config_opts['target_arch'] = 'x86_64'
config_opts['legal_host_arches'] = ('x86_64',)
config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build'
config_opts['dist'] = 'el6' # only useful for --resultdir variable subst
config_opts['yum.conf'] = """
[main]
cachedir=/var/cache/yum
debuglevel=1
reposdir=/dev/null
logfile=/var/log/yum.log
retries=20
obsoletes=1
gpgcheck=0
assumeyes=1
syslog_ident=mock
syslog_device=
# repos
[base]
name=BaseOS
enabled=1
mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os
failovermethod=priority
exclude=http*
[updates]
name=updates
enabled=1
mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates
failovermethod=priority
exclude=http*
[epel]
name=epel
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=x86…
failovermethod=priority
exclude=http*
[testing]
name=epel-testing
enabled=0
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel6&a…
failovermethod=priority
[local]
name=local
baseurl=file:///home/byrnejb/mock/repos/x86_64/
cost=0
enabled=1
[koji]
name=koji
baseurl=http://kojipkgs.fedoraproject.org/repos/dist-6E-epel-build/latest/x…
cost=2000
enabled=0
[epel-debug]
name=epel-debug
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-debug-6&ar…
failovermethod=priority
enabled=0
"""
and one calls it like this:
mock --rebuild --root=epel-6-x86_64 --configdir=/home/byrnejb/mock
/home/byrnejb/rpmbuild/SRPMS/httpd-2.4.9-1.el6.src.rpm
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@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
> On Wed, 18 Feb 2015 05:36:48 +1300
> Jegadeesh Kumar wrote:
>
>> I setup the RPM build server and read some doc to write the spec
>> files. but i did get it clearly. So can you guys please help me
>> to write a new RPM spec.
If you have set up an RPM build server then you should have installed
the rpmbuild and rpmdevtools packages. If you have installed the
latter then you can use vi (vim/gvim) to automatically create an empty
spec template file simply by opening any new file name ending in
'.spec'. It will look like this:
Name:
Version:
Release: 1%{?dist}
Summary:
Group:
License:
URL:
Source0:
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX)
BuildRequires:
Requires:
%description
%prep
%setup -q
%build
%configure
make %{?_smp_mflags}
%install
rm -rf %{buildroot}
make install DESTDIR=%{buildroot}
%clean
rm -rf %{buildroot}
%files
%defattr(-,root,root,-)
%doc
%changelog
* Fri Apr 05 2013 James B. Byrne <byrnejb(a)harte-lyne.ca>
- Rebuild for CentOS-6.4
- This description is an example and is not automatically
- generated for you.
Note that the formats for the date and identity in changelog entries
are very specific and include the leading '*'. You cannot use any
other format (to my knowledge) than that given above as an example.
Each descriptive line thereafter must be prefaced by'- '.
See:
https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pa…
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@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
NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5
Dell PowerEdge 2970, Seagate SATA drive, non-raid.
I have this server which has been dying randomly, with no logs.
I had a tail -f over ssh for a week, when this just happened.
Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080)
Feb 8 00:10:21 thirteen-230 kernel: sd 4:0:0:0: [sda] CDB: Write(10): 2a 00 1a 17 a1 6f 00 00 01 00
Feb 8 00:10:51 thirteen-230 kernel: mptscsih: ioc0: WARNING - Issuing Reset from mptscsih_IssueTaskMgmt!! doorbell=0x24000000
Feb 8 00:10:51 thirteen-230 kernel: mptbase: ioc0: Initiating recovery
Feb 8 00:11:13 thirteen-230 kernel: mptscsih: ioc0: task abort: SUCCESS (rv=2002) (sc=ffff880057a0a080)
Write failed: Connection reset by peer
After reading https://access.redhat.com/solutions/108273, I am increasing the logging (shown below) but I am not confident about this wait and see approach.
sysctl -w dev.scsi.logging_level=98367
I am also going to check smartctl output once I get onsite to power cycle the system.
Other posts I have read, but I can not act on yet:
* http://unix.stackexchange.com/questions/34173/mptscsih-ioc0-task-abort-succ…
* https://bugzilla.kernel.org/show_bug.cgi?id=18652
* https://bugzilla.redhat.com/show_bug.cgi?id=483424
* https://bugzilla.kernel.org/show_bug.cgi?id=42765
* http://sourceforge.net/p/smartmontools/mailman/message/23849184/
* http://kb.softescu.ro/category/hardware/dell/
-Jason
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
OK, I plugged in a web cam device (something called a 'Zoomy' -- a web
cam/microscope). It is recognized by the unc driver. Now what?
Does there exist a program that can use this device? Or do I have to write
one from scratch? I have been searching the web, but all of the links are
about getting and installing *drivers*. I don't need a driver, I need a
userland program.
With Ubuntu 14.04, there is a program named Cheese, but I can't find a
version that works with CentOS 5. And no, don't tell me to install Ubuntu
14.04!
--
Robert Heller -- 978-544-6933
Deepwoods Software -- Custom Software Services
http://www.deepsoft.com/ -- Linux Administration Services
heller(a)deepsoft.com -- Webhosting Services
Hi team,
I setup the RPM build server and read some doc to write the spec files. but
i did get it clearly. So can you guys please help me to write a new RPM
spec.
or give me a scenario to write
Thanks,
Jegadeesh
Send CentOS-announce mailing list submissions to
centos-announce(a)centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request(a)centos.org
You can reach the person managing the list at
centos-announce-owner(a)centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CEBA-2015:0224 CentOS 6 system-config-printer FASTTRACK
BugFix Update (Johnny Hughes)
2. CEBA-2015:0231 CentOS 6 bind-dyndb-ldap BugFix Update
(Johnny Hughes)
----------------------------------------------------------------------
Message: 1
Date: Mon, 16 Feb 2015 14:55:17 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CEBA-2015:0224 CentOS 6
system-config-printer FASTTRACK BugFix Update
Message-ID: <20150216145517.GA2848(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2015:0224
Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0224.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
0b1e102e337bc6ca944887d5a86efce096e4f02b0d453259eb7def61aa100f10 system-config-printer-1.1.16-25.el6.i686.rpm
d9e38068494f5baa375b4b4b2f0fafccbd5da2384e7302253540eb03880afbf7 system-config-printer-libs-1.1.16-25.el6.i686.rpm
3467770de97e623541c1e78d672f5bb60dc58b582fb7732e1375cd084203552b system-config-printer-udev-1.1.16-25.el6.i686.rpm
x86_64:
4c707af2bc1752ceb64bea31b5b49421bc4510b0de09168984bdf619c83f86fc system-config-printer-1.1.16-25.el6.x86_64.rpm
9d6b1a5b04372fb7997490be1314d57865d37ee2f876403af979b8bb7c6ad021 system-config-printer-libs-1.1.16-25.el6.x86_64.rpm
e10ae7473a8400abc3434a98ac765344915227f388a1f1fab953f088ab7e3af4 system-config-printer-udev-1.1.16-25.el6.x86_64.rpm
Source:
30b20b371dfa2f021d329e5fa1d215595792417b07e6b18bb8d3fa77f75e2884 system-config-printer-1.1.16-25.el6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
------------------------------
Message: 2
Date: Mon, 16 Feb 2015 18:18:53 +0000
From: Johnny Hughes <johnny(a)centos.org>
To: centos-announce(a)centos.org
Subject: [CentOS-announce] CEBA-2015:0231 CentOS 6 bind-dyndb-ldap
BugFix Update
Message-ID: <20150216181853.GA7919(a)n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Bugfix Advisory 2015:0231
Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0231.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
ca86c5483876d2f979bff731622c5508248baecf4a61b13c77a522c153384587 bind-dyndb-ldap-2.3-6.el6_6.i686.rpm
x86_64:
fd444fbc66c4058cb422976051822ddbb6ba72d77e9307fe38e7ed52fc9dfddb bind-dyndb-ldap-2.3-6.el6_6.x86_64.rpm
Source:
9d772df68036dd0915327569616b79ab429016b68b669ac532ae37cf3e86f826 bind-dyndb-ldap-2.3-6.el6_6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos(a)irc.freenode.net
------------------------------
_______________________________________________
CentOS-announce mailing list
CentOS-announce(a)centos.org
http://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 120, Issue 5
***********************************************
Hello,
I wan to know the details steps about how to do OS upgrade?
Say for an example currently i am using CentOS 6.2 and plan to upgrade that to 7. Please detail me the steps.
Thanks,
Jegadeesh