Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Problems installing packages from the CD
by Mauricio Tavares 23 Feb '17

23 Feb '17

So I did a minimal install of centos 7 vm guest just to find out it did not install perl. Since as of right now I have no properly functioning network on that machine (different issue; we can talk about that in another post), I went for the next best thing: install CD. I grabbed the CentOS-7-x86_64-Everything-1611.iso CD (around 8GB), attached it to the guest, and mounted it on /mnt. Then I edited the cat /etc/yum.repos.d/CentOS-Media.repo # CentOS-Media.repo # # This repo can be used with mounted DVD media, verify the mount point for # CentOS-7. You can use this repo and yum to install items directly off the # DVD ISO that we release. # # To use this repo, put in your DVD and use it with the other repos too: # yum --enablerepo=c7-media [command] # # or for ONLY the media repo, do this: # # yum --disablerepo=\* --enablerepo=c7-media [command] [c7-media] name=CentOS-$releasever - Media baseurl=file:///mnt/ gpgcheck=1 enabled=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7 I then run yum clean all and then decided to look for perl only on the cd repo, i.e. yum --disablerepo=\* --enablerepo=c7-media search perl It gave me back the pcre package, which is already installed. I did check the /mnt.Packages dir and there are plenty of perl-related packages including itself. yum --disablerepo=\* --enablerepo=c7-media list all shows only installed packages, some of which are shown (?) to have been installed from c7-media.

2 2

OT: hardware, IBM 3650 M2 won't power on
by m.roth＠5-cent.us 23 Feb '17

23 Feb '17

I've never seen anything like this. We moved it from the data center yesterday, and this morning I plug it in, and it won't power up. I find a manual for it online, and it says that on plugging it in, wait 3 minutes. The power button will flash 4x/sec, then slow down to once a sec, and at that time you can power it up. Well, it never stops flashing at 4x/sec. I've connected a network cable, wondering if it's in wake-on-lan; I've tried connecting to it via its management port, and *zip*. I'm not going to do, as several folks' posts that I googled (been at that for hours), cut the cable and solder in an on/off switch. I have taken the lid uff, reseated the PSUs, and the cable connecting to the front panel, and nada. Anyone got any ideas? mark

8 16

CentOS-announce Digest, Vol 144, Issue 7
by centos-announce-request＠centos.org 23 Feb '17

23 Feb '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. CESA-2017:0190 Critical CentOS 5 firefox Security Update (Johnny Hughes) 2. CESA-2017:0190 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2017:0190 Critical CentOS 7 firefox Security Update (Johnny Hughes) 4. CESA-2017:0293 Important CentOS 6 kernel Security Update (Johnny Hughes) 5. CESA-2017:0294 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Feb 2017 13:18:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 5 firefox Security Update Message-ID: <20170222131810.GA7707(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4f351259abd6614da05b1ea8e9e4b83486631cadb9aa439996c7070f9eff8588 firefox-45.7.0-2.el5.centos.i386.rpm x86_64: 4f351259abd6614da05b1ea8e9e4b83486631cadb9aa439996c7070f9eff8588 firefox-45.7.0-2.el5.centos.i386.rpm 1e2b1680b6c395039fafb267db3426fde8c4f2c06b2ba9744f11e18736d2917f firefox-45.7.0-2.el5.centos.x86_64.rpm Source: fb33febf301919266593261c3e79a43af3957012b04083b99dc89b5053990019 firefox-45.7.0-2.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 22 Feb 2017 13:20:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 6 firefox Security Update Message-ID: <20170222132044.GA45572(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f34f42fb0d7c2d68da3493786c3ea6db8a5c3025ec23c4920f33739466aee8c5 firefox-45.7.0-2.el6.centos.i686.rpm x86_64: f34f42fb0d7c2d68da3493786c3ea6db8a5c3025ec23c4920f33739466aee8c5 firefox-45.7.0-2.el6.centos.i686.rpm b905dbe1aeb129fcf9dfcdae0476003f4d6f5e73615762346badf37e76c3a43d firefox-45.7.0-2.el6.centos.x86_64.rpm Source: 98283468cf9d1e539fc7dfbe25e79160d9b9c631dd30d1fd4cef84d1fd64b573 firefox-45.7.0-2.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 22 Feb 2017 13:44:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0190 Critical CentOS 7 firefox Security Update Message-ID: <20170222134406.GA58643(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0190 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0190.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 38bdd177d609902c6d514deae731df1f6778409730fa61dd213ad0937d54223c firefox-45.7.0-2.el7.centos.i686.rpm 4ce5659c46dee0b5a25d4e6583e9d498b2d146a9ba33565d1c35a2b983766942 firefox-45.7.0-2.el7.centos.x86_64.rpm Source: 7db60cb74cd564e32e8e9341c8b1c80e032afa31acfe7c155d0a725a2c80126b firefox-45.7.0-2.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Thu, 23 Feb 2017 04:21:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0293 Important CentOS 6 kernel Security Update Message-ID: <20170223042138.GA3656(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0293 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0293.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8e5db1418cf0c4cc98c3b3f75c73ae681e6d1af6e6af960bc03f96dd38c444c6 kernel-2.6.32-642.13.2.el6.i686.rpm 7b7c0130f6d949dbab08c622d33d3a965189992d9f790d2422ab847f7524266a kernel-abi-whitelists-2.6.32-642.13.2.el6.noarch.rpm d34bf5af966a9598fa12736e7cae72c3a02da76332774123b0e16905f88d4e95 kernel-debug-2.6.32-642.13.2.el6.i686.rpm bcef4faf1884b67f02e7b5a046bfc28ddb9f3c2f5009e86afefe00123a8d74e8 kernel-debug-devel-2.6.32-642.13.2.el6.i686.rpm 2b2ca285b26e3b90eee5ac182fcb8588532fb882632304f8a21c3e78dbb9c4a2 kernel-devel-2.6.32-642.13.2.el6.i686.rpm 83bc6d344aff521bc6b5766347fec8f2ccb482330be746661624d5e76624616a kernel-doc-2.6.32-642.13.2.el6.noarch.rpm ca77321a113b1a089c61a9d053efc06063476a0a6aeb08c257a3fb58591e8feb kernel-firmware-2.6.32-642.13.2.el6.noarch.rpm 60fb671174abdfa8ed467ff6cd71cf8ecae26f06ed94e6cd8aaca6b3820f29d5 kernel-headers-2.6.32-642.13.2.el6.i686.rpm e1ddc8fce78af40b1202267e7bdbefbb01f7b8ad9a75d68e0e88587dc68b7d4c perf-2.6.32-642.13.2.el6.i686.rpm 70bbabecf85895e3d7a1fb2d3cc6ffeccdcf0bc664bd3d994670a05cf7c6e7f7 python-perf-2.6.32-642.13.2.el6.i686.rpm x86_64: d42ff04a27c00197952bb3b84c66891022fadff49b2a907039061189e648820c kernel-2.6.32-642.13.2.el6.x86_64.rpm 7b7c0130f6d949dbab08c622d33d3a965189992d9f790d2422ab847f7524266a kernel-abi-whitelists-2.6.32-642.13.2.el6.noarch.rpm eebf181ae2c9217b4a65831903298e74454c11788ff3c4b66d66796f0d539736 kernel-debug-2.6.32-642.13.2.el6.x86_64.rpm bcef4faf1884b67f02e7b5a046bfc28ddb9f3c2f5009e86afefe00123a8d74e8 kernel-debug-devel-2.6.32-642.13.2.el6.i686.rpm 6224f08bbc8ec073385e4d9c6a4d18d1689e9914b44710214660d37a1725e4bf kernel-debug-devel-2.6.32-642.13.2.el6.x86_64.rpm af93fee2aa92ca20fc2b2a88415b9abeb1a4d8bb348f694216d7a3eaf07f7d61 kernel-devel-2.6.32-642.13.2.el6.x86_64.rpm 83bc6d344aff521bc6b5766347fec8f2ccb482330be746661624d5e76624616a kernel-doc-2.6.32-642.13.2.el6.noarch.rpm ca77321a113b1a089c61a9d053efc06063476a0a6aeb08c257a3fb58591e8feb kernel-firmware-2.6.32-642.13.2.el6.noarch.rpm 49e71d4eb8403a790910ad73529e72a52971ba0aebbe07dac25172946e94f200 kernel-headers-2.6.32-642.13.2.el6.x86_64.rpm 5b0d68de2c859691712276038c2640da96aeec17754b0aa5d0ffbd0fc2013261 perf-2.6.32-642.13.2.el6.x86_64.rpm 0455e0f63e3966926a1bbf0bd7882b90a67db437ad2e63b38800d8b6aa94c4be python-perf-2.6.32-642.13.2.el6.x86_64.rpm Source: 888ead19200985f6ad2a8f8fd53336e57b695ceb0ae47c026f82a28f67f70e7c kernel-2.6.32-642.13.2.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Thu, 23 Feb 2017 05:45:33 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:0294 Important CentOS 7 kernel Security Update Message-ID: <20170223054533.GA18280(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:0294 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-0294.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 399d85490609511d4f57270f4db2ae22aff1e77dbfb9fa1735f3acd74a32b15d kernel-3.10.0-514.6.2.el7.x86_64.rpm ade938b455c925303441ff53433c55c4507501c34537a8dac3267f2027ac70a9 kernel-abi-whitelists-3.10.0-514.6.2.el7.noarch.rpm b9cbfd11d08961b8c9c78e82e669693b33063f7e5c5cd4835f17403e7a8adfd4 kernel-debug-3.10.0-514.6.2.el7.x86_64.rpm f845b17f3955c7e37c80ae44810c623e5e8679159395eb71374e3f081dbf8695 kernel-debug-devel-3.10.0-514.6.2.el7.x86_64.rpm b7fe4fc10de18db85e12d32dcb702229ed2fb3137e7cee784f5a15a2459f5db2 kernel-devel-3.10.0-514.6.2.el7.x86_64.rpm d2043d02d55f4189e3462149fbe80f8e281170d07acd5f4153636fdec89ab3c5 kernel-doc-3.10.0-514.6.2.el7.noarch.rpm 5849bd28663d4c8a112121b13c19b10b2f43decfc3a1bc3b4246227a3e255297 kernel-headers-3.10.0-514.6.2.el7.x86_64.rpm 640ba1792316b03339098f76f3bab13d2ca79a1f309122df21c3bf85ccba90e4 kernel-tools-3.10.0-514.6.2.el7.x86_64.rpm 8e9dd3262234c4d1cd6bb1cfe591111189bba8282e56cf284c5086c5977c7f96 kernel-tools-libs-3.10.0-514.6.2.el7.x86_64.rpm 35d8fee07d663665c297c3d6bd4dc623afc6fcae7bde1f09be88d4773a2837f9 kernel-tools-libs-devel-3.10.0-514.6.2.el7.x86_64.rpm c416658118df7791b9b8eb4fe9fbf941e1cb2005fd91b7f80b29232bf3b1aa7b perf-3.10.0-514.6.2.el7.x86_64.rpm 14c06f8de0921bd9a671feff1813b6af0c58a75fbe5f47ef92e4e6324c6c7249 python-perf-3.10.0-514.6.2.el7.x86_64.rpm Source: 19b33fba0c0c2c8eb838fcb65983c7dadc1c67b42c9b72e7dcd271d2c7b73572 kernel-3.10.0-514.6.2.el7.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 144, Issue 7 ***********************************************

