users August 2017

users@lists.fedoraproject.org

126 participants
113 discussions

Install on Zotac Zbox CI327?
by wwp 11 Dec '18

11 Dec '18

Hello there, (after a looong time not using Fedora, just back to it!) I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron N3450 inside) but this happens to fail. I've tried F25 but it has not the right kernel to make it (I've read about 4.10 minimum), then tried F26-Alpha-1.7 Live and Rawhide-20170518 Live but none could reach the graphical login. They both boot, some steps take a lot of time and I end up in a state I don't understand but which is not friendly ;-). Here's a link to a rdsosreport.txt file generated using Rawhide, I must admit that I don't know what to do now.. https://paste.fedoraproject.org/paste/iRx8d~7Luk2TC3bsaDuuT15M1UNdIGYhyRLiv… BTW, I could install and run a Ubuntu 17.10 daily (artful-desktop-amd64-20170519.iso) - wow it starts up pretty quickly - and that gave me hope! Any hint or experience w/ such hardware? Regards, -- wwp

2 3

How to turn on networking from rescue boot
by vendor＠billoblog.com 29 Oct '18

29 Oct '18

So... I did a "sudo dnf upgrade" and things seemed to do well. However, when I rebooted, it hangs on bootup with the statment "Holding until bootup processes complete" or something like that -- I'm doing this from memory. I tried with a couple of older kernels, but they also hung. I assume that this is some transient thing associated with the upgrade. Over the years, I've had glitches appear on an upgrade and disappear on the next upgrade. Accordingly, I'd like to boot into rescue mode and see if I can upgrade again. However, I've forgotten how to turn on wifi networking from rescue mode. Can anybody point me to a tutorial? Thanks, billo

6 5

suspends shutdowns system instead of suspending
by Sudhir Khanger 21 Jul '18

21 Jul '18

Hi, A new bug has cropped up on my system Dell Precision 5510 running Fedora 25 Plasma Desktop. Anytime I suspend my device it shutdowns and obviously I lose all my unsaved work. I have tried all the kernel currently installed on my system 4.10.10-200.fc25.x86_64, 4.10.9, and 4.10.8. I have also tried downgrading systemd to systemd-231-10.fc25.x86_64. I continue to have the problem. sysinfo - https://paste.fedoraproject.org/paste/9nY1-YH4IKXt4wJhyIbMGV5M1UNdIGYhyRLiv… dmesg - https://paste.fedoraproject.org/paste/WK2NAqy3PRxrR6Fze2baIl5M1UNdIGYhyRLiv… What I can do to troubleshoot the problem?

8 17

F26 update: gnome-terminal doesn't launch; locale issues
by Mike Zingale 07 May '18

07 May '18

I just did an update from F25 to F26 via dnf. After it boots, I can no longer start gnome terminal (nothing shows). If I ssh into the machine and try it remotely, I see the following: $ gnome-terminal (process:3586): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached So it looks like there is a locale issue in my update. Does anyone know how to fix this?

2 2

how to correctly log without journald (and its blobs)?
by Franta Hanzlík 09 Apr '18

09 Apr '18

In previous Fedora distros was (IMHO) right way to log only to syslog, without journald and its (for me) unwanted annoying binary logs, by using configuration as: *) Set systemd log target to syslog: systemd.log_target=syslog (syslog-or-kmsg) ---- on kernel cmdline systemd.default_standard_output=syslog --/ and LogTarget=syslog ---- in systemd.conf DefaultStandardOutput=syslog --/ *) configuring rsyslog to listen on /dev/log unix socket: $SystemLogSocketName /dev/log ------ in rsyslog.conf $ModLoad imuxsock ----/ $OmitLocalLogging off ---/ $AddUnixListenSocket /run/systemd/journal/syslog --/(legacy directives) $AddUnixListenSocket /run/systemd/journal/socket -/ $AddUnixListenSocket /run/systemd/journal/stdout / (not sure when all last three directives needed) *) prevent to run journald: systemctl mask systemd-journald.service (and maybe mask systemd-journal-flush.service) And it works fine. But in actual Fedora 24 in systemd man page values syslog-or-kmsg and syslog are missing in LogTarget option. As systemd/journald man pages say hardly anything about exact mean of appropriate configuration for this purpose, then please when someone more knowledgeable can advise: - where to direct the systemd output? Maybe to kmsg an then read it in rsyslog via imklog? (rsyslog should have also imkmsg module, but is not in rsyslog-8.12.0-3.fc24) - what about /run/log/journal/.../system.journal ? On my test F24 system it have open rsyslogd, abrt-dump-journal-oops and abrt-dump-journal-xorg (no need for these last two) processes. Uses it also something else? - what about /run/systemd/journal/{dev-log,socket,stdout} unix sockets? Should rsyslogd listen on them? - /dev/log seems be now symlink to /run/systemd/journal/dev-log socket (as defined by systemd-journald-dev-log.socket) Should it be left (because now something sends to /run/systemd/journal/dev-log), or can be /run/systemd/journal/dev-log removed? Thanks in advance for some clarification about this. Franta Hanzlik

5 14

how to (re-?)construct grub menu?
by William 22 Feb '18

22 Feb '18

Good afternoon, I found out the rather hard way what caused those boot failure problems that were the subject of a threat starting last month. After my weekly "dnf upgrade" last Thursday, I checked my root e-mail, and found the hard drive had 8 bad sectors, then 16 bad sectors. A smartctl short test showed several parameters "pre-fail", and the others "old-age". I obtained a new drive. My Cray Research friend gave me a USB stick with "Clonezilla-Live-Version" on it. That duplicated the old hard drive onto the new one, but apparently not 100%. After the old drive was removed and the new drive installed, I could not boot. The system was being put into a grub shell(?). (It displayed the "grub> " prompt.) After beating out heads against the wall (or the phone), my Cray research friend gave me another USB stick with "Boot-Repair-Disk" on it. That rebuilt a grub file, but not correctly. But at least I got a grub menu when booting, and I was able to edit the shell that the grub menu entry would run. I had to take the "efi" off the commands "linuxefi" and "initrdefi". That allows me to boot up Fedora. But the menu is missing an entry for windows, and I still have to edit that script every time. I want the grub menu to offer the three most recent patches of Fedora, the most recent Fedora rescue shell, and windows-7, in that order. (This is a dual-boot system.) And I want the shells launched by the menu entries to be correct. How do I get that accomplished - the correct Fedora-25 way? If it matters, the motherboard uses UEFI bios. Thank-you in advance. Bill.

11 60

Running local SSH as background process - possible??
by bruce 04 Oct '17

04 Oct '17

Ok guys, I know this isn't strictly "Fed" related, but the group might have suggestions. My use case, the process has a number of remote servers. I'd like to be able to run a bunch of commands on the remote servers as fast as posible. The initial thought was to loop through the different IPAddresses, and SSH into each server, to run the commands. However, this process was still "sequential" in that each SSH session needs to complete, prior to running the next server/ssh command. So, my question/need -- is to figure out how to run a ssh as a background on the local server. This approach would/should allow the process to quickly fire off commands to the remote ipaddresses/servers in a much faster/parallel manner. sortof: foreach iplist as ipaddress ssh user1@ipaddress command & (assuming that the '&' runs the local ssh in the background -- it doesn't!) Running "stuff" on the remote can occur in a "Screen" session, which would allow the ssh process to fire off the remote cmd, but it still doesn't run the local ssh as a "background" process.. Rick has mentioned/discussed the "Screen" function in past threads. Thoughts/comments....

6 7

Error building mkvtoolnix-9.6.0-1.fc26.src.rpm
by JD 30 Sep '17

30 Sep '17

$ rpmbuild -v -bb mkvtoolnix.spec 2>&1 | tee mkvtoolnix.build.out . . . WARNING: unable to read lib/avilib-0.6.10/avilib.c: invalid byte sequence in US-ASCII WARNING: unable to read lib/avilib-0.6.10/avimisc.c: invalid byte sequence in US-ASCII WARNING: unable to read src/common/checksums/adler32.cpp: invalid byte sequence in US-ASCII WARNING: unable to read src/common/checksums/base.cpp: invalid byte sequence in US-ASCII WARNING: unable to read src/common/checksums/crc.cpp: invalid byte sequence in US-ASCII WARNING: unable to read src/common/checksums/md5.cpp: invalid byte sequence in US-ASCII WARNING: unable to read src/common/spu.cpp: invalid byte sequence in US-ASCII . . . At end of build, it belched g++ -Wall -Wno-comment -Wfatal-errors -Wlogical-op -D_FILE_OFFSET_BITS=64 -DMTX_LOCALE_DIR=\"/usr/share/locale\" -DMTX_PKG_DATA_DIR=\"/usr/share/mkvtoolnix\" -DMTX_DOC_DIR=\"/usr/share/doc/mkvtoolnix\" -fstack-protector -fPIC -std=gnu++11 -Wnon-virtual-dtor -Woverloaded-virtual -Wextra -Wno-missing-field-initializers -Wno-maybe-uninitialized -I/usr/include/qt5/QtWidgets -I/usr/include/qt5 -I/usr/include/qt5/QtGui -I/usr/include/qt5 -I/usr/include/qt5/QtNetwork -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I/usr/include/qt5 -I/usr/include -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -include src/common/common_pch.h -I. -Ilib -Ilib/avilib-0.6.10 -Isrc -c -MMD -MF ./rake.d/dependency.d/tmp/src_common_json_o.d -o src/common/json.o -x c++ src/common/json.cpp In file included from src/common/json.cpp:19:0: src/common/json.h:23:76: error: 'nlohmann::json<std::map, std::vector, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, long int, double, std::allocator>::parser_callback_t' has not been declared nlohmann::json parse(nlohmann::json::string_t const &data, nlohmann::json::parser_callback_t callback = nullptr); ^ compilation terminated due to -Wfatal-errors.

3 7

autofs and ssh fail over ipsec tunnel
by David A. De Graaf 28 Sep '17

28 Sep '17

I use an ipsec tunnel to connect my LAN (192.168.2.h) in North Carolina to my son's LAN (192.168.1.h) in Maryland. We each have a primary machine that manages the ipsec tunnel and several secondary machines. Static routing tables direct traffic for the remote LAN to the local primary machine and thence through the tunnel. Cross-referenced DNS tables effectively join the two LANs as one. We expect all the usual network tools (autofs/nfs, ssh, rsync, etc.) to work thru the tunnel. Recently we've noticed that autofs/nfs and ssh don't work between a secondary machine and any remote machine. Autofs/nfs and ssh work perfectly between the primaries. Ping works perfectly between all machines, primary or secondary. For autofs the key subfunction seems to be rpcinfo. From the primary (datium) to the remote primary (octopus) 'rpcinfo -p name' yields good data: # rpcinfo -p octopus program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100005 1 udp 20048 mountd 100005 1 tcp 20048 mountd 100005 2 udp 20048 mountd 100005 2 tcp 20048 mountd 100005 3 udp 20048 mountd 100005 3 tcp 20048 mountd 100024 1 udp 35631 status 100024 1 tcp 58519 status 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1 udp 47742 nlockmgr 100021 3 udp 47742 nlockmgr 100021 4 udp 47742 nlockmgr 100021 1 tcp 35983 nlockmgr 100021 3 tcp 35983 nlockmgr 100021 4 tcp 35983 nlockmgr But from a secondary to the remote primary it fails: # rpcinfo -p octopus octopus: RPC: Port mapper failure - Unable to receive: errno 113 (No route to host) Similarly, for ssh the basic test seems to be telnet <name> 22. From primary to primary it works correctly: # telnet octopus 22 Trying 192.168.1.2... Connected to octopus. Escape character is '^]'. SSH-2.0-OpenSSH_7.4 But from a secondary to the remote primary, it fails: # telnet octopus 22 Trying 192.168.1.2... telnet: connect to address 192.168.1.2: No route to host In both failures the complaint is "No route to host", but clearly there is a route to the host, because ping works: # ping octopus PING octopus.dino.lan (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2 (192.168.1.2): icmp_seq=1 ttl=63 time=107 ms From router.datix.lan (192.168.2.1): icmp_seq=2 Redirect Host(New nexthop: datium.datix.lan (192.168.2.2)) 64 bytes from 192.168.1.2 (192.168.1.2): icmp_seq=2 ttl=63 time=45.1 ms From router.datix.lan (192.168.2.1): icmp_seq=3 Redirect Host(New nexthop: datium.datix.lan (192.168.2.2)) 64 bytes from 192.168.1.2 (192.168.1.2): icmp_seq=3 ttl=63 time=85.2 ms From router.datix.lan (192.168.2.1): icmp_seq=4 Redirect Host(New nexthop: datium.datix.lan (192.168.2.2)) 64 bytes from 192.168.1.2 (192.168.1.2): icmp_seq=4 ttl=63 time=80.4 ms ^C --- octopus.dino.lan ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 45.154/79.682/107.905/22.475 ms Each LAN has a router that connects to the internet. All LAN machines use the router's IP for the default gateway. In the router is a static route that sends packets destined for the remote LAN back to the primary machine that handles the ipsec tunnel. What's the problem here? Why is ping more clever in finding the route? Any advice or insight gratefully received. -- David A. De Graaf DATIX, Inc. Hendersonville, NC dad(a)datix.us www.datix.us

6 10

Openvpn start fails on reboot
by Stephen Davies 24 Sep '17

24 Sep '17

If I reboot my F24 system, openvpn server fails to properly start but a subsequent manual systemctl start openvpn@server does succeed. The reboot log shows: Mar 5 11:52:51 mustang audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvpn@server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 5 11:52:51 mustang systemd: Started OpenVPN Robust And Highly Flexible Tunneling Application On server. Mar 5 11:52:51 mustang audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvpn@server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 5 11:52:53 mustang systemd: openvpn(a)server.service: Main process exited, code=exited, status=1/FAILURE Mar 5 11:52:53 mustang systemd: openvpn(a)server.service: Unit entered failed state. Mar 5 11:52:53 mustang audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvpn@server comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Mar 5 11:52:53 mustang systemd: openvpn(a)server.service: Failed with result 'exit-code'. It looks as if the automatic start may be happening too early in the boot process.

2 3