recive mail on error cron.php Unable to connect to the database No route to host

waluszek

Hello,
I have a problem that I can't solve.
for some time, I get a return e-mail every two minutes
originally assumed cron.php was responsible for this but after disabling it the alerts still come.

Unable to connect to the database — No route to host
http://:var/www/html/itss/api/cron.php
Ref-Mid: BCHWZTy-DzX7U-AAAAAAAAAAAAAAAAP1D3YU/S-@osTicketMailer

self hosted server, ubuntu22.04, php8.1-fpm, OsTicket 1.18
(update from 1.17 did not bring a solution)
Cron executes correctly, downloads e-mails correctly.
Does anyone have an idea what could be causing this behavior?

KevinTheJedi

waluszek

Apparently you have another cron running. It's complaining that there is no route to the database host which is odd. I would disable Auto-cron if you have it enabled (under Admin Panel > Emails > Settings) and see if that helps. If not then you need to check your other cron jobs to see where it's running at.

Cheers.

waluszek

I checked all the cron jobs I have in the system, the only one that is outside the system ones is
www-data /usr/bin/php /var/www/html/itss/api/cron.php

KevinTheJedi

waluszek

Then that’s the one it’s having issues with I guess. When you run /usr/bin/php --version on the server's command line what version do you see?

Cheers.

jessencan

I've same issue. Any other solution?

A calendar for the year 2024 is a planner used to organize and keep track of days, weeks, and months in the next year. Most standard 2024 calendars will be structured as a 12-month grid, with each month containing the dates for that month, days of the week, and notable holidays or observances. Calendars allow people to plan ahead, schedule appointments and events, and maintain productivity. The calendar 2024 will follow the same basic format used in previous years, often with creative designs or themes. With 2024 being a leap year, the 2024 calendar will account for the extra day in February. Whether in print form or digital form, calendars remain an essential organizational tool for managing time.

KevinTheJedi

jessencan

If your error includes the path to the cron.php file as the OP described, then as I mentioned above it does seem you have another cron job running. You will need to track all running cron jobs on the server. You may also have an old server and/or old instance of osTicket with a cron running that's causing these errors.

Cheers.