January 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Recent leap second
by Roger Oberholtzer 08 Jan '17

08 Jan '17

At the end of 2016, my openSUSE system reported: Clock: inserting leap second 23:59:60 UTC This always worries me, as there are a number of links in the chain. And it seems any can insert a leap second. I have two configurations on openSUSE systems: Use ntpd to sync time with a time server. My local ntp can be told whether to insert leap seconds. I have to assume that the ntp protocol ensures that the time communicated between systems is properly identified as to whether it has a leap second adjustment or not. gpsd and chrony. gpsd, it seems, can have a compiled-in leap second offset. If I understand this correctly, this offset will be added to the time gpsd makes available to clients. Can the clients know this offset has been added? chrony can also add a leap second, depending on how it is configured. In all cases, I am using openSUSE-compiled binaries. Is there a coordinated discussion of how these apps are compiled and configured (e.g., ntpd via yast)? Especially as relates to leap seconds. Redhat have some info at https://developers.redhat.com/blog/2015/06/01/five-different-ways-handle-le…. But that still does not address how the deliverables are actually configured when compiled and then configured for use. The reason I am so interested is that we have been working to use the system clock (set with gpsd/chrony) to timestamp data via gettimeofday(). That time can be used to locate things in the GPS location data. The GPS time does not have leap seconds. So we are trying to be sure we have not missed anything. The data is collected in a moving vehicle. At 90 km/h, each second of error is 25 meters. So it is a rather important thing to track... Knowing how this is dealt with through the complete openSUSE chain is important. All pointers to information are welcome. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 30

[opensuse] /etc/permissions.d on openSuSE 13.2 / nagvis/mk-livestatus
by Paul Neuwirth 08 Jan '17

08 Jan '17

