Anacron question

2024-07-18 Thread Frederic Muller

Hi!

Following up on a old question of mine about daily backup tools I did 
follow the advice and am using borg successfully. So thank you for that: 
very easy to setup and works great.


However wanting to do that daily automatically from my laptop to a local 
network drive I looked for a way to start the backup like 10 minutes 
after I switched on the PC and only once a day which led me to anacron.


Installed it, set up the anacron job and the problems arrived. Initially 
tried to run it as my user but that didn't work.


@daily  10  daily-backup    su fred -c "/home/fred/dao2/tech/daily.sh"

Simplified the command to run as root but that also didn't work. It 
seems anacron doesn't run.


@daily  10  daily-backup    /home/fred/dao2/tech/daily.sh


Finally found one or two post saying you can add a cron job that runs 
hourly and launch the anacron tasks.


I have this in my user crontab:

@hourly /usr/sbin/anacron -s -t $HOME/.anacron/etc/anacrontab -S 
$HOME/.anacron/spool


This unfortunately get the task run randomly and definitely not once per 
day. I sometimes get it to run 3 or 4 times in the same day while 
sometimes I feel it's does not run and so I run it manually.


So my question is how do I get anacron "fixed" and running once daily?

Thank you.

Fred

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Anacron question

2024-07-18 Thread Patrick O'Callaghan
On Thu, 2024-07-18 at 14:12 +0700, Frederic Muller wrote:
> Hi!
> 
> Following up on a old question of mine about daily backup tools I did
> follow the advice and am using borg successfully. So thank you for
> that: 
> very easy to setup and works great.
> 
> However wanting to do that daily automatically from my laptop to a
> local 
> network drive I looked for a way to start the backup like 10 minutes 
> after I switched on the PC and only once a day which led me to
> anacron.
> 
> Installed it, set up the anacron job and the problems arrived.
> Initially 
> tried to run it as my user but that didn't work.
> 
> @daily  10  daily-backup    su fred -c
> "/home/fred/dao2/tech/daily.sh"
> 
> Simplified the command to run as root but that also didn't work. It 
> seems anacron doesn't run.
> 
> @daily  10  daily-backup    /home/fred/dao2/tech/daily.sh
> 
> 
> Finally found one or two post saying you can add a cron job that runs
> hourly and launch the anacron tasks.
> 
> I have this in my user crontab:
> 
> @hourly /usr/sbin/anacron -s -t $HOME/.anacron/etc/anacrontab -S 
> $HOME/.anacron/spool
> 
> This unfortunately get the task run randomly and definitely not once
> per 
> day. I sometimes get it to run 3 or 4 times in the same day while 
> sometimes I feel it's does not run and so I run it manually.
> 
> So my question is how do I get anacron "fixed" and running once
> daily?

Anacron probably isn't the right tool for this, since you don't want to
run the backup at a fixed time but "10 minutes after I switch on the PC
and only once per day". Unless you always switch on the PC at the same
time, you may be better triggering the job at boot time. You can
trigger something at boot by using the "@reboot" keyword (crontab(5)).
You'll want to run a script that a) checks if backup has already run,
and b) waits 10 minutes before running it. You can check if it has run
by adding a hook to your backup script that just logs the last time it
finished successfully.

BTW, I recommend using borgmatic for regular borg runs, but you still
have to take care of the timing yourself.

poc


-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Updating failed midway. System will not boot.

2024-07-18 Thread murph nj
I got it running.  The write-up will not be super complete, but here goes.

When I checked for kernels, I saw that there was a new one available
(6.9.9?)  That installed OK, and seemed to resolve the uname-r issue.

