Discuss July 2015

discuss@lists.centos.org

116 participants
115 discussions

wicd problem 4: wicd restarts itself when as root user making terminal commands
by g 27 Jul '15

27 Jul '15

greetings, to further check wicd problem, i decided to run test as root user and as user. i verified wicd problems 1, 2, 3 happen when logged in as root user. to further test wicd problems, i tried a few command line problems using virtual terminals. in following, note changing of status for eth0. [root@boxen Documents]# ifconfig eth0 down [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:886 errors:0 dropped:0 overruns:0 frame:0 TX packets:491 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:78924 (77.0 KiB) TX bytes:63994 (62.4 KiB) Interrupt:19 Memory:f0180000-f01a0000 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:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:900 errors:0 dropped:0 overruns:0 frame:0 TX packets:520 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:80504 (78.6 KiB) TX bytes:69267 (67.6 KiB) Interrupt:19 Memory:f0180000-f01a0000 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:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) [root@boxen Documents]# ifconfig eth0 down;ifconfig;date 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:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) Sun Jul 26 21:30:00 CDT 2015 [root@boxen Documents]# ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:993 errors:0 dropped:0 overruns:0 frame:0 TX packets:575 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:87572 (85.5 KiB) TX bytes:76022 (74.2 KiB) Interrupt:19 Memory:f0180000-f01a0000 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:296 errors:0 dropped:0 overruns:0 frame:0 TX packets:296 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22964 (22.4 KiB) TX bytes:22964 (22.4 KiB) virbr0 Link encap:Ethernet HWaddr 52:54:00:B3:A7:95 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3417 (3.3 KiB) Sun Jul 26 21:30:20 CDT 2015 i used date command to show time interval of eth0 state changing. a 5th problem i see with 'wicd' is in post "Subject: wicd problem"; 5: wicd restarts itself when as user making terminal commands -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 3: wicd blocking 1st attempt connection for firefox and yumex
by g 27 Jul '15

27 Jul '15

greetings, wicd is preventing firefox and yumex to connect to internet. when i first try to connect to a web site with firefox, i get err message; Unable to connect when i click [Try Again], connection is made. all further connection attempts are ok. when i try to run yumex, i get error message; Not connected to a network. Do you want to continue selecting [Yes] continues starting yumex, but i have active repositories. when i run yum cl command; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6& arch=x86_64&repo=os error was 14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrorlist.centos.org'" Error: Cannot find a valid baseurl for repo: base when i run yum cl command again; ]$ yum check-update Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, : refresh-packagekit, security, tmprepo, verify, versionlock Loading mirror speeds from cached hostfile epel/metalink | 13 kB 00:00 which indicates yum has made connection. a 4th problem i see with 'wicd' is in post "Subject: wicd problem"; 4: wicd restarts itself when as root user making terminal commands -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 2: wicd does not sync when ifconfig commands are given from a terminal
by g 27 Jul '15

27 Jul '15

greetings, during past week or so, i have been having problems with mozilla firefox locking up kde desktop and i have to open a terminal to reboot system. to insure that i get kde back to a desired state, i make backups of ~/.kde path when ever i change any settings of kde. after system reboots and desktop manager is displayed, i <ctrl+alt+f1> to terminal, delete current ~/.kde, then copy ~/.kde-backup to ~/.kde. while in terminal, i run 'ifconfig' to see if network is connected, which it is, so i 'sudo ifconfig eth0 down' to disconnect. after starting kde, wicd icon in system tray is showing wicd has connection to network, which it does not. when i click wicd icon and then select 'disconnect', and close wicd window, then reopen wicd and select 'connect', there is no connection. a 3rd problem i see with 'wicd' is in post "Subject: wicd problem"; 3: wicd blocking 1st attempt connection for firefox and yumex -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

wicd problem 1: wicd allows network to be connected on reboot
by g 27 Jul '15

27 Jul '15

greetings, i find this strange because i see problems when using 'wicd'. 1st problem is that wicd allows network to be connected on reboot, even when network is disconnected at time of reboot. such does not seem to be good because i leave system up 24/7/365 and if there is a mains failure and ups takes system down, system will come back up with network connected, which i prefer not to have happen. is there a way to set up 'wicd' so that it does not start connected? a 2nd problem i see with 'wicd' is in post "Subject: wicd problem"; 2: wicd does not sync when ifconfig commands are given from a terminal -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g .

1 0

Re: [CentOS] rsyslog.conf
by James B. Byrne 25 Jul '15

25 Jul '15

On Thu, July 23, 2015 13:19, m.roth(a)5-cent.us wrote: > Physically dragging the thread back on topic... > > I really am going crazy, trying to deal with the hourly logs from the > loghost. We've got 170+ servers and workstations... but a *very* large > percentage of what's showing up is from his bloody new fedora 22, with > its idiot systemd logging of *ever* selinux message to > /var/log/messages. > > I tried creating a rule, /etc/rsyslog.d/audit.conf, that reads: > > if $msg contains "audit" and $msg,contains,'res=success' then - > > but that seemed to send *everything* to /dev/null. That was my best > guess, > based on googling (yahooing?) and man pages. Can anyone tell me what's > wrong with that syntax? > > mark > > > And Lennart blames Linus[1] for why he gets hate mail. We are giving RHEL-7 a pass on this iteration. We have installed it on a couple of test hosts and are not favourably impressed with much of the user interface. At least not from the sys-admin side of things. This is not to imply that there is nothing good in 7. There are at lot of improvements that we certainly value. But it is too early in systemd development for us to waste time debugging somebody else's pipe-dream on our dime. We will see what 8 offers and decide then whether to move to something else. [1]. https://plus.google.com/app/basic/stream/z13rdjryqyn1xlt3522sxpugoz3gujbhh04 -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail 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

