• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 699
  • Last Modified:

sh: /cat: No such file or directory

Hello,

I'm running a daily cron job which triggers a php script name ee-boom.php.  I've attached it to this question.

Essentially, what you will see is that the PHP script queries a "product_catalog.txt" file and extracts matching query string values and dumps them into another file called R.txt.  

That R.txt is then used on the front end of the site to serve up relevant data.  

There was nothing wrong with the script or the cron job, until I recently updated Plesk.  Upon updating Plesk, I began receiving a daily email stating:

Subject: Cron <root@domain> php -f /var/www/vhosts/domain.org/httpdocs/ee-boom.php

sh: /cat: No such file or directory

This issue has now prevented the cron job from triggering ee-boom.php successfully, thereby negating the update to R.txt.

Any insight to get this script running successfully again is greatly appreciated.

Thank you!
ee-boom.php
0
pmagony
Asked:
pmagony
  • 9
  • 6
  • 3
  • +1
2 Solutions
 
ozoCommented:
try
$cat_cmd = 'cat ' . $txt_catalog . ' | grep "Value String" > /var/www/vhosts/domain.org/httpdocs/boom/R.txt';
0
 
woolmilkporcCommented:
I could imagine that changing

$cat_cmd = 'cat' . $txt_catalog  .....

to

$cat_cmd = '/usr/bin/cat' . $txt_catalog

would help, but that's just a wild guess ...
0
 
Ray PaseurCommented:
The strategy I would follow here is to learn what the CRON job sees.  Make the appropriate changes in the email address and try this.  It is untested, but valid in principle.
<?php
ini_set("error_reporting", E_ALL);
ini_set("display_errors", TRUE);
ini_set("memory_limit","100M");

// START THE OUTPUT BUFFERS
ob_start();

// GET THE ENVIRONMENTAL INFORMATION
phpinfo();

// VISUAL DELIMITER
echo PHP_EOL . '****************************************************************';

$txt_catalog = '/var/www/vhosts/domain.org/httpdocs/product_catalog.txt';
$cat_cmd = 'cat ' . $txt_catalog . ' | grep "Value String" > /var/www/vhosts/domain.org/httpdocs/boom/R.txt';

$cmd   = fopen('/var/www/vhosts/domain.org/httpdocs/product_catalog.txt', 'w'); 
$lines = gzfile('/var/www/vhosts/domain.org/httpdocs/product_catalog.txt.gz'); 
$lines = implode(PHP_EOL, $lines); 
fwrite($cmd, $lines); 
fclose($cmd);

if(file_exists($txt_catalog)) {
	$ret2 = exec($cat_cmd, $ret_val2);
}
else
{
    echo "!file_exists($txt_catalog)";
}

// CAPTURE AND MAIL THE OUTPUT BUFFER
$buf = ob_get_clean();
mail ('You@Your.org', 'CRON INFO' $buf);

Open in new window

0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
pmagonyAuthor Commented:
@Ozo,

Your suggestion is identical to what is already in the file.

@woolmilkporc, I will give your suggestion a try.  My only issue is, is that I won't know the actual results until tomorrow, after the cron job has execute.  Unless there is a way to manually trigger the cron without interrupting it's schedule?

@Ray, thank you for the lovely code.  I have amended the file with the additional information, however, I do not see a reason to output phpinfo(); into the message.  Any reason why this was recommended?

If I run ee-boom.php in the browser manually, I receive an email chock full of html code from the php info output.  But nothing else.  If I comment it out, and run the file, then I simply get an email with the PHP_EOL visual delimiter.  Should I be receiving any other output data?
0
 
ozoCommented:
My suggestion is not identical to what is already in the file.
It contains an essential change.
(other changes may be called for, but try that first)
0
 
ozoCommented:
http:#a37714772 also contains the change I suggested
0
 
pmagonyAuthor Commented:
Thanks Ozo,

Are you referring to the space after t in 'cat '? If so, will implement, thank you!
0
 
Ray PaseurCommented:
I do not see a reason to output phpinfo(); into the message.  Any reason why this was recommended?
Yes, it is there so that you can find and compare things like $_SERVER["DOCUMENT_ROOT"] and the basepath, any other things that might not be the same when you compare its operation as a CRON job to its operation as a web script.

If you're not getting enough information to begin understanding the script's operation, you might want to add some additional visualization to the script.  You might want to add var_dump($lines) after line 20.  Etc, until you can find something that smells fishy.
0
 
Ray PaseurCommented:
the space after t in 'cat '?
Yes, I think it belongs there.
0
 
pmagonyAuthor Commented:
Good morning!

This morning I received the exact same CRON notification, it appears the issue still persists.

Subject: Cron <root@domain> php -f /var/www/vhosts/domain.org/httpdocs/ee-boom.php
Body: sh: /cat: No such file or directory

I can confirm the 'cat ' has a space in it.  There is one thing I have not tried and that is @woolmilkporc suggestion of putting '/usr/bin/cat ' for the $cat_cmd variable.

Just a friendly reminder, all this starting occurring after a PLESK update. Could it be a permission issue?
0
 
Ray PaseurCommented:
It could be permissions, but it is more likely a path issue.  Going down the directory tree, I would try to verify that /var/ is a directory, then /www/ is a directory, etc.  See:
http://php.net/manual/en/function.is-dir.php
0
 
Ray PaseurCommented:
Have you had a chance to compare the outputs of phpinfo() yet?
0
 
pmagonyAuthor Commented:
Hi Ray,

If this was working and the site has not been moved, how could a path change have transpired?  The site has always resided at /var/www/vhosts/domain.org/httpdocs/

I'm not sure what you mean by compare the outputs of phpinfo.  The email comes in as text, and all the html makes it nearly impossible to read it correctly.  What should I be comparing?

Thanks!
0
 
pmagonyAuthor Commented:
I added the following to the headers to fix the HTML issue:

$headers = "MIME-Version: 1.0" . "\r\n";
$headers .= "Content-type:text/html;charset=iso-8859-1" . "\r\n";

Now I just need to know "what" to look for in the phpinfo output :^)
0
 
Ray PaseurCommented:
Look at the Core, Environment and PHP Variables in the phpinfo() output.  You would want to see if they are the same in every environment where you run this script.  Some adjustments may be necessary for scripts that are started in different environments.
0
 
pmagonyAuthor Commented:
Alright guys, I tried:

'cat '
'/usr/bin/cat '

with no luck.  Ray, I have compared the phpinfo criteria you pointed out and I do not see any differences.  I have also confirmed that /var, /www, /vhosts are directories. I walked through them via SSH to finally get to the site itself.

I'm still getting the same error:

sh: /cat: No such file or directory
0
 
pmagonyAuthor Commented:
I think I was able to resolve the issue... I started to play around with the ownership of ee-boom.php and as it turns out, when running directives in a php file, they have to be run as the same owner as the CRON job that is executing it.

So I changed the ownership to apache.  I then ran the file in SSH and started receiving safe mode errors.

Oddly, when I logged into PLESK, to disable "safe mode" in the settings, it was already disabled.  This puzzled me so I opened up php.ini and sure enough, it was set to on.  Once I turned it off, and restarted services, the file now runs error free.

I'm going to get a definitive answer tomorrow morning once the CRON job runs. I 'll report back tomorrow with my findings.
0
 
pmagonyAuthor Commented:
The issue is resolved based on an Ownership change of the files.
0
 
pmagonyAuthor Commented:
I was able to resolve the issue by analyzing the ownership of each file, and how CRON jobs execute shell commands.
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 9
  • 6
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now