Another package (ko-something) that was part of the plamsa desktop was
causing a problem.  I removed plasma desktop, and was able to
continue.   (I've since re-installed, and KDE is working)

It seems I only see one small problem at this point.
libvt-daemon is 4.1.0-1.fc28 (!) so I suspect that this may have been
quietly lurking for a while.
It will not uninstall, even if I have a newer one installed and
updated.  I've double-checked, and removed the last remaining VM on
this machine, no longer an issue.

I am able to boot fully now, as multi-user, as well as graphical.  I
think that with this mess, between the hardware failure, and the
disaster, and subsequent recovery, I may just move all of my work off
of this machine, and onto a newer one, and finally semi-retire this
laptop.

On Wed, Jul 17, 2024 at 11:08 PM murph nj  wrote:
>
> Reinstalling all of those did not seem to resolve it.
>
> As kernel-uname-r is part of kernel-core, I tried reinstalling
> kernel-core 6.8.8, which is installed, but not currently running.
> I got "Installed package kernel-core-6.8.8-300.fc40.x86_64 (From
> @System) not available."
>
> I already removed the 6.8.10 kernel, but that didn't improve things.
> I'm going to put this aside for a few hours before I do something
> ill-advised, and take a fresh look in the morning.
>
> On Wed, Jul 17, 2024 at 10:54 PM Jeffrey Walton  wrote:
> >
> > On Wed, Jul 17, 2024 at 10:20 PM murph nj  wrote:
> > >
> > > Progress:
> > >
> > > I've added mirrors.fedoraproject.org and mirror.math.princeton.edu to
> > > my /etc/hosts, and can do some dnf work:
> > >
> > > When I do a dnf distro-sync I get an error:
> > >
> > > package kernel-modules-extra-6.8.9-300.fc.x86_64 from @System requires
> > > kernel-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the providers
> > > can be installed
> > > package kernel-6.8.9-300.fc.x86_64 from @System requires
> > > kernel-core-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the
> > > providers can be installed
> > > package kernel-6.8.9-300.fc.x86_64 from @System requires
> > > kernel-modules-uname-r - 6.8.9-300.fc40.x86.x86.64 but none of the
> > > providers can be installed
> > > all with --conflicting requests
> > >
> > > (These are are retyped from the other machine, so don't panic if I
> > > made a typo somewhere)
> > >
> > > The system is booted from a 6.8.10 kernel, but got the same error when
> > > I tried to boot from the 6.8.9 kernel as well.
> > >
> > > Suggestions?
> >
> > Maybe try to reinstall dbus first, since that seems to be an earlier 
> > problem?
> >
> > $ lsb_release -a
> > Distributor ID: Fedora
> > Description:Fedora Linux 40 (KDE Plasma)
> > Release:40
> > Codename:   n/a
> >
> > $ dnf reinstall dbus
> > dbus-1:1.14.10-3.fc40.x86_64
> > dbus-broker-36-2.fc40.x86_64
> > dbus-common-1:1.14.10-3.fc40.noarch
> > dbus-daemon-1:1.14.10-3.fc40.x86_64
> > dbus-libs-1:1.14.10-3.fc40.x86_64
> > dbusmenu-qt5-0.9.3-0.34.20160218.fc40.x86_64
> > dbus-tools-1:1.14.10-3.fc40.x86_64
> > dbus-x11-1:1.14.10-3.fc40.x86_64
> >
> > Jeff
> > --
> > ___
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> > Do not reply to spam, report it: 
> > https://pagure.io/fedora-infrastructure/new_issue
-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Updating failed midway. System will not boot.

