openSUSE Users May 2017

users@lists.opensuse.org

88 participants
95 discussions

by James Knott

When installing Oracle Virtualbox, using files downloaded from Oracle, it is necessary to install the virtual box package, extensions and guest additions. In the openSUSE version, there are virtualbox, desktop icons, host kernel and virtualbox-qt. Is there anything that includes the extensions? I downloaded the guest additions from Oracle. The reason I'm asking is that when I use the openSUSE packages, I can't use USB 2, only 1.1. I could use USB 2 previously, when using the packages from Oracle. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] systemd "ipsec.service" under OpenSUSE Leap 42.1 times-out when stopped

by Martin T

Hi, I installed Libreswan 3.20 to OpenSUSE Leap 42.1(systemd v210). It has a following "ipsec.service" file: # cat /usr/lib/systemd/system/ipsec.service [Unit] Description=Internet Key Exchange (IKE) Protocol Daemon for IPsec Wants=network-online.target After=network-online.target Documentation=man:ipsec(8) man:pluto(8) man:ipsec.conf(5) [Service] Type=notify Restart=always # backwards compatible with plutorestartoncrash=no #RestartPreventExitStatus=137 143 SIGTERM SIGKILL # Set WatchdogSec to the amount of time (in seconds) that systemd will wait # before restarting an unresponsive pluto. # EVENT_SD_WATCHDOG updates the heartbeat every 15 seconds, recommended values # are 60, 90, 120. WatchdogSec=0 disables the action NotifyAccess=all WatchdogSec=200 # Check configuration file ExecStartPre=/usr/lib/ipsec/addconn --config /etc/ipsec.conf --checkconfig # Check for kernel modules ExecStartPre=/usr/lib/ipsec/_stackmanager start # Check for nss database status and migration ExecStartPre=/usr/sbin/ipsec --checknss # Check for nflog setup ExecStartPre=/usr/sbin/ipsec --checknflog # Start the actual IKE daemon ExecStart=/usr/lib/ipsec/pluto --leak-detective --config /etc/ipsec.conf --nofork ExecStop=/usr/lib/ipsec/whack --shutdown ExecStopPost=/sbin/ip xfrm policy flush ExecStopPost=/sbin/ip xfrm state flush ExecStopPost=/usr/sbin/ipsec --stopnflog ExecReload=/usr/lib/ipsec/whack --listen [Install] WantedBy=multi-user.target # There are no issues when I enable and start ipsec.service. However, when I stop("systemctl stop ipsec.service") the service, it hangs: May 17 16:41:54 host systemd[1]: Stopping Internet Key Exchange (IKE) Protocol Daemon for IPsec... May 17 16:41:54 host pluto[14064]: shutting down May 17 16:41:54 host pluto[14064]: "v6neighbor-hole-out": deleting non-instance connection May 17 16:41:54 host whack[14105]: 002 shutting down May 17 16:41:54 host pluto[14064]: "v6neighbor-hole-in": deleting non-instance connection May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:ec4b:109b:437:bd64:500 May 17 16:41:54 host pluto[14064]: shutting down interface lo/lo ::1:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:216:3eff:fe76:5b3c:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:555b:2439:e729:2ce7:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:d42e:5ae2:a7c2:be3:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:f84b:815b:e99d:9419:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:fdc0:2ad0:c5b9:7a9c:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:ec05:426a:e0f6:5a92:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 2001:db8:1400:1:a81f:c62e:663c:a1ee:500 May 17 16:41:54 host pluto[14064]: shutting down interface lo/lo 127.0.0.1:4500 May 17 16:41:54 host pluto[14064]: shutting down interface lo/lo 127.0.0.1:500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 10.10.10.246:4500 May 17 16:41:54 host pluto[14064]: shutting down interface eth0/eth0 10.10.10.246:500 May 17 16:43:24 host systemd[1]: ipsec.service stopping timed out. Terminating. May 17 16:44:54 host systemd[1]: ipsec.service stop-sigterm timed out. Killing. May 17 16:44:54 host systemd[1]: ipsec.service: main process exited, code=killed, status=9/KILL May 17 16:44:54 host systemd[1]: Stopped Internet Key Exchange (IKE) Protocol Daemon for IPsec. May 17 16:44:54 host systemd[1]: Unit ipsec.service entered failed state. As seen above, "systemctl stop ipsec.service" command hang from 16:41:54 to 16:43:24. When I run "systemctl stop ipsec.service" using "strace -f", then I see following messages until systemd kills the process: [pid 16306] recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\4\1\1S\0\0\0\f\0\0\0p\0\0\0\1\1o\0\31\0\0\0", 24}], msg_controllen=32, [{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, {pid=1, uid=0, gid=0}}], msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 24 [pid 16306] recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"/org/freedesktop/systemd1\0\0\0\0\0\0\0"..., 187}], msg_controllen=32, [{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS, {pid=1, uid=0, gid=0}}], msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 187 What might cause such behavior? Can I provide any additional information which helps to troubleshoot this issue? thanks, Martin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] eject behaviour in Leap?

by Dave Howorth

If I plug a device (camera as it happens) into my Leap 42.1 PC, it mounts fine at /run/media/my-username/4DIG-IHEX/ where my-username and 4DIG-IHEX match my username and presumably some hardware dependent ID respectively. So far so good. When the time comes that I've finished with the camera I type $ eject /run/media/my-username/4DIG-IHEX which used to be the preferred thing to do, AIUI, (with the then current path, anyway). But now it says: umount: /run/media/my-username/4DIG-IHEX: umount failed: Operation not permitted Looking at the permisssions I see: $ ls -la /run/media/my-username/4DIG-IHEX drwxr-xr-x 5 my-username users 32768 Jan 1 1970 ./ drwxr-x---+ 6 root root 120 May 16 22:14 ../ and I have to unmount the device as root. So what's wrong? Should I be using some different command to eject the device? If root has to unmount it, why is it automatically mounted by my-username and inaccessible to anybody else? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] Is anyone having issues with fdisk making partitions bigger than the physical drive?

by Greg Freemyer

Details: from Leap 42.2 - Using a Sata-USB bridge Insert a brand new 1TB drive - no partition table - Use fdisk to partition the drive, accept default parameters for partition 1 and let it fill 99.9% of the drive - write out the partition table Use fdisk to see if the partition table is okay: > sudo fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204883968 bytes, 1953525164 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x095da008 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G 83 Linux ======================================================== Looks normal to me. But look at the total sector count for the drive and the end sector of the partition. 1953525167 > 1953525164, so the partition extends past the end of the physical drive? That seems to be the root cause of a couple filesystems becoming non-mountable for me. === drive details sudo hdparm -I /dev/sda /dev/sda: ATA device, with non-removable media Model Number: TOSHIBA HDWD110 Serial Number: 17BS7HGFS Firmware Revision: MS2OA8J0 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0; Revision: ATA8 -AST T13 Project D1697 Revision 0b Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 1953525168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 953869 MBytes device size with M = 1000*1000: 1000204 MBytes (1000 GB) cache/buffer size = unknown Form Factor: 3.5 inch Nominal Media Rotation Rate: 7200 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Advanced power management level: disabled DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Advanced Power Management feature set Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test Media Card Pass-Through * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name * URG for READ_STREAM[_DMA]_EXT * URG for WRITE_STREAM[_DMA]_EXT * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * unknown 119[7] * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * NCQ priority information Non-Zero buffer offsets in DMA Setup FIS DMA Setup Auto-Activate optimization Device-initiated interface power management In-order data delivery * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count not supported: enhanced erase 160min for SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000039fedd8a830 NAA : 5 IEEE OUI : 000039 Unique ID : fedd8a830 Checksum: correct Thanks Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] Fwd: Problem with recent MySQL update, bsc#1020976, permissions on /var/run/mysql, cannot connect to MySQL

by Glen

The recent update to mysql-community-server-5.6.36-24.3.3.x86_64 introduced a change to /usr/lib/mysql/mysql-systemd-helper: # diff mysql-systemd-helper.old mysql-systemd-helper 168a169,171 > # set the default umask bsc#1020976 > umask 077 After this update, and a subsequent serve reboot, the permissions on /var/run/mysql (wherein lives the mysql.sock socket) changed from 0755 to 0700. This promptly caused all of the application software and programs on my servers which communicate with MySQL to fail, with an "unable to connect" error. chmod 755 /var/run/mysql fixed the immediate connection problem, and a very hacky change to systemd: # diff mysql.service.old mysql.service 13a14 > ExecStartPost=/usr/bin/chmod 755 /var/run/mysql has made it persist between reboots.... for now. I have read https://lists.opensuse.org/opensuse-security-announce/2017-04/msg00036.html, which says: > This non-security issue was fixed: > - Set the default umask to 077 in rc.mysql-multi [bsc#1020976] So, I am trying to understand why this change was made (since I don't want to revert something deemed an issue) and what the correct response to this change should be. Should all my apps have "just worked anyway?" Is nobody else experiencing problems? Should I be doing something differently? The programs I run were written by different teams, and run on different servers, and they *all* failed with this patch. I can't believe that I'm the only one affected by this, and am seeking to understand what I'm doing wrong that caused all my software to get tripped up by this change, and what the most correct fixes would be to compensate/adjust on my end. Guidance, pointers, redirects all solicited and gratefully accepted! Thanks so much! Glen Glen Barney -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] Leap 42.2 "Plasma 5 Desktop" and "KDE Desktop Environment" patterns

by Istvan Gabor

Hello: In openSUSE Leap 42.2 what is the difference between installation patterns "Plasma 5 Desktop" and "KDE Desktop Environment"? And, is it possible to install KDE4 in 42.2? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] how to remove extra grub from a tertiary disk?

by listreader

I have a machine with a third / add-on controller. On that controller there is a drive that has a copy of an old windows OS that I need to keep. When I boot normally from my primary drive, grub2 currently offers a boot option for that tertiary drive partition as a 'windows loader' and if I choose it I go right into that windows OS. That's fine. But, when I make that tertiary drive the boot drive (through bios selection) I don't go directly into that windows OS but instead get a grub from an old opensuse 12.3 installation. The 12.3 OS is gone but its grub is still there. So, question is, how do I get rid of that old extra grub on the tertiary disk and replace it with generic code so that it boots whatever the active partition is? FWIW, this machine has many OS installed but main OS boot is Leap 42.1 and DE is LXDE (gtk). Thanks in advance, especially if this is a dumb question :-/ Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] wget and pid

by Istvan Gabor

Hello: I would like to use cron to start and stop wget commands using wget -q (quiet) and -b (background) options. For stopping the correct wget connect at given time I need to know its pid. wget -bq url runs like this: wget -b -q -O output-file url-address Continuing in background, pid 10874. I should somehow record the pid in a file and use it with the kill command, but I don't know how I could do it. Any help would be appreciated. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

[opensuse] Is "ovftool" for converting ova files to vmdk's in the distro?

by Greg Freemyer

All, I have some *.ova files a client gave me. They are a VMware container file. I need to extract out the VMDK file inside. I read the ovftool is the tool for doing that. I don't know if openSUSE has that and if so what package it is in. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

Re: [opensuse] Problem with recent MySQL update, bsc#1020976, permissions on /var/run/mysql, cannot connect to MySQL

by Glen

On Sun, May 14, 2017 at 7:45 AM, Patrick Shanahan <paka(a)opensuse.org> wrote: > * Glen <glenbarney(a)gmail.com> [05-14-17 10:39]: > I am at 20170510 and have no problem with mysql after rebooting to latest > kernel-default build there. you don't say which update caused your > problem, but I didn't see any recent hickup. I apologize. I am running Leap 42.2 on about 24 different servers. Every few weeks I run zypper update to fetch the repo updates. Servers which are still on mysql-community-server-5.6.35-22.1.x86_64 do not exhibit this problem. However, servers which have been updated to mysql-community-server-5.6.36-24.3.3.x86_64 do have the problem. In that update, /usr/lib/mysql/mysql-systemd-helper contains an explicit "umask 077" command, which is tagged with a comment "set the default umask bsc#1020976". The effect of that umask command is to cause /var/run/mysql to be created with 700 permissions when the server reboots (inasmuch as /var/run symlinks to /run which is a tmpfs), and this prevents applications not owned by mysql from reaching the socket and communicating with the database. I am trying to determine how best to adjust to these new permissions, which seem to cut off access to MySQL to all user applications needing MySQL. I hope this answers? Please let me know if I need to provide other detail. Thank you! Glen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 years, 8 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users May 2017