Search results for query "Linux ./configure"

6358 messages

Re: [CentOS] sound problems... pulseaudio/pavucontrol

by ken

On 04/03/2017 07:47 PM, Fred Smith wrote: > On Mon, Apr 03, 2017 at 12:53:54PM -0400, ken wrote: >> On 04/02/2017 01:31 PM, Kay Schenk wrote: >>> >>> On 03/29/2017 06:43 AM, ken wrote: >>>> On 03/28/2017 08:53 PM, ken wrote: >>>>> The www has failed me with this, so I'm trying you guys. Sound worked >>>>> great out of the box when I installed 7.2... Yay! I could watch all >>>>> kinds of videos, like on facebook and youtube. And I could listen to >>>>> most podcasts too. But then something happened. It was either a >>>>> kernel upgrade or that I installed vlc (for watching videos on DVD) >>>>> and the whole stack of codecs for it... I don't know exactly when, but >>>>> at some point I no longer had sound with youtube and other web >>>>> videos. The videos played fine, just no sound. Note that using vlc, >>>>> both video and the audio with it play just fine. I need to select the >>>>> audio driver (from a list in a vlc menu), however, else the sound >>>>> won't work in vlc either. >>>>> >>>>> If I go into the Applications menu, then System Tools -> Settings -> >>>>> Sound, under "Choose a device for sound output:" there are no devices >>>>> listed. There used to be. >>>>> >>>>> If I run "aplayer file.wav", nothing plays (no sound at all) and I get >>>>> the error "main:786: audio open error: No such file or directory". >>>>> If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., >>>>> specify the/a device), I do get sound, the file does play. >>>>> >>>>> I ran alsa-info.sh and it posted tons of info from it on my setup at >>>>> http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. >>>>> >>>>> Yet it still doesn't tell me what's missing. >>>>> >>>>> Anyone here have an idea...? or thoughts about where to look next? >>>>> >>>>> tia, >>>>> ken >>>> Still poking around my system for a solution, I found this comment at >>>> the top of /usr/lib/systemd/system/alsa-state.service and two other >>>> files in the same directory: >>>> >>>>> # Note that two different ALSA card state management schemes exist and >>>>> they >>>>> # can be switched using a file exist check - >>>>> /etc/alsa/state-daemon.conf . >>>> The /etc/alsa/state-daemon.conf file consists of one line: >>>> >>>>> # Remove this file to disable the alsactl daemon mode >>>> I understand that a daemon continually runs, waiting for an event and >>>> then acts in some way in response, but it has to mean something more in >>>> this context. Anyone familiar with the internals of this? >>>> >>>> >>> I am not on systemd right now. I'm on CentOS 6.8. However, on an >>> openSUSE version I was. Sound problems were the bane of my >>> existence forever it seemed. So it maye take you a while to >>> troubleshoot this. Using JUST alsa you should be able to play >>> sound files at the command line. See: >>> http://www.alsa-project.org/main/index.php/Main_Page >>> >>> >>> I think I may have installed pulse-audio to get things working >>> under systemd with my GUI. What is your GUI? This may be a factor. >>> >> Thanks for the thought. This is quite plausible. I did a little >> reading at the site you suggested and then at another which was >> linked off of that. I didn't find anything helpful at either place >> yet... well, except that in the audio stack alsa is just one layer; >> jack and pulseaudio ride on top of it. Apparently sound on linux >> can use all of them-- and others on both of the same layers-- all at >> the same time. This is probably what makes the configuration of >> them all so challenging. >> >> In the middle of reading those sites I decided to see if audacity (a >> quite sophisticated and solid program) could somehow handle sound. I >> installed it and fired it up. Out of the box it didn't work. But I >> simply had to choose the correct device from audacity's drop-down >> menu and, viola, it would produce sound from a loaded file. Cool. >> >> Right after that, I tried running "aplay >> /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously >> it didn't, although (as noted above) that same command when >> specifying the device did (i.e., "aplay >> /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently >> installing and/or running audacity fixed something, but not >> everything. >> >> Another trippy discovery: I used rpm to verify all the files >> installed with all the alsa* packages and there were absolutely no >> changes to any of them... they're all exactly as they were when >> first installed. Since sound worked exquisitely when I first >> installed 7.2 on this box and no alsa files have been changed since >> then, it's hard to find the fault with alsa. >> >> Although aplay is back to working without having to specify the >> device, I still don't get sound out of youtube videos (even though I >> checked the settings and restarted Firefox), and gnome3's System >> Settings -> Sound still lists no devices at all. These are two >> major failures. > Are you, perchance, using Firefox-52? At version 52, they switched > Firefox to use Pulse instead of Alsa. So you'll probably need to > fire up pavucontrol and mess with its sliders to get firefox audio > working. Good call, Fred. Just today I got a message when, doing testing, a message came up in Firefox that I needed to install pulseaudio.* Well, I never installed pulseaudio, but it's already installed,** so it must have been installed when I first installed 7.2 on this machine. So then I tried, as you suggested, to start up pavucontrol and play around with it. However, pavucontrol was not installed. So yumd'd it down and installed, then clicked on it in the Applications -> Sound & Video menu, but I just got a window pop with the message, "Fatal Error: Unable to connect to PulseAudio: OK". Well, at least I finally have an explicit statement from the system that there's a problem. *Okay, now we know you're a psychic. Along with that Firefox message was a button for more info. I clicked and it went to a webpage which basically said the same thing in more detail and with a link (allegedly) to more info, https://support.mozilla.org/t5/Videos-sound-pictures-and/Fix-common-audio-a…. **As I did a day or two ago with alsa packages, I used rpm to verify all the pulse* packages (rpm -qaVv pulseaudio*) and found that none of the files in any of the packages had been altered at all. > I'm on Centos-7.3, and when I switched from 7.2 I found that some > things now are controlled by pavucontrol, and not by the volume > control in the top panel (I'm using Mate, not Gnome,... Gah, how can > anyone stand Gnome 3.x??) It's kind of a pain, I haven't yet found > a way to localize controls for all the various audio-producing tools > in one place. Does anyone know how to do that? Sorry, I've never seen anything like that. >> Does anyone know how to restart audio in systemd? That might still >> be worth looking into. # systemctl list-unit-files --type=service ... alsa-restore.service static alsa-state.service static alsa-store.service static ... The above command showed the three alsa services, but nothing for the other audio software I've been poking around in: pulseaudio, jack, oss. Nor did I see anything else listed which told me it had anything directly to do with the system's audio. Moreover, I don't have alsa running as a daemon. So unless I'm misunderstanding what systemd does, I don't think it's playing a role in my sound problems. >> Before doing audacity, I tried gnome's mplayer. Geez, is that a >> stinky pile of code. Just selecting a directory where a file could >> be selected ended up locking up the app; I had to do a kill to get >> it off my screen. Does that actually work for anyone? If so, what >> kind of files or net locations does it work for? >> >> Thanks once more for your thoughtful suggestions.

9 years

Re: [CentOS] Minimal kickstart.cfg requested

by Richard Karhuse

On Fri, Apr 24, 2009 at 9:48 PM, <Daniel_Curry(a)dell.com> wrote: > > Hello, all. > > I'm looking at building about a dozen CentOS VM's for a project. I have > a desire to use kickstart for this coupled with PXE. I'm looking for a > minimal ks.cfg file specifically, I want the bare minimum of software > that is needed for a system to function. I will need sshd and yum as > the only 'services or applications' on top of the OS. Does anyone have > an example I can work with, or suggestions on getting to this minimal > configuration? I'm just looking to save some time, rather than > re-inventing what may and probably is already out there. > > Thanks > > Daniel Since this topic comes up frequently on various e-mail lists, I was surprised that there wasn't a (mild) flame about searching the archives and/or googling ... Here are a few, representative posts that have occurred in the past (and I've saved) and I hope it helps ... -rak- ===================================================================== ---------- Forwarded message ---------- From: David Goldsmith <dgoldsmith(a)sans.org> Date: Sat, Mar 28, 2009 at 6:19 PM Subject: Re: [CentOS] Minimal Install? To: CentOS mailing list <centos(a)centos.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Norberto Bensa wrote: > On Sat, Mar 28, 2009 at 12:05 PM, Jim Wildman <jim(a)rossberry.com> wrote: >> rpm -qf `which <command>` > > Nice. Thanks Frank and Jim > > What about the minimal install? Is it possible? I don't need kerberos, > ldap, and a lot of other things. > > Best regards, > Norberto > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos I was just playing with this myself this week. For CentOS 5.2, the very minimal install is 88 RPMs. This is missing things you will need (like openssh, passwd, yum, etc) but its basically the bare-bones install. If you statically assign IP addresses and don't care about DHCP, you can reduce the list one more and get rid of 'dhclient'. All other RPMs are required because of the dependencies that are laid out. Various other things will be required as you add some of the useful utilities back in. The list of RPMS are: audit-libs basesystem bash beecrypt bzip2-libs centos-release centos-release-notes chkconfig coreutils cpio cracklib cracklib-dicts db4 device-mapper device-mapper-event device-mapper-multipath dhclient diffutils dmraid e2fsprogs e2fsprogs-libs elfutils-libelf ethtool expat filesystem findutils gawk gdbm glib2 glibc glibc-common grep grub gzip info initscripts iproute iputils kernel keyutils-libs kpartx krb5-libs less libacl libattr libcap libgcc libselinux libsepol libstdc++ libsysfs libtermcap lvm2 m2crypto MAKEDEV mcstrans mingett mkinitrd mktemp module-init-tools nash ncurses net-tools openssl pam pcre popt procps psmisc python readline redhat-logos rootfiles rpm rpm-libs sed setup shadow-utils sqlite sysklogd SysVinit tar termcap tzdata udev util-linux vim-minimal zlib If you are building a Kickstart file, here are useful %packages and %post sections: %packages --nobase kernel-PAE - -audit-libs-python - -checkpolicy - -dhcpv6-client - -ecryptfs-utils - -ed - -file - -gnu-efi - -gpm - -hdparm - -kbd - -libhugetlbfs - -libselinux-python - -libsemanage - -nspr - -nss - -openssh - -openssh-clients - -openssh-server - -perl - -policycoreutils - -prelink - -selinux-policy - -selinux-policy-targeted - -setools - -setserial - -sysfsutils - -tcl - -udftools - -vim-enhanced %post rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 yum -y remove kernel iptables slang usermode wireless-tools yum -y remove cryptsetup-luks dbus dmidecode hwdata libgpg-error libusb yum -y remove libvolume_id libxml2-python pciutils yum -y remove cyrus-sasl-lib logrotate Packages that are in the Core group tagged as 'mandatory' will get installed even if you specify them with '-' in the %packages section thus the need to explicitly remove them in the %post section. Packages in the Core group tagged as 'default' can be configured to not be installed by subtracting them in the %packages section. After the install finishes, you can run the following rpm command to get rid of yum stuff if desired: rpm -e libxml2 python-elementtree python-iniparse python-sqlite python-urlgrabber rpm-python yum yum-metadata-parser This 'minimal' load is mainly for educational purposes just to see how small it can get (about 300MB) -- its not very useful. A useful minimal load will be somewhere around 150-200 packages depending on what utilities you want to include. - -- David Goldsmith -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJzqJV417vU8/9QfkRAjYPAKC3k6UMS2qKA6P8BcXYEtDnOWczJQCcCGLG lpoKd9kbkc3Hw6HyKgmdf30= =3/Px -----END PGP SIGNATURE----- ------------------------------------------------------------------------------------------------------- ---------- Forwarded message ---------- From: Paul Heinlein <heinlein(a)madboa.com> Date: Tue, Oct 28, 2008 at 5:15 PM Subject: Re: [CentOS] Kickstart package groups To: CentOS mailing list <centos(a)centos.org> On Tue, 28 Oct 2008, Francisco Puente wrote: Hello, I'm building another kickstart CD, minimal, and creating my own repository. Is there any way I can get the list of files that a group (like @core o @base) will install? Below my .sig is an XSLT stylesheet that will do the trick. Save it to your filesystem as, e.g., comps.xsl. Then use xsltproc to apply it to the comps.xml file, e.g., xsltproc --novalid comps.xsl /path/to/repodata/comps.xml > comps.html The resulting HTML file will provide you a reasonable list of packages associated with each group. Warning: the list might not be complete because any given package in your named group(s) might might require packages not in those groups. That's why anaconda does dependency checking at installation time. -- Paul Heinlein <> heinlein(a)madboa.com <> http://www.madboa.com/ ----- comps.xsl ----- <?xml version='1.0'?> <!DOCTYPE xsl:stylesheet [ <!ENTITY nbsp " "> ]> <xsl:stylesheet version="1.0" mlns="http://www.w3.org/1999/xhtml" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes" encoding="iso-8859-1" doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"/>  <xsl:template match="comps"> <html lang="en-US"> <head> <title>comps.xml</title> <xsl:call-template name="default.css"/> </head> <body> <xsl:call-template name="intro.text"/> <table width="95%"> <tr> <th>Name</th> <th>Default</th> <th>Visible</th> <th>Description</th> </tr> <xsl:apply-templates select="group" mode="group.chart"/> </table> <p> </p> <table width="95%"> <tr> <th>Name</th> <th>Groups Req.</th> <th>Packages Req.</th> </tr> <xsl:apply-templates select="group" mode="package.chart"/> </table> </body> </html> </xsl:template>  <xsl:template match="group" mode="group.chart"> <xsl:variable name="id" select="id"/> <tr> <td id="{$id}-info"> <a href="#{$id}-detail"><xsl:value-of select="name"/></a> </td> <td><xsl:value-of select="default"/> </td> <td><xsl:value-of select="uservisible"/> </td> <td><xsl:value-of select="description"/> </td> </tr> </xsl:template>  <xsl:template match="group" mode="package.chart"> <xsl:variable name="id" select="id"/> <tr> <td id="{$id}-detail"> <a href="#{$id}-info"><xsl:value-of select="name"/></a> </td> <td><xsl:apply-templates select="grouplist"/></td> <td><xsl:apply-templates select="packagelist"/></td> </tr> </xsl:template>  <xsl:template match="grouplist"> <table width="100%"> <xsl:apply-templates select="*" mode="html.table"/> </table> </xsl:template> <xsl:template match="groupreq" mode="html.table"> <tr> <xsl:call-template name="sub.table.row"> <xsl:with-param name="leftcol" select="."/> <xsl:with-param name="rightcol" select="' '"/> </xsl:call-template> </tr> </xsl:template> <xsl:template match="metapkg" mode="html.table"> <tr> <xsl:call-template name="sub.table.row"> <xsl:with-param name="leftcol" select="."/> <xsl:with-param name="rightcol" select="@type"/> </xsl:call-template> </tr> </xsl:template>  <xsl:template match="packagelist"> <table width="100%"> <xsl:apply-templates select="*" mode="html.table"/> </table> </xsl:template> <xsl:template match="packagereq" mode="html.table"> <tr> <xsl:call-template name="sub.table.row"> <xsl:with-param name="leftcol" select="."/> <xsl:with-param name="rightcol" select="@type"/> </xsl:call-template> </tr> </xsl:template>  <xsl:template name="sub.table.row"> <xsl:param name="leftcol"/> <xsl:param name="rightcol"/> <xsl:variable name="last"> <xsl:choose> <xsl:when test="position() = last()">1</xsl:when> <xsl:otherwise>0</xsl:otherwise> </xsl:choose> </xsl:variable> <xsl:choose> <xsl:when test="$last = '1'"> <td style="border-style: none;"><xsl:value-of select="$leftcol"/></td> <td style="border-style: none; text-align: right;"> <xsl:value-of select="$rightcol"/> </td> </xsl:when> <xsl:otherwise> <td><xsl:value-of select="$leftcol"/></td> <td style="text-align: right;"><xsl:value-of select="$rightcol"/></td> </xsl:otherwise> </xsl:choose> </xsl:template> <xsl:template name="default.css"> <xsl:variable name="color" select="'#990000'"/> <style type="text/css"> a, a:link, a:active, a:visited { color: <xsl:value-of select="$color"/>; } body { font-size: small; background-color: white; color: black; width: 700px; } td { border-bottom: 1px solid #999; font-size: small; vertical-align: top; } th { color: white; background-color: <xsl:value-of select="$color"/>; font-weight: bold; text-align: left; padding-right: 15px; } </style> </xsl:template> <xsl:template name="intro.text"> <p> Below is an outline of the package groups available at installation and, later, via yum and other package-management tools. The top table contains descriptions of each group. To see a detailed view of the packages that get installed with each group, click on the group name. </p> </xsl:template> </xsl:stylesheet> ----- end comps.xsl ----- ------------------------------------------------------------------------------------------------ ---------- Forwarded message ---------- From: Barry Brimer <lists(a)brimer.org> Date: Sat, Jul 5, 2008 at 9:32 AM Subject: Re: [CentOS] Wanted: minimal install ks.cfg To: CentOS mailing list <centos(a)centos.org> > I'm in need of a minimal ks.cfg file for the smallest possible install > with yum. I've got the scripting for yum to install the apps I need, I > just want to insure all the cruft is not on the system as well. Using > the s-c-ks app, the smallest I have gotten is 600MB. This is for a > server appliance vm that I need to deploy quickly and dynamically. http://wiki.centos.org/TipsAndTricks/KickStart ===================================================================== ---------- Forwarded message ---------- From: <centos(a)bartbaars.nl> Date: Wed, Jun 25, 2008 at 4:20 AM Subject: Re: [CentOS] truly minimal install To: CentOS mailing list <centos(a)centos.org> Use a kickstart-file that has a "nobase" statement.. And have a look at CLIP (http://oss.tresys.com/projects/clip/wiki/WikiStart) for a truly minimal kickstart (and a lot of other security related stuff, if you're interested).. Cheers, Bart ----- Original Message ----- From: "Karanbir Singh" <mail-lists(a)karan.org> To: "CentOS mailing list" <centos(a)centos.org> Sent: Wednesday, June 25, 2008 1:17:28 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: [CentOS] truly minimal install David Hláčik wrote: > My question is, which way i will achieve really minimum install (with yum). > So far, i have during install unchecked all packages , then customized > groups and removed everything including base system. > As a result my CentOS install was 800MB , which is still to much for us. > Value around 300 - 400 MB is OK. do a bunch of 'yum erase' runs postinstall to remove whatever you dont need ? -- Karanbir Singh : http://www.karan.org/ : 2522219@icq ------------------------------------------------------------------------------------------- http://jons-thoughts.blogspot.com/2007/12/minimal-kickstart.html Friday, December 07, 2007 Minimal kickstart I get a lot of questions regarding the fact that RHEL and CentOS install "too much" by default. They do - not many people require Bluetooth on their servers for example. So here's a kickstart which will install Just enough in order to boot the system. Note that removing some stuff from the below list will result in a less than functional system, possibly even unbootable. There is a bug which could result in the system becoming unbootable if too much is stripped out. Without further ado, here's a working kickstart for CentOS 4. It will also work on RHEL4 if you remove the 'yum' package specification install text reboot url --url (your install source goes here) lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us skipx network --device eth0 --bootproto dhcp rootpw --iscrypted (insert a crypted rootpw here - openssl passwd -1) firewall --disabled selinux --permissive authconfig --enableshadow --enablemd5 timezone America/New_York bootloader --location=mbr # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --initlabel part /boot --fstype ext3 --size=250 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.2 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=256 --grow --maxsize=512 %packages --nobase coreutils yum rpm e2fsprogs lvm2 grub sysstat ntp openssh-server openssh-clients %post # setup NTP eco << EOF > /etc/ntp.conf restrict default noquery notrap nomodfiy restrict 127.0.0.1 server 0.rhel.ntp.org server 1.rhel.ntp.org server 2.rhel.ntp.org driftfile /var/lib/ntp/drift EOF chkconfig ntpd on Posted by Jon Stanley at 11:33 AM ============================================================================== ---------- Forwarded message ---------- From: Jim Wildman <jim(a)rossberry.com> Date: Thu, Sep 28, 2006 at 8:49 AM Subject: Re: [CentOS] Trimming the fat out of a Centos 4.4 Installation To: CentOS mailing list <centos(a)centos.org> On Thu, 28 Sep 2006, Erick Perez wrote: > Hi, just to avoid re-inventing the wheel, is there any document that > can help me reduce even further a "minimum" installation of Centos 4.4 > (BTW can you say 600mb is minimum)? > This is my 'minimal base' that I start from. You could remove the lvm2 stuff as well. It will do an install of 163 packages and take about 540M of disk. About the only thing you will have is ssh and yum. For a card, you obviously want to change the disk layout. Apply all the other comments to this one. # Kickstart file automatically generated by anaconda. install url --url <your url here> lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8 keyboard us # xconfig --card "VMWare" --videoram 16384 --hsync 31.5-37.9 --vsync 50-70 --resolution 800x600 --depth 16 network --device eth0 --bootproto dhcp rootpw --iscrypted <your pw here> firewall --disabled selinux --disabled authconfig --enableshadow --enablemd5 timezone America/New_York bootloader --location=mbr # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --linux --drives=sda part /boot --fstype ext3 --size=100 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.2 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1024 reboot skipx %packages -nobase yum -acpid -authconfig -bc -checkpolicy -dmraid -policycoreutils -selinux-policy-targeted -libxslt -xmlsec1-openssl -xmlsec1 -nc -lsof -apmd -aspell -aspell-en -autofs -bluez-bluefw -bluez-hcidump -bluez-libs -bluez-utils -crash -cups -cups-libs -dapl -desktop-file-utils -dhcpv6_client -diskdumputils -dos2unix -dosfstools -dump -eject -finger -fontconfig -freetype -ftp -gpm -groff -hdparm -htmlview -ibmasm -indexhtml -ipsec-tools -irda-utils -isdn4k-utils -jpackage-utils -jwhois -kernel-ib -kernel-smp -krb5-workstation -lftp -lha -libgssapi -libibverbs -libmthca -librdmacm -libsdp -libwvstreams -lksctp-tools -logrotate -logwatch -m4 -m4 -mailcap -mailx -man -man-pages -mdadm -minicom -mkbootdisk -mt -mtools -mtr -mt-st -nano -netconfig -netdump -net-snmp-libs -NetworkManager -nfs -nfs-utils-lib -nscd -nss_ldap -numactl -OpenIPMI -OpenIPMI-libs -pam_ccreds -pam_krb5 -pam_passwdqc -pam_smb -parted -patch -pax -pcmcia-cs -pdksh -pinfo -portmap -ppp -procmail -psacct -quota -rdate -rdist -redhat-lsb -redhat-menus -rhpl -rmt -rp-pppoe -rsh -rsync -sendmail -setarch -setools -slocate -specspo -stunnel -sudo -syslinux -sysreport -system-config-mouse -system-config-network-tui -system-config-securitylevel-tui -talk -tcpdump -tcsh -telnet -time -traceroute -unix2dos -up2date -vconfig -wget -which -wireless-tools -wvdial -xorg-x11-libs -xorg-x11-Mesa-libGL -ypbind -yp-tools %post ------------------------------------------------------------------------ Jim Wildman, CISSP, RHCE jim(a)rossberry.com http://www.rossberry.com "Society in every state is a blessing, but Government, even in its best state, is a necessary evil; in its worst state, an intolerable one." Thomas Paine