1 0

BOINC
by Alessandro Baggi 23 Feb '17

23 Feb '17

Hi list, I've installed boinc-client and boinc-manager from epel. After starting boinc-client with systemctl when I try to connect from boincmgr I get "Unable to connect to boinc client". I've added to unit file --allow_remote_gui_rpc and on netstat I get: tcp 0 0 0.0.0.0:31416 0.0.0.0:* LISTEN 4762/boinc_client On this machine there aren't iptables rules I've also added my current user to boinc group without success. I've tried also to run boincmgr from root without success. Reading from https://boinc.berkeley.edu/wiki/Client_configuration I've not found any usefull config parameters to save in /var/lib/boinc/cc_config.xml Selinux is Disabled. I've tried also to run from a root shell: /usr/bin/boinc_client Running the manager from root I can connect to the client but from simple user I cannot. So I don't understand where is the problem. What I can do to solve this problem? Thanks in advance.

2 3

Re: [CentOS] Network conections problems
by Rommel Rodriguez Toirac 23 Feb '17

23 Feb '17

El 21 de febrero de 2017 7:00:03 GMT-05:00, centos-request(a)centos.org escribió: >Send CentOS mailing list submissions to > centos(a)centos.org > > >From: Kahlil Hodgson <kahlil.hodgson(a)dp.exchange> >To: CentOS mailing list <centos(a)centos.org> >Subject: Re: [CentOS] Network conections problems > >First guess is that you may have two devices on the network with the >same ip address. > >Next time this happens, try doing > >1. 'arp -n' from a machine other than the db server >2. ping the other machine from the db server, then >3. 'arp -n' from the other machine > >Compare the outputs of the two invocations of arp. If the outputs show >different MAC addresses for 192.168.41.4 then you have two different >devices with the same IP address. > > I resolve the problem of network conection loose, but still a dude of how it happend and how it can be fixe. When I check with arping the MAC of sever change, for example rommel@p6:~$ arping 192.168.41.4 ARPING 192.168.41.4 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.653ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.683ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.622ms Unicast reply from 192.168.41.4 [6C:92:BF:26:C7:03] 0.631ms ^CSent 3 probes (1 broadcast(s)) Received 4 response(s) The first answer is with a MAC diferent to the others one. But when I arping from the server inseft look the MAC associate to de IP address: [root@pgtm ] arping 192.168.41.4 -I eth1 ARPING 192.168.41.4 from 192.168.41.4 eth1 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.658ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.654ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.654ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.662ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.655ms Sent 5 probes (1 broadcast(s)) Received 5 response(s) Looking in the config of network device I can not find the MAC 00:1D:09:FF:44:4B [root@pgtm ] ifconfig eth0 Link encap:Ethernet HWaddr 6C:92:BF:26:C7:02 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Memory:c7220000-c723ffff eth1 Link encap:Ethernet HWaddr 6C:92:BF:26:C7:03 inet addr:192.168.41.4 Bcast:192.168.41.255 Mask:255.255.255.0 inet6 addr: fe80::6e92:bfff:fe26:c703/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:95819 errors:0 dropped:0 overruns:0 frame:0 TX packets:1924 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11728605 (11.1 MiB) TX bytes:263674 (257.4 KiB) Memory:c7200000-c721ffff eth2 Link encap:Ethernet HWaddr 00:E0:ED:33:4E:9C UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Memory:c7120000-c713ffff eth3 Link encap:Ethernet HWaddr 00:E0:ED:33:4E:9D UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Memory:c7100000-c711ffff lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:249609 errors:0 dropped:0 overruns:0 frame:0 TX packets:249609 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:52090343 (49.6 MiB) TX bytes:52090343 (49.6 MiB) The solution was another IP address to this network device and then everything work fine. Why this happend? How I can erase the link beteewn MAC 00:1D:09:FF:44:4B and IP 192.168.41.4? Where can be stored this link? Right now in the network is not assignet the IP address 192.168.41.4 to no one device (printserver, switch, router, workstation or server) and still whe I make arping have the answer: rommel@p6:~$ arping 192.168.41.4 ARPING 192.168.41.4 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.631ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.623ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.623ms Unicast reply from 192.168.41.4 [00:1D:09:FF:44:4B] 0.691ms ^CSent 4 probes (1 broadcast(s)) Received 4 response(s) arping to the new server IP address look like this (this is the MAC of eth0, where a plug the network cable): rommel@p6:~$ arping 192.168.41.7 ARPING 192.168.41.7 from 192.168.41.6 enp3s0 Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.580ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.607ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.613ms Unicast reply from 192.168.41.7 [6C:92:BF:26:C7:02] 0.594ms ^CSent 4 probes (1 broadcast(s)) Received 4 response(s) Rommel Rodriguez Toirac rommelrt(a)nauta.cu

