Strange uptime behavior under qemu-kvm
Hi all, I've experienced some strange behavior on Fedora 28 client systems. I have some of them virtualized on a qemu-kvm hypervisor. All these systems take the hypervisor uptime as their own. This is really annoying, since I can not determine how long a host is up. If I take a look in the boot log I can see this: ...snip... [0.00] Hypervisor detected: KVM [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [137891542.045328] kvm-clock: cpu 0, msr c6c01001, primary cpu clock [137891542.045329] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns ...snap... Is there any possibility to turn this off, so that the VM takes its own uptime? Really much thanks for any solution / suggestion! Sebastian ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: questionable messages
On 12/11/18 10:40 PM, Robert McBroom via users wrote: Looked in the path and no such files were there. Created them but the messages still occur. What creates the real ones in the correct format? You wouldn't have created them in the correct format. Those files are not owned by any package. You could try running "sudo dconf update" to try recreating them properly. # file /etc/dconf/db/distro /etc/dconf/db/distro: GVariant Database file, version 0 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
questionable messages
$ gnome-session & (process:1024): dconf-WARNING **: 00:49:24.721: unable to open file '/etc/dconf/db/local': /etc/dconf/db/local: invalid gvdb header; expect degraded performance (process:1024): dconf-WARNING **: 00:49:24.721: unable to open file '/etc/dconf/db/site': /etc/dconf/db/site: invalid gvdb header; expect degraded performance (process:1024): dconf-WARNING **: 00:49:24.721: unable to open file '/etc/dconf/db/distro': /etc/dconf/db/distro: invalid gvdb header; expect degraded performance (tracker-miner-apps:3204): dconf-WARNING **: 01:04:31.208: unable to open file '/etc/dconf/db/local': /etc/dconf/db/local: invalid gvdb header; expect degraded performance (tracker-miner-apps:3204): dconf-WARNING **: 01:04:31.209: unable to open file '/etc/dconf/db/site': /etc/dconf/db/site: invalid gvdb header; expect degraded performance (tracker-miner-apps:3204): dconf-WARNING **: 01:04:31.209: unable to open file '/etc/dconf/db/distro': /etc/dconf/db/distro: invalid gvdb header; expect degraded performance (abrt:3192): dconf-WARNING **: 01:04:34.113: unable to open file '/etc/dconf/db/local': /etc/dconf/db/local: invalid gvdb header; expect degraded performance (abrt:3192): dconf-WARNING **: 01:04:34.113: unable to open file '/etc/dconf/db/site': /etc/dconf/db/site: invalid gvdb header; expect degraded performance (abrt:3192): dconf-WARNING **: 01:04:34.113: unable to open file '/etc/dconf/db/distro': /etc/dconf/db/distro: invalid gvdb header; expect degraded performance Looked in the path and no such files were there. Created them but the messages still occur. What creates the real ones in the correct format? Robert ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Anyone else have occasional nvidia crashes?
On 12/4/18 8:07 AM, Tom Horsley wrote: I have a GeForce GTX 750 Ti in my system at work, using the rpmfusion nvidia drivers (because nouveau can't go more than a few hours without crashing). Every so often, when the X server starts or is restarted by logging out, the screen will go blank and the system will be frozen, needing a power cycle to get it back. This only happens at work, a very similar system at home with a newer model nvidia card never has this problem (though it certainly had the same crashes under nouveau). Just curious if anyone else with the 750 Ti has seen similar symptoms. NVIDIA GPU GeForce GT 610. I get most consistency using the NVIDIA drivers. Currently using version 390.77. DKMS didn't work with the 4.19.7-300.fc29.x86_64 kernel but the manual install did. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
[389-users] Multiple suppliers for a single consumer
Let's say I have nodes A and B setup in a MMR configuration(providers). Is it possible to have node C configured as a consumer for both A and B? I am wanting to have a high availability setup so node C still receives updates if one of the providers goes down. ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Re: persistent name from ifcfg-internal
On 12/11/18 9:22 AM, sean darcy wrote:
cat /etc/udev/rules.d/40-persistent-net.rules
# this is the pci ethernet port
# udevadm info -a -p /sys/class/net/enp1s0/
# r8169 :01:00.0 eth0: RTL8168g/8111g, 50:7b:9d:0b:8a:ab, XID
50900880, IRQ 44
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="50:7b:9d:0b:8a:ab", ATTR{dev_id}=="0x0",
ATTR{type}=="1", NAME="internal"
But now nm handles naming , not udev, correct ?
Try deleting that file and see what happens.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: downsized grub menu.
On 12/11/18 9:59 AM, home user via users wrote: Now to the greater problem... When I upgraded to Fedora-28, the text of the grub menu was significantly down-sized. It also seems to be a (darker?) gray. It is split into two pieces into the corners of the left side of the left monitor. It is difficult for me to read. How do I make the font bigger and whiter, and get it all back together? That is strange. I would suggest that you backup the current grub config file and create it fresh using "sudo grub2-mkconfig -o /etc/grub2.cfg". Then if there's still a problem, we know it's not caused by some old config. I also wonder if it's necessary to refresh grub's boot files. Does anyone else know if grub upgrades update the boot sectors? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 KDE weirdness
On 12/11/18 3:34 PM, George Avrunin wrote: On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users wrote: Upgraded to F29. On KDE desktop starting EMACS in a privileged command window locks the system. Starting EMACS with sudo locks the system. On XFCE4 normal EMACS access with privilege. Other file managers don't like root but there are times when cli is awkward. I'm now seeing this, too, with F29, kernel 4.19.7, on KDE. I'm pretty sure doing this has worked as expected after the upgrade to F29, so it's a recent change, but I don't know exactly when it started. I'm seeing this with two different machines (a desktop and a laptop). This is emacs-26.1.6.f29.x86_64, in case that matters, and, at the moment, plasma-workspace-5.14.4-1.fc29.x86_64 which was upgraded to on December 5. It doesn't actually lock the system. I can, for instance get to a virtual terminal and kill the startkde process to get back to roughly where I was. And I can still see the cursor and move it around (though it becomes invisible when it's over the konsole window from which I launched emacs), but except for being able to use, e.g., control-F3, to get to a console, I don't seem to be able to interact with the open windows or switch to another virtual desktop (cursor won't cross the desktop boundary). The command "emacs -nw" seems to work fine. On kernel 4.19.6 George Same here on a desktop and a laptop. Switched to gnome-session and have access. On kernel 4.19.6 and plasma-workspace-5.14.4-1 trouble. Robert ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/12/18 9:44 AM, Ed Greshko wrote: > I will check again in a few hours, but I think the defense may drop after a > time. Yep, 1 hour later and "traceroute -n -T -p 999 beartooth.info" reaches 208.100.51.176. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
Allegedly, on or about 11 December 2018, Joe Zeff sent: > If you can't ping someplace, traceroute will show you where the > problem is, because it will stop getting responses. Though you still have to think about it (it's only part of a diagnosis). That failure just means the device doesn't respond to that type of probing. There's plenty of otherwise fully functional things that ignore pings and other probing. -- [tim@localhost ~]$ uname -rsvp Linux 4.16.11-100.fc26.x86_64 #1 SMP Tue May 22 20:02:12 UTC 2018 x86_64 Boilerplate: All mail to my mailbox is automatically deleted. There is no point trying to privately email me, I only get to see the messages posted to the mailing list. Using Windows software is like coating all your handtools with sewage. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: persistent name from ifcfg-internal
On 12/11/18 12:54 PM, Rick Stevens wrote: On 12/11/18 8:52 AM, sean darcy wrote: On 12/11/18 12:54 AM, Samuel Sieb wrote: On 12/10/18 4:22 PM, sean darcy wrote: I'm trying to get the interface on a multi-homed machine named "internal" ifconfig enp1s0: flags=4099 mtu 1500 ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet) Is that the full ifconfig output for that interface or does it have the right IP address as well? I haven't connected the port yet. Before I do I need to make sure I've got the correct internet name. That's the device (ethernet port) name, NOT the host name. The host name is controlled by the contents of the /etc/hostname file, which is read at boot time and sets the FQDN (fully qualified domain name) of the machine. That was fat finger syndrome. I meant interface name ! The stuff in the /etc/sysconfig/network-scripts/ifcfg-* files (and NM's configurations) control how the interfaces themselves are configured and do not affect the hostname of the machine. As I understand, NM scans the ifcfg files for HWADDR's. If there's a match, it names the interface the DEVICE name. I believe NM uses the DEVICE _or_ the HWADDR to set up the interface. Whichever one matches the hardware config first is what gets used (I'm not sure which has precedence). And don't be confused...the values in the NM config are only used to match the hardware. And in answer to your second message, NM doesn't do any renaming of devices. That's still done by the udev rules. If so, why doesn't the udev rule work ? But I think nm now does device renaming: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_device_renaming_procedure sean ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/12/18 7:15 AM, Samuel Sieb wrote: > > traceroute beartooth.info > traceroute -I beartooth.info > traceroute -T -p 999 beartooth.info > > Some (or all) or those might require root, so best to just use root. I was able to get the failure condition again. This is from a working system [root@acer egreshko]# traceroute -n -T -p 999 beartooth.info traceroute to beartooth.info (208.100.51.176), 30 hops max, 60 byte packets 1 211.75.128.254 6.136 ms 6.076 ms 6.208 ms 2 168.95.229.46 6.158 ms 6.078 ms 6.025 ms 3 220.128.27.94 6.525 ms 6.485 ms 6.437 ms 4 220.128.7.69 6.788 ms 220.128.14.93 6.325 ms 220.128.7.69 6.675 ms 5 220.128.30.253 14.755 ms 14.658 ms 220.128.6.85 6.458 ms 6 211.72.108.81 154.862 ms 154.813 ms 211.72.108.49 144.515 ms 7 202.39.83.45 152.368 ms 202.39.83.77 152.717 ms 152.691 ms 8 4.28.172.121 166.896 ms 4.28.172.129 144.516 ms 142.168 ms 9 * * * 10 4.71.248.202 195.003 ms 205.495 ms 193.438 ms 11 208.100.32.35 301.100 ms 205.363 ms 215.205 ms 12 216.86.153.98 205.625 ms 215.884 ms 215.802 ms 13 208.100.51.176 203.412 ms 215.869 ms 189.607 ms [root@acer egreshko]# host 208.100.51.176 176.51.100.208.in-addr.arpa domain name pointer artemis.beartooth.info. And this is from a failing one... [root@meimei ~]# traceroute -n -T -p 999 beartooth.info traceroute to beartooth.info (208.100.51.176), 30 hops max, 60 byte packets 1 192.168.1.1 1.198 ms 0.321 ms 0.454 ms 2 211.75.128.254 8.701 ms 8.184 ms 9.475 ms 3 168.95.229.46 9.358 ms 10.435 ms 7.877 ms 4 220.128.27.94 10.369 ms 9.341 ms 10.332 ms 5 220.128.14.93 8.145 ms 8.735 ms 9.284 ms 6 220.128.6.81 10.359 ms * 9.139 ms 7 211.72.108.5 153.147 ms 211.72.108.49 148.277 ms 211.72.108.5 153.197 ms 8 202.39.83.45 141.591 ms 144.909 ms 202.39.83.77 169.003 ms 9 4.28.172.121 148.228 ms 144.076 ms 4.28.172.129 154.525 ms 10 * * * 11 4.71.248.202 216.858 ms 202.435 ms 216.704 ms 12 208.100.32.35 216.585 ms 202.665 ms 216.622 ms 13 216.86.153.98 216.773 ms 216.103 ms 216.158 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * FWIW, I think I triggered the "defensive" response by doing a port scan on 208.100.51.176. I will check again in a few hours, but I think the defense may drop after a time. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 2:36 PM, Ed Greshko wrote: > On 12/12/18 6:12 AM, Rick Stevens wrote: >> On 12/11/18 1:52 PM, Ed Greshko wrote: >>> >>> I get the feeling the folks at Netwisp, Inc. are doing something to >>> "prevent" hacking. >> Yup. Tried three times from our ASN from two different machines. All >> the test machines are behind a firewall (Cisco 65xx) and only one has >> a reverse DNS record. > > Not quite understanding what you're saying. > > The 2 different machines are in the ASN and work all the time? Are they > pingable? Both are part of our public /22 address space and have public IPs. We do our own DNS and one of the machines I used has a PTR record. The other one doesn't (it has a public IP, but no PTR record as it's part of a load-balanced cluster and the PTR record for the cluster points at the VIP--not the RIP). > All of my assigned IP addresses (even IPV6) have PTR records courtesy of my > ISP. In my > case it just seems to be a case of the IP that the beartooth side sees as the > incoming > connection being pingable or not. > > [Real-Time Update] > > Decided to connect again from my system(s) behind my router and it now works > all time time! > > Odd, very odd. Yup. It may be that Netwisp is doing something weird. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- -"Jimmie crack corn and I don't care." What kind of a lousy attitude - - is THAT to have, huh? -- Dennis Miller - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/2018 04:04 PM, Beartooth wrote: Hoo, boy! I haven't so much as heard of traceroute in ten or fifteen years, and never did grep its uses. I can look it up, of course, but it might be worth your while to just tell me a command (and to use it as root if that should be desirable). For all practical purposes, traceroute pings each hop along the way to the destination three times. (That's not really how it does it, but don't worry about it.) If you can't ping someplace, traceroute will show you where the problem is, because it will stop getting responses. Also, if you've got a slow connection, you can tell where the issue is because the return times will suddenly jump. The only time you need root for it is for traceroute -I, because that uses ICMP ECHO for probes, but can get response where nothing else does. Back when I was doing tech support for an ISP, we used it all the time on calls to find out why connections were slow, and usually to show the caller that it was outside our network. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 3:04 PM, Beartooth wrote: Hoo, boy! I haven't so much as heard of traceroute in ten or fifteen years, and never did grep its uses. I can look it up, of course, but it might be worth your while to just tell me a command (and to use it as root if that should be desirable). traceroute beartooth.info traceroute -I beartooth.info traceroute -T -p 999 beartooth.info Some (or all) or those might require root, so best to just use root. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Tue, 11 Dec 2018 14:23:59 -0800, Samuel Sieb wrote: > On 12/11/18 1:54 PM, Beartooth wrote: >> On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote: >>> I can connect to that port fine. Do you have something like fail2ban >>> on the server that would block your connection? Can you try >>> connecting from another location? >> >> I thought I had fail2ban, but rpm -q says not. >> >> I tried just now on my little netbook, and got what looks to me >> to be the same: > > But you're still trying from the same location, right? Yes: it's a different machine in the next room, using my one access route. > But as others > have said, it depends on where you try from whether or not it works. So > it sounds like a networking issue somewhere. It could be the server, > the hosting provider, or your internet provider. What happens if you > try using traceroute? Hoo, boy! I haven't so much as heard of traceroute in ten or fifteen years, and never did grep its uses. I can look it up, of course, but it might be worth your while to just tell me a command (and to use it as root if that should be desirable). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/12/18 6:12 AM, Rick Stevens wrote: > On 12/11/18 1:52 PM, Ed Greshko wrote: >> >> I get the feeling the folks at Netwisp, Inc. are doing something to >> "prevent" hacking. > Yup. Tried three times from our ASN from two different machines. All > the test machines are behind a firewall (Cisco 65xx) and only one has > a reverse DNS record. Not quite understanding what you're saying. The 2 different machines are in the ASN and work all the time? Are they pingable? All of my assigned IP addresses (even IPV6) have PTR records courtesy of my ISP. In my case it just seems to be a case of the IP that the beartooth side sees as the incoming connection being pingable or not. [Real-Time Update] Decided to connect again from my system(s) behind my router and it now works all time time! Odd, very odd. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 1:54 PM, Beartooth wrote: On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote: I can connect to that port fine. Do you have something like fail2ban on the server that would block your connection? Can you try connecting from another location? I thought I had fail2ban, but rpm -q says not. I tried just now on my little netbook, and got what looks to me to be the same: But you're still trying from the same location, right? But as others have said, it depends on where you try from whether or not it works. So it sounds like a networking issue somewhere. It could be the server, the hosting provider, or your internet provider. What happens if you try using traceroute? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 1:52 PM, Ed Greshko wrote: > On 12/12/18 5:25 AM, Rick Stevens wrote: >> I just did the same. From a Spectrum IP here in Orange County, CA, >> the system doesn't respond (and Spectrum is a Comcast company). >> >> From a monitoring system in our ASN (a /22 network), it works peachy: > > Interesting > > Could you try it a second time? I ask since I tried from Taiwan. The first > attempt.. > > [egreshko@meimei etc]$ ssh -v bearto...@beartooth.info -p 999 > OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf > debug1: Reading configuration data > /etc/crypto-policies/back-ends/openssh.config > debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * > debug1: Connecting to beartooth.info [208.100.51.176] port 999. > debug1: Connection established. > . > . > . > The authenticity of host '[beartooth.info]:999 ([208.100.51.176]:999)' can't > be established. > ECDSA key fingerprint is SHA256:KC2aZ8T2NiqBIcjVVrhwXfPgHunj2BtECvty3QGEzxc. > Are you sure you want to continue connecting (yes/no)? no > > The second time... > > [egreshko@meimei etc]$ ssh -v bearto...@beartooth.info -p 999 > OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf > debug1: Reading configuration data > /etc/crypto-policies/back-ends/openssh.config > debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * > debug1: Connecting to beartooth.info [208.100.51.176] port 999. > ssh: connect to host beartooth.info port 999: Connection timed out > > This happens with a system that is behind a router and the router is not > pingable. > > If I try from another host that is directly connected to the Internet and is > pingable then > connections work all the time. > > I get the feeling the folks at Netwisp, Inc. are doing something to "prevent" > hacking. Yup. Tried three times from our ASN from two different machines. All the test machines are behind a firewall (Cisco 65xx) and only one has a reverse DNS record. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - LOOK OUT!!! BEHIND YOU!!! - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote: > On 12/11/18 12:11 PM, Beartooth wrote: >> ssh -v bearto...@beartooth.info -p 999 debug1: Connecting to >> beartooth.info [208.100.51.176] port 999. >> debug1: connect to address 208.100.51.176 port 999: Connection timed >> out ssh: connect to host beartooth.info port 999: Connection timed out > > I can connect to that port fine. Do you have something like fail2ban on > the server that would block your connection? Can you try connecting > from another location? I thought I had fail2ban, but rpm -q says not. I tried just now on my little netbook, and got what looks to me to be the same: btth@Redback ~]$ ssh -v bearto...@beartooth.info -p 999 OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/ openssh.config debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * debug1: Connecting to beartooth.info [208.100.51.176] port 999. debug1: connect to address 208.100.51.176 port 999: Connection timed out ssh: connect to host beartooth.info port 999: Connection timed out [btth@Redback ~]$ -- Beartooth Staffwright, Erstwhile Historian of Tongues Sclerotic Squirreler, Double Retiree, Linux Evangelist ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/12/18 5:25 AM, Rick Stevens wrote: > I just did the same. From a Spectrum IP here in Orange County, CA, > the system doesn't respond (and Spectrum is a Comcast company). > > From a monitoring system in our ASN (a /22 network), it works peachy: Interesting Could you try it a second time? I ask since I tried from Taiwan. The first attempt.. [egreshko@meimei etc]$ ssh -v bearto...@beartooth.info -p 999 OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * debug1: Connecting to beartooth.info [208.100.51.176] port 999. debug1: Connection established. . . . The authenticity of host '[beartooth.info]:999 ([208.100.51.176]:999)' can't be established. ECDSA key fingerprint is SHA256:KC2aZ8T2NiqBIcjVVrhwXfPgHunj2BtECvty3QGEzxc. Are you sure you want to continue connecting (yes/no)? no The second time... [egreshko@meimei etc]$ ssh -v bearto...@beartooth.info -p 999 OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * debug1: Connecting to beartooth.info [208.100.51.176] port 999. ssh: connect to host beartooth.info port 999: Connection timed out This happens with a system that is behind a router and the router is not pingable. If I try from another host that is directly connected to the Internet and is pingable then connections work all the time. I get the feeling the folks at Netwisp, Inc. are doing something to "prevent" hacking. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 12:53 PM, Samuel Sieb wrote: > On 12/11/18 12:11 PM, Beartooth wrote: >> ssh -v bearto...@beartooth.info -p 999 >> debug1: Connecting to beartooth.info [208.100.51.176] port 999. >> debug1: connect to address 208.100.51.176 port 999: Connection timed out >> ssh: connect to host beartooth.info port 999: Connection timed out > > I can connect to that port fine. Do you have something like fail2ban on > the server that would block your connection? Can you try connecting > from another location? I just did the same. From a Spectrum IP here in Orange County, CA, the system doesn't respond (and Spectrum is a Comcast company). From a monitoring system in our ASN (a /22 network), it works peachy: CUT HERE - # ssh -v -p 999 208.100.51.176 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 208.100.51.176 [208.100.51.176] port 999. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type 1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 debug1: match: OpenSSH_7.4 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-sha1 none debug1: kex: client->server aes128-ctr hmac-sha1 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<2048<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '[208.100.51.176]:999' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:40 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug1: Next authentication method: gssapi-with-mic debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_0' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_0' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_0' not found debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Offering public key: /root/.ssh/id_rsa debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: password root@208.100.51.176's password: CUT HERE - So, it could be that Comcast/Spectrum has blacklisted that IP or its /24 block (appears to be owned by Netwisp, Inc.). Or that system is doing something like reverse DNS lookups that aren't resolving and thus blocking things. Dunno which. Looks like an argument you need to have with Comcast to see if they're blacklisting it and if so, why? -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - IGNORE that man behind the keyboard! - -- The Wizard of OS - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 12:11 PM, Beartooth wrote: ssh -v bearto...@beartooth.info -p 999 debug1: Connecting to beartooth.info [208.100.51.176] port 999. debug1: connect to address 208.100.51.176 port 999: Connection timed out ssh: connect to host beartooth.info port 999: Connection timed out I can connect to that port fine. Do you have something like fail2ban on the server that would block your connection? Can you try connecting from another location? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 KDE weirdness
On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users wrote: > Upgraded to F29. On KDE desktop starting EMACS in a privileged command > window locks the system. Starting EMACS with sudo locks the system. On > XFCE4 normal EMACS access with privilege. > > Other file managers don't like root but there are times when cli is awkward. I'm now seeing this, too, with F29, kernel 4.19.7, on KDE. I'm pretty sure doing this has worked as expected after the upgrade to F29, so it's a recent change, but I don't know exactly when it started. I'm seeing this with two different machines (a desktop and a laptop). This is emacs-26.1.6.f29.x86_64, in case that matters, and, at the moment, plasma-workspace-5.14.4-1.fc29.x86_64 which was upgraded to on December 5. It doesn't actually lock the system. I can, for instance get to a virtual terminal and kill the startkde process to get back to roughly where I was. And I can still see the cursor and move it around (though it becomes invisible when it's over the konsole window from which I launched emacs), but except for being able to use, e.g., control-F3, to get to a console, I don't seem to be able to interact with the open windows or switch to another virtual desktop (cursor won't cross the desktop boundary). The command "emacs -nw" seems to work fine. George pgpyTNlagcajR.pgp Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Tue, 11 Dec 2018 11:59:20 -0800, Samuel Sieb wrote: > On 12/11/18 11:04 AM, Beartooth wrote: >> We've been unable for days to connect to our email at my domain; >> when we try our usual ssh -p , we >> get nothing but eventually "Connection timed out" -- even after having >> left it all night. > > How are you using ssh to get your email? I use it to get to the CLI at my host, sign in, command Alpine, give the password again, and then run Alpine -- which I've been using for nearer thirty years than twenty. > What port are you using? 999 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: [F29] Command dvipdfmx (texlive) does not work
On Tue, Dec 11, 2018 at 8:00 PM Jon Ingason wrote: > > You need to install texlive-xetex-7:20180414-28.fc29.x86_64 which > provide /usr/bin/xdvipdfmx. > > -- > Regards > > Jon Ingason > Hi Jon, Thank you very much. It works. I'll add your suggestion in the reported bug page. Best regards, Marco ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Tue, 11 Dec 2018 12:53:03 -0700, stan wrote: > I think I understand better what is happening. Whether I can help I > don't know. A summary: > > You have no problem with your ISP (Comcast). Your problem is with the > third party that handles your private domain for email. When you try to > connect to that site via ssh, the connection attempts time out. Yes, exactly. > This sounds like an ssh configuration issue, not a firewall issue. I'm > not very familiar with ssh since I don't use it a lot, but here goes. > > Are you using key based login rather than password login? No; I don't even know what the former is. > If you are, is it possible the keys are incorrect with f29, and you need > to generate new keys? > > Have you tried using the -v option to ssh, the verbose option for > debugging so you can see what is happening with the connection process? ssh -v bearto...@beartooth.info -p 999 OpenSSH_7.9p1, OpenSSL 1.1.1 FIPS 11 Sep 2018 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf debug1: Reading configuration data /etc/crypto-policies/back-ends/ openssh.config debug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for * debug1: Connecting to beartooth.info [208.100.51.176] port 999. debug1: connect to address 208.100.51.176 port 999: Connection timed out ssh: connect to host beartooth.info port 999: Connection timed out [btth@localhost ~]$ > Perhaps someone more knowledgeable about ssh will immediately point to > the problem for you. I hope the above helps someone. I've been using ssh ever since telnet became unsafe, and never thought to look at options, fool that I am. It has just worked for about twenty years. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 11:04 AM, Beartooth wrote: > On Sun, 09 Dec 2018 15:27:32 -0700, stan wrote: > >> On Sun, 9 Dec 2018 19:00:25 + (UTC) >> I Beartooth wrote: >> >>> I do some of my email and all of my Gmane activity (including >>> this list) at the address above, from my local access provider, >>> Comcast; but I do most of my email (and my wife does all of hers) at my >>> own domain, to which we connect by ssh. > >>> Recently we've been moving machines about physically, from >>> floor to floor and connection to connection. We've also been getting >>> lots of timeouts. When I asked my domain host about it, he told me it >>> was my own firewall cutting us off. It blocks connections out from our >>> IP address if they fail more than it likes. > > (If he said what caused the initial, triggering failure to > connect, I missed it.) > >> This doesn't make sense to me, unless you have restrictive firewalls on >> your local net in front of the web access. Moving a machine should be >> irrelevant. Fedora's default setting for the firewall is to let nothing >> initiate connections to the system except ssh, and to let anything on >> the system that wants to reach the net do so. If you haven't changed it >> on any of your machines, that is what should be happening. > > It makes no sense to me either, and I don't even know how to > access the firewall; it pretty well has to be whatever F29 defaults to. > >> Are you maybe using wireless, and getting problematic connections with >> lower (or no) speeds in different locations? > > My current router is an ASUS AC-1200, which does both, and we use > both. After fifteen years in this house, and half a dozen routers, we > have a fair idea which locations a wireless access point can reach. We > stick to those when (rarely) we use Wi-Fi. We keep it available mainly > for house guests. > >>> So, I THINK, I ought to enlarge a/o lubricate the opening in >>> the firewall that lets US out, but not make it any easier than I can >>> help for supposed malware to get out. Does that make sense? >>> >>> If so, where do I go (i.e., what file do I open), and what >>> changes do I make, to accomplish that? >> >> I don't think this should be necessary if you are using default Fedora >> settings. Use the program firewall-config (man firewall-config) to look >> at what the firewall settings are on each system. Mine is set to public >> (meaning roughly that I am exposed to the public web, and thus don't >> trust the network I'm on, so play safe). >> >> I used to have all kinds of elaborate rules in my iptables configuration >> (which is what the firewall uses under the covers), but eventually just >> caved and let the firewalld configuration set it. > > We've been unable for days to connect to our email at my domain; > when we try our usual ssh -p , we get > nothing but eventually "Connection timed out" -- even after having left > it all night. > > From my Comcast account, I emailed support at my host (two guys in > a suburb of Chicago afaict). The answer made no sense to me, but > I recited it as best I could to this list-- and meseems it made no sense > here, either. > > According to them, my own firewall cuts us (i.e., our whole IP) off > when we try too many times too soon to connect. (We do that, of course, > by hitting up arrow and Enter.) > > Am I making any more sense yet? Well, yeah, but I really, REALLY doubt it's your router. I've used that model of router myself. While I was never a big fan of its wifi abilities (kinda wimpy for my house), wired connections through it never failed. Unless you took a power hit, did a firmware update or some other action to your router, I doubt it's your problem. Those routers do have a log in them. Check it to see if you see anything like what they're claiming. A far more likely candidate is that the cable modem got an update from Comcast (they do that on occasion and without telling you) and it's screwed up. I had a similar issue with Spectrum (a Comcast company) here. By use of traceroutes and tcpdumps, I proved that their modem was the problem. They reflashed my cable modem to the previous firmware it had (and I had a record of what it was) and suddenly everything was tickety-boo again. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - To understand recursion, you must first understand recursion.- -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
Re: F29 Wail at the Firewall (long; sorry!)
On 12/11/18 11:04 AM, Beartooth wrote: We've been unable for days to connect to our email at my domain; when we try our usual ssh -p , we get nothing but eventually "Connection timed out" -- even after having left it all night. How are you using ssh to get your email? What port are you using? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Tue, 11 Dec 2018 19:04:17 + (UTC) Beartooth wrote: > According to them, my own firewall cuts us (i.e., our whole IP) > off when we try too many times too soon to connect. (We do that, of > course, by hitting up arrow and Enter.) > > Am I making any more sense yet? I think I understand better what is happening. Whether I can help I don't know. A summary: You have no problem with your ISP (Comcast). Your problem is with the third party that handles your private domain for email. When you try to connect to that site via ssh, the connection attempts time out. This sounds like an ssh configuration issue, not a firewall issue. I'm not very familiar with ssh since I don't use it a lot, but here goes. Are you using key based login rather than password login? If you are, is it possible the keys are incorrect with f29, and you need to generate new keys? Have you tried using the -v option to ssh, the verbose option for debugging so you can see what is happening with the connection process? Perhaps someone more knowledgeable about ssh will immediately point to the problem for you. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: F29 Wail at the Firewall (long; sorry!)
On Sun, 09 Dec 2018 15:27:32 -0700, stan wrote: > On Sun, 9 Dec 2018 19:00:25 + (UTC) > I Beartooth wrote: > >> I do some of my email and all of my Gmane activity (including >> this list) at the address above, from my local access provider, >> Comcast; but I do most of my email (and my wife does all of hers) at my >> own domain, to which we connect by ssh. >> Recently we've been moving machines about physically, from >> floor to floor and connection to connection. We've also been getting >> lots of timeouts. When I asked my domain host about it, he told me it >> was my own firewall cutting us off. It blocks connections out from our >> IP address if they fail more than it likes. (If he said what caused the initial, triggering failure to connect, I missed it.) > This doesn't make sense to me, unless you have restrictive firewalls on > your local net in front of the web access. Moving a machine should be > irrelevant. Fedora's default setting for the firewall is to let nothing > initiate connections to the system except ssh, and to let anything on > the system that wants to reach the net do so. If you haven't changed it > on any of your machines, that is what should be happening. It makes no sense to me either, and I don't even know how to access the firewall; it pretty well has to be whatever F29 defaults to. > Are you maybe using wireless, and getting problematic connections with > lower (or no) speeds in different locations? My current router is an ASUS AC-1200, which does both, and we use both. After fifteen years in this house, and half a dozen routers, we have a fair idea which locations a wireless access point can reach. We stick to those when (rarely) we use Wi-Fi. We keep it available mainly for house guests. >> So, I THINK, I ought to enlarge a/o lubricate the opening in >> the firewall that lets US out, but not make it any easier than I can >> help for supposed malware to get out. Does that make sense? >> >> If so, where do I go (i.e., what file do I open), and what >> changes do I make, to accomplish that? > > I don't think this should be necessary if you are using default Fedora > settings. Use the program firewall-config (man firewall-config) to look > at what the firewall settings are on each system. Mine is set to public > (meaning roughly that I am exposed to the public web, and thus don't > trust the network I'm on, so play safe). > > I used to have all kinds of elaborate rules in my iptables configuration > (which is what the firewall uses under the covers), but eventually just > caved and let the firewalld configuration set it. We've been unable for days to connect to our email at my domain; when we try our usual ssh -p , we get nothing but eventually "Connection timed out" -- even after having left it all night. From my Comcast account, I emailed support at my host (two guys in a suburb of Chicago afaict). The answer made no sense to me, but I recited it as best I could to this list-- and meseems it made no sense here, either. According to them, my own firewall cuts us (i.e., our whole IP) off when we try too many times too soon to connect. (We do that, of course, by hitting up arrow and Enter.) Am I making any more sense yet? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: [F29] Command dvipdfmx (texlive) does not work
Den 2018-12-11 kl. 18:43, skrev Marco Guazzone: > Hi, > > On my Fedora 29, the command dvipdfmx does not work: > > $ rpm -q texlive-dvipdfmx > texlive-dvipdfmx-20180414-28.fc29.x86_64 > $ dvipdfmx > bash: dvipdfmx: command not found > > Indeed, the executable file '/usr/bin/dvipdfmx' is a broken link that > points to a nonexistent file: > > $ ls -al /usr/bin/dvipdfmx > lrwxrwxrwx. 1 root root 9 Nov 26 19:22 /usr/bin/dvipdfmx -> xdvipdfmx > $ ls -al /usr/bin/xdvipdfmx > ls: cannot access '/usr/bin/xdvipdfmx': No such file or directory > > I tried to reinstall the texlive-dvipdfmx package with no success. > I already filed a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1657755 > > I would like to know if some of you has this problem too, and if (s)he > already found a workaround. > > Thank you in advance for your help. > > Best, > > > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > You need to install texlive-xetex-7:20180414-28.fc29.x86_64 which provide /usr/bin/xdvipdfmx. -- Regards Jon Ingason ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: downsized grub menu.
(Samuel said) > I would say to comment out all the lines from 91-98. Done. Re-booted. No more error messages before the grub menu appears. Thank-you! Now to the greater problem... When I upgraded to Fedora-28, the text of the grub menu was significantly down-sized. It also seems to be a (darker?) gray. It is split into two pieces into the corners of the left side of the left monitor. It is difficult for me to read. How do I make the font bigger and whiter, and get it all back together? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: persistent name from ifcfg-internal
On 12/11/18 8:52 AM, sean darcy wrote: > On 12/11/18 12:54 AM, Samuel Sieb wrote: >> On 12/10/18 4:22 PM, sean darcy wrote: >>> I'm trying to get the interface on a multi-homed machine named >>> "internal" >>> >>> ifconfig >>> enp1s0: flags=4099 mtu 1500 >>> ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet) >> >> Is that the full ifconfig output for that interface or does it have >> the right IP address as well? > > I haven't connected the port yet. Before I do I need to make sure I've > got the correct internet name. That's the device (ethernet port) name, NOT the host name. The host name is controlled by the contents of the /etc/hostname file, which is read at boot time and sets the FQDN (fully qualified domain name) of the machine. The stuff in the /etc/sysconfig/network-scripts/ifcfg-* files (and NM's configurations) control how the interfaces themselves are configured and do not affect the hostname of the machine. >>> As I understand, NM scans the ifcfg files for HWADDR's. If there's a >>> match, it names the interface the DEVICE name. I believe NM uses the DEVICE _or_ the HWADDR to set up the interface. Whichever one matches the hardware config first is what gets used (I'm not sure which has precedence). And don't be confused...the values in the NM config are only used to match the hardware. And in answer to your second message, NM doesn't do any renaming of devices. That's still done by the udev rules. -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - -- - "Microsoft is a cross between The Borg and the Ferengi. - - Unfortunately they use Borg to do their marketing and Ferengi to - - do their programming." -- Simon Slavin - -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
[F29] Command dvipdfmx (texlive) does not work
Hi, On my Fedora 29, the command dvipdfmx does not work: $ rpm -q texlive-dvipdfmx texlive-dvipdfmx-20180414-28.fc29.x86_64 $ dvipdfmx bash: dvipdfmx: command not found Indeed, the executable file '/usr/bin/dvipdfmx' is a broken link that points to a nonexistent file: $ ls -al /usr/bin/dvipdfmx lrwxrwxrwx. 1 root root 9 Nov 26 19:22 /usr/bin/dvipdfmx -> xdvipdfmx $ ls -al /usr/bin/xdvipdfmx ls: cannot access '/usr/bin/xdvipdfmx': No such file or directory I tried to reinstall the texlive-dvipdfmx package with no success. I already filed a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1657755 I would like to know if some of you has this problem too, and if (s)he already found a workaround. Thank you in advance for your help. Best, Marco ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: persistent name from ifcfg-internal
On 12/11/18 11:52 AM, sean darcy wrote:
On 12/11/18 12:54 AM, Samuel Sieb wrote:
On 12/10/18 4:22 PM, sean darcy wrote:
I'm trying to get the interface on a multi-homed machine named
"internal"
ifconfig
enp1s0: flags=4099 mtu 1500
ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet)
Is that the full ifconfig output for that interface or does it have
the right IP address as well?
I haven't connected the port yet. Before I do I need to make sure I've
got the correct internet name.
As I understand, NM scans the ifcfg files for HWADDR's. If there's a
match, it names the interface the DEVICE name.
What does "nmcli d" give you?
___
nmcli d
DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected 1stFloor_5GHz 2
enp1s0 ethernet unavailable --
lo loopback unmanaged --
sean
___
And, FWIW:
cat /etc/udev/rules.d/40-persistent-net.rules
# this is the pci ethernet port
# udevadm info -a -p /sys/class/net/enp1s0/
# r8169 :01:00.0 eth0: RTL8168g/8111g, 50:7b:9d:0b:8a:ab, XID
50900880, IRQ 44
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="50:7b:9d:0b:8a:ab", ATTR{dev_id}=="0x0",
ATTR{type}=="1", NAME="internal"
But now nm handles naming , not udev, correct ?
sean
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: persistent name from ifcfg-internal
On 12/11/18 12:54 AM, Samuel Sieb wrote: On 12/10/18 4:22 PM, sean darcy wrote: I'm trying to get the interface on a multi-homed machine named "internal" ifconfig enp1s0: flags=4099 mtu 1500 ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet) Is that the full ifconfig output for that interface or does it have the right IP address as well? I haven't connected the port yet. Before I do I need to make sure I've got the correct internet name. As I understand, NM scans the ifcfg files for HWADDR's. If there's a match, it names the interface the DEVICE name. What does "nmcli d" give you? ___ nmcli d DEVICE TYPE STATECONNECTION wlp2s0 wifi connected1stFloor_5GHz 2 enp1s0 ethernet unavailable -- lo loopback unmanaged-- sean ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Can't boot kernel-4.19.6-200.fc28.x86_64
Le 11/12/2018 à 17:34, Paolo Galtieri a écrit : > Folks, > this morning I rebooted one of my systems. The system ended up > dropping into emergency mode. I ran journalctl -xb to see why it failed > to boot and I saw the following errors: > > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_memslot > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_pin_pages > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_info_cap_shift (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_set_irqs_validate_and_prepare (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_device_put > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_pfn (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_from_dev > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_put_kvm (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_write_guest > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > kvm_slot_page_track_remove_page (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > kvm_page_track_register_notifier (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_parent_dev > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_unpin_pages > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > kvm_is_visible_gfn (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > kvm_page_track_unregister_notifier (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_device_get_from_dev (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > kvm_slot_page_track_add_page (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_register_notifier (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_info_add_capability (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_get_drvdata > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > mdev_register_device (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_dev (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > mdev_unregister_device (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol > vfio_unregister_notifier (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_read_guest > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_set_drvdata > (err -2) > Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_get_kvm (err -2) > > I'm sure I booted up on 4.19.6 on this system before without errors. In > fact my other system is running 4.19.6 so what might have changed to > cause this failure? The system booted fine on 4.19.5. I had a similar problem: the / partition was not the good one check in the /boot/grub2/grub.cfg file if the / partition is the same for kernels 4.19.6 and 4.19.5 -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Can't boot kernel-4.19.6-200.fc28.x86_64
Folks, this morning I rebooted one of my systems. The system ended up dropping into emergency mode. I ran journalctl -xb to see why it failed to boot and I saw the following errors: Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_memslot (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_pin_pages (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_info_cap_shift (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_set_irqs_validate_and_prepare (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_device_put (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_pfn (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_from_dev (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_put_kvm (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_write_guest (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_slot_page_track_remove_page (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_page_track_register_notifier (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_parent_dev (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_unpin_pages (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_is_visible_gfn (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_page_track_unregister_notifier (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_device_get_from_dev (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_slot_page_track_add_page (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_register_notifier (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_info_add_capability (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_get_drvdata (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_register_device (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_dev (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_unregister_device (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol vfio_unregister_notifier (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_read_guest (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol mdev_set_drvdata (err -2) Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol kvm_get_kvm (err -2) I'm sure I booted up on 4.19.6 on this system before without errors. In fact my other system is running 4.19.6 so what might have changed to cause this failure? The system booted fine on 4.19.5. Any help is appreciated. Thanks, Paolo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mysqld refuses to start after upgrade to Fedora 29
Hello Danny and everybody else, MariaDB & MySQL maintainer here! I see I made it late, however I'll drop here some more answers & tips: > I don't know where else to ask. This is a right place. Other good places could be Fedora IRC, create bugzilla ticket ... or write me personal mail as a last resort :) (can be found in the package changelog) > I've just upgraded from Fedora 28 to Fedora 29 and mysqld (version 8.0.13) > won't start. Between F28 & F29 is a big update MySQL 5.7.24 --> 8.0.13 MariaDB 10.2.19 --> 10.3.10 > Keep in mind that you're really running mariadb ... DNF will resolve "mysql" to "mariadb"; the "community-mysql" is the original MySQL. You can check anytime what you have installed by $ dnf list installed | grep -e "mysql" -e "mariadb" In Fedora it is even possible to have server of one and client from another, but consider it an experimental feature instead of recommended setup. > I don't want to mess around switching to MariaDB, do you think that will > cause more problems if I do? Depends. Shouldn't. It is simmilar to normal database upgrade. For small applications, it may be drop-in replacement, for huge applications, you'd need to fix all incompatibilities and can be tricky. Anyway I wouldn't recommend switching to the other database as an attemp to fix issues with the previous. If you feel you need different software, try downgrade to the previous version. Or try Fedora Modules. (providing MySQL 5.7 on F29) > "systemctl start mysqld" This is the corrct form. For compatibility reasons, the MariaDB can be started with the same command, instead of its native: $ systemctl start mariadb So nothing to change here. > SELinux I keep an eye on both MariaDB & MySQL. Both must run without SELinux issues. If there would be a problem, bugzilla ticket is the solution. Can be worth checking, though. Errors are a human nature. > Found another log file I didn't know existed!! Standard setup are logs in "/var/log/mysqld/" and some usefull messages in the systemd journal. > Some of those are fixable via mysql_upgrade After *every* upgrade, "mysql_upgrade" utility should be ran. Recomended steps for in-place upgrade for MariaDB (for MySQL it would be very simmilar): https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8-beta/html-single/configuring_and_deploying_different_types_of_servers/#mariadb-in-place-upgrade There's: ExecStartPost=@libexecdir@/mysql-check-upgrade check in the service that should have been triggered automaticly, though. Michal -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Tue, Dec 11, 2018 at 11:40 AM Danny Horne via users wrote: > > On 11/12/2018 12:37 am, Rick Stevens wrote: > > > > Yup. Some of those are fixable via mysql_upgrade, others are fairly > > important and appear to be caused by using a newer mysqld that's not > > backwards compatible with your previous version. You didn't say which > > version of MySQL you were running before and whether 8.0.13 was > > compatible with it. Generally, the website has info on what's compatible > > and how to convert from old to new. > > > > mysql_upgrade seems to have done the trick - > > 2018-12-11T10:35:31.114349Z 0 [System] [MY-010910] [Server] > /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.13) Source distribution. > 2018-12-11T10:35:31.627020Z 0 [System] [MY-010116] [Server] > /usr/libexec/mysqld (mysqld 8.0.13) starting as process 7131 > 2018-12-11T10:35:33.197087Z 0 [Warning] [MY-010068] [Server] CA > certificate ca.pem is self signed. > 2018-12-11T10:35:33.217669Z 0 [System] [MY-010931] [Server] > /usr/libexec/mysqld: ready for connections. Version: '8.0.13' socket: > '/var/lib/mysql/mysql.sock' port: 3306 Source distribution. > 2018-12-11T10:35:33.343046Z 0 [System] [MY-011323] [Server] X Plugin > ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' > bind-address: '::' port: 33060 > > Thanks so much for your help Rick > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Install on Zotac Zbox CI327?
Hello, On Sun, 28 May 2017 21:20:13 +0200 Branko Grubic wrote: > On Sun, 2017-05-28 at 15:12 +0200, wwp wrote: > > 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~7Luk2TC3bsaDuuT15M1UNdIG > > YhyRLivL9gydE= > > > > 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, > > > > > Hi, > > I have no experience with that specific hardware, but maybe you can try > stable re-spins[1] (live/installable images with current updates). > Maybe it's a good balance between F25 final and F26/F27 (pre- > release/dev), and it should have 4.10.x kernel. > > > [1] http://dl.fedoraproject.org/pub/alt/live-respins/ For the sake of the archives, I tried booting using RHEL8-beta on this hardware (Zotac Zbox CI327 with Intel Celeron N3450 inside) and it behaves exactly like a CentOS 7, no luck. Debian 9 (as Ubuntu 17+) just works out of the box. Regards, -- wwp pgpdkVjA7PUrQ.pgp Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mysqld refuses to start after upgrade to Fedora 29
On 11/12/2018 12:37 am, Rick Stevens wrote: Yup. Some of those are fixable via mysql_upgrade, others are fairly important and appear to be caused by using a newer mysqld that's not backwards compatible with your previous version. You didn't say which version of MySQL you were running before and whether 8.0.13 was compatible with it. Generally, the website has info on what's compatible and how to convert from old to new. mysql_upgrade seems to have done the trick - 2018-12-11T10:35:31.114349Z 0 [System] [MY-010910] [Server] /usr/libexec/mysqld: Shutdown complete (mysqld 8.0.13) Source distribution. 2018-12-11T10:35:31.627020Z 0 [System] [MY-010116] [Server] /usr/libexec/mysqld (mysqld 8.0.13) starting as process 7131 2018-12-11T10:35:33.197087Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2018-12-11T10:35:33.217669Z 0 [System] [MY-010931] [Server] /usr/libexec/mysqld: ready for connections. Version: '8.0.13' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution. 2018-12-11T10:35:33.343046Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/lib/mysql/mysqlx.sock' bind-address: '::' port: 33060 Thanks so much for your help Rick ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Mysqld refuses to start after upgrade to Fedora 29
On 11/12/2018 12:37 am, Rick Stevens wrote: Also, how did you get it to start? Once I found the right log file I saw that there were a few incompatible entries in my.cnf I'll take a look at the other errors when I'm awake :) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: How do I : one static DNS , one from DHCP ?
On 12/11/18 4:51 PM, Ed Greshko wrote: > dnssec is a concern is *not* a concern -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: How do I : one static DNS , one from DHCP ?
On 12/11/18 3:10 PM, Tim via users wrote: > Allegedly, on or about 8 December 2018, sean darcy sent: >> What I want is: >> >> nameserver 127.0.0.1 >> nameserver > Is the DHCP server configurable by you? If so, then enter the list of > DNS servers that you want clients to use into the DHCP server, and let > it configure your clients. > I think you missed one important line in the original post. # Generated by dnssec-trigger-script dnssec-triggerd overrides what it provided by the DHCP server. I have no experience running dnssec-triggerd, but I would think it has some configuration allowing one to specify additional nameservers. And, it seems to me, dnssec is a concern to the OP so I wonder why run dnssec-trigger at all. -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: kernel 4.19.6-300.fc29.x86_64 does not boot
Le 11/12/2018 à 08:12, Tim via users a écrit : > Allegedly, on or about 11 December 2018, François Patte sent: >> For an unknown reason the installation of the new kernel wrote a >> wrong grub.cfg pointing as the root partition an unused partition on >> my system Strangely when I run grub2-mkconfig this was corrected. >> I cannot understand why the installation script of the kernel has >> made this mistake. > > On some motherboards, when you boot from removable media, all the other > drives get a different drive number than when you don't boot from it. I don't understand your remark: I didn't boot on a removable media, I just updated my system using dnf -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