16 years, 11 months

Re: [CentOS] Probelm solved -- Re: openldap-server 'TLSVerifyClient demand' fails on centos 6.2?

by Craig White

Can't speak with certainty about CentOS6 but assuming that it is using sssd somewhat like Fedora you need to concentrate on /etc/sssd/sssd.conf and include ldap_tls_reqcert = never Note that sssd essentially takes the place of padl tools (/etc/ldap.conf) Also note that /etc/openldap/ldap.conf is only for openldap cli client tools such as ldapsearch/ldapmodify/etc. That's why /root/.ldaprc sort of works for you but it is much more logical/consistent to configure sssd.conf properly because that is where daemons should be looking for system configuration information. Craig On Apr 23, 2012, at 3:01 PM, Robinson Tiemuqinke wrote: > Found the problem and solved. > > > I accidently copied the file /etc/openldap/ldap.conf accidently to under /root account as .ldaprc file and immediately the problem goes away. Read manual again and found that the tls_cert and tls_key are USER_ONLY option! > > So now the problem goes away, and sure I'lll change the TLSVerifyClient option back to 'try'. It is of no immediate uses if TLS client authentication is only user-option. > > Thanks. > > > > > ________________________________ > From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com> > To: CentOS mailing list <centos(a)centos.org> > Sent: Monday, April 23, 2012 2:42 PM > Subject: openldap-server 'TLSVerifyClient demand' fails on centos 6.2? > > > ldapsearch -x -ZZ works fine on clients, when the server side slapd.conf has 'TLSVerifyClient' is set to 'try'. But after I changed that the 'demand' all clients' "ldapsearch -x -ZZ" command fails immediately. I run the 'slapd -d3' at server side too. > > It looks like maybe 'ldapsearch -x -zz' didn't send out client certificates, even though it should with '-ZZ' options -- from ldap.conf manual? > > My client side /etc/openldap/ldap.conf is like below: > > BASE dc=example,dc=com > URI ldap://ldapmaster.example.com > > ## working > TLS_CACERT /etc/openldap/myca.crt > TLS_CERT /etc/openldap/ldapclient01.crt > TLS_KEY > /etc/openldap/ldapclient01.key > > > My server side setup is: > > ## now using my own CA > ## and it works! > TLSCACertificateFile /etc/openldap/myca.crt > TLSCertificateFile /etc/openldap/ldapmaster.crt > TLSCertificateKeyFile /etc/openldap/ldapmaster.key > > > #TLSVerifyClient allow > TLSVerifyClient demand ## testing client TLS keys and my own CA setup, 'demand' failed for ldapsearch > #TLSCipherSuite HIGH:MEDIUM:LOW:+SSLv2 > TLSCipherSuite HIGH:MEDIUM:+SSLv2 > > > The logs on server is attahed below as well, Thanks. > ... > connection_get(14): got connid=1000 > connection_read(14): checking for input on id=1000 > TLS: loaded CA certificate file /etc/openldap/myca.crt. > TLS: certificate [E=admin(a)example.com,CN=ldapmaster.example.com,OU=techOps,O=Pegaclouds Inc.,L=San Mateo,ST=CA,C=US] is valid > tls_read: want=3, got=3 > 0000: 16 03 01 ... > tls_read: want=2, got=2 > 0000: 00 41 .A > tls_read: want=65, > got=65 > 0000: 01 00 00 3d 03 01 4f 95 c1 e0 a9 10 22 30 25 4b ...=..O....."0%K > 0010: f8 da a5 27 64 9e 25 60 35 d0 5c 28 30 74 a8 40 ...'d.%`5.\(0t.@ > ... > > tls_read: want=5 error=Resource temporarily unavailable > connection_get(14): got connid=1000 > connection_read(14): checking for input on id=1000 > tls_read: want=5, got=5 > 0000: 16 03 01 01 0d ..... > tls_read: want=269, got=269 > 0000: 0b 00 00 03 00 00 00 10 00 01 02 01 00 ac 64 b8 ..............d. > 0010: bd bf 20 46 b8 14 e7 38 9a a1 40 2c 36 3a 78 fa .. F...8..@,6:x. > 0020: 8a 12 61 3d e3 5e bf 02 f2 f9 > a1 70 4e 7f 4e 11 ..a=.^.....pN.N. > 0030: cd e6 ba 6d ee 1e 91 95 c7 9f c7 b3 e0 21 ea bb ...m.........!.. > 0040: 11 78 cc 58 c1 b1 37 f4 d5 18 ff 59 ad df 48 52 .x.X..7....Y..HR > 0050: a7 cd 26 0a fe d8 09 bb 7e 70 16 d2 b7 35 de 9f ..&.....~p...5.. > 0060: b3 0a ee 1e aa 42 e4 20 ed 8d 2f 31 f2 5d e9 d7 .....B. ../1.].. > 0070: 82 4c 78 30 48 5d 54 5c cf c2 cc c9 33 31 50 c5 .Lx0H]T\....31P. > 0080: 56 62 f8 ea dd 34 32 ff a1 81 e3 2f f7 a4 0e 58 Vb...42..../...X > 0090: ff 84 39 0a fe 74 20 18 a6 ac 18 00 dc 8c 0e fd ..9..t ......... > 00a0: 5d 2e a3 87 4e 0b e8 51 66 85 8a 60 2e b7 01 a2 ]...N..Qf..`.... > 00b0: 4a 5c d9 74 9b 32 04 16 57 2e f2 60 2d 45 3d > 30 J\.t.2..W..`-E=0 > 00c0: e3 39 c9 a3 af 7b 86 4b f0 f0 7e 34 f8 bf cf 4c .9...{.K..~4...L > 00d0: 73 57 df e5 11 0a 41 de 7f 78 ed f4 cf 9b e8 10 sW....A..x...... > 00e0: ce 1a b1 73 ff 76 ec ff 23 46 85 24 02 b9 aa 4b ...s.v..#F.$...K > 00f0: fe c9 2a c6 06 ff 54 94 25 5d cc 3d de 5b 1d 9f ..*...T.%].=.[.. > 0100: 03 a1 36 da 3b 69 95 67 21 b5 61 d7 e9 ..6.;i.g!.a.. > tls_write: want=7, written=7 > 0000: 15 03 01 00 02 02 2a ......* > TLS: error: accept - force handshake failure: errno 11 - moznss error -12285 > TLS: can't accept: TLS > error -12285:Unable to find the certificate or key necessary for authentication.. > connection_read(14): TLS accept failure error=-1 id=1000, closing > connection_close: conn=1000 sd=14 > ... > --Robinson > > > > > > ________________________________ > From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com> > To: CentOS mailing list <centos(a)centos.org> > Sent: Wednesday, November 23, 2011 11:20 AM > Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? > > > I've tried with cr kernel, not it moves much faster but still fails -- fails at the partition failure, this setup is S3 backed image. > > root (hd0) > Filesystem type is ext2fs, using whole disk > kernel /boot/vmlinuz-2.6.32-131.17.1.el6.x86_64 ro root=/dev/sda1 rd_NO_LUKS rd > _NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTY > PE=pc KEYTABLE=us crashkernel=auto crashkernel=auto > initrd /boot/initramfs-2.6.32-131.17.1.el6.x86_64.img > > close blk: backend at /local/domain/0/backend/vbd/8/2049 > close blk: backend at /local/domain/0/backend/vbd/8/2064 > close blk: backend at /local/domain/0/backend/vbd/8/2080 > close blk: backend at /local/domain/0/backend/vbd/8/2096 > close blk: backend at > /local/domain/0/backend/vbd/8/2112 > Initializing cgroup subsys cpuset > Initializing cgroup subsys cpu > Linux version 2.6.32-131.17.1.el6.x86_64 (mockbuild(a)c6b5.bsys.dev.centos.org) (gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) ) #1 SMP Thu Oct 6 19:24:09 BST 2011 > Command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=auto > KERNEL supported cpus: > Intel GenuineIntel > AMD AuthenticAMD > Centaur CentaurHauls > ACPI in unprivileged domain disabled > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 00000000000a0000 (usable) > Xen: 00000000000a0000 - 0000000000100000 (reserved) > Xen: 0000000000100000 - 00000001c0000000 (usable) > DMI not present or invalid. > last_pfn = 0x1c0000 max_arch_pfn = 0x400000000 > last_pfn = 0x100000 max_arch_pfn = > 0x400000000 > init_memory_mapping: 0000000000000000-0000000100000000 > init_memory_mapping: 0000000100000000-00000001c0000000 > RAMDISK: 02028000 - 0460c000 > No NUMA configuration found > Faking a node at 0000000000000000-00000001c0000000 > Bootmem setup node 0 0000000000000000-00000001c0000000 > NODE_DATA [0000000000008000 - 000000000003bfff] > bootmap [000000000003c000 - 0000000000073fff] pages 38 > (8 early reservations) ==> bootmem [0000000000 - 01c0000000] > #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > #1 [000540f000 - 000543e000] XEN PAGETABLES ==> [000540f000 - 000543e000] > #2 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] > #3 [0001000000 - 0002007524] TEXT DATA BSS ==> [0001000000 - 0002007524] > #4 [0002028000 - > 000460c000] RAMDISK ==> [0002028000 - 000460c000] > #5 [000460c000 - 000540f000] XEN START INFO ==> [000460c000 - 000540f000] > #6 [0000100000 - 00008d3000] PGTABLE ==> [0000100000 - 00008d3000] > #7 [000543e000 - 0005a41000] PGTABLE ==> [000543e000 - 0005a41000] > Reserving 129MB of memory at 96MB for crashkernel (System RAM: 7168MB) > Zone PFN ranges: > DMA 0x00000001 -> 0x00001000 > DMA32 0x00001000 -> 0x00100000 > Normal 0x00100000 -> 0x001c0000 > Movable zone start PFN for each node > early_node_map[2] active PFN ranges > 0: 0x00000001 -> 0x000000a0 > 0: 0x00000100 -> 0x001c0000 > SFI: Simple Firmware > Interface v0.7 http://simplefirmware.org > SMP: Allowing 8 CPUs, 0 hotplug CPUs > No local APIC present > APIC: disable apic facility > PM: Registered nosave memory: 00000000000a0000 - 0000000000100000 > PCI: Warning: Cannot find a gap in the 32bit address range > PCI: Unassigned devices with 32bit resource registers may break! > Allocating PCI resources starting at 1c0100000 (gap: 1c0100000:400000) > Booting paravirtualized kernel on Xen > Xen version: 3.4.3-2.6.18 (preserve-AD) > NR_CPUS:4096 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1 > PERCPU: Embedded 30 pages/cpu @ffff88002804f000 s92504 r8192 d22184 u122880 > pcpu-alloc: s92504 r8192 d22184 u122880 alloc=30*4096 > pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 > Xen: using vcpu_info placement > Built 1 zonelists in Node order, mobility grouping on. Total pages: 1807817 > Policy zone: Normal > Kernel command line: ro root=/dev/sda1 rd_NO_LUKS rd_NO_LVM > rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto crashkernel=129M@0M > PID hash table entries: 4096 (order: 3, 32768 bytes) > Checking aperture... > No AGP bridge found > AMD-Vi disabled by default: pass amd_iommu=on to enable > PCI-DMA: Using software bounce buffering for IO (SWIOTLB) > Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000 > software IO TLB at phys 0x20000000 - 0x24000000 > Memory: 6955572k/7340032k available (5013k kernel code, 388k absent, 384072k reserved, 7291k data, 1232k init) > Hierarchical RCU implementation. > NR_IRQS:33024 nr_irqs:336 > Console: colour dummy device 80x25 > console [tty0] enabled > console [hvc0] enabled > > ... > TCP cubic registered > Initializing XFRM netlink socket > NET: Registered protocol family 17 > registered taskstats version 1 > XENBUS: Device with no driver: > device/vbd/2049 > XENBUS: Device with no driver: device/vbd/2064 > XENBUS: Device with no driver: device/vbd/2080 > XENBUS: Device with no driver: device/vbd/2096 > XENBUS: Device with no driver: device/vbd/2112 > XENBUS: Device with no driver: device/vif/0 > XENBUS: Device with no driver: device/console/0 > drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > Initalizing network drop monitor service > Freeing unused kernel memory: 1232k freed > Write protecting the kernel read-only data: 10240k > Freeing unused kernel memory: 1112k freed > Freeing unused kernel memory: 1796k freed > dracut: dracut-004-33.2.el6_0 > dracut: rd_NO_LUKS: removing cryptoluks activation > dracut: rd_NO_LVM: removing LVM activation > device-mapper: uevent: version 1.0.3 > device-mapper: ioctl: 4.20.6-ioctl (2011-02-02) initialised: dm-devel(a)redhat.com > udev: starting version 147 > dracut: Starting plymouth daemon > dracut: rd_NO_DM: removing DM RAID > activation > dracut: rd_NO_MD: removing MD RAID activation > xlblk_init: register_blkdev major: 202 > blkfront: xvde1: barriers disabled > blkfront: xvdf: barriers disabled > xvdf: > unknown partition table > blkfront: xvdg: barriers disabled > xvdg: unknown partition table > blkfront: xvdh: barriers disabled > xvdh: unknown partition table > blkfront: xvdi: barriers disabled > xvdi: unknown partition table > > Boot has failed, sleeping forever. > > > > > > ________________________________ > From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com> > To: Johnny Hughes <johnny(a)centos.org> > Cc: CentOS mailing list <centos(a)centos.org> > Sent: Wednesday, November 23, 2011 10:48 AM > Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? > > Hi Johnny, > > Thanks a lot. I'll upgrade kernel to the cr repository, and give it a try now. > > --Guolin > > > ________________________________ > From: Johnny Hughes <johnny(a)centos.org> > To: centos(a)centos.org > Sent: Wednesday, November 23, 2011 9:55 AM > Subject: Re: [CentOS] Any ideas?? -- Re: EC2 compatible kernel for centos 6? > > On 11/23/2011 11:40 AM, Robinson Tiemuqinke wrote: >> I tried several ways but still no help. The following are the output (stock Centos 6 2.6.32-71.29.1.el6.x86_64 kernel), grub works fine and it located kernel and initial ramdisk. but kernel booting faied at the very beginning... >> >> Any suggestions are more than appreciated. >> >> >> > -------------------------------------------------- >> >> > 2011-11-23T17:19:21+0000 >> Xen Minimal OS! >> start_info: 0x1890000(VA) >> nr_pages: 0x1e0000 >> shared_inf: 0xb2cea000(MA) >> pt_base: 0x1893000(VA) >> nr_pt_frames: 0x11 >> mfn_list: 0x990000(VA) >> mod_start: 0x0(VA) >> mod_len: 0 >> flags: 0x0 >> cmd_line: root=/dev/sda1 ro 4 >> stack: 0x94f860-0x96f860 >> MM: Init >> _text: 0x0(VA) >> _etext: 0x6000d(VA) >> _erodata: 0x78000(VA) >> _edata: 0x80b00(VA) >> stack start: 0x94f860(VA) >> _end: 0x98fe68(VA) >> start_pfn: 18a7 >> max_pfn: 1e0000 >> Mapping memory range > 0x1c00000 - 0x1e0000000 >> setting 0x0-0x78000 readonly >> skipped 0x1000 >> MM: Initialise page allocator for 27a0000(27a0000)-1e0000000(1e0000000) >> MM: done >> Demand map pfns at 1e0001000-21e0001000. >> Heap resides at 21e0002000-41e0002000. >> Initialising timer interface >> Initialising console ... done. >> gnttab_table mapped at 0x1e0001000. >> Initialising scheduler >> Thread "Idle": pointer: 0x21e0002010, stack: 0x36f0000 >> Initialising xenbus >> Thread "xenstore": pointer: 0x21e00027c0, stack: 0x3700000 >> Dummy main: start_info=0x96f960 >> Thread "main": pointer: 0x21e0002f70, stack: 0x3710000 >> "main" "root=/dev/sda1" "ro" "4" >> vbd 2049 is hd0 >> ******************* BLKFRONT for device/vbd/2049 ********** >> >> >> backend at /local/domain/0/backend/vbd/162/2049 >> Failed to read > /local/domain/0/backend/vbd/162/2049/feature-barrier. >> Failed to read /local/domain/0/backend/vbd/162/2049/feature-flush-cache. >> 20971520 sectors of 512 bytes >> ************************** >> vbd 2064 is hd1 >> ******************* BLKFRONT for device/vbd/2064 ********** >> >> >> backend at /local/domain/0/backend/vbd/162/2064 >> Failed to read /local/domain/0/backend/vbd/162/2064/feature-barrier. >> Failed to read /local/domain/0/backend/vbd/162/2064/feature-flush-cache. >> 880732160 sectors of 512 bytes >> ************************** >> vbd 2080 is hd2 >> ******************* BLKFRONT for device/vbd/2080 ********** >> >> >> backend at /local/domain/0/backend/vbd/162/2080 >> Failed to read /local/domain/0/backend/vbd/162/2080/feature-barrier. >> Failed to read /local/domain/0/backend/vbd/162/2080/feature-flush-cache. >> 880732160 sectors of 512 > bytes >> ************************** >> [H[J >> GNU GRUB version 0.97 (7864320K lower / 0K upper memory) >> >> [m[4;2H+-------------------------------------------------------------------------+[5;2H|[5;76H|[6;2H|[6;76H|[7;2H|[7;76H|[8;2H|[8;76H|[9;2H|[9;76H|[10;2H|[10;76H|[11;2H|[11;76H|[12;2H|[12;76H|[13;2H|[13;76H|[14;2H|[14;76H|[15;2H|[15;76H|[16;2H|[16;76H|[17;2H+-------------------------------------------------------------------------+[m >> Use the ^ and v keys to select which entry is highlighted. >> Press enter to boot the selected OS, 'e' to edit the >> commands before booting, or 'c' for a command-line.[5;78H [m[7m[5;3H CentOS (2.6.32-71.29.1.el6.x86_64) [5;75H[m[m[6;3H > [6;75H[m[m[7;3H [7;75H[m[m[8;3H [8;75H[m[m[9;3H > >> [9;75H[m[m[10;3H [10;75H[m[m[11;3H [11;75H[m[m[12;3H [12;75H[m[m[13;3H > [13;75H[m[m[14;3H >> [14;75H[m[m[15;3H [15;75H[m[m[16;3H > [16;75H[m[16;78H [5;75H[23;4H The highlighted entry will be booted automatically in 5 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 4 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 3 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 2 seconds. [5;75H[23;4H The highlighted entry will be booted automatically in 1 seconds. [5;75H[H[J Booting 'CentOS (2.6.32-71.29.1.el6.x86_64)' >> >> root (hd0) >> Filesystem type is ext2fs, using whole disk >> >> kernel /boot/vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=/dev/sda1 rhgb quiet >> initrd /boot/initramfs-2.6.32-71.29.1.el6.x86_64.img >> >> close blk: backend at /local/domain/0/backend/vbd/162/2049 >> close blk: > backend at /local/domain/0/backend/vbd/162/2064 >> close blk: backend at /local/domain/0/backend/vbd/162/2080 >> PCI: Warning: Cannot find a gap in the 32bit address range >> PCI: Unassigned devices with 32bit resource registers may break! >> PCI: Fatal: No config space access function found >> >> Boot has failed, sleeping forever. >> >> >> >> >> >> >> ________________________________ >> From: Robinson Tiemuqinke <hahaha_30k(a)yahoo.com> >> To: CentOS mailing list <centos(a)centos.org> >> Sent: Tuesday, November 22, 2011 3:35 PM >> Subject: [CentOS] EC2 compatible kernel for centos 6? >> >> Hi all, >> >> I'm just scrambling to collect clues to build an Amazon AWS > AMI based on Centos 6. the AWS PV-GRUB kernel loads my kernel but failed immediately. I'm using stock Centos 6 kernel 2.6.32-71.29.1.el6. and the kernel seems have xen? support? My questions are: >> >> 1, Are the centos 6 stock kernels, like kernel-2.6.32-71.29.1.el6.x86_64, EC2 compatible? >> >> 2, If the answer to the above #1 question is NO, the are the centos plus kernels, like kernel-2.6.32-71.29.1.el6.centos.plus.x86_64, EC2 compatible? >> >> 3, If the answers to both above are 'NO', then Are there any instructions to build a EC2 kernel based on kernel source RPMs? >> >> >> Any help are greatly appreciated. >> >> --Tie > > I do not use amazon services, but does this help: > > https://forums.aws.amazon.com/thread.jspa?threadID=78007 > > > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white(a)ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help!

13 years, 11 months

Re: [CentOS-es] Conexion Centos y SQL Server

by Luis T

Estimados, Estoy instalando nuevamente el CentOS de cero. Alguien me puede pasar link donde se explique como instalar los drivers de SQL Server 2014. Ya segui el tutorial de este link pero no funciono https://www.microsoft.com/en-us/download/details.aspx?id=20098. Ahora voy a probar con este tutorial https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-… . La idea es poder conectar los dos servidores usando un script PHP. Cualquier sugerencia es bienvenida, gracias. Saludos, Luis 2017-06-28 6:08 GMT-05:00 Elio Bastias, Project Managers < elio.bastias(a)gmail.com>: > Luis, > Buenos días, > > si bien desde la consola de CentOS tenes conectividad a la DB que esta en > un Windows, no tiene nada que ver, por que los parametros de configuración > del comando de línea es uno y los del script son otros, por ejemplo en el > script tenes que pasar un array asociativo mientra que en el comando de > línea no.- > > Así que te sugiero revises la configuración del php.ini si esta todo lo > necesario para soportar el conector de la db de MS SQL Server, y fíjate > también si esta configurado el acceso remoto a aplicaciones en este caso > del script.- y Te sugiero que pruebes con el poniendo el nombre del > servidor como se ve en windows y el nombre de la db como se ve en el > MSSQLServer.- > > Sin más, > Saluda Atte., > Eb > > El 27 de junio de 2017, 23:37, Luis T <reywes(a)gmail.com> escribió: > > > Estimados, > > > > Gracias por responder, voy revisar la información que me enviaron. Como > les > > digo tengo problemas en la conexión con el script de PHP y tengo > instalada > > la versión 7.1 nose si solo es compatible con la versión PHP 5.5. Lo que > si > > es que al momento de digitar en la consola de CentOS: *sqlcmd -S > > 172.10.10.50 -U user -P 123456* se conecta sin problemas y tengo acceso a > > las bases de datos del SQL Server y consultar datos de las tablas. Voy a > > seguir revisando para ver donde esta el problema. > > > > > > Saludos, > > > > Luis > > > > 2017-06-27 19:48 GMT-05:00 Aland Laines <aland.laines(a)gmail.com>: > > > > > Hola nuevamente, > > > > > > http://php.net/manual/es/sqlsrv.requirements.php > > > > > > aunque dice que tiene soporte en linux: > > > > > > https://docs.microsoft.com/en-us/sql/connect/php/system- > > > requirements-for-the-php-sql-driver#operating-systems > > > > > > anota que soporta estas distros > > > > > > > > > - Ubuntu 15.04 (64-bit) > > > - Ubuntu 16.04 (64-bit) > > > - Red Hat Enterprise Linux 7 (64-bit) > > > > > > debes de utilizar la version correctar del driver, en tu phpinfo: te > > > muestra el driver sqlsrv instalado? > > > > > > > > > Saludos.. > > > > > > > > > > > > > > > El 27 de junio de 2017, 18:21, Elio Bastias, Project Managers < > > > elio.bastias(a)gmail.com> escribió: > > > > > > > Buenas tardes, Luis, > > > > Mira con respecto al error, lo que rescato es "Login timeout", lo que > > > > parece que ni encuentra la db, lo que intentaría sería colocar el > data > > > > source name (dsn), como lo recomienda el sitio ( > > > > https://docs.microsoft.com/en-us/sql/connect/php/connection-options > ), > > lo > > > > importante también es que si se instalo bien el driver ( > > > > https://www.microsoft.com/download/details.aspx?id=20098) y saber > > bien > > > la > > > > versión que tenes instalada de PHP, lo que te recomendaría sería ir a > > > PDO, > > > > ya que te permite tener una capa de abstracción de las DB, y no > > > preocuparte > > > > cuando manejes diferentes tipos de DB ó migres a otro.- > > > > También tene en cuenta la sintaxis que te da php: > > > > <?php > > > > $serverName = "serverName\sqlexpress"; //serverName\instanceName > > > > $connectionInfo = array( "Database"=>"dbName", "UID"=>"userName", > > "PWD"=> > > > > "password"); > > > > $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > > > > if( $conn ) { > > > > echo "Conexión establecida.<br />"; > > > > }else{ > > > > echo "Conexión no se pudo establecer.<br />"; > > > > die( print_r( sqlsrv_errors(), true)); > > > > } > > > > ?> > > > > ya que en $serverName, te pide el nombre del servidor y no una IP, > por > > > > ejemplo por hay no esta resolviendo la IP con el nombre de la Db, ya > > que > > > > por lo que entiendo vos estas en un CentOS y la DB en un windows así > > que > > > > puede llegar a ser ese el problema, para decirte me apoyo en el > mensaje > > > de > > > > error "Server is not found or not accessible. Check if instance name > is > > > > correct and if SQL Server is configured to allow remote connections" > > > > > > > > Espero haberte dado una mano, y sino comenta como lo solucionaste > para > > > que > > > > otros lo puedan tener en cuenta.- > > > > Saludos > > > > > > > > > > > > El 27 de junio de 2017, 18:24, Luis T <reywes(a)gmail.com> escribió: > > > > > > > > > Estimado Aland, > > > > > > > > > > Gracias por responder, he instalado algunas librerias para ver si > > > > funciona. > > > > > El escenario que tengo es por un lado el Server SQL 2014 y por otro > > el > > > > > CentOS 7.3 con PHP 7.1 necesito conectarme desde CentOS a la base > de > > > > datos > > > > > de SQL Server. Probe la conexion remota hacia el SQL Server y > > funciona > > > OK > > > > > desde otro Windows. Hice una prueba desde Centos hacia Windows > Server > > > con > > > > > el comando sqlcmd -S <IP> -U <USUARIO> -P <PASSWORD> y se conecta > sin > > > > > problema incluso puedo consultar datos de las tablas. Me presenta > el > > > > > siguiente error: > > > > > > > > > > Conexión no se pudo establecer. > > > > > Array ( [0] => Array ( [0] => HYT00 [SQLSTATE] => HYT00 [1] => 0 > > [code] > > > > => > > > > > 0 [2] => [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]Login > > > > timeout > > > > > expired [message] => [unixODBC][Microsoft][ODBC Driver 13 for SQL > > > > > Server]Login timeout expired ) [1] => Array ( [0] => 08001 > [SQLSTATE] > > > => > > > > > 08001 [1] => 10013 [code] => 10013 [2] => > [unixODBC][Microsoft][ODBC > > > > Driver > > > > > 13 for SQL Server]TCP Provider: Error code 0x271D [message] => > > > > > [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]TCP Provider: > > Error > > > > > code 0x271D ) [2] => Array ( [0] => 08001 [SQLSTATE] => 08001 [1] > => > > > > 10013 > > > > > [code] => 10013 [2] => [unixODBC][Microsoft][ODBC Driver 13 for SQL > > > > > Server]A network-related or instance-specific error has occurred > > while > > > > > establishing a connection to SQL Server. Server is not found or not > > > > > accessible. Check if instance name is correct and if SQL Server is > > > > > configured to allow remote connections. For more information see > SQL > > > > Server > > > > > Books Online. [message] => [unixODBC][Microsoft][ODBC Driver 13 for > > SQL > > > > > Server]A network-related or instance-specific error has occurred > > while > > > > > establishing a connection to SQL Server. Server is not found or not > > > > > accessible. Check if instance name is correct and if SQL Server is > > > > > configured to allow remote connections. For more information see > SQL > > > > Server > > > > > Books Online. ) ) > > > > > > > > > > La conexion PHP que tengo es: > > > > > > > > > > <?php > > > > > $serverName = "172.10.10.50"; //serverName\instanceName > > > > > $connectionInfo = array( "Database"=>"TEST", "UID"=>"user", > > > > > "PWD"=>"123456"); > > > > > $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > > > > > > if( $conn ) { > > > > > echo "Conexión establecida.<br />"; > > > > > }else{ > > > > > echo "Conexión no se pudo establecer.<br />"; > > > > > die( print_r( sqlsrv_errors(), true)); > > > > > } > > > > > ?> > > > > > > > > > > Esto se puede deber algun error de sintaxis en el sqlsrv_connect?? > > > > > > > > > > > > > > > Saludos, > > > > > > > > > > Luis > > > > > > > > > > > > > > > > > > > > 2017-06-27 12:26 GMT-05:00 Aland Laines <aland.laines(a)gmail.com>: > > > > > > > > > > > Hola Ojo que estas con dos cosas distintas.. has instalado mssql, > > > pero > > > > > > quieres usar sqlsrv_connect, lo cual esta mal, lo correcto es > usar > > > > > > http://php.net/manual/es/function.mssql-connect.php, otra cosa > > > revisa > > > > la > > > > > > version de php que estas usando en el servidor en algunas tiene > > > > problemas > > > > > > de compatibilidad y en otras esta deprecated. > > > > > > > > > > > > Un abrazo.. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > El 23 de junio de 2017, 16:30, Efraín Déctor < > > > > efraindector(a)motumweb.com> > > > > > > escribió: > > > > > > > > > > > > > Que raro. > > > > > > > > > > > > > > Checa esta respuesta: https://stackoverflow.com/a/43687495 > > > > > > > > > > > > > > > > > > > > > El 23/06/2017 a las 04:20 p. m., Luis T escribió: > > > > > > > > > > > > > >> Hola Efraín, > > > > > > >> > > > > > > >> Si realice la instalacion de php-mssql. de hecho en CentOS me > > > > aparece > > > > > > >> esto: > > > > > > >> > > > > > > >> Inline image 1 > > > > > > >> > > > > > > >> Nose si es un error en la sintaxis del sqlsrv_connect aunque > ya > > he > > > > > > >> probado varios ejemplos que estan en la web y no doy con el > > error. > > > > > Nose > > > > > > que > > > > > > >> pueda estar afectando la conexion. > > > > > > >> > > > > > > >> > > > > > > >> Saludos, > > > > > > >> > > > > > > >> Luis > > > > > > >> > > > > > > >> 2017-06-23 16:11 GMT-05:00 Efraín Déctor < > > > efraindector(a)motumweb.com > > > > > > >> <mailto:efraindector@motumweb.com>>: > > > > > > >> > > > > > > >> > > > > > > >> Hola. > > > > > > >> > > > > > > >> Seguro que instalaste php-mssql (yum install php-mssql) ? > > > > > > >> > > > > > > >> Saludos > > > > > > >> > > > > > > >> > > > > > > >> El 23/06/2017 a las 03:13 p. m., Luis T escribió: > > > > > > >> > > > > > > >>> Hola Efraín, > > > > > > >>> > > > > > > >>> Gracias por tu respuesta, sabes que sigue todos los pasos > > > pero > > > > no > > > > > > >>> me permite conectar la base SQL. Habilite la conexion > > remota > > > > del > > > > > > >>> SQL, desactive firewall. Probe con las tres opciones de > > > > conexion > > > > > > >>> pero nada, por telnet si se establece la conexion. Este > > > momento > > > > > > >>> estoy usando esto: > > > > > > >>> > > > > > > >>> <?php > > > > > > >>> $serverName = "172.10.10.50\SQL2014, 1433"; > > > > > > >>> //serverName\instanceName, portNumber (default is 1433) > > > > > > >>> $connectionInfo = array( "Database"=>"PRUEBA", > > > "UID"=>"user1", > > > > > > >>> "PWD"=>"123456"); > > > > > > >>> $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > > >>> > > > > > > >>> if( $conn ) { > > > > > > >>> echo "Connection established.<br />"; > > > > > > >>> }else{ > > > > > > >>> echo "Connection could not be established.<br />"; > > > > > > >>> die( print_r( sqlsrv_errors(), true)); > > > > > > >>> } > > > > > > >>> ?> > > > > > > >>> > > > > > > >>> Revise los logs y me aparece esto: > > > > > > >>> > > > > > > >>> PHP Fatal error: Call to undefined function > > sqlsrv_connect() > > > > in > > > > > > >>> /var/www/html/prueba.php on line 4 > > > > > > >>> > > > > > > >>> Toda la configuracion la realice tal como esta en el > > > tutorial, > > > > > > >>> nose si hay algun error de sintaxis o es necesario > > habilitar > > > > algo > > > > > > >>> en Windows o Centos. > > > > > > >>> > > > > > > >>> Cualquier ayuda de antemano gracias. > > > > > > >>> > > > > > > >>> > > > > > > >>> Saludos, > > > > > > >>> > > > > > > >>> Luis > > > > > > >>> > > > > > > >>> > > > > > > >>> 2017-06-22 14:43 GMT-05:00 Efraín Déctor > > > > > > >>> <efraindector(a)motumweb.com <mailto:efraindector@motumweb > . > > com > > > > >>: > > > > > > >>> > > > > > > >>> Que tal. > > > > > > >>> > > > > > > >>> Primero que nada en Centos necesitas instalar > php-mssql > > > que > > > > > > >>> está en el repositorio EPEL. > > > > > > >>> > > > > > > >>> Para la conexion en PHP sigue la documentación > oficial: > > > > > > >>> http://php.net/manual/es/function.sqlsrv-connect.php > > > > > > >>> <http://php.net/manual/es/ > function.sqlsrv-connect.php> > > > > > > >>> > > > > > > >>> > > > > > > >>> Saludos > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> El 22/06/2017 a las 02:36 p. m., Luis T escribió: > > > > > > >>> > > > > > > >>> Estimados, > > > > > > >>> > > > > > > >>> Tengo desarrollado una aplicacion PHP en un > Centos > > 7 > > > y > > > > > > >>> necesito conectarlo > > > > > > >>> a un servidor SQL Server donde tengo una base de > > > datos, > > > > > > >>> para poder > > > > > > >>> almacenar ahi la informacion. He buscando en > > internet > > > > > > >>> informacion pero > > > > > > >>> todavia no lo tengo bien claro. Alguien que me > > pueda > > > > > > >>> indicar cual es la > > > > > > >>> mejor forma para realizar esto, de antemano > > agradezco > > > > sus > > > > > > >>> respuestas, > > > > > > >>> gracias. > > > > > > >>> > > > > > > >>> > > > > > > >>> Saludos, > > > > > > >>> > > > > > > >>> Luis > > > > > > >>> _______________________________________________ > > > > > > >>> CentOS-es mailing list > > > > > > >>> CentOS-es(a)centos.org <mailto: > CentOS-es(a)centos.org> > > > > > > >>> https://lists.centos.org/ > > mailman/listinfo/centos-es > > > > > > >>> <https://lists.centos.org/ > > mailman/listinfo/centos-es > > > > > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >>> > > > > > > >> > > > > > > >> > > > > > > > _______________________________________________ > > > > > > > CentOS-es mailing list > > > > > > > CentOS-es(a)centos.org > > > > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > _______________________________________________ > > > > > > CentOS-es mailing list > > > > > > CentOS-es(a)centos.org > > > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > _______________________________________________ > > > > > CentOS-es mailing list > > > > > CentOS-es(a)centos.org > > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > > > > > > > -- > > > > Elio Bastias > > > > Project Manager > > > > Smart - IT > > > > |Open Source Innovation | Open Source Communications > > > > Estrategia y Management en Comunicaciones e Infraestructurade IT > > > > > > > > |Gtalk/Mail: consultor(a)eliobastias.com.ar > > > > > > > > |Soporte & Mantenimiento ->http://goo.gl/BEvg73 > > > > > > > > |----------------------------------------------------------- > > > > ------------------------------------- > > > > Los precios cotizados por el equipamiento están expresados en Dólares > > > > Estadounidenses e incluyen todos los impuestos vigentes que gravan > este > > > > tipo de operaciones, excepto el Impuesto al Valor Agregado (I.V.A.) > > que, > > > en > > > > caso de corresponder, será adicionado en el porcentaje que establezca > > la > > > > ley al momento de realizar la facturación. Los precios resultantes de > > la > > > > presente serán pagaderos en dólares estadounidenses billete o en su > > > defecto > > > > en pesos, según cotización del dólar libre tipo vendedor del Banco de > > la > > > > Nación Argentina del día inmediato anterior al de efectivo pago. > > > > Referencia: www.bna.com.ar > > > > |----------------------------------------------------------- > > > > ------------------------------------- > > > > Este mensaje y, en su caso, sus archivos adjuntos, son informaión > > > > confidencial enviada para uso exclusivo de su destinatario. Está > > > > terminantemente prohibida la lectura, copia, duplicado o reenvío de > > esta > > > > información por parte de cualquier persona distinta del destinatario. > > Si > > > > usted ha recibido este mensaje por error, por favor elimínelo e > informe > > > de > > > > inmediato a su remitente. > > > > |----------------------------------------------------------- > > > > ------------------------------------- > > > > Antes de imprimir, pensá en tu responsabilidad y compromiso con el > > MEDIO > > > > AMBIENTE.- > > > > _______________________________________________ > > > > CentOS-es mailing list > > > > CentOS-es(a)centos.org > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > _______________________________________________ > > > CentOS-es mailing list > > > CentOS-es(a)centos.org > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > _______________________________________________ > > CentOS-es mailing list > > CentOS-es(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos-es > > > _______________________________________________ > CentOS-es mailing list > CentOS-es(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-es >

8 years, 9 months

Re: [CentOS-es] Conexion Centos y SQL Server

by Elio Bastias, Project Managers

Luis, Buenos días, si bien desde la consola de CentOS tenes conectividad a la DB que esta en un Windows, no tiene nada que ver, por que los parametros de configuración del comando de línea es uno y los del script son otros, por ejemplo en el script tenes que pasar un array asociativo mientra que en el comando de línea no.- Así que te sugiero revises la configuración del php.ini si esta todo lo necesario para soportar el conector de la db de MS SQL Server, y fíjate también si esta configurado el acceso remoto a aplicaciones en este caso del script.- y Te sugiero que pruebes con el poniendo el nombre del servidor como se ve en windows y el nombre de la db como se ve en el MSSQLServer.- Sin más, Saluda Atte., Eb El 27 de junio de 2017, 23:37, Luis T <reywes(a)gmail.com> escribió: > Estimados, > > Gracias por responder, voy revisar la información que me enviaron. Como les > digo tengo problemas en la conexión con el script de PHP y tengo instalada > la versión 7.1 nose si solo es compatible con la versión PHP 5.5. Lo que si > es que al momento de digitar en la consola de CentOS: *sqlcmd -S > 172.10.10.50 -U user -P 123456* se conecta sin problemas y tengo acceso a > las bases de datos del SQL Server y consultar datos de las tablas. Voy a > seguir revisando para ver donde esta el problema. > > > Saludos, > > Luis > > 2017-06-27 19:48 GMT-05:00 Aland Laines <aland.laines(a)gmail.com>: > > > Hola nuevamente, > > > > http://php.net/manual/es/sqlsrv.requirements.php > > > > aunque dice que tiene soporte en linux: > > > > https://docs.microsoft.com/en-us/sql/connect/php/system- > > requirements-for-the-php-sql-driver#operating-systems > > > > anota que soporta estas distros > > > > > > - Ubuntu 15.04 (64-bit) > > - Ubuntu 16.04 (64-bit) > > - Red Hat Enterprise Linux 7 (64-bit) > > > > debes de utilizar la version correctar del driver, en tu phpinfo: te > > muestra el driver sqlsrv instalado? > > > > > > Saludos.. > > > > > > > > > > El 27 de junio de 2017, 18:21, Elio Bastias, Project Managers < > > elio.bastias(a)gmail.com> escribió: > > > > > Buenas tardes, Luis, > > > Mira con respecto al error, lo que rescato es "Login timeout", lo que > > > parece que ni encuentra la db, lo que intentaría sería colocar el data > > > source name (dsn), como lo recomienda el sitio ( > > > https://docs.microsoft.com/en-us/sql/connect/php/connection-options) > lo > > > importante también es que si se instalo bien el driver ( > > > https://www.microsoft.com/download/details.aspx?id=20098) y saber > bien > > la > > > versión que tenes instalada de PHP, lo que te recomendaría sería ir a > > PDO, > > > ya que te permite tener una capa de abstracción de las DB, y no > > preocuparte > > > cuando manejes diferentes tipos de DB ó migres a otro.- > > > También tene en cuenta la sintaxis que te da php: > > > <?php > > > $serverName = "serverName\sqlexpress"; //serverName\instanceName > > > $connectionInfo = array( "Database"=>"dbName", "UID"=>"userName", > "PWD"=> > > > "password"); > > > $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > > if( $conn ) { > > > echo "Conexión establecida.<br />"; > > > }else{ > > > echo "Conexión no se pudo establecer.<br />"; > > > die( print_r( sqlsrv_errors(), true)); > > > } > > > ?> > > > ya que en $serverName, te pide el nombre del servidor y no una IP, por > > > ejemplo por hay no esta resolviendo la IP con el nombre de la Db, ya > que > > > por lo que entiendo vos estas en un CentOS y la DB en un windows así > que > > > puede llegar a ser ese el problema, para decirte me apoyo en el mensaje > > de > > > error "Server is not found or not accessible. Check if instance name is > > > correct and if SQL Server is configured to allow remote connections" > > > > > > Espero haberte dado una mano, y sino comenta como lo solucionaste para > > que > > > otros lo puedan tener en cuenta.- > > > Saludos > > > > > > > > > El 27 de junio de 2017, 18:24, Luis T <reywes(a)gmail.com> escribió: > > > > > > > Estimado Aland, > > > > > > > > Gracias por responder, he instalado algunas librerias para ver si > > > funciona. > > > > El escenario que tengo es por un lado el Server SQL 2014 y por otro > el > > > > CentOS 7.3 con PHP 7.1 necesito conectarme desde CentOS a la base de > > > datos > > > > de SQL Server. Probe la conexion remota hacia el SQL Server y > funciona > > OK > > > > desde otro Windows. Hice una prueba desde Centos hacia Windows Server > > con > > > > el comando sqlcmd -S <IP> -U <USUARIO> -P <PASSWORD> y se conecta sin > > > > problema incluso puedo consultar datos de las tablas. Me presenta el > > > > siguiente error: > > > > > > > > Conexión no se pudo establecer. > > > > Array ( [0] => Array ( [0] => HYT00 [SQLSTATE] => HYT00 [1] => 0 > [code] > > > => > > > > 0 [2] => [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]Login > > > timeout > > > > expired [message] => [unixODBC][Microsoft][ODBC Driver 13 for SQL > > > > Server]Login timeout expired ) [1] => Array ( [0] => 08001 [SQLSTATE] > > => > > > > 08001 [1] => 10013 [code] => 10013 [2] => [unixODBC][Microsoft][ODBC > > > Driver > > > > 13 for SQL Server]TCP Provider: Error code 0x271D [message] => > > > > [unixODBC][Microsoft][ODBC Driver 13 for SQL Server]TCP Provider: > Error > > > > code 0x271D ) [2] => Array ( [0] => 08001 [SQLSTATE] => 08001 [1] => > > > 10013 > > > > [code] => 10013 [2] => [unixODBC][Microsoft][ODBC Driver 13 for SQL > > > > Server]A network-related or instance-specific error has occurred > while > > > > establishing a connection to SQL Server. Server is not found or not > > > > accessible. Check if instance name is correct and if SQL Server is > > > > configured to allow remote connections. For more information see SQL > > > Server > > > > Books Online. [message] => [unixODBC][Microsoft][ODBC Driver 13 for > SQL > > > > Server]A network-related or instance-specific error has occurred > while > > > > establishing a connection to SQL Server. Server is not found or not > > > > accessible. Check if instance name is correct and if SQL Server is > > > > configured to allow remote connections. For more information see SQL > > > Server > > > > Books Online. ) ) > > > > > > > > La conexion PHP que tengo es: > > > > > > > > <?php > > > > $serverName = "172.10.10.50"; //serverName\instanceName > > > > $connectionInfo = array( "Database"=>"TEST", "UID"=>"user", > > > > "PWD"=>"123456"); > > > > $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > > > > if( $conn ) { > > > > echo "Conexión establecida.<br />"; > > > > }else{ > > > > echo "Conexión no se pudo establecer.<br />"; > > > > die( print_r( sqlsrv_errors(), true)); > > > > } > > > > ?> > > > > > > > > Esto se puede deber algun error de sintaxis en el sqlsrv_connect?? > > > > > > > > > > > > Saludos, > > > > > > > > Luis > > > > > > > > > > > > > > > > 2017-06-27 12:26 GMT-05:00 Aland Laines <aland.laines(a)gmail.com>: > > > > > > > > > Hola Ojo que estas con dos cosas distintas.. has instalado mssql, > > pero > > > > > quieres usar sqlsrv_connect, lo cual esta mal, lo correcto es usar > > > > > http://php.net/manual/es/function.mssql-connect.php, otra cosa > > revisa > > > la > > > > > version de php que estas usando en el servidor en algunas tiene > > > problemas > > > > > de compatibilidad y en otras esta deprecated. > > > > > > > > > > Un abrazo.. > > > > > > > > > > > > > > > > > > > > > > > > > El 23 de junio de 2017, 16:30, Efraín Déctor < > > > efraindector(a)motumweb.com> > > > > > escribió: > > > > > > > > > > > Que raro. > > > > > > > > > > > > Checa esta respuesta: https://stackoverflow.com/a/43687495 > > > > > > > > > > > > > > > > > > El 23/06/2017 a las 04:20 p. m., Luis T escribió: > > > > > > > > > > > >> Hola Efraín, > > > > > >> > > > > > >> Si realice la instalacion de php-mssql. de hecho en CentOS me > > > aparece > > > > > >> esto: > > > > > >> > > > > > >> Inline image 1 > > > > > >> > > > > > >> Nose si es un error en la sintaxis del sqlsrv_connect aunque ya > he > > > > > >> probado varios ejemplos que estan en la web y no doy con el > error. > > > > Nose > > > > > que > > > > > >> pueda estar afectando la conexion. > > > > > >> > > > > > >> > > > > > >> Saludos, > > > > > >> > > > > > >> Luis > > > > > >> > > > > > >> 2017-06-23 16:11 GMT-05:00 Efraín Déctor < > > efraindector(a)motumweb.com > > > > > >> <mailto:efraindector@motumweb.com>>: > > > > > >> > > > > > >> > > > > > >> Hola. > > > > > >> > > > > > >> Seguro que instalaste php-mssql (yum install php-mssql) ? > > > > > >> > > > > > >> Saludos > > > > > >> > > > > > >> > > > > > >> El 23/06/2017 a las 03:13 p. m., Luis T escribió: > > > > > >> > > > > > >>> Hola Efraín, > > > > > >>> > > > > > >>> Gracias por tu respuesta, sabes que sigue todos los pasos > > pero > > > no > > > > > >>> me permite conectar la base SQL. Habilite la conexion > remota > > > del > > > > > >>> SQL, desactive firewall. Probe con las tres opciones de > > > conexion > > > > > >>> pero nada, por telnet si se establece la conexion. Este > > momento > > > > > >>> estoy usando esto: > > > > > >>> > > > > > >>> <?php > > > > > >>> $serverName = "172.10.10.50\SQL2014, 1433"; > > > > > >>> //serverName\instanceName, portNumber (default is 1433) > > > > > >>> $connectionInfo = array( "Database"=>"PRUEBA", > > "UID"=>"user1", > > > > > >>> "PWD"=>"123456"); > > > > > >>> $conn = sqlsrv_connect( $serverName, $connectionInfo); > > > > > >>> > > > > > >>> if( $conn ) { > > > > > >>> echo "Connection established.<br />"; > > > > > >>> }else{ > > > > > >>> echo "Connection could not be established.<br />"; > > > > > >>> die( print_r( sqlsrv_errors(), true)); > > > > > >>> } > > > > > >>> ?> > > > > > >>> > > > > > >>> Revise los logs y me aparece esto: > > > > > >>> > > > > > >>> PHP Fatal error: Call to undefined function > sqlsrv_connect() > > > in > > > > > >>> /var/www/html/prueba.php on line 4 > > > > > >>> > > > > > >>> Toda la configuracion la realice tal como esta en el > > tutorial, > > > > > >>> nose si hay algun error de sintaxis o es necesario > habilitar > > > algo > > > > > >>> en Windows o Centos. > > > > > >>> > > > > > >>> Cualquier ayuda de antemano gracias. > > > > > >>> > > > > > >>> > > > > > >>> Saludos, > > > > > >>> > > > > > >>> Luis > > > > > >>> > > > > > >>> > > > > > >>> 2017-06-22 14:43 GMT-05:00 Efraín Déctor > > > > > >>> <efraindector(a)motumweb.com <mailto:efraindector@motumweb. > com > > > >>: > > > > > >>> > > > > > >>> Que tal. > > > > > >>> > > > > > >>> Primero que nada en Centos necesitas instalar php-mssql > > que > > > > > >>> está en el repositorio EPEL. > > > > > >>> > > > > > >>> Para la conexion en PHP sigue la documentación oficial: > > > > > >>> http://php.net/manual/es/function.sqlsrv-connect.php > > > > > >>> <http://php.net/manual/es/function.sqlsrv-connect.php> > > > > > >>> > > > > > >>> > > > > > >>> Saludos > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> El 22/06/2017 a las 02:36 p. m., Luis T escribió: > > > > > >>> > > > > > >>> Estimados, > > > > > >>> > > > > > >>> Tengo desarrollado una aplicacion PHP en un Centos > 7 > > y > > > > > >>> necesito conectarlo > > > > > >>> a un servidor SQL Server donde tengo una base de > > datos, > > > > > >>> para poder > > > > > >>> almacenar ahi la informacion. He buscando en > internet > > > > > >>> informacion pero > > > > > >>> todavia no lo tengo bien claro. Alguien que me > pueda > > > > > >>> indicar cual es la > > > > > >>> mejor forma para realizar esto, de antemano > agradezco > > > sus > > > > > >>> respuestas, > > > > > >>> gracias. > > > > > >>> > > > > > >>> > > > > > >>> Saludos, > > > > > >>> > > > > > >>> Luis > > > > > >>> _______________________________________________ > > > > > >>> CentOS-es mailing list > > > > > >>> CentOS-es(a)centos.org <mailto:CentOS-es@centos.org> > > > > > >>> https://lists.centos.org/ > mailman/listinfo/centos-es > > > > > >>> <https://lists.centos.org/ > mailman/listinfo/centos-es > > > > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >>> > > > > > >> > > > > > >> > > > > > > _______________________________________________ > > > > > > CentOS-es mailing list > > > > > > CentOS-es(a)centos.org > > > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > _______________________________________________ > > > > > CentOS-es mailing list > > > > > CentOS-es(a)centos.org > > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > _______________________________________________ > > > > CentOS-es mailing list > > > > CentOS-es(a)centos.org > > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > > > > > > > > > > > > -- > > > Elio Bastias > > > Project Manager > > > Smart - IT > > > |Open Source Innovation | Open Source Communications > > > Estrategia y Management en Comunicaciones e Infraestructurade IT > > > > > > |Gtalk/Mail: consultor(a)eliobastias.com.ar > > > > > > |Soporte & Mantenimiento ->http://goo.gl/BEvg73 > > > > > > |----------------------------------------------------------- > > > ------------------------------------- > > > Los precios cotizados por el equipamiento están expresados en Dólares > > > Estadounidenses e incluyen todos los impuestos vigentes que gravan este > > > tipo de operaciones, excepto el Impuesto al Valor Agregado (I.V.A.) > que, > > en > > > caso de corresponder, será adicionado en el porcentaje que establezca > la > > > ley al momento de realizar la facturación. Los precios resultantes de > la > > > presente serán pagaderos en dólares estadounidenses billete o en su > > defecto > > > en pesos, según cotización del dólar libre tipo vendedor del Banco de > la > > > Nación Argentina del día inmediato anterior al de efectivo pago. > > > Referencia: www.bna.com.ar > > > |----------------------------------------------------------- > > > ------------------------------------- > > > Este mensaje y, en su caso, sus archivos adjuntos, son informaión > > > confidencial enviada para uso exclusivo de su destinatario. Está > > > terminantemente prohibida la lectura, copia, duplicado o reenvío de > esta > > > información por parte de cualquier persona distinta del destinatario. > Si > > > usted ha recibido este mensaje por error, por favor elimínelo e informe > > de > > > inmediato a su remitente. > > > |----------------------------------------------------------- > > > ------------------------------------- > > > Antes de imprimir, pensá en tu responsabilidad y compromiso con el > MEDIO > > > AMBIENTE.- > > > _______________________________________________ > > > CentOS-es mailing list > > > CentOS-es(a)centos.org > > > https://lists.centos.org/mailman/listinfo/centos-es > > > > > _______________________________________________ > > CentOS-es mailing list > > CentOS-es(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos-es > > > _______________________________________________ > CentOS-es mailing list > CentOS-es(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-es >

8 years, 9 months

[Arm-dev] reset network kills network

by david

Folks I'm playing with a Raspberry Pi 2 and Centos. Here are some issues I've bumped into. I'm not sure this is the right medium for commenting; please correct me if needed. I wrote a copy of the distributed image (1151) to my MicroSD card, then turned on the Rpi2. Issue 1: Even though my DHCP server was configured to give the node a name, it showed up as "rpi2" as the host name. Issue 2: Network works, but if I issue the command systemctl reset network the command fails and I haven't found a way to get the network back. I saved the output of "journalctl -ce", rebooted, and installed "ftp" so I could copy the data to a real machine. The text is as below. I issued the "systemctl reset network" command towards the bottom, where you see the time jump from 00:01:01 to 00:02:28 -------------------------------------------------------------- -- Logs begin at Thu 1970-01-01 00:00:04 UTC, end at Thu 1970-01-01 00:02:28 UTC. -- Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using 5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M available ? current limit 46.3M). Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using 5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M available ? current limit 46.3M). Jan 01 00:00:04 rpi2 kernel: Booting Linux on physical CPU 0xf00 Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpuset Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpu Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys cpuacct Jan 01 00:00:04 rpi2 kernel: Linux version 4.1.11-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.8.3 20140303 (prerelease) (crosstool-NG linaro-1.13.1+bzr2650 - Linaro GCC 2014.03) ) #822 SMP PREEMPT Fri Oct 23 16:22:18 BST 2015 Jan 01 00:00:04 rpi2 kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d Jan 01 00:00:04 rpi2 kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Jan 01 00:00:04 rpi2 kernel: Machine: BCM2709 Jan 01 00:00:04 rpi2 kernel: cma: Reserved 8 MiB at 0x3a800000 Jan 01 00:00:04 rpi2 kernel: Memory policy: Data cache writealloc Jan 01 00:00:04 rpi2 kernel: On node 0 totalpages: 241664 Jan 01 00:00:04 rpi2 kernel: free_area_init_node: node 0, pgdat 80859000, node_mem_map b9fa6000 Jan 01 00:00:04 rpi2 kernel: Normal zone: 2124 pages used for memmap Jan 01 00:00:04 rpi2 kernel: Normal zone: 0 pages reserved Jan 01 00:00:04 rpi2 kernel: Normal zone: 241664 pages, LIFO batch:31 Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_init_cpus] enter (9420->f3003010) Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_init_cpus] ncores=4 Jan 01 00:00:04 rpi2 kernel: PERCPU: Embedded 13 pages/cpu @b9f6d000 s20608 r8192 d24448 u53248 Jan 01 00:00:04 rpi2 kernel: pcpu-alloc: s20608 r8192 d24448 u53248 alloc=13*4096 Jan 01 00:00:04 rpi2 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Jan 01 00:00:04 rpi2 kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 239540 Jan 01 00:00:04 rpi2 kernel: Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1872 bcm2708_fb.fbheight=1168 bcm2709.boardrev=0xa21041 bcm2709.serial=0x72e14965 smsc95xx.macaddr=B8:27:EB:E1:49:65 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 elevator=deadline rootwait Jan 01 00:00:04 rpi2 kernel: PID hash table entries: 4096 (order: 2, 16384 bytes) Jan 01 00:00:04 rpi2 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Jan 01 00:00:04 rpi2 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Jan 01 00:00:04 rpi2 kernel: Memory: 939572K/966656K available (5955K kernel code, 534K rwdata, 1644K rodata, 416K init, 757K bss, 18892K reserved, 8192K cma-reserved) Jan 01 00:00:04 rpi2 kernel: Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xbb800000 - 0xff000000 (1080 MB) lowmem : 0x80000000 - 0xbb000000 ( 944 MB) modules : 0x7f000000 - 0x80000000 ( 16 MB) .text : 0x80008000 - 0x80773e88 (7600 kB) .init : 0x80774000 - 0x807dc000 ( 416 kB) .data : 0x807dc000 - 0x80861b6c ( 535 kB) .bss : 0x80864000 - 0x8092179c ( 758 kB) Jan 01 00:00:04 rpi2 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Jan 01 00:00:04 rpi2 kernel: Preemptible hierarchical RCU implementation. Jan 01 00:00:04 rpi2 kernel: Additional per-CPU info printed with stalls. Jan 01 00:00:04 rpi2 kernel: NR_IRQS:608 Jan 01 00:00:04 rpi2 kernel: Architected cp15 timer(s) running at 19.20MHz (phys). Jan 01 00:00:04 rpi2 kernel: clocksource arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns Jan 01 00:00:04 rpi2 kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns Jan 01 00:00:04 rpi2 kernel: Switching to timer-based delay loop, resolution 52ns Jan 01 00:00:04 rpi2 kernel: Console: colour dummy device 80x30 Jan 01 00:00:04 rpi2 kernel: console [tty1] enabled Jan 01 00:00:04 rpi2 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) Jan 01 00:00:04 rpi2 kernel: pid_max: default: 32768 minimum: 301 Jan 01 00:00:04 rpi2 kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Jan 01 00:00:04 rpi2 kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys blkio Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys memory Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys devices Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys freezer Jan 01 00:00:04 rpi2 kernel: Initializing cgroup subsys net_cls Jan 01 00:00:04 rpi2 kernel: CPU: Testing write buffer coherency: ok Jan 01 00:00:04 rpi2 kernel: ftrace: allocating 20224 entries in 60 pages Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 0 Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 1 Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 2 Jan 01 00:00:04 rpi2 kernel: missing device node for CPU 3 Jan 01 00:00:04 rpi2 kernel: CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00 Jan 01 00:00:04 rpi2 kernel: [bcm2709_smp_prepare_cpus] enter Jan 01 00:00:04 rpi2 kernel: Setting up static identity map for 0x8240 - 0x8274 Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:1 started (0) 16 Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:1 Jan 01 00:00:04 rpi2 kernel: CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01 Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:2 started (0) 18 Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:2 Jan 01 00:00:04 rpi2 kernel: CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02 Jan 01 00:00:04 rpi2 kernel: [bcm2709_boot_secondary] cpu:3 started (0) 18 Jan 01 00:00:04 rpi2 kernel: [bcm2709_secondary_init] enter cpu:3 Jan 01 00:00:04 rpi2 kernel: CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03 Jan 01 00:00:04 rpi2 kernel: Brought up 4 CPUs Jan 01 00:00:04 rpi2 kernel: SMP: Total of 4 processors activated (153.60 BogoMIPS). Jan 01 00:00:04 rpi2 kernel: CPU: All CPU(s) started in HYP mode. Jan 01 00:00:04 rpi2 kernel: CPU: Virtualization extensions available. Jan 01 00:00:04 rpi2 kernel: devtmpfs: initialized Jan 01 00:00:04 rpi2 kernel: VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 Jan 01 00:00:04 rpi2 kernel: clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Jan 01 00:00:04 rpi2 kernel: pinctrl core: initialized pinctrl subsystem Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 16 Jan 01 00:00:04 rpi2 kernel: DMA: preallocated 4096 KiB pool for atomic coherent allocations Jan 01 00:00:04 rpi2 kernel: bcm2709.uart_clock = 3000000 Jan 01 00:00:04 rpi2 kernel: of_platform_populate failed: -22 Jan 01 00:00:04 rpi2 kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. Jan 01 00:00:04 rpi2 kernel: hw-breakpoint: maximum watchpoint size is 8 bytes. Jan 01 00:00:04 rpi2 kernel: Serial: AMBA PL011 UART driver Jan 01 00:00:04 rpi2 kernel: dev:f1: ttyAMA0 at MMIO 0x3f201000 (irq = 83, base_baud = 0) is a PL011 rev3 Jan 01 00:00:04 rpi2 kernel: console [ttyAMA0] enabled Jan 01 00:00:04 rpi2 kernel: bcm2835-mbox bcm2835-mbox: mailbox enabled Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: DMA legacy API manager at f3007000, dmachans=0x7f35 Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: failed to get irq for DMA channel 13 Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: Initialized 8 DMA channels (+ 1 legacy) Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: Load BCM2835 DMA engine driver Jan 01 00:00:04 rpi2 kernel: bcm2708-dmaengine bcm2708-dmaengine: dma_debug:0 Jan 01 00:00:04 rpi2 kernel: SCSI subsystem initialized Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver usbfs Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver hub Jan 01 00:00:04 rpi2 kernel: usbcore: registered new device driver usb Jan 01 00:00:04 rpi2 kernel: raspberrypi-firmware raspberrypi-firmware.0: Attached to firmware from 2015-10-23 16:24 Jan 01 00:00:04 rpi2 kernel: Switched to clocksource arch_sys_counter Jan 01 00:00:04 rpi2 kernel: FS-Cache: Loaded Jan 01 00:00:04 rpi2 kernel: CacheFiles: Loaded Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 2 Jan 01 00:00:04 rpi2 kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes) Jan 01 00:00:04 rpi2 kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes) Jan 01 00:00:04 rpi2 kernel: TCP: Hash tables configured (established 8192 bind 8192) Jan 01 00:00:04 rpi2 kernel: UDP hash table entries: 512 (order: 2, 16384 bytes) Jan 01 00:00:04 rpi2 kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 1 Jan 01 00:00:04 rpi2 kernel: RPC: Registered named UNIX socket transport module. Jan 01 00:00:04 rpi2 kernel: RPC: Registered udp transport module. Jan 01 00:00:04 rpi2 kernel: RPC: Registered tcp transport module. Jan 01 00:00:04 rpi2 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Jan 01 00:00:04 rpi2 kernel: bcm2708_gpio: bcm2708_gpio_probe 80800a68 Jan 01 00:00:04 rpi2 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes) Jan 01 00:00:04 rpi2 kernel: VFS: Disk quotas dquot_6.6.0 Jan 01 00:00:04 rpi2 kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Jan 01 00:00:04 rpi2 kernel: FS-Cache: Netfs 'nfs' registered for caching Jan 01 00:00:04 rpi2 kernel: NFS: Registering the id_resolver key type Jan 01 00:00:04 rpi2 kernel: Key type id_resolver registered Jan 01 00:00:04 rpi2 kernel: Key type id_legacy registered Jan 01 00:00:04 rpi2 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) Jan 01 00:00:04 rpi2 kernel: io scheduler noop registered Jan 01 00:00:04 rpi2 kernel: io scheduler deadline registered (default) Jan 01 00:00:04 rpi2 kernel: io scheduler cfq registered Jan 01 00:00:04 rpi2 kernel: BCM2708FB: allocated DMA memory fac00000 Jan 01 00:00:04 rpi2 kernel: BCM2708FB: allocated DMA channel 0 @ f3007000 Jan 01 00:00:04 rpi2 kernel: Console: switching to colour frame buffer device 234x73 Jan 01 00:00:04 rpi2 kernel: Serial: 8250/16550 driver, 0 ports, IRQ sharing disabled Jan 01 00:00:04 rpi2 kernel: vc-cma: Videocore CMA driver Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_base = 0x00000000 Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_size = 0x00000000 (0 MiB) Jan 01 00:00:04 rpi2 kernel: vc-cma: vc_cma_initial = 0x00000000 (0 MiB) Jan 01 00:00:04 rpi2 kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3dc00000 mem_size:0x3f000000(1008 MiB) Jan 01 00:00:04 rpi2 kernel: brd: module loaded Jan 01 00:00:04 rpi2 kernel: loop: module loaded Jan 01 00:00:04 rpi2 kernel: vchiq: vchiq_init_state: slot_zero = 0xbac80000, is_master = 0 Jan 01 00:00:04 rpi2 kernel: Loading iSCSI transport class v2.0-870. Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver smsc95xx Jan 01 00:00:04 rpi2 kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Jan 01 00:00:04 rpi2 kernel: Core Release: 2.80a Jan 01 00:00:04 rpi2 kernel: Setting default values for core params Jan 01 00:00:04 rpi2 kernel: Finished setting default values for core params Jan 01 00:00:04 rpi2 kernel: Using Buffer DMA mode Jan 01 00:00:04 rpi2 kernel: Periodic Transfer Interrupt Enhancement - disabled Jan 01 00:00:04 rpi2 kernel: Multiprocessor Interrupt Enhancement - disabled Jan 01 00:00:04 rpi2 kernel: OTG VER PARAM: 0, OTG VER FLAG: 0 Jan 01 00:00:04 rpi2 kernel: Dedicated Tx FIFOs mode Jan 01 00:00:04 rpi2 kernel: WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xbac14000 dma = 0xfac14000 len=9024 Jan 01 00:00:04 rpi2 kernel: FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Jan 01 00:00:04 rpi2 kernel: dwc_otg: Microframe scheduler enabled Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:412: FIQ on core 1 at 0x80400a40 Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:413: FIQ ASM at 0x80400d9c length 36 Jan 01 00:00:04 rpi2 kernel: WARN::hcd_init_fiq:438: MPHI regs_base at 0xbb89a000 Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: DWC OTG Controller Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1 Jan 01 00:00:04 rpi2 kernel: dwc_otg bcm2708_usb: irq 32, io mem 0x00000000 Jan 01 00:00:04 rpi2 kernel: Init: Port Power? op_state=1 Jan 01 00:00:04 rpi2 kernel: Init: Power Port (0) Jan 01 00:00:04 rpi2 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Jan 01 00:00:04 rpi2 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jan 01 00:00:04 rpi2 kernel: usb usb1: Product: DWC OTG Controller Jan 01 00:00:04 rpi2 kernel: usb usb1: Manufacturer: Linux 4.1.11-v7+ dwc_otg_hcd Jan 01 00:00:04 rpi2 kernel: usb usb1: SerialNumber: bcm2708_usb Jan 01 00:00:04 rpi2 kernel: hub 1-0:1.0: USB hub found Jan 01 00:00:04 rpi2 kernel: hub 1-0:1.0: 1 port detected Jan 01 00:00:04 rpi2 kernel: dwc_otg: FIQ enabled Jan 01 00:00:04 rpi2 kernel: dwc_otg: NAK holdoff enabled Jan 01 00:00:04 rpi2 kernel: dwc_otg: FIQ split-transaction FSM enabled Jan 01 00:00:04 rpi2 kernel: Module dwc_common_port init Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver usb-storage Jan 01 00:00:04 rpi2 kernel: mousedev: PS/2 mouse device common for all mice Jan 01 00:00:04 rpi2 kernel: bcm2835-cpufreq: min=600000 max=700000 Jan 01 00:00:04 rpi2 kernel: sdhci: Secure Digital Host Controller Interface driver Jan 01 00:00:04 rpi2 kernel: sdhci: Copyright(c) Pierre Ossman Jan 01 00:00:04 rpi2 kernel: mmc-bcm2835 mmc-bcm2835.0: mmc_debug:0 mmc_debug2:0 Jan 01 00:00:04 rpi2 kernel: mmc-bcm2835 mmc-bcm2835.0: DMA channels allocated Jan 01 00:00:04 rpi2 kernel: sdhci-pltfm: SDHCI platform and OF driver helper Jan 01 00:00:04 rpi2 kernel: ledtrig-cpu: registered to indicate activity on CPUs Jan 01 00:00:04 rpi2 kernel: hidraw: raw HID events driver (C) Jiri Kosina Jan 01 00:00:04 rpi2 kernel: usbcore: registered new interface driver usbhid Jan 01 00:00:04 rpi2 kernel: usbhid: USB HID core driver Jan 01 00:00:04 rpi2 kernel: Initializing XFRM netlink socket Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 17 Jan 01 00:00:04 rpi2 kernel: Indeed it is in host mode hprt0 = 00021501 Jan 01 00:00:04 rpi2 kernel: Key type dns_resolver registered Jan 01 00:00:04 rpi2 kernel: Registering SWP/SWPB emulation handler Jan 01 00:00:04 rpi2 kernel: registered taskstats version 1 Jan 01 00:00:04 rpi2 kernel: vc-sm: Videocore shared memory driver Jan 01 00:00:04 rpi2 kernel: [vc_sm_connected_init]: start Jan 01 00:00:04 rpi2 kernel: [vc_sm_connected_init]: end - returning 0 Jan 01 00:00:04 rpi2 kernel: Waiting for root device /dev/mmcblk0p3... Jan 01 00:00:04 rpi2 kernel: mmc0: host does not support reading read-only switch, assuming write-enable Jan 01 00:00:04 rpi2 kernel: mmc0: new high speed SDHC card at address 0001 Jan 01 00:00:04 rpi2 kernel: mmcblk0: mmc0:0001 00000 29.8 GiB Jan 01 00:00:04 rpi2 kernel: mmcblk0: p1 p2 p3 Jan 01 00:00:04 rpi2 kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg Jan 01 00:00:04 rpi2 kernel: Indeed it is in host mode hprt0 = 00001101 Jan 01 00:00:04 rpi2 kernel: EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Jan 01 00:00:04 rpi2 kernel: VFS: Mounted root (ext4 filesystem) on device 179:3. Jan 01 00:00:04 rpi2 kernel: devtmpfs: mounted Jan 01 00:00:04 rpi2 kernel: Freeing unused kernel memory: 416K (80774000 - 807dc000) Jan 01 00:00:04 rpi2 kernel: usb 1-1: New USB device found, idVendor=0424, idProduct=9514 Jan 01 00:00:04 rpi2 kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 01 00:00:04 rpi2 kernel: hub 1-1:1.0: USB hub found Jan 01 00:00:04 rpi2 kernel: hub 1-1:1.0: 5 ports detected Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: new high-speed USB device number 3 using dwc_otg Jan 01 00:00:04 rpi2 kernel: NET: Registered protocol family 10 Jan 01 00:00:04 rpi2 systemd[1]: Inserted module 'ipv6' Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 Jan 01 00:00:04 rpi2 kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 01 00:00:04 rpi2 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team Jan 01 00:00:04 rpi2 systemd[1]: Inserted module 'ip_tables' Jan 01 00:00:04 rpi2 kernel: smsc95xx v1.0.4 Jan 01 00:00:04 rpi2 kernel: random: systemd urandom read with 64 bits of entropy available Jan 01 00:00:04 rpi2 systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) Jan 01 00:00:04 rpi2 systemd[1]: Detected architecture arm. Jan 01 00:00:04 rpi2 systemd[1]: Set hostname to <rpi2>. Jan 01 00:00:04 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:e1:49:65 Jan 01 00:00:04 rpi2 kernel: uart-pl011 dev:f1: no DMA platform data Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: new low-speed USB device number 4 using dwc_otg Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: New USB device found, idVendor=045e, idProduct=0040 Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: Product: Microsoft 3-Button Mouse with IntelliEye(TM) Jan 01 00:00:04 rpi2 kernel: usb 1-1.3: Manufacturer: Microsoft Jan 01 00:00:04 rpi2 kernel: input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:045E:0040.0001/input/input0 Jan 01 00:00:04 rpi2 kernel: hid-generic 0003:045E:0040.0001: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-bcm2708_usb-1.3/input0 Jan 01 00:00:04 rpi2 systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway. Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: new low-speed USB device number 5 using dwc_otg Jan 01 00:00:04 rpi2 systemd[1]: Configuration file /usr/lib/systemd/system/ebtables.service is marked executable. Please remove executable permission bits. Proceeding anyway. Jan 01 00:00:04 rpi2 systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. Jan 01 00:00:04 rpi2 systemd[1]: Reached target Encrypted Volumes. Jan 01 00:00:04 rpi2 systemd[1]: Starting Encrypted Volumes. Jan 01 00:00:04 rpi2 systemd[1]: Started Forward Password Requests to Wall Directory Watch. Jan 01 00:00:04 rpi2 systemd[1]: Starting Forward Password Requests to Wall Directory Watch. Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: New USB device found, idVendor=413c, idProduct=2105 Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: Product: Dell USB Keyboard Jan 01 00:00:04 rpi2 kernel: usb 1-1.5: Manufacturer: Dell Jan 01 00:00:04 rpi2 kernel: input: Dell Dell USB Keyboard as /devices/platform/bcm2708_usb/usb1/1-1/1-1.5/1-1.5:1.0/0003:413C:2105.0002/input/input1 Jan 01 00:00:04 rpi2 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Jan 01 00:00:04 rpi2 systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. Jan 01 00:00:04 rpi2 kernel: hid-generic 0003:413C:2105.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-bcm2708_usb-1.5/input0 Jan 01 00:00:04 rpi2 systemd[1]: Reached target Remote File Systems. Jan 01 00:00:04 rpi2 systemd[1]: Starting Remote File Systems. Jan 01 00:00:04 rpi2 systemd[1]: Created slice Root Slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting Root Slice. Jan 01 00:00:04 rpi2 systemd[1]: Listening on udev Control Socket. Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Control Socket. Jan 01 00:00:04 rpi2 systemd[1]: Listening on Delayed Shutdown Socket. Jan 01 00:00:04 rpi2 systemd[1]: Starting Delayed Shutdown Socket. Jan 01 00:00:04 rpi2 systemd[1]: Created slice System Slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting System Slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting Collect Read-Ahead Data... Jan 01 00:00:04 rpi2 systemd[1]: Started Replay Read-Ahead Data. Jan 01 00:00:04 rpi2 systemd[1]: Created slice system-getty.slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting system-getty.slice. Jan 01 00:00:04 rpi2 systemd[1]: Created slice system-serial\x2dgetty.slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting system-serial\x2dgetty.slice. Jan 01 00:00:04 rpi2 systemd[1]: Created slice User and Session Slice. Jan 01 00:00:04 rpi2 systemd[1]: Starting User and Session Slice. Jan 01 00:00:04 rpi2 systemd[1]: Reached target Slices. Jan 01 00:00:04 rpi2 systemd[1]: Starting Slices. Jan 01 00:00:04 rpi2 systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. Jan 01 00:00:04 rpi2 systemd[1]: Starting /dev/initctl Compatibility Named Pipe. Jan 01 00:00:04 rpi2 systemd[1]: Listening on udev Kernel Socket. Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Kernel Socket. Jan 01 00:00:04 rpi2 systemd[1]: Listening on Journal Socket. Jan 01 00:00:04 rpi2 systemd[1]: Starting Journal Socket. Jan 01 00:00:04 rpi2 systemd[1]: Mounting Debug File System... Jan 01 00:00:04 rpi2 systemd[1]: Starting Create list of required static device nodes for the current kernel... Jan 01 00:00:04 rpi2 systemd[1]: Mounted Huge Pages File System. Jan 01 00:00:04 rpi2 systemd[1]: Mounting POSIX Message Queue File System... Jan 01 00:00:04 rpi2 systemd[1]: Starting Journal Service... Jan 01 00:00:04 rpi2 systemd[1]: Mounted POSIX Message Queue File System. Jan 01 00:00:04 rpi2 systemd[1]: Mounted Debug File System. Jan 01 00:00:04 rpi2 systemd[1]: Started Collect Read-Ahead Data. Jan 01 00:00:04 rpi2 systemd[1]: Started Create list of required static device nodes for the current kernel. Jan 01 00:00:04 rpi2 systemd-journal[81]: Journal started -- Subject: The journal has been started -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The system journal process has started up, opened the journal -- files for writing and is now ready to process requests. Jan 01 00:00:04 rpi2 systemd[1]: Started Journal Service. Jan 01 00:00:04 rpi2 systemd[1]: Starting Setup Virtual Console... -- Subject: Unit systemd-vconsole-setup.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-vconsole-setup.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Starting Remount Root and Kernel File Systems... -- Subject: Unit systemd-remount-fs.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-remount-fs.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Started Load legacy module configuration. -- Subject: Unit rhel-loadmodules.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-loadmodules.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Set Up Additional Binary Formats. -- Subject: Unit systemd-binfmt.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-binfmt.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Starting Create Static Device Nodes in /dev... -- Subject: Unit systemd-tmpfiles-setup-dev.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-setup-dev.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Started Load Kernel Modules. -- Subject: Unit systemd-modules-load.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-modules-load.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Starting Apply Kernel Variables... -- Subject: Unit systemd-sysctl.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-sysctl.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Mounting Configuration File System... -- Subject: Unit sys-kernel-config.mount has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sys-kernel-config.mount has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Mounted FUSE Control File System. -- Subject: Unit sys-fs-fuse-connections.mount has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sys-fs-fuse-connections.mount has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Setup Virtual Console. -- Subject: Unit systemd-vconsole-setup.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-vconsole-setup.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Apply Kernel Variables. -- Subject: Unit systemd-sysctl.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-sysctl.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Mounted Configuration File System. -- Subject: Unit sys-kernel-config.mount has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sys-kernel-config.mount has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Create Static Device Nodes in /dev. -- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-setup-dev.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Starting udev Kernel Device Manager... -- Subject: Unit systemd-udevd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-udevd.service has begun starting up. Jan 01 00:00:04 rpi2 systemd-udevd[96]: starting version 219 Jan 01 00:00:04 rpi2 kernel: EXT4-fs (mmcblk0p3): re-mounted. Opts: (null) Jan 01 00:00:04 rpi2 systemd[1]: Started Remount Root and Kernel File Systems. -- Subject: Unit systemd-remount-fs.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-remount-fs.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Reached target Local File Systems (Pre). -- Subject: Unit local-fs-pre.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit local-fs-pre.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Starting Local File Systems (Pre). -- Subject: Unit local-fs-pre.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit local-fs-pre.target has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Starting Rebuild Dynamic Linker Cache... -- Subject: Unit ldconfig.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ldconfig.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Starting Load/Save Random Seed... -- Subject: Unit systemd-random-seed.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-random-seed.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Starting Flush Journal to Persistent Storage... -- Subject: Unit systemd-journal-flush.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-journal-flush.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Starting Configure read-only root support... -- Subject: Unit rhel-readonly.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-readonly.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Started First Boot Wizard. -- Subject: Unit systemd-firstboot.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-firstboot.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Starting Rebuild Hardware Database... -- Subject: Unit systemd-hwdb-update.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hwdb-update.service has begun starting up. Jan 01 00:00:04 rpi2 systemd[1]: Started udev Kernel Device Manager. -- Subject: Unit systemd-udevd.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-udevd.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Load/Save Random Seed. -- Subject: Unit systemd-random-seed.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-random-seed.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd-journal[81]: Runtime journal is using 5.7M (max allowed 46.3M, trying to leave 69.4M free of 457.1M available ? current limit 46.3M). Jan 01 00:00:04 rpi2 systemd[1]: Started Flush Journal to Persistent Storage. -- Subject: Unit systemd-journal-flush.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-journal-flush.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:04 rpi2 systemd[1]: Started Configure read-only root support. -- Subject: Unit rhel-readonly.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-readonly.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:05 rpi2 kernel: random: nonblocking pool is initialized Jan 01 00:00:05 rpi2 systemd[1]: Started Rebuild Dynamic Linker Cache. -- Subject: Unit ldconfig.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ldconfig.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Started Rebuild Hardware Database. -- Subject: Unit systemd-hwdb-update.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-hwdb-update.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Starting udev Coldplug all Devices... -- Subject: Unit systemd-udev-trigger.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-udev-trigger.service has begun starting up. Jan 01 00:00:07 rpi2 systemd[1]: Started udev Coldplug all Devices. -- Subject: Unit systemd-udev-trigger.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-udev-trigger.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Found device /dev/ttyAMA0. -- Subject: Unit dev-ttyAMA0.device has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-ttyAMA0.device has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Starting Show Plymouth Boot Screen... -- Subject: Unit plymouth-start.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-start.service has begun starting up. Jan 01 00:00:07 rpi2 kernel: bcm2708_spi bcm2708_spi.0: master is unqueued, this is deprecated Jan 01 00:00:07 rpi2 kernel: bcm2708_spi bcm2708_spi.0: SPI Controller at 0x3f204000 (irq 80) Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c_init_pinmode(1,2) Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c_init_pinmode(1,3) Jan 01 00:00:07 rpi2 kernel: bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x3f804000 (irq 79) (baudrate 100000) Jan 01 00:00:07 rpi2 systemd[1]: Received SIGRTMIN+20 from PID 138 (plymouthd). Jan 01 00:00:07 rpi2 systemd[1]: Started Show Plymouth Boot Screen. -- Subject: Unit plymouth-start.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-start.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. -- Subject: Unit systemd-ask-password-plymouth.path has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-ask-password-plymouth.path has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Starting Forward Password Requests to Plymouth Directory Watch. -- Subject: Unit systemd-ask-password-plymouth.path has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-ask-password-plymouth.path has begun starting up. Jan 01 00:00:07 rpi2 systemd[1]: Started Dispatch Password Requests to Console Directory Watch. -- Subject: Unit systemd-ask-password-console.path has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-ask-password-console.path has finished starting up. -- -- The start-up result is done. Jan 01 00:00:07 rpi2 systemd[1]: Found device /dev/disk/by-label/1BBF2D52. -- Subject: Unit dev-disk-by\x2dlabel-1BBF2D52.device has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2dlabel-1BBF2D52.device has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Found device /dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce. -- Subject: Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.device has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.device has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Activating swap /dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce... -- Subject: Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Mounting /boot... -- Subject: Unit boot.mount has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit boot.mount has begun starting up. Jan 01 00:00:08 rpi2 kernel: Adding 524284k swap on /dev/mmcblk0p2. Priority:-1 extents:1 across:524284k SSFS Jan 01 00:00:08 rpi2 systemd[1]: Activated swap /dev/disk/by-uuid/f28d9939-d00d-4e9e-aceb-1ac7b3e607ce. -- Subject: Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2duuid-f28d9939\x2dd00d\x2d4e9e\x2daceb\x2d1ac7b3e607ce.swap has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Mounted /boot. -- Subject: Unit boot.mount has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit boot.mount has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 kernel: wm8804 1-003b: Failed to read device ID: -5 Jan 01 00:00:08 rpi2 kernel: wm8804: probe of 1-003b failed with error -5 Jan 01 00:00:08 rpi2 systemd[1]: Reached target Local File Systems. -- Subject: Unit local-fs.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit local-fs.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Local File Systems. -- Subject: Unit local-fs.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit local-fs.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Reconfigure the system on administrator request. -- Subject: Unit rhel-configure.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-configure.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... -- Subject: Unit plymouth-read-write.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-read-write.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Import network configuration from initramfs. -- Subject: Unit rhel-import-state.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-import-state.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Started Commit a transient machine-id on disk. -- Subject: Unit systemd-machine-id-commit.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-machine-id-commit.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Create Volatile Files and Directories... -- Subject: Unit systemd-tmpfiles-setup.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-setup.service has begun starting up. Jan 01 00:00:08 rpi2 kernel: pcm512x 1-004d: Failed to reset device: -5 Jan 01 00:00:08 rpi2 kernel: pcm512x: probe of 1-004d failed with error -5 Jan 01 00:00:08 rpi2 kernel: pcm512x 1-004c: Failed to reset device: -5 Jan 01 00:00:08 rpi2 kernel: pcm512x: probe of 1-004c failed with error -5 Jan 01 00:00:08 rpi2 systemd[1]: Starting Mark the need to relabel after reboot... -- Subject: Unit rhel-autorelabel-mark.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-autorelabel-mark.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Relabel all filesystems, if necessary. -- Subject: Unit rhel-autorelabel.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-autorelabel.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Rebuild Journal Catalog... -- Subject: Unit systemd-journal-catalog-update.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-journal-catalog-update.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Reached target Swap. -- Subject: Unit swap.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit swap.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Swap. -- Subject: Unit swap.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit swap.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Create Volatile Files and Directories. -- Subject: Unit systemd-tmpfiles-setup.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-setup.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Started Mark the need to relabel after reboot. -- Subject: Unit rhel-autorelabel-mark.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-autorelabel-mark.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. -- Subject: Unit plymouth-read-write.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-read-write.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Started Rebuild Journal Catalog. -- Subject: Unit systemd-journal-catalog-update.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-journal-catalog-update.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Update is Completed... -- Subject: Unit systemd-update-done.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-done.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Starting Security Auditing Service... -- Subject: Unit auditd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit auditd.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Update is Completed. -- Subject: Unit systemd-update-done.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-done.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 auditd[164]: Error - audit support not in kernel Jan 01 00:00:08 rpi2 auditd[164]: Cannot open netlink audit socket Jan 01 00:00:08 rpi2 auditd[164]: The audit daemon is exiting. Jan 01 00:00:08 rpi2 systemd[1]: auditd.service: main process exited, code=exited, status=1/FAILURE Jan 01 00:00:08 rpi2 augenrules[165]: Error - audit support not in kernel Jan 01 00:00:08 rpi2 augenrules[165]: Error - audit support not in kernel Jan 01 00:00:08 rpi2 augenrules[165]: Cannot open netlink audit socket Jan 01 00:00:08 rpi2 systemd[1]: Failed to start Security Auditing Service. -- Subject: Unit auditd.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit auditd.service has failed. -- -- The result is failed. Jan 01 00:00:08 rpi2 systemd[1]: Unit auditd.service entered failed state. Jan 01 00:00:08 rpi2 systemd[1]: auditd.service failed. Jan 01 00:00:08 rpi2 systemd[1]: Starting Update UTMP about System Boot/Shutdown... -- Subject: Unit systemd-update-utmp.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Update UTMP about System Boot/Shutdown. -- Subject: Unit systemd-update-utmp.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Reached target System Initialization. -- Subject: Unit sysinit.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sysinit.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting System Initialization. -- Subject: Unit sysinit.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sysinit.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Flexible branding. -- Subject: Unit brandbot.path has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit brandbot.path has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Flexible branding. -- Subject: Unit brandbot.path has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit brandbot.path has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Reached target Paths. -- Subject: Unit paths.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit paths.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Paths. -- Subject: Unit paths.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit paths.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started Daily Cleanup of Temporary Directories. -- Subject: Unit systemd-tmpfiles-clean.timer has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-clean.timer has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Daily Cleanup of Temporary Directories. -- Subject: Unit systemd-tmpfiles-clean.timer has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-tmpfiles-clean.timer has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Reached target Timers. -- Subject: Unit timers.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit timers.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Timers. -- Subject: Unit timers.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit timers.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Listening on D-Bus System Message Bus Socket. -- Subject: Unit dbus.socket has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dbus.socket has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting D-Bus System Message Bus Socket. -- Subject: Unit dbus.socket has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dbus.socket has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Reached target Sockets. -- Subject: Unit sockets.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sockets.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Sockets. -- Subject: Unit sockets.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sockets.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Reached target Basic System. -- Subject: Unit basic.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit basic.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting Basic System. -- Subject: Unit basic.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit basic.target has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started irqbalance daemon. -- Subject: Unit irqbalance.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit irqbalance.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:08 rpi2 systemd[1]: Starting irqbalance daemon... -- Subject: Unit irqbalance.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit irqbalance.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Starting firewalld - dynamic firewall daemon... -- Subject: Unit firewalld.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit firewalld.service has begun starting up. Jan 01 00:00:08 rpi2 systemd[1]: Started D-Bus System Message Bus. -- Subject: Unit dbus.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dbus.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting D-Bus System Message Bus... -- Subject: Unit dbus.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dbus.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting Permit User Sessions... -- Subject: Unit systemd-user-sessions.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-user-sessions.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting System Logging Service... -- Subject: Unit rsyslog.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rsyslog.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting OpenSSH Server Key Generation... -- Subject: Unit sshd-keygen.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sshd-keygen.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting Root Filesystem Auto-Resizer... -- Subject: Unit rootfs-resize.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rootfs-resize.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting Login Service... -- Subject: Unit systemd-logind.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting Dump dmesg to /var/log/dmesg... -- Subject: Unit rhel-dmesg.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-dmesg.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Started Permit User Sessions. -- Subject: Unit systemd-user-sessions.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-user-sessions.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting Terminate Plymouth Boot Screen... -- Subject: Unit plymouth-quit.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-quit.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Starting Wait for Plymouth Boot Screen to Quit... -- Subject: Unit plymouth-quit-wait.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-quit-wait.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Started Command Scheduler. -- Subject: Unit crond.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit crond.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting Command Scheduler... -- Subject: Unit crond.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit crond.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Received SIGRTMIN+21 from PID 138 (plymouthd). Jan 01 00:00:09 rpi2 systemd[1]: Started Dump dmesg to /var/log/dmesg. -- Subject: Unit rhel-dmesg.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-dmesg.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 crond[208]: (CRON) INFO (RANDOM_DELAY will be scaled with factor 67% if used.) Jan 01 00:00:09 rpi2 systemd[1]: Started Terminate Plymouth Boot Screen. -- Subject: Unit plymouth-quit.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-quit.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Started Wait for Plymouth Boot Screen to Quit. -- Subject: Unit plymouth-quit-wait.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit plymouth-quit-wait.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 crond[208]: (CRON) INFO (running with inotify support) Jan 01 00:00:09 rpi2 systemd[1]: Started Serial Getty on ttyAMA0. -- Subject: Unit serial-getty(a)ttyAMA0.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit serial-getty(a)ttyAMA0.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting Serial Getty on ttyAMA0... -- Subject: Unit serial-getty(a)ttyAMA0.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit serial-getty(a)ttyAMA0.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Started Getty on tty1. -- Subject: Unit getty(a)tty1.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit getty(a)tty1.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting Getty on tty1... -- Subject: Unit getty(a)tty1.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit getty(a)tty1.service has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Reached target Login Prompts. -- Subject: Unit getty.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit getty.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd[1]: Starting Login Prompts. -- Subject: Unit getty.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit getty.target has begun starting up. Jan 01 00:00:09 rpi2 systemd[1]: Started Login Service. -- Subject: Unit systemd-logind.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-logind.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:09 rpi2 systemd-logind[201]: New seat seat0. -- Subject: A new seat seat0 is now available -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new seat seat0 has been configured and is now available. Jan 01 00:00:09 rpi2 systemd[1]: Started System Logging Service. -- Subject: Unit rsyslog.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rsyslog.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:10 rpi2 systemd[1]: Started Root Filesystem Auto-Resizer. -- Subject: Unit rootfs-resize.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rootfs-resize.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:11 rpi2 kernel: nf_conntrack version 0.5.0 (14815 buckets, 59260 max) Jan 01 00:00:11 rpi2 kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team Jan 01 00:00:11 rpi2 kernel: Ebtables v2.0 registered Jan 01 00:00:11 rpi2 kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. Jan 01 00:00:12 rpi2 systemd[1]: Started firewalld - dynamic firewall daemon. -- Subject: Unit firewalld.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit firewalld.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:12 rpi2 systemd[1]: Starting Network Manager... -- Subject: Unit NetworkManager.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager.service has begun starting up. Jan 01 00:00:12 rpi2 NetworkManager[269]: <info> NetworkManager (version 1.0.6-27.el7) is starting... Jan 01 00:00:12 rpi2 NetworkManager[269]: <info> Read config: /etc/NetworkManager/NetworkManager.conf and conf.d: 10-ibft-plugin.conf Jan 01 00:00:12 rpi2 systemd[1]: Started Network Manager. -- Subject: Unit NetworkManager.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:12 rpi2 systemd[1]: Starting Network Manager Wait Online... -- Subject: Unit NetworkManager-wait-online.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager-wait-online.service has begun starting up. Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib/NetworkManager/libnm-settings-plugin-ifcfg-rh.so) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib/NetworkManager/libnm-settings-plugin-ibft.so) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-eth0 (0cb1274f-af94-4a51-a5bc-7608a1e37d63,"eth0") Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> monitoring kernel firmware directory '/lib/firmware'. Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMVxlanFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMVlanFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMVethFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMTunFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMMacvlanFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMInfinibandFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMGreFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMEthernetFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMBridgeFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMBondFactory (internal) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/libnm-device-plugin-team.so) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WiFi enabled by radio killswitch; enabled by state file Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WWAN enabled by radio killswitch; enabled by state file Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> WiMAX enabled by radio killswitch; enabled by state file Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> Networking is enabled by state file Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (lo): link connected Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (eth0): new Ethernet device (carrier: OFF, driver: 'smsc95xx', ifindex: 2) Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 01 00:00:13 rpi2 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 01 00:00:13 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup Jan 01 00:00:13 rpi2 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jan 01 00:00:13 rpi2 dbus[193]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' Jan 01 00:00:13 rpi2 systemd[1]: Starting Authorization Manager... -- Subject: Unit polkit.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit polkit.service has begun starting up. Jan 01 00:00:13 rpi2 dbus[193]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' Jan 01 00:00:13 rpi2 systemd[1]: Configuration file /usr/lib/systemd/system/wpa_supplicant.service is marked executable. Please remove executable permission bits. Proceeding anyway. Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' Jan 01 00:00:13 rpi2 systemd[1]: Starting WPA Supplicant daemon... -- Subject: Unit wpa_supplicant.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wpa_supplicant.service has begun starting up. Jan 01 00:00:13 rpi2 dbus[193]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jan 01 00:00:13 rpi2 dbus-daemon[193]: dbus[193]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jan 01 00:00:13 rpi2 systemd[1]: Started WPA Supplicant daemon. -- Subject: Unit wpa_supplicant.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wpa_supplicant.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:13 rpi2 NetworkManager[269]: <info> wpa_supplicant running Jan 01 00:00:13 rpi2 polkitd[319]: Started polkitd version 0.112 Jan 01 00:00:13 rpi2 polkitd[319]: Loading rules from directory /etc/polkit-1/rules.d Jan 01 00:00:13 rpi2 polkitd[319]: Loading rules from directory /usr/share/polkit-1/rules.d Jan 01 00:00:14 rpi2 polkitd[319]: Finished loading, compiling and executing 2 rules Jan 01 00:00:14 rpi2 dbus[193]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Jan 01 00:00:14 rpi2 dbus-daemon[193]: dbus[193]: [system] Successfully activated service 'org.freedesktop.PolicyKit1' Jan 01 00:00:14 rpi2 systemd[1]: Started Authorization Manager. -- Subject: Unit polkit.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit polkit.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:14 rpi2 polkitd[319]: Acquired the name org.freedesktop.PolicyKit1 on the system bus Jan 01 00:00:14 rpi2 kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 Jan 01 00:00:14 rpi2 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): link connected Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> Auto-activating connection 'eth0'. Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): Activation: starting connection 'eth0' (0cb1274f-af94-4a51-a5bc-7608a1e37d63) Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> NetworkManager state is now CONNECTING Jan 01 00:00:14 rpi2 NetworkManager[269]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 01 00:00:18 rpi2 NetworkManager[269]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Jan 01 00:00:18 rpi2 NetworkManager[269]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds) Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> dhclient started with pid 564 Jan 01 00:00:19 rpi2 dhclient[564]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 (xid=0x58650026) Jan 01 00:00:19 rpi2 dhclient[564]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x58650026) Jan 01 00:00:19 rpi2 dhclient[564]: DHCPOFFER from 192.168.155.2 Jan 01 00:00:19 rpi2 dhclient[564]: DHCPACK from 192.168.155.2 (xid=0x58650026) Jan 01 00:00:19 rpi2 dhclient[564]: suspect value in | option - discarded Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> address 192.168.155.116 Jan 01 00:00:19 rpi2 dhclient[564]: bound to 192.168.155.116 -- renewal in 898 seconds. Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> plen 24 (255.255.255.0) Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> gateway 192.168.155.2 Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> server identifier 192.168.155.2 Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> lease time 1800 Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> nameserver '192.168.155.2' Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> domain name 'daku.org' Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): DHCPv4 state changed unknown -> bound Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0] Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> NetworkManager state is now CONNECTED_LOCAL Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> NetworkManager state is now CONNECTED_GLOBAL Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> Policy set 'eth0' (eth0) as default for IPv4 routing and DNS. Jan 01 00:00:19 rpi2 NetworkManager[269]: <info> (eth0): Activation: successful, device activated. Jan 01 00:00:19 rpi2 dbus[193]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jan 01 00:00:19 rpi2 dbus-daemon[193]: dbus[193]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Jan 01 00:00:19 rpi2 systemd[1]: Starting Network Manager Script Dispatcher Service... -- Subject: Unit NetworkManager-dispatcher.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager-dispatcher.service has begun starting up. Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 RSA host key: [ OK ] Jan 01 00:00:19 rpi2 dbus[193]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 00:00:19 rpi2 systemd[1]: Started Network Manager Script Dispatcher Service. -- Subject: Unit NetworkManager-dispatcher.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager-dispatcher.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:19 rpi2 dbus-daemon[193]: dbus[193]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 01 00:00:19 rpi2 nm-dispatcher[571]: Dispatching action 'up' for eth0 Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 ECDSA host key: [ OK ] Jan 01 00:00:19 rpi2 sshd-keygen[199]: Generating SSH2 ED25519 host key: [ OK ] Jan 01 00:00:19 rpi2 systemd[1]: Started OpenSSH Server Key Generation. -- Subject: Unit sshd-keygen.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sshd-keygen.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:20 rpi2 NetworkManager[269]: <info> startup complete Jan 01 00:00:20 rpi2 systemd[1]: Started Network Manager Wait Online. -- Subject: Unit NetworkManager-wait-online.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit NetworkManager-wait-online.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:20 rpi2 systemd[1]: Starting LSB: Bring up/down networking... -- Subject: Unit network.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.service has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: network.service: control process exited, code=exited status=6 Jan 01 00:00:20 rpi2 systemd[1]: Failed to start LSB: Bring up/down networking. -- Subject: Unit network.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.service has failed. -- -- The result is failed. Jan 01 00:00:20 rpi2 systemd[1]: Unit network.service entered failed state. Jan 01 00:00:20 rpi2 systemd[1]: network.service failed. Jan 01 00:00:20 rpi2 systemd[1]: Reached target Network. -- Subject: Unit network.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:20 rpi2 systemd[1]: Starting Network. -- Subject: Unit network.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.target has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: Started OpenSSH server daemon. -- Subject: Unit sshd.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sshd.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:20 rpi2 systemd[1]: Starting OpenSSH server daemon... -- Subject: Unit sshd.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sshd.service has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: Starting Postfix Mail Transport Agent... -- Subject: Unit postfix.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postfix.service has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: Reached target Network is Online. -- Subject: Unit network-online.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network-online.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:20 rpi2 systemd[1]: Starting Network is Online. -- Subject: Unit network-online.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network-online.target has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: Starting Crash recovery kernel arming... -- Subject: Unit kdump.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kdump.service has begun starting up. Jan 01 00:00:20 rpi2 systemd[1]: Starting Dynamic System Tuning Daemon... -- Subject: Unit tuned.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tuned.service has begun starting up. Jan 01 00:00:20 rpi2 sshd[605]: Server listening on 0.0.0.0 port 22. Jan 01 00:00:20 rpi2 sshd[605]: Server listening on :: port 22. Jan 01 00:00:22 rpi2 systemd[1]: Started Dynamic System Tuning Daemon. -- Subject: Unit tuned.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tuned.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:23 rpi2 kdumpctl[607]: Kdump is not supported on this kernel Jan 01 00:00:23 rpi2 kdumpctl[607]: Starting kdump: [FAILED] Jan 01 00:00:23 rpi2 systemd[1]: kdump.service: main process exited, code=exited, status=1/FAILURE Jan 01 00:00:23 rpi2 systemd[1]: Failed to start Crash recovery kernel arming. -- Subject: Unit kdump.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit kdump.service has failed. -- -- The result is failed. Jan 01 00:00:23 rpi2 systemd[1]: Unit kdump.service entered failed state. Jan 01 00:00:23 rpi2 systemd[1]: kdump.service failed. Jan 01 00:00:24 rpi2 postfix/postfix-script[1216]: starting the Postfix mail system Jan 01 00:00:24 rpi2 postfix/master[1218]: daemon started -- version 2.10.1, configuration /etc/postfix Jan 01 00:00:24 rpi2 systemd[1]: Started Postfix Mail Transport Agent. -- Subject: Unit postfix.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit postfix.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:24 rpi2 systemd[1]: Reached target Multi-User System. -- Subject: Unit multi-user.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit multi-user.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:24 rpi2 systemd[1]: Starting Multi-User System. -- Subject: Unit multi-user.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit multi-user.target has begun starting up. Jan 01 00:00:24 rpi2 systemd[1]: Reached target Graphical Interface. -- Subject: Unit graphical.target has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit graphical.target has finished starting up. -- -- The start-up result is done. Jan 01 00:00:24 rpi2 systemd[1]: Starting Graphical Interface. -- Subject: Unit graphical.target has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit graphical.target has begun starting up. Jan 01 00:00:24 rpi2 systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. -- Subject: Unit systemd-readahead-done.timer has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.timer has finished starting up. -- -- The start-up result is done. Jan 01 00:00:24 rpi2 systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup. -- Subject: Unit systemd-readahead-done.timer has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.timer has begun starting up. Jan 01 00:00:24 rpi2 systemd[1]: Starting Update UTMP about System Runlevel Changes... -- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp-runlevel.service has begun starting up. Jan 01 00:00:25 rpi2 systemd[1]: Started Update UTMP about System Runlevel Changes. -- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-update-utmp-runlevel.service has finished starting up. -- -- The start-up result is done. Jan 01 00:00:25 rpi2 systemd[1]: Startup finished in 2.388s (kernel) + 22.636s (userspace) = 25.025s. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- successfully started. Note that this does not mean that the machine is -- now idle as services might still be busy with completing start-up. -- -- Kernel start-up required 2388988 microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 22636223 microseconds. Jan 01 00:00:49 rpi2 login[214]: pam_unix(login:account): account root has password changed in future Jan 01 00:00:49 rpi2 systemd[1]: Created slice user-0.slice. -- Subject: Unit user-0.slice has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user-0.slice has finished starting up. -- -- The start-up result is done. Jan 01 00:00:49 rpi2 systemd[1]: Starting user-0.slice. -- Subject: Unit user-0.slice has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user-0.slice has begun starting up. Jan 01 00:00:49 rpi2 systemd-logind[201]: New session c1 of user root. -- Subject: A new session c1 has been created for user root -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID c1 has been created for the user root. -- -- The leading process of the session is 214. Jan 01 00:00:49 rpi2 systemd[1]: Started Session c1 of user root. -- Subject: Unit session-c1.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c1.scope has finished starting up. -- -- The start-up result is done. Jan 01 00:00:49 rpi2 systemd[1]: Starting Session c1 of user root. -- Subject: Unit session-c1.scope has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c1.scope has begun starting up. Jan 01 00:00:49 rpi2 login[214]: pam_unix(login:session): session opened for user root by LOGIN(uid=0) Jan 01 00:00:49 rpi2 login[214]: ROOT LOGIN ON tty1 Jan 01 00:00:55 rpi2 systemd[1]: Starting Stop Read-Ahead Data Collection... -- Subject: Unit systemd-readahead-done.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has begun starting up. Jan 01 00:00:55 rpi2 systemd[1]: Started Stop Read-Ahead Data Collection. -- Subject: Unit systemd-readahead-done.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-readahead-done.service has finished starting up. -- -- The start-up result is done. Jan 01 00:01:01 rpi2 crond[1255]: pam_unix(crond:account): account root has password changed in future Jan 01 00:01:01 rpi2 systemd[1]: Started Session c2 of user root. -- Subject: Unit session-c2.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c2.scope has finished starting up. -- -- The start-up result is done. Jan 01 00:01:01 rpi2 systemd[1]: Starting Session c2 of user root. -- Subject: Unit session-c2.scope has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-c2.scope has begun starting up. Jan 01 00:01:01 rpi2 CROND[1264]: (root) CMD (run-parts /etc/cron.hourly) Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1267]: starting 0anacron Jan 01 00:01:01 rpi2 anacron[1273]: Anacron started on 1970-01-01 Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.daily' in 13 min. Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.weekly' in 33 min. Jan 01 00:01:01 rpi2 anacron[1273]: Will run job `cron.monthly' in 53 min. Jan 01 00:01:01 rpi2 anacron[1273]: Jobs will be executed sequentially Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1275]: finished 0anacron Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1277]: starting 0yum-hourly.cron Jan 01 00:01:01 rpi2 run-parts(/etc/cron.hourly)[1281]: finished 0yum-hourly.cron Jan 01 00:02:28 rpi2 polkitd[319]: Registered Authentication Agent for unix-process:1299:14877 (system bus name :1.12 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Jan 01 00:02:28 rpi2 systemd[1]: Starting LSB: Bring up/down networking... -- Subject: Unit network.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.service has begun starting up. Jan 01 00:02:28 rpi2 systemd[1]: network.service: control process exited, code=exited status=6 Jan 01 00:02:28 rpi2 systemd[1]: Failed to start LSB: Bring up/down networking. -- Subject: Unit network.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit network.service has failed. -- -- The result is failed. Jan 01 00:02:28 rpi2 systemd[1]: Unit network.service entered failed state. Jan 01 00:02:28 rpi2 systemd[1]: network.service failed. Jan 01 00:02:28 rpi2 polkitd[319]: Unregistered Authentication Agent for unix-process:1299:14877 (system bus name :1.12, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)

10 years, 3 months

Re: [CentOS] Another Fedora decision

by Valeri Galtsev

On Wed, February 4, 2015 9:17 am, James B. Byrne wrote: > > On Tue, February 3, 2015 14:01, Valeri Galtsev wrote: >> >> On Tue, February 3, 2015 12:39 pm, Les Mikesell wrote: >>> On Tue, Feb 3, 2015 at 12:24 PM, Valeri Galtsev >>> <galtsev(a)kicp.uchicago.edu> wrote: >>>> >>>> Sounds so I almost have to feel shame for securing my boxes no >>>> matter what job vendor did ;-) >>> >>> Yes, computers and the way people access them are pretty much a >>> commodity now. If you are spending time building something exotic >>> for a common purpose, isn't that a waste? >> >> Do I have to take that people who are not sysadmins themselves just >> hate an existence of sysadmins? >> > > I had a friend, now deceased, who worked as an RCA colour TV > technician when he was very young. In the 1950s he would be sent to > the homes of people having trouble adjusting the colour settings on > their new RCA's. That was system administration then. Who needs them > now? Not exact analogy. But I know what you are leading to. Once my department decides they will not need me as they will get what is necessary done by faceless big corporation shipping unified services, then I'm out of my job, and will go slaving for that corporation to do what I'm told to do how I'm told to do (which has to yield unified standard product allegedly good). We are not going to break machines and conveyors resisting progress as individual craftsmen of the past did. Even more, few best craftsmen stayed as such even after conveyors were there. But I'm not considering myself such. > > We are dinosaurs. People do not hate us. They just do not understand > why we are still around. I didn't say sysadmins. My language was deliberate, I said an existence of sysadmins. > > Other than lifting the display into a comfortable position for viewing > the latest MacBooks cannot even be physically opened for servicing (by > a user) as far as I can discover. An iPhone is a sealed unit. Both > devices are orders of magnitude more powerful computers than the i486 > I first installed RH on. The point Les makes is entirely correct. > The systems we install should not require the degree of slavish > attention to arcane details that is necessary to make them both useful > and safe to use. > > That said, the original issue remains, making manual configuration > slightly more cumbersome than it already is. That this is done solely > in order to make a claim that it somehow improves security is, in my > opinion, self-defeating. It is certainly a deceit. Whether it is > self-delusion or overt pretence I have no idea. Yes, these are decisions of incompetent bosses who cover their backsides, and if something bad has happened, they are covered by saying "We did an appropriate thing but still end users defeated our good effort". And they will get away with it (as they always do) as they will be judged by another bunch of yet also incompetent people. > > One might question why *nix distributions insist on providing a known > point of attack to begin with. Why does user 0 have to be called > root? Why not beatlebailey, cinnamon or pasdecharge? If brute > forcing passwords is the problem then why not make it ever more > difficult by forcing crackers to guess what the superuser name is to > begin with? > > Oh, I know. Too much software exists that presumes that the superuser > name is root. Evidently adherence to that convention is valued more > highly than providing security. God forbid that one simply check for > user 0. I'm a creature of habit. Unix is in agreement with me on that (as I like to flatter myself ;-) So, I endorse "do not change anything unless it is absolutely necessary". Another way of stressing it is: if you change things people are less likely to do right things until they accommodate to your newly changed environment, so in my judgement, no change here promotes higher average security of computer community. [ Of course I mean meaningful things, i.e. do not change root to another name, UID=0 to another number. Staying abreast with password requirements (i.e. password should be better that three lowercase letter which might have been sufficient at some point in time, but not anymore) is not fundamental change. It's tiny increment. Not the fundamental changes I meant above ] > > I seldom use root other than for peer-to-peer rsync via password-less > login. Consequently I do not really care whether Anaconda forces me to > use 32 character Base64 encoded passwords for root or none at all. I > just cannot bear to stand by and read the BS about how anything of > that nature improves security. It is just self-deception. Twenty > years ago it might have had some validity, although I doubt it. > Things that are hard to remember tend to get written down. Things > that are written down tend to be read by eyes other than those that > were intended. Well, I build Linux boxes with kickstart (after I built manually this kind of box with this release of OS). My root passwords in kickstart are really strong ones. They are being changed however as soon as newly built system is booted (as kickstart content has to be remotely accessible, I don't care if it is only on "secure" private network. No network medium can be considered secure if more than one - yours - machine is connected to it. Those who disagree... please, consider of taking yet another computer security course). That said, I still agree with your feelings about nonsense we are forced to follow. You can not do good to the person who does not wish to do god for himself. And yes, some may follow their own security practice (still I for one will take all of A, B and C security measured even if only A meets the goal). > > The whole matter of attending to the risk of brute force password > discovery rather misses the point. Amateurs hack systems, > professionals hack people. No matter how resistant your password is > to brute force discovery, it only takes one careless mistake to have > it revealed by an incautious or suitably deceived sysadmin. Look up > 'Robin Sage' and the follow on study 'Emily Williams' and then ask > yourself: How does a strong password on the root account deal with > that? Yep. I've seen sysadmin typing root password in one of his user's shell (and got owned) - I mentioned that in this thread. That, BTW, was nice justification to always do excessive typing and type the whole path to the command beginning from leading slash - when you do sysadmin task at least. There also can be a blunder like changing root password instead of changing user password to trivial temporary password. I've seen that done by someone (and mentioned it at some point). I myself was pressed once by very powerful (and knowledgeable!) department member to give him root password for the server. Up to the threat to take it up to the highest boss. I didn't, but were it the highest boss himself, I can't make my judgement about outcome even now after over a decade... So, holes vary, yet bad passwords do have their teeny-tiny share IMHO. > > I really wonder sometimes if the software development people that > write so much about security 'best-practice' have much of a clue about > how penetrations are actually carried out. For example, how many of > you have ever plugged a USB key into one of your hosts? If you have > then you have permanently compromised the security of that system and > nothing, short of pulling the entire USB controller, can ever undo it; > and not even then I suspect. You may not, probably have not (yet), > have been infected, but then you will never know for sure whether you > have or not. Indeed, you need to think what you are plugging into what. The same as you initiate all connections only in the direction from more trusted machine to less trusted. Never other way around. (Does everybody always follow this rule? No, do not confess ;-) > > There are so many computer control systems that are embedded in the > devices we call computers that the attack surface is incomprehensibly > large. And most of these embedded systems are completely open to > exploitation; at the fabrication level. The Internet is not even the > preferred vector. Have you ever used a USB charging station in an > airport for your laptop, tablet or phone? Too bad. Have you ever > plugged a personal device into one of your hosts at work via USB or > Thunderbolt (not likely for the latter I admit)? Oh well. At least > you can increase the strength of your root password. > > Is your home or business network device provided to you by your > provider? Has it been changed (upgraded) recently without your > request (or even with it)? I have to SSH tunnel all of my traffic on > my home network now because traffic through my (recently upgraded) > xxxxxx provided yyyyy router phones home to yyyyy; and I cannot stop > it short of jail-breaking, which is in violation of my terms of > service (AND I have to pay rent for this device). This is not > paranoia, this is observed activity. (Sorry about the xxxxx yyyyy > stuff, but on consideration I would rather not run the risk of being > harassed by either or both of the two major corporations involved.) Yes, so true. The list goes on. Android devices that have proprietary google code in the kernel. You just reverse engineer it and tell what it does, and even it is evil, it is you who will go to jail for crimes you just admitted above. Or binary proprietary drives, that are in the variety of places - who ever audited these? How about "firmware" - the programs that more sophisticated computer boards run (RAID controllers are the simplest example)? Well, luckily I trust most of the board manufacturers (I hate some of BIOSes or EFIs of some, but that is different story). So, the life is not that bad as we have depicted above (hopefully), but at least we realize what we deal with... Valeri > > Sometimes I just cannot bear to think about this stuff anymore. > > -- > *** 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 > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

