Use of uninitialized value $cmd in pattern match

[mbroadstreet]

After the most recent WHM update, my cron is giving the following error:

Use of uninitialized value $cmd in pattern match (m//) at /usr/local/cpanel/Cpanel/BUse of uninitialized value $cmd in pattern match (m//) at /usr/local/cpanel/Cpanel/Backup/Sync.pm line 489. ackup/Sync.pm line 489.

 

[cPanelLauren]

Hello,

Is there more to that error? The full chunk of output would be helpful in this instance. Is the cron a custom backup cron or otherwise?

 

[mbroadstreet]

That was all. I use JetBackup for backups.

I checked /usr/local/cpanel/logs/error_log and didn't see anything there either with the appropriate timestamp (or anything really, just a periodic permissions check that passed fine.) Would there be another log location to check?

 

[cPanelLauren]

Hello,


Helpful to know when you have an issue that you're using a 3rd party plugin. JetBackup is supported but its error logs are in a different location. They are noted here: Home

/etc/serverbackupsmanager/logs

 

[mbroadstreet]

No such directory, I'll check the documentation when I have time. Interesting times we're in atm!

Thanks for your help.

 

[Stu_m]

I have just got up this morning to be greeted with this exact same message but I'm not using any third party service!

 

[cPanelLauren]

@Stu_m

Is anything noted in the cPanel error logs? You can find them at /usr/local/cpanel/logs/error_log

 

[Stu_m]

@Stu_m

Is anything noted in the cPanel error logs? You can find them at /usr/local/cpanel/logs/error_log

I think cPanel updated while a back up was being taken!

 

[cPanelLauren]

What would lead you to that conclusion, specifically - what is the output in the logs?

 

[mbroadstreet]

Fwiw there was nothing relevant that I saw in my JetBackup logs.

My thinking was that perhaps a background (cron job) task ran in the middle of the update that night and so a script was mismatched somehow with the environment around it, so I ran a manual WHM forced upgrade (to the same version) and the error message didn't appear that time.