April 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] su/sudo pam errors in log files
by Otto Rodusek 16 Apr '14

16 Apr '14

Hi ListMates, I've been using OpenSuse 13.1 x86_64 for some time now and everything seems fine. However, after taking a closer look at my logs I noticed the following errors (warnings?) ever time I use the su or sudo commands. The commands seem to work and execute properly but each time generate the following in my logs: 2014-04-02T12:00:10.328293+08:00 xxxxx sudo: pam_systemd(sudo:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR or 2014-04-02T12:00:18.625093+08:00 xxxxx su: pam_systemd(su-l:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR I tried to google but to little/no avail with any info. Has anyone else seen this and is it something I need concern myself with? Thanks and best regards. Otto. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Problem - OpenSSL 1.0.1g Fix and OpenSuSE 12.1
by andreil1 16 Apr '14

16 Apr '14

Hi, I have an old OpenSuSE 12.1 which is quite difficult to upgrade due to very complex setup. In order to upgrade to the latest OpenSSL without Heartbleed bug, I had used this repository: http://download.opensuse.org/repositories/home:/aljex/openSUSE_12.1/ However, after upgrade BIND stopped working, with message: Apr 15 15:19:31 SRV named[2463]: error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(/usr/lib/engines/libgost.so): /usr/lib/engines/libgost.so: cannot open shared object file: No such file or directory Apr 15 15:19:31 SRV named[2463]: error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: Apr 15 15:19:31 SRV named[2463]: error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: Apr 15 15:19:31 SRV named[2463]: error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:418:id=gost Apr 15 15:19:31 SRV named[2463]: initializing DST: crypto failure Apr 15 15:19:31 SRV named[2463]: exiting (due to fatal error) Apr 15 15:19:31 SRV named[1722]: Starting name server BIND ..failed Looks like CryptoDev module can't be loaded anymore. Additionally, there seem to be a problem with Apache / PHP. Anyone have any idea about upgrade path? Apart from OpenSSL / ssh packages, what else need to be upgraded / installed ? Thanks in advance for any suggestion(s). Andrei -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 8

[opensuse] mdadm man page is bad too
by Felix Miata 15 Apr '14

15 Apr '14

Like most man pages, examples that would clarify meanings are absent. What does that last parameter mean exactly in the following example I found Googling? mdadm --assemble /dev/md/alpha --name=alpha --update=name /dev/sd[fg] I want to change the name of /dev/md1 from what it is now to something else. /dev/md1 is made from /dev/sda15 and /dev/sdb15 using v1.0 metadata. This is its detail: /dev/md7: Version : 1.0 Creation Time : Sun Apr 15 16:41:25 2012 Raid Level : raid1 Array Size : 156280216 (149.04 GiB 160.03 GB) Used Dev Size : 156280216 (149.04 GiB 160.03 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Sat Apr 12 00:34:16 2014 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : big31:7 (local to host big31) UUID : 922adc12:0bb3652b:d6259dfa:37406525 Events : 440 Number Major Minor RaidDevice State 0 8 15 0 active sync /dev/sda15 1 8 31 1 active sync /dev/sdb15 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 8

[opensuse] Heartbleed Bug - for all internet users - get your head out of the sand
by Greg Freemyer 14 Apr '14

14 Apr '14

Just changing the subject line and re-sending. The old subject implied it was openSUSE 12.1 specific. This is likely the biggest security event in the Internet's history. 99% or more of all Internet users will have to develop their own PERSONAL remediation plan and follow it. That is true of Google/Amazon/etc., but it also includes every user that conducts secure transactions across the Internet. Think about and banks, stores, ISPs, SAAS providers, etc. you interact with. Most problematic will be the 70+ year old that manages their financial holdings via the Internet. They need to follow steps to ensure everything they thought was secure last week is still believed secure this week. I don't even know enough yet to implement my own remediation plan, but here's a 3-line example out of it: 1 - change bank online password immediately 2 - verify bank was either never susceptible to the heartbleed bug, or that they have remediated it. 3 - once 2) is done, change the password again since it may have been breached between steps 1 & 2. I have no idea how to implement step 2. Now magnify that issue for every internet based account I have that I login into. So that very undefined plan addresses internet passwords. Next, every credit card transaction conducted over the internet during the last 2 years should be considered potentially breached, so all credit cards / ATM cards need to be re-issued with new cards. What about PINs? Do they need to be changed? I don't know. I'm not saying you need to run around like chicken little, but if you think you just have to get the latest security patches and go on with your life, you're wrong. If you use SSL to serve secure data, keep reading: ---------- Forwarded message ---------- From: Greg Freemyer <greg.freemyer(a)gmail.com> Date: Thu, Apr 10, 2014 at 9:40 AM Subject: Re: [opensuse] SuSE 12.1 and Heartbleed Bug To: opensuse(a)opensuse.org On April 10, 2014 4:45:16 AM EDT, Dsant <forum(a)votreservice.com> wrote: >Le 10/04/2014 01:22, Cristian Rodríguez a écrit : >> >> El 09/04/14 19:53, Matt Darnell escribió: >> >> Fixes has been released already for 13.1.. zypper patch is your best >> friend >Will "zypper up" be enough ? >Or within some time ? This is a critical bug/vulnerability with huge impacts. Maybe the worst to ever effect Linux, but it only affects the server side of a SSL connection as I understand it. For most opensuse users it is not an issue from an admin perspective. As users of the internet, this bug means everything transferred across the internet in the last 2 years that depended solely on SSL for security should be considered potentially breached. That assumes the server end of the connection was running a vulnerable version of openSSL, but as normal users you have to assume that. That means the best practice for all users (including MS users) is to change all passwords used on the internet and watch credit info closely. Then give your internet providers (isps/SAAS providers/banks/stores/auction sites) some time to fix their end and do it all again. I don't know how to test those providers to see if they are secure or not. I'm sure guidance will be forthcoming. Assuming you are running a server serving encrypted data via openSSL: Zypper up should be a superset of zypper patch, so yes it should get it but if this is important to you then don't just assume it will work. Get the openSSL patch, install it and read the description of the installed patch to make sure you have it. Then, if it is important to you, you have a security key you use in conjunction with openSSL to serve secure data. You should consider your key breached. That means that key needs to be replaced with a new one. That is manual work and you may have to go buy a new one if it is a registered key. It should be done after you get the openSSL security patch installed on every machine in your network that uses the same key and openSSL. Normally that is only one machine, but some web farms share a key between machines. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

16 54

[opensuse] OpenSUSE Documentation is Bad
by Lars Kruczynski 14 Apr '14

14 Apr '14

Hi, I have noticed that the documentation for openSuse is terribly organized and in many cases outdated. For a newcomer who visits opensuse.org, the first thing they have to click on to get help is "Discover It", which is not very relevant to directing someone new to the wiki. There should be simple designations, such as "Help", "Wiki", "Support" on the main page, or something as such. Once you click on "Discover it", you're directed to a page with a hodgepodge discombobulated kerfuffle of information a new person to openSUSE is most likely not going to find useful. When you click on "Discover It" and are taken to "Main_Page", the title "Main Page" should be titled something relevant. On the main page, the topics "Project" and "Distribution" don't have to be in separate sections, and why is "Wiki" at the bottom? That makes zero sense. I can't even begin to touch on the problems with the complete mess the entire wiki is, but let's do an example. I'm a new user, and I click on "Discover It". How does it make any sense that when clicking on "Discover It" and being taken to the Main_Page wiki, that when clicking on the "wiki" link on the left sidebar, you're then taken to "Wiki > Portal:Wiki"? So, now we're in "Portal:Wiki". We're displaed with a big long mess of explaining structure. How is this relvant to helping a new user, or even an experienced one? It isn't. In the right pain, we're shown "help pages" and "Navigation". So, if the new user got this far which they probably haven't, let's say they click on "13.1" in the right sidebar, because that's the version they have installed or are having trouble installing. We learn that openSUSE is "stabilized", "networked", "evolved", "polished", and the list goes on. That's all find and dandy, but now the user has to scroll all the way down to the bottom of the page to actually find something which may be relevant to the problem they are having. Let's say the use is having a problem with PulseAudio. Nothing relevant to PulseAudio can be found, and still to this day, I can't find where the documentation to PulseAudio is without searching for it on Google. Getting support for openSUSE shouldn't be this painstakingly difficult, and there needs to be be a discussion had about how awful it is right now. If the documentation is bad, people aren't going to want to use the distribution. I am doing some edits to pages in order to improve the ones written in broken English, but I am one little guy and I am unable to do it all myself. There needs to be a concerted effort to get the documentation better than any other distribution, and the stuff needs to be easy to find, easy to navigate, and easy to read. I don't have access to the Main Page, but this is the first thing that needs improvement, and the "Discover It" needs to go. Thank you, Lars Kruczynski -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 8

[opensuse] Pesky Red entries in Yast
by John Andersen 14 Apr '14

14 Apr '14

Having cut over to the CURRENT KDE repositories, I have some packages that are offered both by KDE and some portion of Opensuse. These show up in YAST as red version numbers "(installed)available" and the version from KDE Current is invariably the one listed as Available, and it is a LOWER version than the currently installed one. One (of many) examples: SCANLITE Alternate Version_____________________________Installed Version Version: 1.1-4.1 1.1-4.3 Build Time: Sat 29 Mar 2014 02:29:28 AM PDT Sun 12 Jan 2014 08:46:33 PM PST Now I would expect that the KDE version would be the latest, because that repository is newer, and the build time is later than the version that is installed. But because someone is playing fast and loose with the version numbers, the older one has a later version number. That older version came from repository KDE:Extra / KDE_Release_412_openSUSE_12.3 PRIOR to the creation and publication of the CURRENT kde extra repositories. Why is this? Why does the old (no longer visible) KDE EXTRA repository have newer versions than the NEWly created CURRENT branch? What should be done with the RED Yast entries? Just ignore them in the hopes that they eventually sort themselves out? (Some NEVER will, because the version numbers differ so wildly). -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] How to autostart MariaDB
by Vojtěch Zeisek 14 Apr '14

14 Apr '14

Hi, after upgrade of our server to 13.1 I finally decided to switch from MySQL to MariaDB. I uninstalled MySQL packages and installed MariaDB. No problem, it works fine, including automysqlbackup and other tools. I just wonder how to start the DB automatically during computer boot. # rpm -qa | grep mysql php5-pear-MDB2_Driver_mysql-1.4.1-14.1.1.noarch php5-mysql-5.4.20-4.1.x86_64 libmysqlclient18-5.5.33-2.2.x86_64 perl-DBD-mysql-4.021-6.1.3.x86_64 # rpm -qa | grep mariadb mariadb-client-5.5.33-2.2.x86_64 mariadb-5.5.33-2.2.x86_64 mariadb-tools-5.5.33-2.2.x86_64 mariadb-errormessages-5.5.33-2.2.x86_64 # systemctl enable mysql.service mysql.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig mysql on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). Well, I added /bin/systemctl start mysql.service to /etc/rc.d/boot.local and it works, but I think, this isn't the desired solution... ;-) Any idea why systemctl enable doesn't work? It worked fine for original MySQL. Have a nice day, Vojtěch -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux http://www.opensuse.org/ http://trapa.cz/

3 16

[opensuse] btrfs howto
by Michael Dunsavage 13 Apr '14

13 Apr '14

I have a ssd drive with /boot and / on it and 2 3TB drives formatted in BTRFS. One has /home and /pub on it the other is blank that I want to use for the mirror. Is there a howto any where on how to set this up? -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] new 13.1 DVD installation would not autostart rpcbind
by Felix Miata 13 Apr '14

13 Apr '14

