It seems that fcron.minutely on core 178, installed from new not from update, does not work.
In the folder I have my own script and that of the WIO.
Mine doesn’t run and I noticed that the WIO data also doesn’t update as it should every 15 minutes.
If I run my script by hand it works, it is made executable and does not generate errors.
On the contrary if I put this line:
*/1 * * * * /home/nobody/keep-alive/keep-alive
everything works directly in fcrontab
I tried to launch this line by hand, the one present in fcrontab,
test -x /usr/local/bin/run-parts && /usr/local/bin/run-parts /etc/fcron.minutely
both my script and the WIO script are executed, at this point it seems like something related to fcrontab isn’t working
Crontab services are working.
I tried putting the launch of my script and that of WIO in the fcron.hourly folder, but again nothing happens.
fcron as a service is running, I don’t see any alarms in the log.
I have two other ipfires updated and everything works
I think any type of timer doesen’tworks, in fact even updating the pakfire list doesn’t work.
Do you have any idea how to understand where the error is, I wouldn’t want to have to do it all again from scratch.
Incorrect system time can affect SSL/TLS certificate validation, potentially disrupting Pakfire’s functionality. To check time synchronization, run the command ntpq -p.
Here’s an example output from my IPFire setup:
remote refid st t when poll reach delay offset jitter
LOCAL(0) .LOCL. 10 l 47h 64 0 0.000 +0.000 0.000
*crd.circl.lu 220.127.116.11 2 u 667 1024 377 14.577 +1.239 0.574
+18.104.22.168 10.13.100.155 2 u 246 1024 377 9.691 +0.956 0.498
the offset field shows the time difference in milliseconds between your local system and the NTP server. A small offset typically indicates that the time is reasonably synchronized. In my case, around 1 second.
I would also check NTP logs: in the Web Interface /Logs/System Logs/NTP.
this morning when the announcement of the core 179 arrived, on my home firewall I found the list of updates compiled, on this firewall on the contrary the packfire update was stopped at 4 days ago, when I installed it
Unfortunately I think re-installation is your best bet.
I would suggest running the above test on your system after installing and before restoring a backup. Just in case there is something in your configuration setup that is causing this, although I can’t imagine what that might be.
that everything works well again after the re-installation.