Hello group, after websearching around, I did not find anything, about this: How are permissions, set in /etc/permissions.* and /etc/permissions.d/* processed? I added a file according to a manual in /etc/permissions.d/, but these permissions do not get applied (after file creation by a daemon). Old documentation/threads mention SuSEconfig, but this tool is not used anymore... How do I apply these settings/ which service needs to be reloaded/restarted? files seem to be handled by chkstat according to rpm -qf .. or is this the wrong point to set this up? in my example, I want to set up apache2/nagvis/mk-livestatus/nagios link, but the socket created by mk-livestatus is set to the wrong group. /usr/share/doc/packages/mk-livestatus/livestatus-README.SUSE recommends to fix it with setting up permissions in /etc/permissions.d/ thank you for any hints -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 14

[opensuse] Problem installing an rpm that uses hardlinks.
by Carlos E. R. 08 Jan '17

08 Jan '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This is an old problem that I had on 13.1 and remains on Leap. YaST fails installing a certain package with an error message that explains nothing (sorry, I didn't copy it). Running rpm directly on it explains just a bit more: Telcontar:~ # rpm --install /var/cache/zypp/packages/OBS_Games/noarch/FlightGear-data-2016.2.1-2.1.noarch.rpm error: unpacking of archive failed on file /usr/share/doc/packages/FlightGear-data/COPYING;586ff82e: cpio: link error: FlightGear-data-2016.2.1-2.1.noarch: install failed Telcontar:~ # So I try trace. Telcontar:~ # strace -ff -o rpmtrace rpm --install --verbose /var/cache/zypp/packages/OBS_Games/noarch/FlightGear-data-2016.2.1-2.1.noarch.rpm ... It seems the problem is here: open("/usr/share/flightgear/Fonts/LiberationFonts/COPYING;586ffa1a", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 20 fcntl(20, F_SETFD, FD_CLOEXEC) = 0 umask(022) = 0777 write(20, "\t\t GNU GENERAL PUBLIC LICENSE"..., 17992) = 17992 close(20) = 0 link("/usr/share/flightgear/Fonts/LiberationFonts/COPYING;586ffa1a", "/usr/share/doc/packages/FlightGear-data/COPYING;586ffa1a") = -1 EXDEV (Invalid cross-device link) lstat("/usr/share/flightgear/Fonts/LiberationFonts/COPYING;586ffa1a", {st_mode=S_IFREG, st_size=17992, ...}) = 0 unlink("/usr/share/flightgear/Fonts/LiberationFonts/COPYING;586ffa1a") = 0 close(19) = 0 munmap(0x7f6916c58000, 4096) = 0 write(2, "error: ", 7) = 7 write(2, "unpacking of archive failed on f"..., 105) = 105 close(18) = 0 write(2, "error: ", 7) = 7 write(2, "FlightGear-data-2016.2.1-2.1.noa"..., 52) = 52 It is trying to link /usr/share/flightgear/Fonts/LiberationFonts/COPYING to /usr/share/doc/packages/FlightGear-data/COPYING or the other way round, and it happens that /usr/share/flightgear is a diferent filesystem here⁽¹⁾: /etc/fstab: LABEL=c_usr_gamedta /usr/gamedata reiserfs acl,user_xattr,barrier=flush,relatime 1 4 and /usr/share/flightgear was a symlink to /usr/gamedata/flightgear/ Seeing the problem, I changed to a bind mount: /etc/fstab: /usr/gamedata/flightgear/ /usr/share/flightgear none bind 0 0 with this 'mount' result: /dev/sdd12 on /usr/gamedata type reiserfs (rw,relatime,user_xattr,acl) /dev/sdd12 on /usr/share/flightgear type reiserfs (rw,relatime,user_xattr,acl) but it is not working. Perhaps I should instead make /usr/share/doc/packages/FlightGear-data/ a symlink or bind mount to somewhere in /usr/gamedata. Ideas? I need another view... (1) The reason to use a different filesystem for FlightGear is that the rpm is 1 GB of data consisting of a ton of very small files (and more that can be downloaded), so ideal for reiserfs. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlhwATkACgkQtTMYHG2NR9UlcQCcDIZ+PHauHYthqlri+HeSZBat sosAoJUY4okOcwWIQicPLcKCAqlpKmvD =1X/X -----END PGP SIGNATURE-----

5 8

[opensuse] Display dimensions
by Jeffrey L. Taylor 08 Jan '17

08 Jan '17

My Lenovo T520 with 1366x768 screen shows the following on 13.2: viajero:~ # xrandr | fgrep '*' 1366x768 60.00*+ viajero:~ # xdpyinfo | grep dimensions dimensions: 2390x768 pixels (631x203 millimeters) This is an zypper dup upgrade from 13.1. It behaves funny with tooltips and menus extending off screen to the right. On 13.1, windows respected Gkrellm's space. On 13.2, new windows will extend behind Gkrellm to the screen's edge. The results above tell me why, but not how to correct it. Any suggestions? TIA, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] ntp synchronizes to broadcast source despite no configuration ??
by Per Jessen 07 Jan '17

07 Jan '17

Trying to disprove Carlos' suggestion that the kernel "knows" about leap seconds, I installed a Leap421 desktop, at first leaving out ntp, then installing it later. To avoid the time being set on startup (with sntp), I created # l `which sntp` lrwxrwxrwx 1 root root 13 Jan 6 18:05 /usr/sbin/sntp -> /usr/bin/true* I was a bit surprised to see ntpd being started with '-g' anyway, which meant setting the time as well, I amend ed/etc/sysconfig/ntp to prevent that. My ntp.config: --------------- server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized driftfile /var/lib/ntp/drift/ntp.drift logfile /var/log/ntp logconfig =all --------------------- Seems to me that ought to be good for a stand-alone ntpd. However, a little while after starting it: # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 127.127.1.0 .LOCL. 10 l 546 64 0 0.000 0.000 0.000 *192.168.2.254 .DCFa. 1 u 66 64 377 0.239 -4.834 4.087 Surely that is not correct. -- Per Jessen, Zürich (-6.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] LXQt installation cannot mount luks volumes
by Stanislav Baiduzhyi 07 Jan '17

07 Jan '17

So, I've finally decided to upgrade from 42.1 to 42.2, and to try LXQt (used LXDE on that machine previously). Everything went fine, but then I could not get LXQt to mount encrypted volumes. Couple of seconds after I turn on external hard drive, the window border appears without a content and just hangs on my desktop. Looking at some logs it showed me that secret service DBus was not found, or something along those lines. I tried installing libsecret and gnome-keyring one by one and then both at the same time, could not fix it. I am back with LXDE now, but would appreciate a link to some guide how to make it work if it is a known issue, so I could try later again. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] knode identity field is grey out (was copying knode identity to new installation)
by Per Jessen 07 Jan '17

07 Jan '17

On Mon, 22 Aug 2016 17:54:00 I wrote: > I know it's a bit of a long shot, but still - I want to copy my knode > config from (a) to (b) - (a) being a current Leap421 system, (b) being > a new one. > I have copied .kde4/share/apps/knode and .kde4/share/config/knoderc, > this seems to have mostly worked, except for my identity setting. > Currently I dont have one, and the field for chaning it is greyed out. > > I obviously missed something? I'm trying the same now - copying a knode client setup from one leap422 to another. Just as above, I have copied .kde4/share/apps/knode and .kde4/share/config/knoderc, this seems to have mostly worked, except for my identity setting. The field for adding an identity in knode is greyed out. I somehow managed to fix this in August, but I simply cannot remember what I did ... I have grepped around the source system (a backup), looking for files that contain the identity information, no luck. -- Per Jessen, Zürich (-4.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Trouble formatting a linux partition
by Terry Eck 07 Jan '17

07 Jan '17

Hello, Hope someone can shine some light on the problem I'm having. I've formatted several drives in the past and have not seen this problem. I'm trying to use a 500G drive which was a linux system with swap. I fdisk to delete all the old partitions and created one single partition. One strange thing is the partition starts at 2048. Had no choice. =========== The following is from fdisk Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 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: gpt Disk identifier: 0x000af975 Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 976773167 976771120 465.8G 83 Linux ============= Try to format it with fsck.ext2 yields: e2fsck 1.43.3 (04-Sep-2016) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc1 The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> /dev/sdc1 contains a swap file system ============= Any ideas how to format this drive for use and a data storage/backup drive? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 29

[opensuse] Raid 1 + Encrypted Btrfs
by Daniel Selinger 06 Jan '17

06 Jan '17

Hi, I have spent some time now trying to set up my notebook with a software raid 1 built from 2 SSDs and encrypted btrfs and so far failed miserably. Sseems the installer doesn't support this combination at all. What i tried: All those attempts have been tried with and without a separate unencrypted /boot and /boot/efi. I only would need encrypted root and home, boot can be unencrpyted if needed. 1) Raid + Encrypted Btrfs When creating btrfs on a raid device, the encryption checkbox is disabled, while it's available for other filesystems. 2) Raid + Encrypted LVM While creating "normal" LVM Partitions has a encryption checkbox, the installer directly uses raid devices in the LVM creation interface, encryption option nowhere to be seen. 3) Raid + Manual cryptsetup I created a raid 1 and did a manual cryptsetup on it. The installer detects the encrypted raid and asks for a password. From there on the installer seems to work as expected. Can create a LVM on the encrypted raid (also the installer shows correcty that it's encrypted), i can create my needed filesystems and the installer completes without errors. Sadly the installed system fails to boot. At this point i've given up and haven't investigated further. I would know how to do all necessary stuff manually i probably manage to make everything boot up, but i don't want to intervene with standard setup too much, as this probably will cause problems with future upgrades / updates. Did i miss something or is it really impossible to combine raid + btrfs+ encryption at the current state of the installer? Best Regards Daniel -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 13

[opensuse] nagcon on openSuSE 13.2
by Paul Neuwirth 06 Jan '17

06 Jan '17

Hello, has anyone a clue what may be broken, package nagcon on my openSuSE 13.2 shows after a refresh just " {obsess} ??? {obsess} ??? {obsess} ??? {obsess} ??? 6 {obsess} ??? {obsess} "... could not find out where the obsess comes from. # zypper if nagcon Loading repository data... Reading installed packages... Information for package nagcon: ------------------------------- Repository: opensuse_monitoring Name: nagcon Version: 0.0.30-2.1 Arch: x86_64 Vendor: obs://build.opensuse.org/server:monitoring Installed: Yes Status: up-to-date Installed Size: 38.6 KiB Summary: Nagios Service Overview Console Description: Nagcon is a console application interfacing to Nagios which gives you an overview of all services with troubled services. The Package seems to be quiet old (last update 6yrs ago), if it's broken, does someone know a good alternative? thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1