why some of us look for solutions here

walt

• November 20, 2015 11:14

Hello, I just wanted to write a note about why some people, me included, look for answers here. Some questions obviously should be directed to our service provider, but you just would not believe the incompetence we can be faced with. So... thank you for this forum and your patience. While it's fresh on my mind, here's just a quick example. I have been receiving daily emails from a 'cron' job error. After contacting my isp chat support, I was asked if I had any email cron jobs. I answered I don't even know what an email cron job is. I was directed to look for entries in cpanel under 'cron jobs'. I informed them that there were 2 entries. Their answer was something like the following: "Someone must have put them there at some time, can you check to see if you need them?" I had time to reply with one of the cron job entries: /usr/local/cpanel/3rdparty/bin/perl /usr/local/cpanel/3rdparty/quickinstall/scripts/checkupdates.pl The reply that came back was "Is there anything else I can help you with? I guess not, thank you.

• 

  dalem

  • November 20, 2015 23:30

  You would be surprised how many service providers are just kids with mommy's credit card our just plain adults who have no business managing a server. But getting back to your issue to your hosts defense since you used live chat many hosts man live chat with level one type support techs that only have basic technical knowledge and if the issue requires more experiences hands the will escalate it with a ticket. Do have more than that one

  0
• 

  walt

  • November 21, 2015 02:00

  Hi Dalem, you have a point. I didn't even ask to have a ticket opened, all I could think of was to end the conversation as quickly and politely as possible. I'll have them open a ticket.

  0
• 

  dalem

  • November 21, 2015 14:31

  Just copy & paste the cron mail so they can investigate i properly

  0
• 

  cPanelMichael

  • November 23, 2015 16:22

  So... thank you for this forum and your patience.

  
  Hello :) We are happy to see you find the forum helpful. Thank you for taking the time to provide us with this feedback.

  0
• 

  walt

  • November 23, 2015 21:24

  Thank you both for your feedback as well. I did start a ticket the same day I made my original post. It turned out that isolating the faulty cron job was easy, just match the time of the email with the scheduled time of the cron job. The offending one is this: /usr/local/bin/perl /usr/local/cpanel/3rdparty/quickinstall/scripts/checkupdates.pl I came across something very similar to this problem, on a post here. I think the solution was to run a command to force an update. At this point I'm just curious to see how long it takes them to fix it. Three days so far :).

  0
• 

  walt

  • November 24, 2015 12:24

  It's fixed. The error you were getting was the result of an old cron job having not been updated for newer versions of QuickInstall. /usr/local/bin/perl /usr/local/cpanel/3rdparty/quickinstall/scripts/checkupdates.pl has been replaced with the following: /usr/local/cpanel/3rdparty/bin/perl /usr/local/cpanel/3rdparty/quickinstall/scripts/checkupdates.pl Please let us know if you encounter any other issues.
  I did have 2 very similar looking cron jobs, now this is the only one listed. It's a shared hosting account. Thanks again for the prodding, I have a little more faith in my isp.

  0
• 

  dalem

  • November 24, 2015 14:18

  Glad you got it sorted :)

  0

Please sign in to leave a comment.