I've been in the habit since long before systemd replaced sysvinit of doing most installations via HTTP, since most have been from various Factory incarnations rather than GA releases. These I start from Grub, with stanzas that include network configuration. Consequently, YaST uses this configuration for the installed network, giving me functional network in all cases in which network is not generally broken. NFS was never configured to autostart that I can recall, but it was always easy enough to fix via 'chkconfig [rpcbind,nfs,nfsserver] on'. I have more than a dozen 13.1 installations, all of which are autostarting rpcbind. Last night I started the same way, except the source was the 13.1 iso file on HD instead of an HTTP URL. Apparently YaST totally ignored the cmdline network configs, including net.ifnames=0, and set up DHCP on enp3s0 instead of fixed on eth0. In spite of my attempts to get rpcbind to start automatically via systemctl, it simply wouldn't. 'systemctl enable rpcbind' produced no result. Until I started rpcbind myself, I couldn't mount NFS resources. After hours of frustration hunting for clues and rebooting, I tried 'systemctl enable rpcbind' again, and now it is working as expected. ******** Why doesn't YaST at installation time configure rpcbind to start automatically if any packages depending on it are installed? e.g. nfs-kernel-server? ******** tails from dmesg, localmessages, messages, warn, all prior to 'systemctl enable rpcbind' producing a positive result: http://fm.no-ip.com/Tmp/Linux/mtail-big31-os131.txt # systemctl list-units | egrep 'nfs|inet|rpc' sys-devices-pci...net-eth0.device loaded active plugged RTL8101E/RTL8102E PCI Express Fast Ethernet controller sys-subsystem-net-devices-eth0.device loaded active plugged RTL8101E/RTL8102E PCI Express Fast Ethernet controller proc-fs-nfsd.mount loaded active mounted /proc/fs/nfsd var-lib-nfs-rpc_pipefs.mount loaded active mounted /var/lib/nfs/rpc_pipefs network.service loaded active exited LSB: Configure network interfaces and set up routing network(a)eth0.service loaded active exited ifup managed network interface eth0 nfs.service loaded failed failed LSB: NFS client services nfsserver.service loaded failed failed LSB: Start the kernel based NFS daemon system-network.slice loaded active active system-network.slice network.target loaded active active Network # systemctl status rpcbind rpcbind.service - RPC Bind Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; disabled) Active: inactive (dead) # systemctl status nfs nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: failed (Result: exit-code) since Sat 2014-04-12 20:37:51 EDT; 4min 31s ago Process: 1192 ExecStart=/etc/init.d/nfs start (code=exited, status=3) nfs[1192]: Starting NFS client services:portmap/rpcbind is not running systemd[1]: nfs.service: control process exited, code=exited status=3 systemd[1]: Failed to start LSB: NFS client services. systemd[1]: Unit nfs.service entered failed state. # systemctl status nfsserver nfsserver.service - LSB: Start the kernel based NFS daemon Loaded: loaded (/etc/init.d/nfsserver) Active: failed (Result: exit-code) since Sat 2014-04-12 20:37:51 EDT; 4min 34s ago Process: 1199 ExecStart=/etc/init.d/nfsserver start (code=exited, status=7) CGroup: /system.slice/nfsserver.service └─1227 /usr/sbin/rpc.idmapd -p /var/lib/nfs/rpc_pipefs rpc.mountd[1230]:Could not make a socket: (97) Address family not supported by protocol rpc.mountd[1230]:Could not bind socket: (98) Address already in use rpc.mountd[1230]:Could not make a socket: (97) Address family not supported by protocol rpc.mountd[1230]:Could not make a socket: (97) Address family not supported by protocol rpc.mountd[1230]:mountd: could not create listeners startproc[1229]: startproc: exit status of parent of /usr/sbin/rpc.mountd: 1 nfsserver[1199]: Starting kernel based NFS server: idmapd mountd..failed systemd[1]: nfsserver.service: control process exited, code=exited status=7 systemd[1]: Failed to start LSB: Start the kernel based NFS daemon. systemd[1]: Unit nfsserver.service entered failed state. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Minecraft Not Loading
by Matt Darnell 12 Apr '14

12 Apr '14

[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] Hello, I am new to the mailing-lists so please forgive me if I am in the wrong place. I have read the rules, and anything pertaining to the mailing-list already. I have tried to find a solution to this problem with no solution or answer whatsoever. So here is my problem. Minecraft Launcher 1.3.11 is not seeming to load Minecraft the actual game. I have everything installed running from Terminal. I can give the error codes, and the commands I used if they are needed. I was wondering if anyone could try to explain how exactly I should be running Minecraft on OpenSUSE 13.1 [20:52:11 INFO]: Client> Error: Could not find or load main class net.minecraft.client.main.Main [20:52:11 ERROR]: java.io.IOException: Stream closed [20:52:11 ERROR]: Game ended with bad state (exit code 1) [20:52:11 INFO]: Deleting /home/matt/.minecraft/versions/1.6.4/1.6.4-natives-11828119729505 [20:52:11 INFO]: Ignoring visibility rule and showing launcher due to a game crash Thanks, Matt -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 7