| 1 |
On 4/3/20 8:58 am, Jack wrote: |
| 2 |
> On 2020.03.03 19:33, Philip Webb wrote: |
| 3 |
>> 200303 Jack wrote: |
| 4 |
> |
| 5 |
> Can you try to run fetchmail manually, perhaps with increased |
| 6 |
> verbosity or debug output? |
| 7 |
|
| 8 |
|
| 9 |
Fetchmail itself is independent of cron - it doesn't use it for |
| 10 |
scheduling (at least in the configurations I use (fcron). You can cron |
| 11 |
fetchmail, buts that's not normal. |
| 12 |
|
| 13 |
cron programs by default have a very stripped down environment which is |
| 14 |
the usual cause of cron errors - can be hard to identify whats missing. |
| 15 |
|
| 16 |
If its something like emailing an error log or test commands: run the |
| 17 |
commands from the error message manually, then via a test cron entry to |
| 18 |
narrow it down. Try grep'ing /etc to find the actual commands. |
| 19 |
|
| 20 |
|
| 21 |
BillK |
Archives