Issue Cron errors after Hostname change

[PlesxUser346456]

Server operating system version

CentOS Linux 7.9.2009 (Core)

Plesk version and microupdate number

Plesk Obsidian v18.0.60_build1800240421.18

After changing the server hostname via the Plesk console, I began to receive emailed cron job alerts. Below are samples of the cron job errors. I've tested it on 3 servers and all 3 servers send the exact same errors at the same scheduled cron job time.

Details:

Linux server is CentOS 7 and has to be due to older code that is not supported on newer OSs​

Plesk and the server are all updated​

restarted the server​

Running the command hostname within SSH provides the same expected output.​

Emailed Error 1:

Subject:​

Cron <root@example1> run-parts /etc/cron.hourly​

Body:​

/etc/cron.hourly/0yum-hourly.cron:​

'import sitecustomize' failed; use -v for traceback​

Emailed Error 2:

Subject:​

Cron <root@example1> /usr/lib64/sa/sa1 1 1​

Body:​

error reading file /tmp/dd_process_info_2c07a3f2-eb76-1ac6-282f-ae02f97253e7​

error reading file /tmp/dd_process_info_c91fe205-3c8c-a901-dddf-13f77609f7b0​

error reading file /tmp/dd_process_info_bb6d914e-7f41-2507-ca81-6c90870f1a54​

Has anyone else seen this and know how to resolve it?

 

[Kaspar@Plesk]

I could not find much information on those cron errors. Best suggestion I have is to open a ticket with Plesk support for an investigation on your server.

Out of curiosity how did you change the hostname exactly?

 

[PlesxUser346456]

I could not find much information on those cron errors. Best suggestion I have is to open a ticket with Plesk support for an investigation on your server.

Out of curiosity how did you change the hostname exactly?

Hi Kaspar,

I changed the hostname via Plesk Admin > Tools and Settings > General Settings (Server Settings)

 

[Kaspar@Plesk]

I changed the hostname via Plesk Admin > Tools and Settings > General Settings (Server Settings)

Perfect, that would be the right way to change the hostname. I thought I'd ask to be sure

Seems unlikely to me that changing the hostname would cause those cron errors, but I can't be sure.