[CentOS] Cange from Samba 3.0 to samba 3 3.6.6
Hi Folks, I'd like to change from Smaba 3.0.33 to 3.6.6. Reason: WINDOWS 7 and PDC Is something to consider when changing (config-Files or so on)? Have I to uninstall Samba 3.0.33 before or just run an update? Thx for hints. Timothy ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] FYI: CentOS legalese
Putting the Genie Back in the Bottle: More RedHat Legal Shenanigans with CentOS http://nerdvittles.com/?p=8721 Closing the Book on CentOS: [...] http://nerdvittles.com/ Thanks to the author of the above articles. jb ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FYI: CentOS legalese
On Mon, 2014-02-24 at 12:28 +, jb wrote: > Putting the Genie Back in the Bottle: > More RedHat Legal Shenanigans with CentOS > http://nerdvittles.com/?p=8721 > > Closing the Book on CentOS: [...] > http://nerdvittles.com/ > > Thanks to the author of the above articles. The author of those pieces needs to read a bit closer. His claim: In a nutshell, the new RedHat Terms of Service outlaw use of CentOS in any product “unless the combined distribution is an official CentOS distribution.” is not supported by any evidence he provides. What is made clear is that one cannot use the CentOS marks (ie logos, etc.) in a derivative distribution. Seems to be much sound and fury... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] system hangs
Every so often, one of our servers will go into what I can only describe as an undefined state: it pings, but there's zero access - you can't ssh in, and if I go plug a keyboard and monitor into the server itself, you can see the monitor's live, it's not the "monitor turned off" color, but there is zero response to the keyboard. The upshot is that I wind up having to power cycle it. Well, it just happened again on one of our servers Friday evening, as I found this morning. Looking at the logs this morning, I see that sar last shows 10:20:01 PM all 34.38 0.00 8.29 0.00 0.00 57.33 On of my users dropped me an email at 22:45 that it was "off", and the last things I see in /var/log/messages are one of those annoying Feb 21 22:26:23 kernel: INFO: task perl:20596 blocked for more than 120 seconds. Feb 21 22:26:23 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. I also see Feb 21 22:26:23 kernel: perl D 80158250 0 20596 20557 which, as I just found by googling perl NOTLD, means that this is in a kernel uninterruptable state In addition, in the stack trace, some nfs messages Feb 21 22:26:23 kernel: [] :nfs:nfs_wait_bit_uninterruptible+0x0/0xd So, it *appears* to be either an NFS issue, or a NIC issue. The user's home directory server is CentOS running 6.5, and the server that hung is 5.10. Mount on the formerly hung server, su-d to his account shows merely nfs, so I'm guessing it's NFS3. Looking at lsmod and /var/log/dmesg, I see it's running the tg3 NIC driver. Anyone else seeing this, and if so, any thoughts on the matter? Note that I've had this on Penguins, which are all Supermicro, and they're using the igb NIC driver, but the one this past weekend is a Dell, so it's not just one system. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FYI: CentOS legalese
On 2014-02-24, Brian Miller wrote: > On Mon, 2014-02-24 at 12:28 +, jb wrote: >> http://nerdvittles.com/?p=8721 > > The author of those pieces needs to read a bit closer. His claim: > > In a nutshell, the new RedHat Terms of Service outlaw use of > CentOS in any product ???unless the combined distribution is an > official CentOS distribution.??? > > is not supported by any evidence he provides. What is made clear is > that one cannot use the CentOS marks (ie logos, etc.) in a derivative > distribution. The actual text from what the original blog author cites (https://www.centos.org/legal/trademarks/): "Use of the CentOS Marks to identify software that combines any portion of the CentOS software with any other software , unless the combined distribution is an official CentOS distribution. For example, you may not distribute a combination of the CentOS software with software released by the FooStack project under the name ''CentOS FooStack Distro''." So the guidelines prohibit the use of CentOS *Marks*, not CentOS in his hypothetical scenario. --keith -- kkel...@wombat.san-francisco.ca.us ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system hangs
On Mon, 24 Feb 2014, m.r...@5-cent.us wrote: > Every so often, one of our servers will go into what I can only describe > as an undefined state: it pings, but there's zero access - you can't ssh > in, and if I go plug a keyboard and monitor into the server itself, you > can see the monitor's live, it's not the "monitor turned off" color, but > there is zero response to the keyboard. The upshot is that I wind up > having to power cycle it. > > Well, it just happened again on one of our servers Friday evening, as I > found this morning. Looking at the logs this morning, I see that sar last > shows > 10:20:01 PM all 34.38 0.00 8.29 0.00 0.00 > 57.33 > > On of my users dropped me an email at 22:45 that it was "off", and the > last things I see in /var/log/messages are one of those annoying > Feb 21 22:26:23 kernel: INFO: task perl:20596 blocked for more > than 120 seconds. > Feb 21 22:26:23 kernel: "echo 0 > > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > I also see > Feb 21 22:26:23 kernel: perl D 80158250 0 > 20596 20557 > which, as I just found by googling perl NOTLD, means that this is in a > kernel uninterruptable state > In addition, in the stack trace, some nfs messages > Feb 21 22:26:23 kernel: [] > :nfs:nfs_wait_bit_uninterruptible+0x0/0xd > > So, it *appears* to be either an NFS issue, or a NIC issue. The user's > home directory server is CentOS running 6.5, and the server that hung is > 5.10. Mount on the formerly hung server, su-d to his account shows merely > nfs, so I'm guessing it's NFS3. Looking at lsmod and /var/log/dmesg, I see > it's running the tg3 NIC driver. > > Anyone else seeing this, and if so, any thoughts on the matter? Note that > I've had this on Penguins, which are all Supermicro, and they're using the > igb NIC driver, but the one this past weekend is a Dell, so it's not just > one system. > > >mark > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > What CPU's do these systems have? AMD or Intel. What kernel are the server and client running? -Connie Sieh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FYI: CentOS legalese
On Mon, 2014-02-24 at 08:34 -0500, Brian Miller wrote: > On Mon, 2014-02-24 at 12:28 +, jb wrote: > > Putting the Genie Back in the Bottle: > > More RedHat Legal Shenanigans with CentOS > > http://nerdvittles.com/?p=8721 > > > > Closing the Book on CentOS: [...] > > http://nerdvittles.com/ > > > > Thanks to the author of the above articles. > The author of those pieces needs to read a bit closer. His claim: > > In a nutshell, the new RedHat Terms of Service outlaw use of > CentOS in any product “unless the combined distribution is an > official CentOS distribution.” > > is not supported by any evidence he provides. What is made clear is > that one cannot use the CentOS marks (ie logos, etc.) in a derivative > distribution. > > Seems to be much sound and fury... Do you mean Red Hat's ownership of the Centos brand name prohibits something like this example http://nerdvittles.com/wp-images/piaf20642.gif ? (source: http://nerdvittles.com/?p=5844) Why does Red Hat need to 'own' the Centos brand name and do the Centos maintainers, who work hard on Centos for all our benefit, possess the legal ownership - individually or collectively - of the Centos brand that was, or is, being transferred or sold or donated by them to Red Hat Inc. ? If the Centos maintainers do not own the Centos brand name, which entity does and which entity has the legal ability to give away to a third party complete ownership of the brand name ? Thank you. -- Paul. England, EU. Our systems are exclusively Centos. No Micro$oft Windoze here. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Changing from samba 3.0.33 to Samba 3,6,6
Hi Folks, I'd like to change from Samba 3.0.33 to 3.6.6. Reason: WINDOWS 7 and PDC Is something to consider when changing (config-Files or so on)? Have I to uninstall Samba 3.0.33 before or just run an update? Thx for hints. Timothy ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Changing from samba 3.0.33 to Samba 3,6,6
On 2/24/2014 9:03 AM, Timothy Kesten wrote: > Hi Folks, I'd like to change from Samba 3.0.33 to 3.6.6. > Reason: WINDOWS 7 and PDC > > Is something to consider when changing (config-Files or so on)? > Have I to uninstall Samba 3.0.33 before or just run an update? what OS and version are you running? CentOS 6 with current updates should be running Samba 3.6.9 -- 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] FYI: CentOS legalese
On Mon, Feb 24, 2014 at 10:44 AM, Keith Keller < kkel...@wombat.san-francisco.ca.us> wrote: > On 2014-02-24, Brian Miller wrote: > > On Mon, 2014-02-24 at 12:28 +, jb wrote: > >> http://nerdvittles.com/?p=8721 > > > > The author of those pieces needs to read a bit closer. His claim: > > > > In a nutshell, the new RedHat Terms of Service outlaw use of > > CentOS in any product ???unless the combined distribution is an > > official CentOS distribution.??? > > > > is not supported by any evidence he provides. What is made clear is > > that one cannot use the CentOS marks (ie logos, etc.) in a derivative > > distribution. > > The actual text from what the original blog author cites > (https://www.centos.org/legal/trademarks/): > > "Use of the CentOS Marks to identify software that combines any portion > of the CentOS software with any other software , unless the combined > distribution is an official CentOS distribution. For example, you may > not distribute a combination of the CentOS software with software > released by the FooStack project under the name ''CentOS FooStack > Distro''." > > So the guidelines prohibit the use of CentOS *Marks*, not CentOS in his > hypothetical scenario. > Derivative projects are probably in the same boat CentOS is ... removing the trademarked items. ie: CentOS removes Red Hat trademarks (name, logo, whatever else) That would be my expectation if anything at all were necessary. Hopefully that author will consult the proper people and get a clear answer. Some people like to rant to rant ... it's rather sad because more time is wasted than actually doing something. > > --keith > > -- > kkel...@wombat.san-francisco.ca.us > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- ---~~.~~--- Mike // SilverTip257 // ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] system hangs
Connie Sieh wrote: > On Mon, 24 Feb 2014, m.r...@5-cent.us wrote: > >> Every so often, one of our servers will go into what I can only describe >> as an undefined state: it pings, but there's zero access - you can't ssh >> in, and if I go plug a keyboard and monitor into the server itself, you >> can see the monitor's live, it's not the "monitor turned off" color, but >> there is zero response to the keyboard. The upshot is that I wind up >> having to power cycle it. >> >> Well, it just happened again on one of our servers Friday evening, as I >> found this morning. Looking at the logs this morning, I see that sar >> last shows >> 10:20:01 PM all 34.38 0.00 8.29 0.00 0.00 >> 57.33 >> >> On of my users dropped me an email at 22:45 that it was "off", and the >> last things I see in /var/log/messages are one of those annoying >> Feb 21 22:26:23 kernel: INFO: task perl:20596 blocked for more >> than 120 seconds. >> Feb 21 22:26:23 kernel: "echo 0 > >> /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> >> I also see >> Feb 21 22:26:23 kernel: perl D 80158250 0 >> 20596 20557 >> which, as I just found by googling perl NOTLD, means that this is in a >> kernel uninterruptable state >> In addition, in the stack trace, some nfs messages >> Feb 21 22:26:23 kernel: [] >> :nfs:nfs_wait_bit_uninterruptible+0x0/0xd >> >> So, it *appears* to be either an NFS issue, or a NIC issue. The user's >> home directory server is CentOS running 6.5, and the server that hung is >> 5.10. Mount on the formerly hung server, su-d to his account shows >> merely nfs, so I'm guessing it's NFS3. Looking at lsmod and /var/log/dmesg, I >> see it's running the tg3 NIC driver. >> >> Anyone else seeing this, and if so, any thoughts on the matter? Note >> that I've had this on Penguins, which are all Supermicro, and they're using >> the igb NIC driver, but the one this past weekend is a Dell, so it's not >> just one system. >> > What CPU's do these systems have? AMD or Intel. > > What kernel are the server and client running? In the case from this weekend, the NFS home directory server is running an AMD Opteron - that's the Dell with th Broadcom NIC; the one that's running 5.10 and hung is running Intel Xeon, and the tg3 NIC driver, and the other server - don't remember which of them it was, several have done this, so I'm just picking one Penguin - is a different model AMD Opteron, and the Intel with igb as the driver. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Need help resolving yum update issues on mixed architecture system
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
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
[CentOS] KVM and Win7-64 Sound
Dear Gurus I have been unable to make sound (and microphone) work in Windows 7 (64-bit) as a VM with KVM. Google searches reveal this to be a common problem, with various solutions recommended, primarily Ubuntu oriented, none of which have worked for me. So I wonder if anyone has a working Windows sound condition with: Centos 6.5 with KVM, all on a 64-bit Intel platform. Sound works on the host machine, verified when I switch into GUI mode and run a sound-producing program Sound does not work in the Windows 7 (64-bit) PRO installation as a Virtual Machine, and I have tried specifying the emulated hardware as AC97, and ICH6. Any working examples? David ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Monitor Wireless Networks OT
On Thu, Feb 20, 2014 at 3:50 PM, Frank Cox wrote:
> On Thu, 20 Feb 2014 15:42:35 -0600
> Joseph Hesse wrote:
>
>> Apparently my hardware is not sufficient. When I run "iwlist scan" I get:
>>
>> lo p5p1; Interface doesn't support scanning
>
> I'm pretty sure you have to run it as root user.
You also have to run it on your wireless nic. p5p1 sounds like a
gig-ethernet wired nic. wlp should be your wireless
You might also have to ifup wlan0 or ifconfig wlan0 up to get it to
scan. Sometimes if its down, it won't scan.
I thought I might share my scripts anyway. First the awk, then the cronjob.
# cat bin/iwlistparse.awk
$1 == "BSS" {
MAC = $2
wifi[MAC]["enc"] = "Open"
wifi[MAC]["mac"] = $MAC
}
$1 == "SSID:" {
wifi[MAC]["SSID"] = $2
}
$1 == "freq:" {
wifi[MAC]["freq"] = $NF
}
$1 == "signal:" {
wifi[MAC]["sig"] = $2 " " $3
}
$1 == "WPA:" {
wifi[MAC]["enc"] = "WPA"
}
$1 == "WEP:" {
wifi[MAC]["enc"] = "WEP"
}
END {
#printf "%s\t\t%s\t%s\t\t%s\n","SSID","Frequency","Signal","Encryption"
for (w in wifi) {
printf
"%s\t\t%s\t\t%s\t%s\n",wifi[w]["SSID"],wifi[w]["mac"],wifi[w]["freq"],wifi[w]["sig"],wifi[w]["enc"]
}
}
# cat bin/wlanpatrol
#!/bin/bash
tstamp="$(date +\%Y\%m\%d\%H\%M\%S)"
#Wirelss is flakey. Retry a 'few' times to get the right number of
authorized APs, or any APs at all. sometimes scans just fail
iter=0
while [[ "${iter}" -le 60 ]]
do
iter=$(( ${iter} + 1 ))
/sbin/iwlist wlp12s0 scanning 2>&1 | grep -v 'wlp12s0\ \ \
Interface\ doesn'\''t\ support\ scanning\ :\ Device\ or\ resource\
busy' > /root/iwlistlogs/${tstamp}
#Replace 00.11.22.33.44.55's with the mac addresses of your authorised APs
OurAPCount="$( awk -f /root/bin/iwlist.awk <
/root/iwlistlogs/${tstamp} | grep -i -e '00.11.22.33.44.55' -e
'00.11.22.33.44.55' -e '00.11.22.33.44.55' -e '00.11.22.33.44.55' -e
'00.11.22.33.44.55' -e '00.11.22.33.44.55' | wc -l)"
if [[ ! -s "/root/iwlistlogs/${tstamp}" ]]
then
continue
fi
#In our environment, I expect 6 legitimate APs be visible at all times.
if [[ ${OurAPCount} -eq 6 ]]
then
break
fi
#echo OurAPCountError: ${OurAPCount} found.
sleep 0.1
done
APCount="$( awk -f /root/bin/iwlist.awk /root/iwlistlogs/${tstamp} | wc -l)"
#Here we check for bits and pieces of our actual company name in the
names of all detected APs. Then we ignore the authorized mac
addresses, to come upwith a list of APs pretending to be us.
RogueAPs="$( awk -f /root/bin/iwlist.awk < /root/iwlistlogs/${tstamp} | \
grep -i -e my -e company -e mc -e myc -e yco -e com -e omp -e mpa -e
pan -e any | \
grep -i -v -e '00.11.22.33.44.55' -e '00.11.22.33.44.55' -e
'00.11.22.33.44.55' -e '00.11.22.33.44.55' -e '00.11.22.33.44.55' -e
'00.11.22.33.44.55' )"
if [[ $OurAPCount != 6 ]]
then
awk -f /root/bin/iwlist.awk < /root/iwlistlogs/${tstamp} |
mail -s "Abnormal number of Our authorized APs: ${OurAPCount}"
bcr...@mycompany.com
fi
if [[ ! -z "${RogueAPs}" ]]
then
mail -s "ROGUE APS IN USE" bcr...@ourapcount.com <<< "${RogueAPs}"
fi
___
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
On Feb 24, 2014, at 18:59, John R Pierce 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
> 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] system hangs
It seems system was in hung state . The message > Feb 21 22:26:23 kernel: INFO: task perl:20596 blocked for more than 120 seconds. Just indicates that process 20596 was stuck/hang in cpu for more than 120 seconds. To begin with the troubleshooting, I would suggest you to check what this process does. Whether this required any REMOTE storage/disk access. Btw, the same perl process is going to D state/hang state first/always ? If no remote storage/disk access is required for this perl application AND In case you are running this application as root user, try run this application as a normal user in which a resource limitation is applicable via limits.conf. If the process required a storage/NFS access, you may want to check the disk/storage status at the time when application moved to D state. I understand that you can't predict the issue time and perform all the checks mentioned above. afaik, to find the root cause of this problem, you may want to analyse core dump collected at the time of the issue. Cheers, Dominic ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KVM and Win7-64 Sound
On Tue, Feb 25, 2014 at 6:40 AM, david wrote: > > Sound does not work in the Windows 7 (64-bit) PRO installation as a > Virtual Machine, and I have tried specifying the emulated hardware as > AC97, and ICH6. The few times I have tried desktop VM with LKVM, the user experience within the VM, has been spotty. Whereas with VB it has been acceptable (same no. of CPUs, RAM etc in LKVM v/s VB). For desktop VM, I would suggest Virtual Box. -- Arun Khan ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