3 3

question about directory size in linux..
by Jason Welsh 23 Feb '17

23 Feb '17

on a CentOS release 6.8 (Final) I was looking around and noticed the following in a directory. [jason@server /app-vol/applications/]$ls -ld temp drwxr-xr-x 4 jason users 2899968 Feb 18 06:31 temp/ [jason@server /app-vol/applications/]$ How does the directory *itself* have a size of 2.8 megs? yes the contents in that temp directory add up to 2.8 megs, but.. umm. huh? when I run a stat on the temp directory, i get File: `temp' Size: 2899968 Blocks: 5672 IO Block: 4096 directory Device: fd02h/64770d Inode: 1836137 Links: 4 Access: (0755/drwxr-xr-x) Uid: ( 1022/ jason) Gid: ( 501/ users) Access: 2017-02-22 06:31:51.414190071 -0500 Modify: 2017-02-18 06:31:56.135448424 -0500 Change: 2017-02-18 06:31:56.135448424 -0500 on other "normal" directories, I see something like Size: 4096 Blocks: 8 IO Block: 4096 directory Jason

6 12

Re: [CentOS] Network conections problems
by Istimsak Abdulbasir 23 Feb '17

23 Feb '17

On Feb 20, 2017 2:42 PM, "Rommel Rodriguez Toirac" <rommelrt(a)nauta.cu> wrote: Hi; I have a CentOS 6.8 x86_64 server where just run Oracle 11g 64 bit data base server. Is happen that sometimes it loose all connections (no ping, I can not access via ssh, no TNSping of Oracle server have success). When this happend I make ping from this server to some IP address of my network and then everything work fine again. I check logs looking for some mistake or problem in the network device, but I do not find anything or maybe I not looking where must be. I check that from a workstation (Windows XP or Windows 7 or Windows 10) when I make ping to the server, after ~ 8 seconds in get answer and always the first one is loose. If you try again ping, everything work fine (no answers are loose) C:\Users\administrator>ping pgtm.gtm.gob.cu Haciendo ping a pgtm.gtm.gob.cu [192.168.41.4] con 32 bytes de datos: Tiempo de espera agotado para esta solicitud. Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Estadísticas de ping para 192.168.41.4: Paquetes: enviados = 4, recibidos = 3, perdidos = 1 (25% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 0ms, Máximo = 0ms, Media = 0ms This are some of the configs related with networks [root@pgtm ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=Ethernet UUID=11dcddd4-6530-457a-8d3e-01a8339fb113 ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none HWADDR=6C:92:BF:26:C7:02 IPADDR=192.168.41.4 PREFIX=24 GATEWAY=192.168.41.1 DNS1=192.168.41.17 DOMAIN=gtm.gob.cu DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" L I noticed from your ipcfg-eth0 file, the address 192.168.41.1 is assigned to eth0. When you typed the command "ifconfig", that same address was assigned to eth1. Try changing the name of this file to ipcfg-eth1 and restart networkmanager. As was stated earlier, check your gateway and see what other devices could be using that address. Put a block on that unknown MAC address if you can. cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.41.4 pgtm pgtm.gtm.gob.cu [root@pgtm ~]# cat /etc/resolv.conf # Generated by NetworkManager search gtm.gob.cu nameserver 192.168.41.17 [root@pgtm mail]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=pgtm.gtm.gob.cu GATEWAY=192.168.41.1 Someone that happend something like this, or some place for where keep looking to try to fix this loose of conection? Thank and sorry for my horryble English. Rommel Rodriguez Toirac rommelrt(a)nauta.cu _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] how to resize a partition of a disk define as a physical volume
by Istimsak Abdulbasir 22 Feb '17

22 Feb '17

On Feb 22, 2017 7:45 AM, "Bernard Fay" <bernard.fay(a)gmail.com> wrote: Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized K Xvda does not seem to be read as an LVM volume. Xvda2 is handled by lvm so this can be resized. However xvda is just the harddrive itself. From what I have learned using lvm briefly, you can only resize lvm volumes or partitions created using lvm. [root ~]# pvresize /dev/xvda2 Physical volume "/dev/xvda2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Does someone have seen this problem before or could have an idea of the problem? Thanks, Bernard _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

how to resize a partition of a disk define as a physical volume
by Bernard Fay 22 Feb '17

22 Feb '17

Hello, I have a CentOS VM with only one disk on a Xenserver. The disk has 2 partitions: /dev/xvda1 -> /boot /dev/xvda2 -> a physical volume for LVM I added 5GB to this disk via Xencenter to extend /dev/xvda2. Usually I just have to do "pvresize /dev/xvda" to have the additional space added to the disk. But for some reason it does not work for this disk. [root ~]# pvresize /dev/xvda Failed to find physical volume "/dev/xvda". 0 physical volume(s) resized / 0 physical volume(s) not resized [root ~]# pvresize /dev/xvda2 Physical volume "/dev/xvda2" changed 1 physical volume(s) resized / 0 physical volume(s) not resized Does someone have seen this problem before or could have an idea of the problem? Thanks, Bernard

6 8

Centos7 Postfixadmin with SELInux
by Robert Moskowitz 22 Feb '17

22 Feb '17

Anyone here running Postfixadmin on Centos7 with SELinux? The config.inc.php script has lots of warning comments about what you will have to do to get functions to work with SELinux, but does not supply any policy rules. I am still configuring, and so far I have only done: chcon -R -t httpd_sys_content_rw_t /usr/share/postfixadmin/templates_c (thanks Daniel) I suspect here are more so it can do things like create directories and files in the mail store (e.g. /home/vmail/). Oh my current server is running without SELinux (shutter) and that is one of the many reasons I want to upgrade. Bob

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss