October 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] linux rules the world :-)
by jdd＠dodin.org 26 Oct '17

26 Oct '17

was not GKH the launcher of tumbleweed? I remember his wooden kayak :-)) http://www.zdnet.com/article/whos-building-linux-in-2017/?loc=newsletter_fe… jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] systemd stops postfix/nfsserver for false(?) reasons
by Peter Suetterlin 25 Oct '17

25 Oct '17

Hi, I'm running a server on Leap 42.2. Amongst other things, it is mail and NFS server for the home directories. After a reboot today neither postfix nor the nfs server were running. A look at the boot log: Oct 23 07:44:43 royac6 systemd[1]: Stopped Postfix Mail Transport Agent. Oct 23 07:44:43 royac6 systemd[1]: Created slice system-mdadm\x2dlast\x2dresort.slice. Oct 23 07:44:43 royac6 systemd[1]: Starting Activate md array even though degraded... Oct 23 07:44:43 royac6 systemd[1]: Stopped NFS server and services. Oct 23 07:44:43 royac6 systemd[1]: Stopping NFSv4 ID-name mapping service... Oct 23 07:44:43 royac6 systemd[1]: Stopped NFS Mount Daemon. Oct 23 07:44:43 royac6 systemd[1]: Stopped NFSv4 ID-name mapping service. Oct 23 07:44:43 royac6 systemd[1]: Started Activate md array even though degraded. Oct 23 07:44:43 royac6 systemd[1]: Stopped target Local File Systems. Oct 23 07:44:43 royac6 systemd[1]: Unmounting /home... Oct 23 07:44:43 royac6 systemd[1]: Stopped (with error) /dev/md1. Oct 23 07:44:43 royac6 systemd[1]: Unmounted /home. So obviously it is because a 'problem' with the home directories (/home is served by nfs-server, and postfix uses Maildir in the home directories). But /home is mounted... So I looked at that: Oct 23 07:44:09 royac6 kernel: sdb: sdb1 Oct 23 07:44:09 royac6 kernel: sda: sda1 Oct 23 07:44:12 royac6 kernel: md: bind<sda1> Oct 23 07:44:13 royac6 kernel: md: bind<sdb1> Oct 23 07:44:13 royac6 kernel: md/raid1:md1: active with 2 out of 2 mirrors Oct 23 07:44:13 royac6 kernel: created bitmap (8 pages) for device md1 Oct 23 07:44:13 royac6 kernel: md1: bitmap initialized from disk: read 1 pages, set 11 of 15260 bits Oct 23 07:44:13 royac6 kernel: md1: detected capacity change from 0 to 1024061145088 Oct 23 07:44:13 royac6 systemd[1]: Found device /dev/disk/by-uuid/133b616a-1100-4278-86a7-9eb677783e9b. Oct 23 07:44:13 royac6 systemd[1]: Mounting /home... Oct 23 07:44:13 royac6 kernel: EXT4-fs (md1): 1 orphan inode deleted Oct 23 07:44:13 royac6 kernel: EXT4-fs (md1): recovery complete Oct 23 07:44:13 royac6 kernel: EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: discard Oct 23 07:44:13 royac6 systemd[1]: Mounted /home. No further mentions of md1 or /home until the first message block above. A second after the umount I see Oct 23 07:44:44 royac6 systemd[1]: Stopped Timer to wait for more drives before activating degraded array.. Oct 23 07:44:44 royac6 systemd[1]: Found device /dev/disk/by-uuid/133b616a-1100-4278-86a7-9eb677783e9b. Oct 23 07:44:44 royac6 systemd[1]: Mounting /home... What the **** is going on there? Sidenote: It is stopping the nfs and mail services before they even are started... As I don't see any real error message it seems to be some race condition in the systemd dependencies(?), but I'm not sure what to do to locate it. It seems to be the wait timer, but why is it still running? The device is already active, and has all it's disks... Any help appreciated! Pit -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 17

[opensuse] MCE: The hardware reports a non fatal,
by David C. Rankin 24 Oct '17

24 Oct '17