11 years, 2 months

Re: [CentOS] IPv6 broken on Linode

by Alice Wonder

On 02/16/2017 03:28 AM, James Hogarth wrote: > On 16 February 2017 at 10:42, Alice Wonder <alice(a)domblogger.net> wrote: >> On 02/16/2017 02:32 AM, James Hogarth wrote: >>> >>> On 16 February 2017 at 10:17, Alice Wonder <alice(a)domblogger.net> wrote: >>>> >>>> On 02/16/2017 02:03 AM, James Hogarth wrote: >>>>> >>>>> >>>>> On 16 February 2017 at 09:09, Alice Wonder <alice(a)domblogger.net> wrote: >>>>>> >>>>>> >>>>>> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e(a)domblogger.net>, >>>>>>> Alice Wonder <alice(a)domblogger.net> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> https://forum.linode.com/viewtopic.php?f=19&t=14570&p=72785 >>>>>>>> >>>>>>>> I can not figure out what I need to do. >>>>>>>> >>>>>>>> Apparently according to linode support, the VM is trying to grab an >>>>>>>> IPv6 >>>>>>>> address with some privacy stuff enabled by default causing it to not >>>>>>>> grab the IPv6 address that is assigned to me. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Does the accepted answer at the following link give you any useful >>>>>>> hints? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> http://superuser.com/questions/243669/how-to-avoid-exposing-my-mac-address-… >>>>>>> >>>>>>> Cheers >>>>>>> Tony >>>>>>> >>>>>> >>>>>> Not really - I tried >>>>>> >>>>>> net.ipv6.conf.all.use_tempaddr = 0 >>>>>> >>>>>> and it still fails to grab the proper IPv6 >>>>>> >>>>>> -=- >>>>>> >>>>>> Just in case, I did ask Linode support to verify that my hardware >>>>>> address >>>>>> is >>>>>> what it is suppose to be. Still waiting to hear on that. >>>>>> >>>>>> _______________________________________________ >>>>> >>>>> >>>>> >>>>> >>>>> it still is key=value ... it uses the ifcfg- files (via the rh >>>>> plugin) and they are all key=value >>>>> >>>>> It would be helpful if you could paste the journal output (journalctl >>>>> -u NetworkManager) from the time period of attempting to get an >>>>> address ... >>>>> >>>>> also the nmcli conn sh <connection_name> information for the interface >>>>> along with your ifcfg- files >>>> >>>> >>>> >>>> ifcfg-lo is the only one that exists on any of the servers - including >>>> the >>>> VMs that grab the correct IPv6 address. >>>> >>>> from /sbin/ifconfig -a : >>>> >>> >>> For a start stop using ifconfig ... it's broken at this point on >>> linux, especially on multi ip and ipv6 scenarios >>> >>> Use `ip -6 addr sh` for ipv6 specfic stuff, or just ip addr sh to see >>> all IP address stuff regardless of family >>> >>>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 >>>> inet 178.79.185.217 netmask 255.255.255.0 broadcast >>>> 178.79.185.255 >>>> inet6 fe80::a8ad:d312:4ef4:7272 prefixlen 64 scopeid 0x20<link> >>>> inet6 2a01:7e00::825f:e564:ad53:72fc prefixlen 64 scopeid >>>> 0x0<global> >>>> ether f2:3c:91:18:8a:7e txqueuelen 1000 (Ethernet) >>>> RX packets 9903 bytes 1088621 (1.0 MiB) >>>> RX errors 0 dropped 0 overruns 0 frame 0 >>>> TX packets 7786 bytes 1087223 (1.0 MiB) >>>> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >>>> >>>> That hardware address - the 18:8a:7e corresponds with what the IPv6 >>>> address >>>> is suppose to be. But that's not the address it is grabbing, despite the >>>> fact that net.ipv6.conf.all.use_tempaddr = 0 is set. >>>> >>>> I'm seriously wondering if the real issue is a mis-configured dhcp server >>>> in >>>> their London facility because nothing makes sense. >>>> >>>> journalctl -u NetworkManager >>>> >>>> reports no journal entries found. >>>> >>> >>> So are you not using NetworkManager then? there should be some logs ... >>> >>> >>>> I think the problem must be on their end. >>>> >>>> It all was working fine until they migrated the VM because of a hardware >>>> issue, and I suspect now all the hardware address privacy stuff being the >>>> issue is barking up the wrong tree because all the reading I have done >>>> seems >>>> to indicate that with >>>> >>>> net.ipv6.conf.all.use_tempaddr = 0 >>>> >>>> that a fake temporary hardware address would not be sent to their dhcp >>>> server when obtaining the address, but the real one, that should be >>>> fetching >>>> my assigned address. >>> >>> >>> Only if the kernel is doing SLAAC ... if other things (eg NM) are >>> handling it directly they may act differently ... but then from the >>> lack of logs is NM actually handling this? >>> >>> Does systemctl status NetworkManager show it running and does nmcli >>> show anything? >>> >> >> systemctl status NetworkManager >> ● NetworkManager.service - Network Manager >> Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; >> vendor preset: enabled) >> Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago >> >> * more stuff * >> >> nmcli >> eth0: connected to Wired connection 1 >> "Red Hat Virtio network device" >> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >> ip4 default, ip6 default >> inet4 178.79.185.217/24 >> route4 178.79.187.246/32 >> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >> inet6 fe80::a8ad:d312:4ef4:7272/64 >> route6 2a01:7e00::/64 >> >> * more stuff for other interfaces * >> >> -=- >> >> The output of >> >> sysctl -a | grep net.ipv6 : >> >> https://librelamp.com/sysctl.txt >> >> It looks from that like it should not be hiding the real MAC address. >> > > > do nmcli conn show "Wired connection 1" > > the entries of interest are: > > ipv6.ip6-privacy > ipv6.addr-gen-mode > > man nm-settings to get what they mean > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: stable-privacy

9 years, 1 month

Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd

by Terre Porter

I have the latest bios installed - DMI: MICRO-STAR INTERNATIONAL CO.,LTD MS-7596/785GM-E51 (MS-7596), BIOS V2.12 02/18/2011 However, I just used the ELRepo to install kernel-ml (Linux version 3.11.4-1.el6.elrepo.x86_64) and it shuts down fine,.. Of course, it has other errors - lol So I'm leaning toward it’s a kernel bug with these kernel-2.6.32-358.18.1.el6.x86_64 and kernel-2.6.32-358.el6.x86_64 (the two installed by default) Now I'm going to try to locate the kernel version list so I can see if I can get a smaller jump in version up to test with. kernel-ml-3.11.4-1.el6.elrepo.x86_64 worked as expected on the shutdown, but has some other issues. -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of James A. Peltier Sent: Friday, October 11, 2013 6:58 PM To: CentOS mailing list Subject: Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd Update your BIOS if there is one. I've found that to often be the cause. ----- Original Message ----- | Same result, doesn't turn off. | | Any other ideas? | | -----Original Message----- | From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On | Behalf Of Andrew Wyatt | Sent: Friday, October 11, 2013 4:41 PM | To: CentOS mailing list | Subject: Re: [CentOS] Centos 6.4 - doesnt power off with | shutdown/poweroff cmd | | Try using the reboot=pci grub parameter. | | | On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter | <tporter(a)webpage-builders.com | > wrote: | | > Hello, | > | > | > | > I'm looking for help figuring out why I am having problems with | > shutting down a machine. | > | > | > | > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's | > and both power down without issues. | > | > | > | > I added acpi.debug_level=1 to the grub boot as it was suggested to | > see more info about ACPI in the logs | > | > | > | > I found the following ACPI Errors in the /var/log/messages | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] | > Namespace lookup failure, AE_NOT_FOUND | > | > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method | > parse/execution failed [\] (Node ffffffff81fdbeb0), AE_NOT_FOUND | > | > | > | > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io | > 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] | > | > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available | > for this device, you should use it instead of the native driver | > | > | > | > I used the Centos 6.4 Live CD last night with no hard drive in the | > system. | > | > | > | > I photo'd the shutdown, here is the type up: | > | > | > | > Sending all processes the TERM signal... | > | > Sendng all processes the KILL signal... | > | > Saving random seed: | > | > Syncing hardware clock to system time | > | > Turning off quotas: | > | > umount2: Device or resource busy | > | > umount: /dev/.initramfs/live: device is busy. | > | > (In some cases useful info about processes that use | > | > the device is found by lsof(8) or fuser(11)) | > | > init: Re-executing /sbin/init | > | > Halting System... | > | > r8169 0000:02:00.0: PME# enabled | > | > ACPI: Preparing to enter system sleep state S5 | > | > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, | > AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed | > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] | > (Node ffff88019d043560), AE_NOT_FOUND | > | > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] | > (Node ffff88019dbcf9e8), AE_NOT_FOUND | > | > Disabling non-boot CPUS... | > | > SMP alternatives: switching to UP code | > | > Power Down. | > | > acpi_power_off called | > | > | > | > The system doesn't power off, it just sits there. I have to hold the | > power button in for it to shut down. | > | > | > | > The same still occurs with a completed a fresh minimum install of | > Centos 6.4, installed the EPEL repo and did yum update. | > | > | > | > I'm running the latest bios for the motherboard, and even tried | > going back one version. | > | > | > | > MB: 785GM-E51 (MS-7596 1.2) | > | > CPU: AMD Phenom II x4 945 3ghz | > | > 1TB HD, 6 Gig Mem | > | > | > | > Any ideas? | > | > | > | > (Besides using a baseball bat - I am considering it) | > | > | > | > Here is some hardware info from the getinfo.sh script listed the | > forums. | > | > | > | > == BEGIN uname -rmi == | > | > 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64 | > | > == END uname -rmi == | > | > | > | > == BEGIN rpm -qa \*-release\* == | > | > centos-release-6-4.el6.centos.10.x86_64 | > | > epel-release-6-8.noarch | > | > == END rpm -qa \*-release\* == | > | > | > | > == BEGIN cat /etc/redhat-release == | > | > CentOS release 6.4 (Final) | > | > == END cat /etc/redhat-release == | > | > | > | > == BEGIN getenforce == | > | > Enforcing | > | > == END getenforce == | > | > | > | > == BEGIN rpm -qa kernel\* | sort == | > | > kernel-2.6.32-358.18.1.el6.x86_64 | > | > kernel-2.6.32-358.el6.x86_64 | > | > kernel-firmware-2.6.32-358.18.1.el6.noarch | > | > == END rpm -qa kernel\* | sort == | > | > | > | > == BEGIN lspci -nn == | > | > 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host | > Bridge [1022:9601] | > | > 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 | > PCI to PCI bridge (int gfx) [1022:9602] | > | > 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 | > PCI to PCI bridge (PCIE port 1) [1022:9605] | > | > 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] | > | > 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] | > | > 00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0 USB OHCI1 Controller [1002:4398] | > | > 00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] | > | > 00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] | > | > 00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0 USB OHCI1 Controller [1002:4398] | > | > 00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396] | > | > 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 | > SMBus Controller [1002:4385] (rev 3c) | > | > 00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] | > | > 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI | > SBx00 Azalia (Intel HDA) [1002:4383] | > | > 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] | > | > 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI | > SBx00 | > PCI to PCI Bridge [1002:4384] | > | > 00:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI | > SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399] | > | > 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h | > Processor HyperTransport Configuration [1022:1200] | > | > 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h | > Processor Address Map [1022:1201] | > | > 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h | > Processor DRAM Controller [1022:1202] | > | > 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h | > Processor Miscellaneous Control [1022:1203] | > | > 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h | > Processor Link Control [1022:1204] | > | > 01:05.0 VGA compatible controller [0300]: Advanced Micro Devices | > [AMD] nee ATI RS880 [Radeon HD 4200] [1002:9710] | > | > 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. | > RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] | > (rev | > 03) | > | > == END lspci -nn == | > | > | > | > | > | > | > | > _______________________________________________ | > CentOS mailing list | > CentOS(a)centos.org | > http://lists.centos.org/mailman/listinfo/centos | > | _______________________________________________ | CentOS mailing list | CentOS(a)centos.org | http://lists.centos.org/mailman/listinfo/centos | | _______________________________________________ | CentOS mailing list | CentOS(a)centos.org | http://lists.centos.org/mailman/listinfo/centos | -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.sfu.ca/itservices “A successful person is one who can lay a solid foundation from the bricks others have thrown at them.” -David Brinkley via Luke Shaw _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

12 years, 6 months

Re: [CentOS] Fwd: Re: SELinux triggered during Libvirt snapshots

by Daniel J Walsh

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/17/2011 03:40 PM, Trey Dockendorf wrote: > > On Oct 17, 2011 2:06 PM, "Daniel J Walsh" <dwalsh(a)redhat.com > <mailto:dwalsh@redhat.com>> wrote: >> > On 10/17/2011 02:09 PM, Trey Dockendorf wrote: >> On Oct 17, 2011 10:30 AM, "Daniel J Walsh" <dwalsh(a)redhat.com >> <mailto:dwalsh@redhat.com> <mailto:dwalsh@redhat.com >> <mailto:dwalsh@redhat.com>>> wrote: > >> On 10/17/2011 11:19 AM, Trey Dockendorf wrote: >>> Forwarding back to list. ---------- Forwarded message >>> ---------- From: "Trey Dockendorf" <treydock(a)gmail.com >>> <mailto:treydock@gmail.com> <mailto:treydock@gmail.com >>> <mailto:treydock@gmail.com>>> Date: Oct >> 17, 2011 10:06 AM Subject: >>> Re: [CentOS] SELinux triggered during Libvirt snapshots To: >>> "Daniel J Walsh" <dwalsh(a)redhat.com <mailto:dwalsh@redhat.com> >> <mailto:dwalsh@redhat.com <mailto:dwalsh@redhat.com>>> > > > >>> On Mon, Oct 17, 2011 at 7:47 AM, Daniel J Walsh >>> <dwalsh(a)redhat.com <mailto:dwalsh@redhat.com> >> <mailto:dwalsh@redhat.com <mailto:dwalsh@redhat.com>>> wrote: > >>> On 10/14/2011 08:17 PM, Trey Dockendorf wrote: >>>>>> I recently began getting periodic emails from SEalert >>>>>> that SELinux is preventing /usr/libexec/qemu-kvm >>>>>> "getattr" access from the directory I store all my >>>>>> virtual machines for KVM. >>>>>> >>>>>> All VMs are stored under /vmstore , which is it's own >>>>>> mount point, and every file and folder under /vmstore >>>>>> currently has the correct context that was set by doing >>>>>> the following: >>>>>> >>>>>> semanage fcontext -a -t virt_image_t "/vmstore(/.*)?" >>>>>> restorecon -R /vmstore >>>>>> >>>>>> So far I've noticed then when taking snapshots and also >>>>>> when using virsh to make changes to a domain's XML file. >>>>>> I haven't had any problems for the 3 or 4 months I've >>>>>> run this KVM server using SELinux on Enforcing, and so >>>>>> I'm not really sure what information is helpful to debug >>>>>> this. The server is CentOS 6 x86_64 updated to CR. This >>>>>> is the raw audit entry, (hostname removed) >>>>>> >>>>>> node=kvmhost.tld type=AVC msg=audit(1318634450.285:28): >>>>>> avc: denied { getattr } for pid=1842 comm="qemu-kvm" >>>>>> name="/" dev=dm-2 ino=2 >>>>>> scontext=system_u:system_r:svirt_t:s0:c772,c779 >>>>>> tcontext=system_u:object_r:fs_t:s0 tclass=filesystem >>>>>> node=kvmhost.tld type=SYSCALL >>>>>> msg=audit(1318634450.285:28): arch=c000003e syscall=138 >>>>>> success=no exit=-13 a0=9 a1=7fff1cf153f0 a2=0 >>>>>> a3=7fff1cf15170 items=0 ppid=1 pid=1842 auid=4294967295 >>>>>> uid=107 gid=107 euid=107 suid=107 fsuid=107 egid=107 >>>>>> sgid=107 fsgid=107 tty=(none) ses=4294967295 >>>>>> comm="qemu-kvm" exe="/usr/libexec/qemu-kvm" >>>>>> subj=system_u:system_r:svirt_t:s0:c772,c779 key=(null) >>>>>> >>>>>> I've attached the alert email as a quote below, >>>>>> (hostname removed) >>>>>> >>>>>> Any help is greatly appreciated, I've had to deal little >>>>>> with SELinux fortunately, but at the moment am not >>>>>> really sure if my snapshots are actually functional or if >>>>>> this is just some false positive. >>>>>> >>>>>> Thanks - Trey >>>>>> >>>>>> Summary >>>>>>> >>>>>>> SELinux is preventing /usr/libexec/qemu-kvm "getattr" >>>>>>> access on /vmstore. >>>>>>> >>>>>>> Detailed Description >>>>>>> >>>>>>> SELinux denied access requested by qemu-kvm. It is not >>>>>>> expected that this >>>>>>>> access is required by qemu-kvm and this access may >>>>>>>> signal an intrusion attempt. It is also possible >>>>>>>> that the specific version or configuration of the >>>>>>>> application is causing it to require additional >>>>>>>> access. >>>>>>> >>>>>>> Allowing Access >>>>>>> >>>>>>> You can generate a local policy module to allow this >>>>>>> access - see FAQ >>>>>>>> Please file a bug report. >>>>>>> >>>>>>> Additional Information >>>>>>> >>>>>>> Source Context: >>>>>>> system_u:system_r:svirt_t:s0:c772,c779 >>>>>>> >>>>>>> Target Context: system_u:object_r:fs_t:s0 >>>>>>> >>>>>>> Target Objects: /vmstore [ filesystem ] >>>>>>> >>>>>>> Source: qemu-kvm >>>>>>> >>>>>>> Source Path: /usr/libexec/qemu-kvm >>>>>>> >>>>>>> Port: <Unknown> >>>>>>> >>>>>>> Host: kvmhost.tld >>>>>>> >>>>>>> Source RPM Packages: qemu-kvm-0.12.1.2-2.160.el6_1.8 >>>>>>> >>>>>>> Target RPM Packages: >>>>>>> >>>>>>> Policy RPM: selinux-policy-3.7.19-93.el6_1.7 >>>>>>> >>>>>>> Selinux Enabled: True >>>>>>> >>>>>>> Policy Type: targeted >>>>>>> >>>>>>> Enforcing Mode: Enforcing >>>>>>> >>>>>>> Plugin Name: catchall >>>>>>> >>>>>>> Host Name: kvmhost.tld >>>>>>> >>>>>>> Platform: Linux kvmhost.tld >>>>>>> 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27 >>>>>>>> 19:49:27 BST 2011 x86_64 x86_64 >>>>>>> >>>>>>> Alert Count: 1 >>>>>>> >>>>>>> First Seen: Fri Oct 14 18:20:50 2011 >>>>>>> >>>>>>> Last Seen: Fri Oct 14 18:20:50 2011 >>>>>>> >>>>>>> Local ID: c73c7440-06ee-4611-80ac-712207ef9aa6 >>>>>>> >>>>>>> Line Numbers: >>>>>>> >>>>>>> Raw Audit Messages : >>>>>>> >>>>>>> >>>>>>>> node=kvmhost.tld type=AVC >>>>>>>> msg=audit(1318634450.285:28): avc: denied { getattr >>>>>>>> } for pid=1842 comm="qemu-kvm" name="/" dev=dm-2 >>>>>>>> ino=2 >>>>>>>> scontext=system_u:system_r:svirt_t:s0:c772,c779 >>>>>>>> tcontext=system_u:object_r:fs_t:s0 tclass=filesystem >>>>>>> >>>>>>> node=kvmhost.tld type=SYSCALL >>>>>>> msg=audit(1318634450.285:28): arch=c000003e >>>>>>>> syscall=138 success=no exit=-13 a0=9 a1=7fff1cf153f0 >>>>>>>> a2=0 a3=7fff1cf15170 items=0 ppid=1 pid=1842 >>>>>>>> auid=4294967295 uid=107 gid=107 euid=107 suid=107 >>>>>>>> fsuid=107 egid=107 sgid=107 fsgid=107 tty=(none) >>>>>>>> ses=4294967295 comm="qemu-kvm" >>>>>>>> exe="/usr/libexec/qemu-kvm" >>>>>>>> subj=system_u:system_r:svirt_t:s0:c772,c779 >>>>>>>> key=(null) >>>>>>> >>>>>>> >>>>>>> >>>>>> _______________________________________________ CentOS >>>>>> mailing list CentOS(a)centos.org >>>>>> <mailto:CentOS@centos.org> >> <mailto:CentOS@centos.org <mailto:CentOS@centos.org>> >>>>>> http://lists.centos.org/mailman/listinfo/centos > > >>> THis is a bug in policy. It can be allowed for now. > >>> We have 6.2 selinux-policy preview package available on >>> http://people.redhat.com/dwalsh/SELinux/RHEL6 > >>> I believe all that is happening is qemu-kvm is noticing you >>> have a file system mounted, and doing a getattr on it. > > >>> Thanks for the help Dan. Is there something that could have >>> triggered this between 6.0 and 6.1? This server was updated >>> to 6.0 CR around the same time this began happening, so I want >>> to make sure if it's an issue in CR that I can file a useful >>> bug report. > >>> When updating selinux-policy, do I have to update all the RPMs >>> listed or will that one package suffice? > >>> Thanks - Trey _______________________________________________ >>> CentOS mailing list CentOS(a)centos.org >>> <mailto:CentOS@centos.org> >> <mailto:CentOS@centos.org <mailto:CentOS@centos.org>> >>> http://lists.centos.org/mailman/listinfo/centos > >> Did you add additional file systems? > >> Not after the upgrade. The same filesystems were in place using >> 6.0 and 6.0 CR. The only change was the upgrade to CR. > >> - Trey > > > Well I have no idea. Anyways it is not a problem allowing this > access. > > What do I have to do to allow that access? Or should I update to > the selinux-policy you linked ? Ive had little in the way of > experience with selinux so this is all new. > > Thanks - Trey > You can allow it by executing the following as root. # grep svirt /var/log/audit/audit.log | audit2allow -M mysvirt # semodule -i mysvirt.pp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6dcVYACgkQrlYvE4MpobPduQCfZyY00S+74FBlLFqsBbk5bX5R YKIAnjM+/Gb2H7BUgqKbn6xPVJARrkii =uazZ -----END PGP SIGNATURE-----

14 years, 5 months

Jump to page: