I have a fedora29 system in our colo that's a few years old now and
just goes catatonic and stops responding after a few days. It's
happened a few times now, even with different kernels, so I suspect
it's a memory or hardware problem.
Is it possible to run memtest without having physical access to the
machine to insert a USB stick or CDROM?
After the machine reboots (via IPMI access), there's nothing in the
logs and no abrt-cli info on a kernel crash or other info I can find
about why it died.
What else can I do to troubleshoot this without having to drive to the
colo to check on it?
The last entry from journalctl just before it stopped responding was
just a regular nrpe entry, unrelated to the crash.
I've pasted the current dmesg output here:
Any ideas greatly appreciated.
I've got an old system, unmodified for years. I run emacs 21.2.1
on it using ssh X forwarding to put the emacs window on my
desktop. I've just done an update of my fedora 29 system
after being away for a couple of weeks, and now the fonts
are all messed up.
I'm never absolutely sure about these things, but I believe the
old X programs get their fonts from the server, and suddenly the
fonts when I try to run this old emacs with my fedora 29 desktop
as the server have gone completely wacko.
For instance, emacs claims the frame is 101 characters wide, but
if I type characters across the window, I can see it is actually
81 characters wide (this is using terminus fonts which were also
updated in the pile of updates I got this morning).
Anyone have any clue what might be going on here? Who is lying to whom
about the fonts?
I am not able to install the java compiler on fedora (
I read that fedora not support directly gcj ...
So I try to work around, to install it indirectly, but I have to much
problem to find the necessary dependencies...
Ho to do ?
any advice will welcome
Anyone know what happened to wireshark-qt? I looked at the devel list and was
only able to find wireshark-gtk being dropped, with the possible renaming of
John M. Harris, Jr. <johnmh(a)splentity.com>
I'd like to ask about mod_authnz_pam. I've trying to test a
very simple config, like here:
You can see I'm trying dovecot's pam.
But this fails:
check pass; user unknown
password check failed for user (me)
pam_unix(dovecot:auth): authentication failure; logname=
uid=48 euid=48 tty= ruser= rhost=10.3.1.21 user=me
This should be simple and should work, right?
many thanks, L.
F28 Pgadmin4 experience out of the box is not good for me
sudo dnf install pgadmin4
"An error occurred initialising the application server: Failed to launch
the application server, server thread exiting."
I already had a similar problem with official rpm package in F25, this
looks exactly the same. Anyone else?
I setup my first Fedora 29 server (for FreeIPA).
Now I need to copy a file to another client.
When I execute scp I get this in terminal (after entering password) and file is not transferred:
[admin@pc7-cubi3 ~]$ scp firstname.lastname@example.org:/tmp/client1.keytab krb5.keytab
The authenticity of host 'ipa-master.biszumbitterenen.de (192.168.100.252)' can't be established.
\033[0m\033[1;34m /:-------------:\ \033[0m\033[1;34m locadmin\033[0m\033[1m(a)\033[0m\033[0m\033[1;34mipa-master.biszumbitterenen.de\033[0m
I didn't experience any similar issue on other Linux distros (Arch, Debian, Suse).
Can you please advise what's causing this error?
I have a desktop and a laptop, both with fully updated Fedora 29. The
laptop is a fresh installation while the desktop has been upgraded from
previous versions of Fedora. And I have Josm installed on both.
Now the problem is that on the desktop Josm has become really slow. You
need some serious patience to use it. On the laptop it works fine as it
did on the desktop before. I've tried to reinstall Josm, but that
Josm is a Java application.
Any idea what could be wrong?
Does anyone have suggestions for easily simulating a missing volume in
LVM on bare metal? I'm trying to test behaviour like a network
attached physical volume going missing (actually, a network mounted
virtual disc image). The normal loopback approach to testing falls a
bit short, while overwriting the file can corrupt the PV, removing it
seems very hard, as even force removing the loop device seems to leave
it connected to the file handle, meaning a reboot is required to
really clear things, and so at the minute I can only test what happens
if a drive is missing after boot, rather than disappears during
operation. (A bit easier to do with discs on a VM, but doing testing
on a laptop.)
I currently run a couple of VMs (one Windows 10 and one Fedora Server)
under QEMU/KVM. I wanted to create a new one and got this:
Unable to complete install: 'internal error: process exited while connecting to monitor: 2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global IvyBridge-IBRS-x86_64-cpu.osxsave=on: Property '.osxsave' not found'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 2559, in _do_async_install
File "/usr/share/virt-manager/virtinst/guest.py", line 465, in start_install
File "/usr/share/virt-manager/virtinst/guest.py", line 401, in _create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
File "/usr/lib64/python3.7/site-packages/libvirt.py", line 3718, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirt.libvirtError: internal error: process exited while connecting to monitor: 2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global IvyBridge-IBRS-x86_64-cpu.osxsave=on: Property '.osxsave' not found
The last line is the key. This is similar to a bug I had a while back and reported at the time:
When it happened before I edited the XML file to remove the .osxsave
flag and that solved the problem. However now it's happening with a
fresh VM so there's no XML file to edit. Note that the new VM is a
small Windows test install with no special configuration, i.e.
everything just uses the default settings.
I've posted about this on the VFIO list but haven't received a solution
so far. See