Use of uninitialized value $cmd in pattern match

mbroadstreet

• March 26, 2020 03:25

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

  • March 26, 2020 18:27

  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?

  0
• 

  mbroadstreet

  • March 26, 2020 19:06

  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?

  0
• 

  cPanelLauren

  • March 27, 2020 16:02

  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
  

  0
• 

  mbroadstreet

  • April 01, 2020 16:10

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

  0
• 

  Stu_m

  • May 05, 2020 05:53

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

  0
• 

  cPanelLauren

  • May 05, 2020 13:55

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

  0
• 

  Stu_m

  • May 05, 2020 16:58

  @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!

  0
• 

  cPanelLauren

  • May 05, 2020 17:14

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

  0
• 

  mbroadstreet

  • May 05, 2020 17:15

  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.

  0

Please sign in to leave a comment.