From eng-partner-management at redhat.com Wed Jun 4 16:45:04 2014 From: eng-partner-management at redhat.com (Engineering Partner Management) Date: Wed, 04 Jun 2014 12:45:04 -0400 Subject: [rhelv6-list] Red Hat Software Collections 1.1 Now Available Message-ID: <538F4D10.1080701@redhat.com> Red Hat is pleased to announce the general availability of Red Hat Software Collections 1.1. Red Hat Software Collections 1.1 delivers a comprehensive suite of powerful web development tools, dynamic languages, and open source databases to help developers and systems administrators accelerate the creation of stable, modern web applications. Red Hat Software Collections 1.1 offers several new options, including: * Two new open source HTTP server options. Apache HTTP Server 2.4 and Nginx 1.4.4 (available as a Technology Preview) * PHP 5.5, a server-side scripting language designed for web development * Ruby 2.0 and Rails 4.0, which for the first time will be packaged separately, providing developers with access to an updated version of Ruby without requiring the installation of Rails * MongoDB 2.4, a high-performance open source document database and leading NoSQL database that provides high availability and easy scalability * Thermostat 1.0, a tool for monitoring Java virtual machine (JVM) instances on multiple hosts * Enhancements to the software collections utilities that simplify the extension of software collections through the use of dependent collections Delivered on a separate life cycle from Red Hat Enterprise Linux with a more frequent release cadence, Red Hat Software Collections expedites the delivery of dynamic languages and open source databases, a significant benefit to organizations seeking to accelerate software development and deployment through agile methods. Additionally, subscribers deploying applications built using Red Hat Software Collections into production can do so with confidence, as individual releases of Red Hat Software Collections are supported for three years. RED HAT SOFTWARE COLLECTIONS 1.1 AVAILABILITY Red Hat Software Collections 1.1 is available now for use with Red Hat Enterprise Linux 6 to customers and partners with select active Red Hat Enterprise Linux subscriptions. For more information on how to install Red Hat Software Collections view the Red Hat Software Collections 1.1 release notes available at the following location: https://access.redhat.com/site/documentation/en-US/Red_Hat_Software_Collections/1/html/1.1_Release_Notes/index.html Customers with active Red Hat Enterprise Linux 6 subscriptions who do not see Red Hat Software Collections channels on Red Hat Network (RHN) can visit: http://www.redhat.com/GetRedHatSoftwareCollections.html ADDITIONAL RESOURCES To access documentation for Red Hat Software Collections, visit: - Latest Red Hat Software Collections release notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Software_Collections/1/html/1.1_Release_Notes/index.html - Red Hat Enterprise Linux Developer Guide: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Developer_Guide/index.html - Red Hat Enterprise Linux documentation: https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/ Sincerely, The Red Hat Enterprise Linux Team From vu at sivell.com Mon Jun 9 13:11:29 2014 From: vu at sivell.com (Vu Pham) Date: Mon, 09 Jun 2014 08:11:29 -0500 Subject: [rhelv6-list] cannot su to any users, cannot login via console. Message-ID: <5395B281.1070304@sivell.com> System: RHEL 6.5 Although I can log in to non-root users via ssh, I cannot su to any users, root or non-root. When using su, after typing in the user name, the su command just hangs there without the password prompt. When trying to login from the console, the password prompt never shows, and after a few minutes, the screen is cleared and the login prompt shows again. I cannot log in to root via ssh, because it is disabled by the sshd config file. top shows dbus-daemon get %100 CPU. Any help is greatly appreciated. Thanks, Vu -- Vu Pham -------- Sivell Corp 13101 Northwest Freeway, #325 Houston, TX 77040 Tel: 713-821-9800 x 2203 Fax: 713-821-9899 From gianluca.cecchi at gmail.com Mon Jun 9 14:07:06 2014 From: gianluca.cecchi at gmail.com (Gianluca Cecchi) Date: Mon, 9 Jun 2014 16:07:06 +0200 Subject: [rhelv6-list] cannot su to any users, cannot login via console. In-Reply-To: <5395B281.1070304@sivell.com> References: <5395B281.1070304@sivell.com> Message-ID: On Mon, Jun 9, 2014 at 3:11 PM, Vu Pham wrote: > System: RHEL 6.5 > > Although I can log in to non-root users via ssh, I cannot su to any users, > root or non-root. When using su, after typing in the user name, the su > command just hangs there without the password prompt. > > When trying to login from the console, the password prompt never shows, > and after a few minutes, the screen is cleared and the login prompt shows > again. > I cannot log in to root via ssh, because it is disabled by the sshd config > file. > > > top shows dbus-daemon get %100 CPU. > > Any help is greatly appreciated. > > Thanks, > Vu > > Do you have ldap configured on your system perhaps? In that case you could have a problem with it causing the problem... because messagebus runs as dbus local user In that case, if not already there, you could put inside /etc/nslcd.conf a line to ignore group membership lookups for dbus nss_initgroups_ignoreusers root,ldap,named,.....,dbus the "...." above is to be substituted with a comma seprated list of other local users you want not to make lookup for. if you can make that change you can start in single user mode and change from there. Also, during boot you could have problems with messagebus service to start and proceed the boot because of this. There are other parameters to tune config files in case of problems with ldap.... if this is the problem HIH, Gianluca -------------- next part -------------- An HTML attachment was scrubbed... URL: From vu at sivell.com Mon Jun 9 14:28:18 2014 From: vu at sivell.com (Vu Pham) Date: Mon, 09 Jun 2014 09:28:18 -0500 Subject: [rhelv6-list] cannot su to any users, cannot login via console. In-Reply-To: References: <5395B281.1070304@sivell.com> Message-ID: <5395C482.7070108@sivell.com> On 06/09/2014 09:07 AM, Gianluca Cecchi wrote: > On Mon, Jun 9, 2014 at 3:11 PM, Vu Pham > wrote: > > System: RHEL 6.5 > > Although I can log in to non-root users via ssh, I cannot su to > any users, root or non-root. When using su, after typing in the > user name, the su command just hangs there without the password > prompt. > > When trying to login from the console, the password prompt never > shows, and after a few minutes, the screen is cleared and the > login prompt shows again. > I cannot log in to root via ssh, because it is disabled by the > sshd config file. > > > top shows dbus-daemon get %100 CPU. > > Any help is greatly appreciated. > > Thanks, > Vu > > > Do you have ldap configured on your system perhaps? > In that case you could have a problem with it causing the problem... > because messagebus runs as dbus local user > > In that case, if not already there, you could put inside > /etc/nslcd.conf a line to ignore group membership lookups for dbus > > nss_initgroups_ignoreusers root,ldap,named,.....,dbus > > the "...." above is to be substituted with a comma seprated list of > other local users you want not to make lookup for. > > if you can make that change you can start in single user mode and > change from there. > Also, during boot you could have problems with messagebus service to > start and proceed the boot because of this. > There are other parameters to tune config files in case of problems > with ldap.... if this is the problem > > HIH, > Gianluca > Gianluca, Thank you for your reply. No, I do not use ldap on this server. This server just uses the default login with the default settings of pam.d. Vu -------------- next part -------------- An HTML attachment was scrubbed... URL: From eng-partner-management at redhat.com Tue Jun 10 14:12:40 2014 From: eng-partner-management at redhat.com (Engineering Partner Management) Date: Tue, 10 Jun 2014 10:12:40 -0400 Subject: [rhelv6-list] Red Hat Unveils Red Hat Enterprise Linux 7, Redefining the Enterprise OS Message-ID: <53971258.70800@redhat.com> Today marks an exciting milestone for Red Hat as we share news of the general availability of Red Hat Enterprise Linux 7, the latest major release of the flagship platform. Red Hat Enterprise Linux 7 not only lays the foundation for the open hybrid cloud and serves enterprise workloads across converged infrastructures; it pushes the operating system beyond today?s position as a commodity platform. Built to meet modern datacenter demands along with next-generation IT requirements, Red Hat Enterprise Linux 7 powers the spectrum of enterprise IT, from application containers to cloud services. With today?s announcement, we invite Red Hat customers, partners, and members of the public to join the Red Hat hosted virtual event, Redefining the Enterprise OS, at 11 a.m. EDT today at http://bit.ly/RHELjune10 to learn more about Red Hat Enterprise Linux 7. Red Hat Enterprise Linux 7 offers customers agility and flexibility to meet new requirements head-on without increasing complexity, from rapidly delivering new applications via secure, lightweight containers to scaling infrastructure to meet big data requirements with new and enhanced file systems. Key Red Hat Enterprise Linux 7 features to address future IT needs include: * Enhanced application development, delivery, portability and isolation through Linux Containers, including Docker, across physical, virtual, and cloud deployments as well as development, test and production environments. * Significant file system improvements, including XFS as the default file system, scaling to 500 TB. * Cross-realm trust to easily enable secure access for Microsoft Active Directory users across Microsoft Windows and Red Hat Enterprise Linux domains, providing the flexibility for Red Hat Enterprise Linux to co-exist within heterogeneous datacenters. * Powerful and secure application runtimes and development, delivery and troubleshooting tools, integrated into the platform and container-ready. While serving as a catalyst for enterprise innovation, Red Hat Enterprise Linux 7 also delivers the military-grade security, mission-critical reliability, as well as the performance, and ease-of-use capabilities to efficiently ?keep the lights on,? including: * Innovative infrastructure components like systemd, a new standard for modernizing the management of processes, services, security and other resources. * Built-in performance profiles, tuning and instrumentation for optimized performance and easy scalability. * Unified management tooling and an industry-standard management framework with OpenLMI for streamlined administration and system configuration. * Enhanced application isolation and security applied via containerization to protect against both unintentional interference and malicious attacks. Since its introduction more than a decade ago, Red Hat Enterprise Linux has become the world?s leading enterprise Linux platform, and it has set industry standards for performance and security while continuously innovating and evolving. Today, Red Hat Enterprise Linux is a leading force in the enterprise datacenter and in the cloud. More than 90 percent of 2013 Fortune 500 companies, along with organizations in nearly every industry and around the globe, rely on Red Hat Enterprise Linux. Red Hat Enterprise Linux 7 answers the heterogeneous realities of modern enterprise IT with a cohesive, unified foundation that enables customers to balance modern demands while reaping the benefits of computing innovation, like Linux Containers and big data, across physical systems, virtual machines and the cloud ? the open hybrid cloud. LEARN MORE ABOUT RED HAT ENTERPRISE LINUX 7 Attend the Virtual Event and Webcast: To join the virtual event or view the replay after the event, visit http://bit.ly/RHELjune10 Read the press release: http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7 Download Red Hat Enterprise Linux 7 (requires login): https://access.redhat.com/site/products/Red_Hat_Enterprise_Linux/ Access the documentation (requires login): * Red Hat Enterprise Linux 7 documentation: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/ * Release notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/index.html Get the latest news on Red Hat Enterprise Linux 7 We?ll be communicating announcements on betas, availability and more on Red Hat Enterprise Linux 7 via the Red Hat Enterprise Linux Blog moving forward. Subscribe today at http://rhelblog.redhat.com Sincerely, The Red Hat Enterprise Linux Team From derek at umiacs.umd.edu Wed Jun 11 00:36:20 2014 From: derek at umiacs.umd.edu (Derek Yarnell) Date: Tue, 10 Jun 2014 20:36:20 -0400 Subject: [rhelv6-list] Subscription Management Message-ID: <5397A484.1030203@umiacs.umd.edu> Maybe someone can give me a little direction in how to deal with the new subscription management requirement for RHEL7. We have always used RHN Classic with activation keys. This worked great and we use a RHN Proxy only (no satellite, we already have years of man hours invested in Cobbler and Puppet). I created a case in December when the beta was released and got very vague answers and didn't have time to deal with it. It seems that you can no longer use an activation key unless you have SAM. This looks to be licensed separately which is hilarious that you have to pay manage the licenses that you already payed for. I have re-opened that case but wanted to ask others what they have been doing with this. Putting a username and password in a kickstart script[1] seems stupid, the activation key was not perfect but at least the exposure was minimal. Subscription Management really seems to be more about Red Hat imposing draconian licensing hurdles on me as a customer rather than helping me solve any real problems[2]. [1] - https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1/html/Subscription_Concepts_and_Workflows/kickstart.html [2] - https://access.redhat.com/site/articles/502883 -- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies From bda20 at cam.ac.uk Fri Jun 13 09:40:01 2014 From: bda20 at cam.ac.uk (Ben) Date: Fri, 13 Jun 2014 10:40:01 +0100 (BST) Subject: [rhelv6-list] Kickstarting RHEL7 Message-ID: Hi Guys, Apologies for using the RHEL6 list for a RHEL7 issue. But in the absence of an official RHEL7 discussion list... I'm trying to manually kickstart a RHEL7 Workstation. By which I mean booting from a USB stick, specifying network details manually once the install screens appear, and then specifying the installation method as HTTP and giving the URL. As I've done with RHELs 3-6 I copied the vmlinuz and initrd.img from the ISO's /images/pxeboot directory to a USB stick and added a section to the stick's syslinux.cfg of the form: label manual7-64 kernel vmli7-64 append initrd=init7-64.img Booting from the stick, at the boot: prompt I then type "manual7-64". This causes the usual boot scroll I'm used to... until it ends with dracut-initqueue[620]: mount: no medium found on /dev/sr0 dracut-initqueue[620]: Warning: Couldn't mount /dev/sr0 dracut-initqueue[620]: Warning: no suitable images dracut-initqueue[620]: Warning: Could not boot. dracut-initqueue[620]: Warning: /dev/root does not exist It then drops to a dracut emergency shell and seems to have run sosreport (which doesn't seem to contain anything helpful). What am I missing, please? Do I need to specify something to tell it not to look at the DVD drive? Ben -- Unix Support, MISD, University of Cambridge, England From brilong at cisco.com Fri Jun 13 11:03:53 2014 From: brilong at cisco.com (Brian Long (brilong)) Date: Fri, 13 Jun 2014 11:03:53 +0000 Subject: [rhelv6-list] Kickstarting RHEL7 In-Reply-To: References: Message-ID: <07D0B4BE-0069-4BCD-8E5C-23643B4ACDCD@cisco.com> On Jun 13, 2014, at 5:40 AM, Ben wrote: > Hi Guys, > > Apologies for using the RHEL6 list for a RHEL7 issue. But in the absence of an official RHEL7 discussion list? There is an unofficial RHEL 7 list here: http://lists.clefos.org/mailman/listinfo/enterpriseseven-list > > I'm trying to manually kickstart a RHEL7 Workstation. By which I mean booting from a USB stick, specifying network details manually once the install screens appear, and then specifying the installation method as HTTP and giving the URL. The RHEL 7 Kickstart instructions should be perused: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-howto.html Specifically, it says that any kickstart _requires_ the special boot option ks.inst=/path/to/ks.cfg. If I were you, I would create an absolute minimum ks.cfg, put it on your USB stick and reference it from syslinux.cfg file on the append line. Please note I have not yet tried this. Also, under Chapter 20 boot options, it gives more details on ks.inst: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html /Brian/ -- Brian Long | | Research Triangle Park, NC . | | | . | | | . ' ' C I S C O From bda20 at cam.ac.uk Fri Jun 13 11:06:42 2014 From: bda20 at cam.ac.uk (Ben) Date: Fri, 13 Jun 2014 12:06:42 +0100 (BST) Subject: [rhelv6-list] Kickstarting RHEL7 (solved) In-Reply-To: References: Message-ID: On Fri, 13 Jun 2014, Ben wrote: > [RHEL7 manual kickstart woes] It looks like I've found the solution in the shape of adding the following to my syslinux.cfg "append" line: inst.repo=http:// (which is now working) "This option will allow you to load the installer and specify the installation source at the same time." Which is nice. or instead root=dracut (and specifying the location of the initrd.img) "If you use this option, you must specify the location of the initrd.img file extracted from Red Hat Enterprise Linux 7 bootable media. Using this option will allow you to boot the installer, but you will need to specify an installation source in another way (using a Kickstart file or manually in the graphical installer interface)." I haven't tried the latter, yet. Quotes taken from https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/pdf/Installation_Guide/Red_Hat_Enterprise_Linux-7-Installation_Guide-en-US.pdf (page 296, as labeled) Sorry for the spam. I wish there was a RHEL7 mailing list. Ben -- Unix Support, MISD, University of Cambridge, England From Tim.Mooney at ndsu.edu Fri Jun 13 19:46:09 2014 From: Tim.Mooney at ndsu.edu (Tim Mooney) Date: Fri, 13 Jun 2014 14:46:09 -0500 (CDT) Subject: [rhelv6-list] rhelv6-list Digest, Vol 44, Issue 4 In-Reply-To: References: Message-ID: In regard to: [rhelv6-list] Subscription Management, Derek Yarnell said: > I created a case in December when the beta was released and got very > vague answers and didn't have time to deal with it. It seems that you > can no longer use an activation key unless you have SAM. This looks to > be licensed separately which is hilarious that you have to pay manage > the licenses that you already payed for. I have re-opened that case but > wanted to ask others what they have been doing with this. I'm right there with you regarding frustration about this. We *are* a Satellite user, so in many ways we have it even worse than you do. It's not clear to me what Red Hat expects current Satellite customers to do. So far, https://access.redhat.com/site/articles/887923 is the best catch-all document I've seen, relating to differences and trouble spots that people are having. I have, however, been completely unable to find any documentation on what current Satellite customers are supposed to do regarding the new subscription management requirement for 7. Even if RHEL 7 turns out to be well-engineered from the start, Red Hat really dropped the ball on the communication component. Tim -- Tim Mooney Tim.Mooney at ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 From b.j.smith at ieee.org Fri Jun 13 22:01:17 2014 From: b.j.smith at ieee.org (Bryan J Smith) Date: Fri, 13 Jun 2014 18:01:17 -0400 Subject: [rhelv6-list] rhelv6-list Digest, Vol 44, Issue 4 In-Reply-To: References: Message-ID: ? On Fri, Jun 13, 2014 at 3:46 PM, Tim Mooney wrote: > I'm right there with you regarding frustration about this. > We *are* a Satellite user, so in many ways we have it even worse than > you do. It's not clear to me what Red Hat expects current Satellite > customers to do. > Red Hat Satellite 5.6 works perfectly fine with RHEL7 -- Beta and now GA. [1] So far, > https://access.redhat.com/site/articles/887923 > is the best catch-all document I've seen, relating to differences and > trouble spots that people are having. I have, however, been completely > unable to find any documentation on what current Satellite customers > are supposed to do regarding the new subscription management requirement > for 7. > If you have Satellite, you don't have to use Subscription Management. If you don't have Satellite, and don't want to use on-line Red Hat "hosted" Subscription Management, then Subscription Asset Manager (SAM) is now the solution. SAM allows off-line, internal usage, unlike Classic without Satellite. SAM is compatible with RHEL5.8+, RHEL6 and RHEL7, and has been around for 3 years. Even if RHEL 7 turns out to be well-engineered from the start, Red Hat > really dropped the ball on the communication component. >From my own experience, nothing has changed since December at the start of the RHEL7 Beta, when the Beta channels became available in the Content Delivery Network (CDN). [1a] The only issue I know of was when doing an minimal install. Only the Subscription Manager tools are installed, and not the rhn_setup package required for Satellite. [1b] SIDE NOTE: The RHEL7 Release Candidate (RC) didn't have channels separate from the Beta channels. [1c] As always, new software channels in the CDN often require a new certificate. These can be generated with the self-service tool. [2] This is one of the many reasons why I see Red Hat regularly encourage customers to sync the channels and test them with their existing provisioning and deployment workflow. I always make a point to test Satellite with any new certificate and channels whenever they become available. RHEL7 Beta and GA went much smoother for myself using Satellite 5.6 than even RHEL6 Beta and GA did back with 5.4. So, unless there is an experience I missed that you are running into, Satellite 5.6 should have "just worked" for RHEL7 (after generating a new certificate, of course). Even the Kickstarts have limited changes required, other than some comp.xml groupings and related details that may change with every, major update. Again, I ran into no issues myself back in December, and nothing else with GA. Definitely reach out to Red Hat GSS and/or your representative if you're having any issues. -- bjs P.S. Per the article, RHEL7 requires Satellite 5.6 for new platform channel-tool support. This is no different than back in 2010, when RHEL6 also required customers to be on Satellite 5.4 for new channel-tool support as well. [1] https://access.redhat.com/site/solutions/916273 [1a] https://access.redhat.com/site/solutions/737373 [1b] https://access.redhat.com/site/solutions/649023 [1c] https://access.redhat.com/site/solutions/883343 ?[2] ?https://rhn.redhat.com/rhn/systems/GenerateCertificate.do -- Bryan J Smith - UCF '97 Engr ----------------------------------------------------------------- "In a way, Bortles is the personification of the UCF football program. Each has many of the elements that everyone claims to want, and yet they are nobody's first choice. Coming out of high school, Bortles had the size and the arm to play at a more prestigious program. UCF likewise has the market size and the talent base to play in a more prestigious conference than the American Athletic. But timing and circumstances conspired to put both where they are now." -- Andy Staples, CNN-Sports Illustrated ? -------------- next part -------------- An HTML attachment was scrubbed... URL: