Cron errors(?) in logwatch
by SternData
In F33's logwatch, I'm seeing a CRON block full of lines like this:
This seems to be new. Or, at least, I can't tie it to anything I've
done diffrently....
--------------------- Cron Begin ------------------------
**Unmatched Entries**
CMDEND (run-parts /etc/cron.hourly)
--
-- Steve
3 years
Inhibit sleep from systemd service
by Gordon Messmer
I'd like to inhibit suspend while backups run on my laptop. I'm
scheduling those backups with a systemd timer[1] and service[2]. I've
read that the default polkit policy only permits inhibiting suspend from
within a login session, so I've also tried to add rules to allow the
root user to inhibit suspend[3]. However, with all of those in place, I
still get errors that I think indicate that the "systemd-inhibit"
command is failing[4].
I'm running this on Fedora 33. Has anyone successfully used
systemd-inhibit from a systemd unit?
1:
# cat /usr/lib/systemd/system/run-borg.timer
[Unit]
Description=Periodic borg backup
[Timer]
OnCalendar=08..20/2:00
Persistent=true
[Install]
WantedBy=timers.target
2:
# cat /usr/lib/systemd/system/run-borg.service
[Unit]
Description=Run borg backup
RequiresMountsFor=/var/log
ConditionACPower=true
[Service]
Type=oneshot
ExecStart=/usr/bin/systemd-inhibit --who=borg-backup '--why=Backup in
progress' --mode=block /root/run-borg
3:
# cat /etc/polkit-1/rules.d/root-inhibit-suspend.rules
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.inhibit-block-shutdown" &&
subject.isInGroup("root")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.inhibit-block-sleep" &&
subject.isInGroup("root")) {
return polkit.Result.YES;
}
});
polkit.addRule(function(action, subject) {
if (action.id == "org.freedesktop.login1.inhibit-block-idle" &&
subject.isInGroup("root")) {
return polkit.Result.YES;
}
});
4:
Mar 21 18:00:41 vagabond systemd[1]: Starting Run borg backup...
Mar 21 18:00:41 vagabond systemd-inhibit[19767]: read: Connection reset
by peer
Mar 21 18:00:41 vagabond systemd-inhibit[19761]: /root/run-borg failed
with exit status 1.
Mar 21 18:00:41 vagabond systemd[1]: run-borg.service: Main process
exited, code=exited, status=1/FAILURE
Mar 21 18:00:41 vagabond systemd[1]: run-borg.service: Failed with
result 'exit-code'.
Mar 21 18:00:41 vagabond systemd[1]: Failed to start Run borg backup.
3 years
f33:: php not working
by Adrian Sevcenco
Hi! I'm trying to make work something like this:
cat phpinfo.php
<?php
phpinfo();
?>
it would seem that mod_php is no longer used .. ok, i installed php_fpm
(which was excluded and masked because it seems silly to me to run 2 processes for some crappy pages)
i tried to increase the log level for php.ini but nothing worked ..
Does anyone know the magic for php to work again?
Thank you!
Adrian
3 years
fan control
by GianPiero Puccioni
Hi,
I have a Toshiba satellite pro (R50-B-109) and since I updated to kernel 5.11.17
the fan runs constantly even if sensors report Temps around 35C.
If I load the previous Kernel 5.10.21 fans are silent and Temp is around 40C.
What changed?
I have no control over the fans as pwmconfig cannot find any pwm-capable sensors.
Is there any solution for this? A different utility for Tosh fans maybe?
Or it was wrong before and fans shuold be running?
Thanks,
GianPiero
3 years
skype 8.69
by Patrick Dupre
Hello,
To update skype, I followed the instructions provided by:
https://www.if-not-true-then-false.com/2012/install-skype-on-fedora-cento...
but
it finally failed
dnf install /home/pdupre/rpmbuild/RPMS/x86_64/skypeforlinux-8.69.0.77-1.x86_64.rpm
Last metadata expiration check: 0:25:11 ago on Mon 22 Mar 2021 10:00:16 PM CET.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Upgrading:
skypeforlinux x86_64 8.69.0.77-1 @commandline 72 M
Transaction Summary
================================================================================
Upgrade 1 Package
Total size: 72 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Error: Transaction test error:
package skypeforlinux-8.69.0.77-1.x86_64 does not verify: Header SHA256 digest: BAD (Expected e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 != 08f28c1f908057f6490ac39c9f6b9ee1a4225b0f0df64f2008c64027b5268739)
What is wrong?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===========================================================================
3 years
Fedora 33 - FIPS - Cups
by Winfried de Heiden
Hi all,
I enabled FIPS-mode on my Fedora 33 machine (fips-mode-setup --enable;
reboot) and it all looks fine except printing using Cups. Printing will
throw an error:
Process 10708 (bannertopdf) of user 4 dumped core.
Stack trace of thread 10708:
#0
0x00007f4d169d89d5 raise (libc.so.6 + 0x3d9d5)
#1
0x00007f4d169c18a4 abort (libc.so.6 + 0x268a4)
#2
0x00007f4d16c1f926 _ZN9__gnu_cxx27__verbose_terminate_handlerEv.cold
(libstdc++.so.6 + 0x9e926)
#3
0x00007f4d16c2b1ac _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 +
0xaa1ac)
#4
0x00007f4d16c2b217 _ZSt9terminatev (libstdc++.so.6 + 0xaa217)
#5
0x00007f4d16c2b4c9 __cxa_throw (libstdc++.so.6 + 0xaa4c9)
#6
0x00007f4d16da64e2 _ZN17QPDFCrypto_gnutls8MD5_initEv.cold (libqpdf.so.28
+ 0x3d4e2)
#7
0x00007f4d16dafaa1 _ZN3MD5C1Ev (libqpdf.so.28 + 0x46aa1)
#8
0x00007f4d16e17c67
_ZN4QPDF16compute_data_keyERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiibii
(libqpdf.so.28 + 0xaec67)
#9
0x00007f4d16dfe538 _ZN10QPDFWriter10setDataKeyEi (libqpdf.so.28 + 0x95538)
#10
0x00007f4d16e048fe _ZN10QPDFWriter11writeObjectE16QPDFObjectHandlei
(libqpdf.so.28 + 0x9b8fe)
#11
0x00007f4d16e0f8df _ZN10QPDFWriter5writeEv (libqpdf.so.28 + 0xa68df)
#12
0x000055e157a50c89 generate_banner_pdf (bannertopdf + 0x8c89)
#13
0x000055e157a4c559 main (bannertopdf + 0x4559)
#14
0x00007f4d169c31e2 __libc_start_main (libc.so.6 + 0x281e2)
#15
0x000055e157a4c9ee _start (bannertopdf + 0x49ee)
mrt 23 11:56:06 xxx cupsd[1870]: Job stopped due to filter errors;
please consult the syslog file for details.
Disabling FIPS will make it work again.
Running bannertopdf gives a clue why it is not allowed when using FIPS.
It uses MD% which is not allowed in FIPS:
/usr/lib/cups/filter/bannertopdf 1 xxx '' 1 ''
</usr/share/cups/data/testprint >bannertopdf.pdf
DEBUG: PDF template file doesn't have form. It's okay.
terminate called after throwing an instance of 'std::runtime_error'
what(): gnutls: MD5 error: An algorithm that is not enabled was
negotiated.
Aborted (core dumped)
Any idea how to fix this? Or since Cups seems problematic for FIPS,
bypass FIPS for Cups only?
There is an interesting Bugzilla voor RHEL8 on this
(https://bugzilla.redhat.com/show_bug.cgi?id=1650233) but I can't find
out whether or not this is fixed for Fedora.
Winfried
3 years
boot hang on F33 this morning
by Chris Murphy
Some folks are reporting a hang when booting Fedora 33 this morning
(or also possibly wake from sleep). We're still digging into it but
looks like a work around right now is to boot with parameter:
systemd.mask=raid-check.timer
You can subsequently 'systemctl disable raid-check.timer'. Folks with
md raid setups might want to set a reminder to enable the timer again
once the issue is sorted out.
--
Chris Murphy
3 years