how to correctly log without journald (and its blobs)?
by Franta Hanzlík
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 years, 11 months
how to (re-?)construct grub menu?
by William
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.
6 years, 1 month
Running local SSH as background process - possible??
by bruce
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 years, 5 months
Error building mkvtoolnix-9.6.0-1.fc26.src.rpm
by JD
$ 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.
6 years, 6 months
Openvpn start fails on reboot
by Stephen Davies
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.
6 years, 6 months
Pulseaudio: Hardware Routing
by Frank Elsner
Hello,
for reasons I have to send the input from an audio interface to an other.
I can do this with
pactl load-module module-loopback \
source="alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo" \
sink="alsa_output.usb-M-AUDIO_M-Track_Hub-00.analog-stereo"
and this works as desired.
Currently I have to issue this command (realized as procedure) after each login.
I want a permanent solution. Where to place this command? Or is there an other
permant solution beside this command?
BTW, rc.local doesnt't work.
Any pointer welcome.
Kind regards, Frank
6 years, 8 months
Lost wired connection
by Lucélio Gomes de Freitas
Hi,
Somebody helps?
Old "Fedora 20-x86_64" installed and working. Due to a problem,
I Changed my motherboard and lost network(Internet) connection.
How to recover connection before install Fedora-Kde-live-25-1-3?
Thanks.
6 years, 8 months
Fedora on a NUC?
by Temlakos
Everyone:
Does anyone have experience with installing Fedora on a NUC?
In case anyone here doesn't know what a NUC is: it happens to stand for
Next Unit of Computing. It is a 5.4 x 4.9 x 4.5-/inch/ box having the
minimal number of components to support desktop functions. You equip it
with your own hard drive, keyboard, mouse, etc., and can drive up to a
4K Ultra-style monitor. Some people use its VESA mount to mount it on
the back of their TV. Result: instant smart TV--smarter than any TV in
the store, because it can handle word processing and regular Web apps in
addition to video and audio streaming.
Word is that it normally ships with Windows 10, but can support any
number of distributions of Linux. I want to know whether Fedora is one
of them.
It sounds like the ideal small office/media lab/home theater solution.
Pair it with a good NAS and you have all the computing power you need,
with a fraction of the physical--and carbon--footprint.
Comments? Suggestions? Success stories? Horror stories?
Temlakos
6 years, 8 months