Say it ain't so....: Oct 2 22:40:27 nemesis kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0. Oct 2 22:40:27 nemesis kernel: Bank 1: 9000000000000151 Now where am I going to find another 512M 60ns DIMM SDRAM? I suspect e-bay will be my friend. What's wrong with quality now days. It's only been 15 years since it was installed. They just don't make'm like they used to... for my trusty; Processor Information Socket Designation: Socket A Type: Central Processor Family: Duron Manufacturer: AMD ID: 42 06 00 00 FF F9 83 01 Signature: Family 6, Model 4, Stepping 2 Flags: <snip> Version: AMD Athlon(tm) Voltage: 3.3 V External Clock: 100 MHz Max Speed: 500 MHz Current Speed: 800 MHz Status: Populated, Enabled Upgrade: ZIF Socket (Tbird-800) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 23

[opensuse] 42.3 ignoring router priority
by James Knott 24 Oct '17

24 Oct '17

With IPv6, there can be multiple default routers on a network and there is a priority setting so that one is favoured over another. However, it appears 42.3 is ignoring that prioriy. Here's the output of ip -6 route, which shows both as medium priority. default via fe80::1:1 dev eth0 proto ra metric 1024 expires 57sec hoplimit 64 pref medium default via fe80::216:17ff:fea7:f2d3 dev vlan3 proto ra metric 1024 expires 48sec hoplimit 64 pref medium However, the router on eth0 is set for high priority and on VLAN 3, low. This has been verified with Wireshark captures. So, why is openSuse ignoring that priority? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] google-chrome crash?
by Josef Fortier 24 Oct '17

24 Oct '17

A few days ago chrome quit working on my Leap 42.3 desktop. Starting from a command line shows references to "zygote" fork issues. Most google results seem to be from a while ago. It occurs on a re-install, on all three version from the suse repository and on the official google chrome rpm. This is the output (I'd assume the root cert error is harmless) [1326:1363:1020/121628.684837:ERROR:nss_util.cc(725)] After loading Root Certs, loaded==false: NSS error code: -8018 ATTENTION: default value of option force_s3tc_enable overridden by environment. [1326:1361:1020/121628.792864:ERROR:zygote_communication_linux.cc(146)] Did not receive ping from zygote child [5:5:1020/121628.792981:ERROR:zygote_linux.cc(627)] Zygote could not fork: process_type renderer numfds 6 child_pid -1 .... (more repetitions of the last two lines) Thanks for any help :-) -- __________________________________________________________________________ Josef Fortier Systems Administrator fortier(a)augsburg.edu Phone: 612-330-1479 __________________________________________________________________________ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] recent Popular Science article on linux
by listreader 24 Oct '17

24 Oct '17

Popular Science (magazine/web) recently published an article titled "Why and how you should switch to Linux". Generic but in case anyone is interested, below follows the link. https://www.popsci.com/switch-to-linux-operating-system Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Checking for stray cats?
by David C. Rankin 24 Oct '17

24 Oct '17

All time favorite log entry: mandb[9176]: Checking for stray cats under /usr/share/man/sv... Linux devs are some interesting folks... For the curious: https://unix.stackexchange.com/questions/185359/what-is-the-deal-with-mandb… -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] mcelog: CPU 6 on socket 1 received Bus and Interconnect Errors in Other-transaction
by Chuck Davis 23 Oct '17

23 Oct '17

Hi Michael: I got a Dell Precision 7720 laptop and got these mce messages. Dell support told me it was because the folks doing mce have not included the machine chip in their recognized chips and that there is nothing to worry about. It just means mce does not recognize the chip and when mce gets updated the messages will go away. The laptop I got also has Xeon chip. HTH. On Mon, Oct 23, 2017 at 8:46 AM, Chuck Davis <cjgunzel(a)gmail.com> wrote: > Hi Michael: > > I got a Dell Precision 7720 laptop and got these mce messages. Dell support > told me it was because the folks doing mce have not included the machine > chip in their recognized chips and that there is nothing to worry about. It > just means mce does not recognize the chip and when mce gets updated the > messages will go away. > > The laptop I got also has Xeon chip. > > HTH. > > On Mon, Oct 23, 2017 at 8:10 AM, Michael Hirmke <mh(a)mike.franken.de> wrote: >> >> Hi *, >> >> on my main server after a cold boot I see the following messages in my >> journal: >> >> ... >> kernel: mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 20: >> c8012a4000200e0f >> kernel: mce: [Hardware Error]: TSC 0 mce: MISC 800000 mce: >> kernel: mce: [Hardware Error]: PROCESSOR 0:306f2 TIME 1508767394 SOCKET 1 >> APIC 10 microcode 36 >> mcelog[2635]: CPU 6 on socket 1 received Bus and Interconnect Errors in >> Other-transaction >> mcelog[2636]: Location: CPU 6 on socket 1 >> ... >> systemd[1]: Starting Machine Check Exception Logging Daemon... >> systemd[1]: Started Machine Check Exception Logging Daemon. >> mcelog[2628]: Hardware event. This is not a software error. >> mcelog[2628]: MCE 0 >> mcelog[2628]: CPU 6 BANK 20 >> mcelog[2628]: MISC 800000 >> mcelog[2628]: TIME 1508767394 Mon Oct 23 16:03:14 2017 >> mcelog[2628]: MCG status: >> mcelog[2628]: MCi status: >> mcelog[2628]: Error overflow >> mcelog[2628]: Corrected error >> mcelog[2628]: MCi_MISC register valid >> mcelog[2628]: MCA: BUS error: 1 6 Level-3 Generic Generic >> Other-transaction Request-did-not-timeout >> mcelog[2628]: Running trigger `bus-error-trigger' >> mcelog[2628]: QPI: >> mcelog[2628]: Intel QPI physical layer detected a QPI in-band reset but >> aborted initialization >> mcelog[2628]: STATUS c8012a4000200e0f MCGSTATUS 0 >> mcelog[2628]: MCGCAP 7000c16 APICID 10 SOCKETID 1 >> mcelog[2628]: CPUID Vendor Intel Family 6 Model 63 >> mcelog[2628]: <27>Oct 23 16:04:47 mcelog: CPU 6 on socket 1 received Bus >> and Interconnect Errors in Other-transaction >> mcelog[2628]: <27>Oct 23 16:04:47 mcelog: Location: CPU 6 on socket 1 >> ... >> >> This is with kernel 4.4.90-28 on openSuSE Leap 42.3, but after checking >> older journal entries I saw, that it also happened with 4.4.87-25. >> Machine specs: >> >> - Supermicro X10DRi/X10DRi, BIOS 2.0 12/28/2015 >> - 2 x 6 core CPU Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz >> - 128 GB RAM >> >> The error does not happen when restarting the os, only after a cold boot >> of the machine. >> >> I couldn't find appropriate information on the net. >> Is cpu 1 damaged? >> Can I do anything to correct the problem - or just ignore it? >> >> -- >> Michael Hirmke >> >> -- >> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse+owner(a)opensuse.org >> > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] XFCE terminal: the tittle doesn't follow the command line after update.
by Carlos E. R. 21 Oct '17

21 Oct '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, After update to "xfce4-terminal-0.8.5.1-32.3.x86_64", the tittle bar text doesn't follow what happens on the command line, like doing "ssh" or "su -". See small attached photos to understand. The package comes from "https://download.opensuse.org/repositories/X11:/xfce/openSUSE_Leap_42.2/". Some problems are solved, new ones appear :-( - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlnnS2UACgkQtTMYHG2NR9UTCQCfbsspD+7tNUHh2WpwBy/tUNBT 7AoAnjioSZpIL9MKXc6Dw89i9YtqSP3K =we72 -----END PGP SIGNATURE-----

3 9

Re: [opensuse] No network of leap 42.3
by Carlos E. R. 21 Oct '17

21 Oct '17

On 2017-10-10 13:44, Dave Smith wrote: > I am now totally confused. One thing I have always loved about linux > is that when you configure something it just works over and over > without fail. I did not touch anything configuration wise with this > system since the install to when the network failed. Totally clueless > why it failed. When I powered down 42.3 last night to go into knoppix > the network was down and totally dead. After running knoppix I turned > the machine off until now. When I fired up 42.3 to run the commands > you needed run (see attached files) I now have network connectivity > via dhcp. I did nothing to cause this to happen. Totally confused > and not happy at all. I have only one vague theory which I will be > trying next. The only thing I did from when I had network to when I > didn't was boot into Windows 10 build 1703. I am going to boot into > windows and then back into 42.3 to make sure I still have the network. > Will let you know. You may have a random problem. For instance, I replaced the hard disk on my laptop, and now sometimes (few) the laptop doesn't boot, doesn't see the disk at all. Or there may be a problem initializing your network hardware, and knopix knows how to do it, and the current package you have doesn't. So if you reboot from one to the other without powering off, it keeps. Might also happen with Windows. It is important to investigate your repo list and package mix. Please attach your repo list to a message, and maybe upload the package list with the command I posted to susepaste.org (for a limited time), then post the link here. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)

7 9