2024-07-18 Thread Jeffrey Walton
On Thu, Jul 18, 2024 at 10:45 AM murph nj  wrote:
>
> I got it running.  The write-up will not be super complete, but here goes.
>
> When I checked for kernels, I saw that there was a new one available
> (6.9.9?)  That installed OK, and seemed to resolve the uname-r issue.
>
> Another package (ko-something) that was part of the plamsa desktop was
> causing a problem.  I removed plasma desktop, and was able to
> continue.   (I've since re-installed, and KDE is working)
>
> It seems I only see one small problem at this point.
> libvt-daemon is 4.1.0-1.fc28 (!) so I suspect that this may have been
> quietly lurking for a while.
> It will not uninstall, even if I have a newer one installed and
> updated.  I've double-checked, and removed the last remaining VM on
> this machine, no longer an issue.
>
> I am able to boot fully now, as multi-user, as well as graphical.  I
> think that with this mess, between the hardware failure, and the
> disaster, and subsequent recovery, I may just move all of my work off
> of this machine, and onto a newer one, and finally semi-retire this
> laptop.

You may (probably?) be able to cleanup that F28 package by following
the post-upgrades steps at
.
There's also a section on Resolving post-upgrade issues.

Jeff
-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Anacron question

2024-07-18 Thread Mike Wright

On 7/18/24 00:12, Frederic Muller wrote:

Hi!

Following up on a old question of mine about daily backup tools I did 
follow the advice and am using borg successfully. So thank you for that: 
very easy to setup and works great.


However wanting to do that daily automatically from my laptop to a local 
network drive I looked for a way to start the backup like 10 minutes 
after I switched on the PC and only once a day which led me to anacron.
How about a systemd timer that is fired fired 10 minutes after boot. 
Its ExecStart could call a script that checks for a touched file ( a 
semaphore ).  If the semaphore is not from today it would call the 
backup program.  On successful completion it would refresh the semaphore.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


no sound on bluetooth headphones

2024-07-18 Thread Geoffrey Leach
Using bluetooth on Fedora 40/xcfe4 for the first time

Headphone pair OK
Bluetooth is active and running
Bluetooth Manager sees headphones
Volume Control  does not see the headphones

Testing with mplayer foo.mp3; sound at speakers

I'm assuming that there is some critical enabling that needs to happen.
Suggestions?

Thanks

-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: KVM image fails to resume after f38->40 upgrade

2024-07-18 Thread Samuel Sieb

On 7/13/24 8:47 AM, fed...@eyal.emu.id.au wrote:

I still do not have a solution.

Changing the CPU model in the vm details is mostly "to be applied on 
next boot",

but I am not in a position to boot (I need to unpause).

If anyone understands what model to set, or how else to get past this 
issue then please offer your wisdom.


As an aside, what lead to this problem in the first place? The same 
problem when booting my last f30 kernel

so it must be (?) some libvirt change.

I hope that as a last resort I will be able to cold boot the vm, linux 
is rather good with crash recovery.

Last resort.


I ran into this as well.  Something changed with CPU flags.  I couldn't 
find any way to get it to resume, it will most likely need to be restarted.


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Anacron question

2024-07-18 Thread Patrick O'Callaghan
On Thu, 2024-07-18 at 09:23 -0700, Mike Wright wrote:
> On 7/18/24 00:12, Frederic Muller wrote:
> > Hi!
> > 
> > Following up on a old question of mine about daily backup tools I
> > did 
> > follow the advice and am using borg successfully. So thank you for
> > that: 
> > very easy to setup and works great.
> > 
> > However wanting to do that daily automatically from my laptop to a
> > local 
> > network drive I looked for a way to start the backup like 10
> > minutes 
> > after I switched on the PC and only once a day which led me to
> > anacron.
> How about a systemd timer that is fired fired 10 minutes after boot. 
> Its ExecStart could call a script that checks for a touched file ( a 
> semaphore ).  If the semaphore is not from today it would call the 
> backup program.  On successful completion it would refresh the
> semaphore.

Essentially what I said, but I think a crontab "@reboot" line is easier
to set up.

poc
-- 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: KVM image fails to resume after f38->40 upgrade

2024-07-18 Thread fedora

On 19/7/24 6:42 am, Samuel Sieb wrote:

On 7/13/24 8:47 AM, fed...@eyal.emu.id.au wrote:

I still do not have a solution.

Changing the CPU model in the vm details is mostly "to be applied on next boot",
but I am not in a position to boot (I need to unpause).

If anyone understands what model to set, or how else to get past this issue 
then please offer your wisdom.

As an aside, what lead to this problem in the first place? The same problem 
when booting my last f30 kernel
so it must be (?) some libvirt change.

I hope that as a last resort I will be able to cold boot the vm, linux is 
rather good with crash recovery.
Last resort.


I ran into this as well.  Something changed with CPU flags.  I couldn't find 
any way to get it to resume, it will most likely need to be restarted.


I tested a restart (using a clone) and it came up.

I only needed to change the watchdog

old 
new 

I created a thread on the users list

https://lists.libvirt.org/archives/list/us...@lists.libvirt.org/thread/DHYRALPVDMT2LFT2WYXRKHIOU6IAQVBX/
but got no response :-)

--
Eyal at Home (fed...@eyal.emu.id.au)

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Anacron question

2024-07-18 Thread Frederic Muller

On 18/07/2024 18:18, Patrick O'Callaghan wrote:

On Thu, 2024-07-18 at 14:12 +0700, Frederic Muller wrote:

Hi!

Following up on a old question of mine about daily backup tools I did
follow the advice and am using borg successfully. So thank you for
that:
very easy to setup and works great.

However wanting to do that daily automatically from my laptop to a
local
network drive I looked for a way to start the backup like 10 minutes
after I switched on the PC and only once a day which led me to
anacron.

Installed it, set up the anacron job and the problems arrived.
Initially
tried to run it as my user but that didn't work.

@daily  10  daily-backup    su fred -c
"/home/fred/dao2/tech/daily.sh"

Simplified the command to run as root but that also didn't work. It
seems anacron doesn't run.

@daily  10  daily-backup    /home/fred/dao2/tech/daily.sh


Finally found one or two post saying you can add a cron job that runs
hourly and launch the anacron tasks.

I have this in my user crontab:

@hourly /usr/sbin/anacron -s -t $HOME/.anacron/etc/anacrontab -S
$HOME/.anacron/spool

This unfortunately get the task run randomly and definitely not once
per
day. I sometimes get it to run 3 or 4 times in the same day while
sometimes I feel it's does not run and so I run it manually.

So my question is how do I get anacron "fixed" and running once
daily?

Anacron probably isn't the right tool for this, since you don't want to
run the backup at a fixed time but "10 minutes after I switch on the PC
and only once per day". Unless you always switch on the PC at the same
time, you may be better triggering the job at boot time. You can
trigger something at boot by using the "@reboot" keyword (crontab(5)).
You'll want to run a script that a) checks if backup has already run,
and b) waits 10 minutes before running it. You can check if it has run
by adding a hook to your backup script that just logs the last time it
finished successfully.

BTW, I recommend using borgmatic for regular borg runs, but you still
have to take care of the timing yourself.

poc


I hear you. Now I went the anacron direction as the man page just says that:

"Description

Anacron is used to execute commands periodically, with a **frequency 
specified in days**. Unlike cron(8), it does not assume that the machine 
is running continuously. Hence, it can be used on machines that aren't 
running 24 hours a day, to control regular jobs as daily, weekly, and 
monthly jobs.


Anacron reads a list of jobs from a configuration file, /etc/anacrontab 
(see anacrontab(5)). This file contains the list of jobs that Anacron 
controls. Each job entry specifies a period in days, **a delay in 
minutes**, a unique job identifier, and a shell command.


For each job, Anacron **checks whether this job has been executed** in 
the last n days, where n is the period specified for that job. If not, 
Anacron runs the job's shell command, after waiting for the number of 
minutes specified as the delay parameter. "


So it runs daily, allow for a delay when starting and supposidely checks 
whether the job has been executed... seems like what I was looking for no?


And arguably modifying my backup script to check if it ran today already 
and then run it if not will probably be faster than troubleshooting 
anacron at this point. ;-)


Thank you.

@Mike I also read that on systemd distro cron and anacron are things of 
the past and we should be looking at systemd timers... so thank you for 
that.


Fred


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue