StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19917512
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-11-11T22:47:18.497
FavoriteCount
0
LastActivityDate
2013-11-11T22:47:18.497
LastEditDate
LastEditorUserId
0
OwnerUserId
157957
ParentId
19916949
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
text
Body
I suspect your problem lies in a missing environment variable, specifically the all-important <code>$PATH</code>. When you run this: <pre><code>php -q /tmp/phpinfo.php </code></pre> the system must work out what program you mean by <code>php</code>. It does this by looking, in order, through the directories in the current <code>$PATH</code> environment variable. Executed from a normal shell, your environment is set up in such a way that it finds the CLI version of PHP, as you expect. However, when <code>cron</code> executes a command, it does so without all the environment variables that your interactive shell would set up. Since there will probably be other executables called <code>php</code> on your system, for different "SAPIs", it may pick the "wrong" one - in your case, the <code>cgi-fcgi</code> executable, according to the output you report from <code>php_sapi_name()</code>. To fix this, first find the path to the correct <code>php</code> executable in a normal shell by typing this: <pre><code>which php </code></pre> This should give you a path like <code>/usr/bin/php</code>. You can go one further and check if this is actually a "symbolic link" pointing at a different filename: <pre><code>ls -l $(which php) </code></pre> (you'll see an arrow in the output if it is, like <code>/usr/bin/php -> /usr/bin/php5-cli</code>) Then take this full path to the PHP executable and use that in your crontab entry, so it looks something like this: <pre><code>50 8 * * * /usr/bin/php5-cli -q /tmp/phpinfo.php > /tmp/phpinfo </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORunning php from cron did not run as CLI
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIMSoP
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORunning php from cron did not run as CLI
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. COThat was exactly the problem. Thanks for your suggestion. I ended up adding the following on the top of cron so that I dont need to change the command. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
 singulars
 PostPostId
 PO
 UserUserId
 USAdrian Gunawan

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.