5 6

Timeout before trust answer with iPhone iOS 8
by David McGuffey 25 Jul '15

25 Jul '15

Until recently I've not had any problem connecting my iPhone 4s with iOS 8 to my CentOS 6.6 desktop to move pictures and videos. Problem occurs with my wife's new iPhone 5s. Now, before I can answer the "Trust This Computer" message on the iPhone, I get a DBus error: "org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)" Searching this message reveals a lot of complaints by users on Ubuntu and a bug in a library. But this was back in 2012-2013. Couldn't find anything related to CentOS. Appears to be a timing issue...the timer expires before I can respond to the trust question on the iPhone. Any guidance on how to fix this? Is there a timeout setting somewhere down in udev, fuse, or gvfs? DaveM

1 0

CentOS-announce Digest, Vol 125, Issue 9
by centos-announce-request＠centos.org 25 Jul '15

25 Jul '15

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. CESA-2015:1483 Important CentOS 7 libuser Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 24 Jul 2015 11:44:59 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2015:1483 Important CentOS 7 libuser Security Update Message-ID: <20150724114459.GA26567(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2015:1483 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1483.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ba0dc0818d6776e31b3e52da05203be646938aad0d2594d2db117d65e1a4b716 libuser-0.60-7.el7_1.i686.rpm 226b33436c0c31da87f885761904d09f94d1c578ed5fc2897decd7af64ff940a libuser-0.60-7.el7_1.x86_64.rpm 8401bb23e3725fdfb8cc0c470b641c70097b549ed284d69cfb9eeb0e81ec421f libuser-devel-0.60-7.el7_1.i686.rpm 96523516a410d8ead6ff334e304a751033ac81756d6958bbe748b993383eb8f0 libuser-devel-0.60-7.el7_1.x86_64.rpm 01f0b382502df82273888d2e8caf5933ca9ff2160e6f5d2b69708b3b858d712a libuser-python-0.60-7.el7_1.x86_64.rpm Source: d4fa813133e5cf1c0a0447a1c6ae41eb5734bef5e4cab8af3ec2d1e69d9661b0 libuser-0.60-7.el7_1.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 125, Issue 9 ***********************************************

1 0

Re: [CentOS] rsyslog.conf
by James B. Byrne 25 Jul '15

25 Jul '15

On Thu, July 23, 2015 10:34, Valeri Galtsev wrote: > Well, my habit for regular e-mail exchange is "top posting" thus the > person reads my message thus is right to the point why this particular > message message was sent in a first place... But when mail lists are > concerned, I do an opposite, that is I follow mail lists conventions. > I never thought about rationale behind them, I'm just following them. > I believe, if some day someone gives reasons why top posting is bad > in case of mail lists it will really be great. The only reason I can > come up with myself would be: whoever reads message received through > mail lists usually has no idea about previous exchange in this > thread, thus needs all exchange in chronological order. Which I'm > not certain is a good reason, so those who know and insists > strongly about "no top posting" are encouraged to give others the > reasons behind that. Again, I'm not "top posting" on the lists. > However, _this_ ("top posting") is my regular way in private > exchange (and it has good reasons behind it). > It originates from early Usenet practice where it had some useful purpose given the way Usenet feeds were typically consumed and forwarded. Generally Usenet News servers maintained posts for a limited period of time. If you did not connect to obtain the news-feed within that window then all earlier posts were 'lost' to you. Thus encapsulating the entire discussion in chronological order in each reply compensated for the technological (storage) limits prevalent in the 1980/90s. The orthodox justification for bottom-posting is often exemplified by tag lines similar in content to the following: > Because it makes following the discussion hard. >> Why is top-posting wrong? >>> You are top-posting. >>>> What is wrong with my message? However, forcing your correspondents to wade through an interminable wall of text that regurgitates the previous thread before getting to the point of the message arguably interferes with proper understanding no less than top-posting does. I am unaware of any scientific study that purports to support either position. So, in the absence of that I conclude: De gustibus non est disputandum. At this point the practice, particularly for archived mailing lists, is little more than dogmatic adherence to a style that serves only to distinguish the 'in group' from the 'other'. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail 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

4 3

Unbound nodes using numactl
by Mahmoud A. A. Ibrahim 24 Jul '15

24 Jul '15

Dear Centos Users We were wondering how can we change the default policy of numactl. In other words, our cluster has 10 servers, each server has two nodes, and each node has 16 cores. Recently, we observed a poor performance of our cluster when a couple of jobs run on the same server. By investigating the problem, we found that each job moves randomly among the 32 cores of the server. This returns to the fact that the 32 cores of each server bound together as seen below. How can we make our server back to two numa nodes? Any kind of support will be highly appreciated. B.T.W. We use Rocks6.1 Thanks in advance Sincerely; M. Ibrahim ################ #numactl -show policy: default preferred node: current physcpubind: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 cpubind: 0 1 nodebind: 0 1 membind: 0 1 ################ # numactl --hardware available: 2 nodes (0-1) node 0 cpus: 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 node 0 size: 16287 MB node 0 free: 15619 MB node 1 cpus: 1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 node 1 size: 16384 MB node 1 free: 15839 MB node distances: node 0 1 0: 10 21 1: 21 10 ################

1 0

Automated Reply from Gary Rixon <centos-announce@centos.org>
by Gary Rixon 24 Jul '15

24 Jul '15

I will not have access to email on between Fri 24th July 2015 and Fri 31st July 2015 inclusive. Please send any support requests or enquiries to support(a)dogsbodytechnology.com where it will be picked up by one of my colleagues. If you need urgent support please email or call Dan Benton on dan(a)dogsbodytechnology.com or 07718 679512 Thank you Gary Rixon

1 0

← Newer
1
2
3
4
5
6
7
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss July 2015