Symfony console exception not logged by cron output file





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I have few commands for my SF3.4 project running by crontab.



I have simple adddate.sh script adding datetime before each message line:



while read x; do
echo -n `date +%Y-%m-%d %H:%M:%S`;
echo -n " ";
echo $x;
done


Running cron like this:



* * * * * www-data bin/console the:command >> some.log 2>&1


Result in some.log when command throws exception:



12:12:25 ERROR     [console] Error thrown while running command "the:command". Message: "lol" ["error" => Exception { …},"command" => "the:command","message" => "lol"] 

[Exception]
lol


So in this case everything is ok. Exception is logged.



Running cron like this (with adddate.sh):



* * * * * www-data bin/console the:command | adddate.sh >> some.log 2>&1


Result in some.log with proper execution:



2018-01-01 12:24:01 Result of console line1
2018-01-01 12:24:01 Result of console line2


Nice, this is as expected! But...



Result when command throws exception: nothing...
Literally nothing. Not even single line. There is also no errors in system cron log. Why adding "pipe" script on command result stops logging exception messages?










share|improve this question























  • Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

    – Alex.Barylski
    Nov 16 '18 at 13:29


















1















I have few commands for my SF3.4 project running by crontab.



I have simple adddate.sh script adding datetime before each message line:



while read x; do
echo -n `date +%Y-%m-%d %H:%M:%S`;
echo -n " ";
echo $x;
done


Running cron like this:



* * * * * www-data bin/console the:command >> some.log 2>&1


Result in some.log when command throws exception:



12:12:25 ERROR     [console] Error thrown while running command "the:command". Message: "lol" ["error" => Exception { …},"command" => "the:command","message" => "lol"] 

[Exception]
lol


So in this case everything is ok. Exception is logged.



Running cron like this (with adddate.sh):



* * * * * www-data bin/console the:command | adddate.sh >> some.log 2>&1


Result in some.log with proper execution:



2018-01-01 12:24:01 Result of console line1
2018-01-01 12:24:01 Result of console line2


Nice, this is as expected! But...



Result when command throws exception: nothing...
Literally nothing. Not even single line. There is also no errors in system cron log. Why adding "pipe" script on command result stops logging exception messages?










share|improve this question























  • Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

    – Alex.Barylski
    Nov 16 '18 at 13:29














1












1








1








I have few commands for my SF3.4 project running by crontab.



I have simple adddate.sh script adding datetime before each message line:



while read x; do
echo -n `date +%Y-%m-%d %H:%M:%S`;
echo -n " ";
echo $x;
done


Running cron like this:



* * * * * www-data bin/console the:command >> some.log 2>&1


Result in some.log when command throws exception:



12:12:25 ERROR     [console] Error thrown while running command "the:command". Message: "lol" ["error" => Exception { …},"command" => "the:command","message" => "lol"] 

[Exception]
lol


So in this case everything is ok. Exception is logged.



Running cron like this (with adddate.sh):



* * * * * www-data bin/console the:command | adddate.sh >> some.log 2>&1


Result in some.log with proper execution:



2018-01-01 12:24:01 Result of console line1
2018-01-01 12:24:01 Result of console line2


Nice, this is as expected! But...



Result when command throws exception: nothing...
Literally nothing. Not even single line. There is also no errors in system cron log. Why adding "pipe" script on command result stops logging exception messages?










share|improve this question














I have few commands for my SF3.4 project running by crontab.



I have simple adddate.sh script adding datetime before each message line:



while read x; do
echo -n `date +%Y-%m-%d %H:%M:%S`;
echo -n " ";
echo $x;
done


Running cron like this:



* * * * * www-data bin/console the:command >> some.log 2>&1


Result in some.log when command throws exception:



12:12:25 ERROR     [console] Error thrown while running command "the:command". Message: "lol" ["error" => Exception { …},"command" => "the:command","message" => "lol"] 

[Exception]
lol


So in this case everything is ok. Exception is logged.



Running cron like this (with adddate.sh):



* * * * * www-data bin/console the:command | adddate.sh >> some.log 2>&1


Result in some.log with proper execution:



2018-01-01 12:24:01 Result of console line1
2018-01-01 12:24:01 Result of console line2


Nice, this is as expected! But...



Result when command throws exception: nothing...
Literally nothing. Not even single line. There is also no errors in system cron log. Why adding "pipe" script on command result stops logging exception messages?







php bash symfony cron






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 16 '18 at 12:22









imclickingmaniacimclickingmaniac

1,02411121




1,02411121













  • Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

    – Alex.Barylski
    Nov 16 '18 at 13:29



















  • Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

    – Alex.Barylski
    Nov 16 '18 at 13:29

















Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

– Alex.Barylski
Nov 16 '18 at 13:29





Maybe try something like: { bin/console the:command | adddate.sh; } |& tee -a some.log

– Alex.Barylski
Nov 16 '18 at 13:29












1 Answer
1






active

oldest

votes


















1














The unix pipe connects the standard output of one command to the standard input of another one.
https://en.wikipedia.org/wiki/Pipeline_%28Unix%29



The exception messages seem to be printed to standard error. Try the redirection of stderr to stdout before the piping:



* * * * * www-data bin/console the:command 2>&1 | adddate.sh >> some.log





share|improve this answer
























  • How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

    – imclickingmaniac
    Nov 17 '18 at 9:29












Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337856%2fsymfony-console-exception-not-logged-by-cron-output-file%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














The unix pipe connects the standard output of one command to the standard input of another one.
https://en.wikipedia.org/wiki/Pipeline_%28Unix%29



The exception messages seem to be printed to standard error. Try the redirection of stderr to stdout before the piping:



* * * * * www-data bin/console the:command 2>&1 | adddate.sh >> some.log





share|improve this answer
























  • How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

    – imclickingmaniac
    Nov 17 '18 at 9:29
















1














The unix pipe connects the standard output of one command to the standard input of another one.
https://en.wikipedia.org/wiki/Pipeline_%28Unix%29



The exception messages seem to be printed to standard error. Try the redirection of stderr to stdout before the piping:



* * * * * www-data bin/console the:command 2>&1 | adddate.sh >> some.log





share|improve this answer
























  • How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

    – imclickingmaniac
    Nov 17 '18 at 9:29














1












1








1







The unix pipe connects the standard output of one command to the standard input of another one.
https://en.wikipedia.org/wiki/Pipeline_%28Unix%29



The exception messages seem to be printed to standard error. Try the redirection of stderr to stdout before the piping:



* * * * * www-data bin/console the:command 2>&1 | adddate.sh >> some.log





share|improve this answer













The unix pipe connects the standard output of one command to the standard input of another one.
https://en.wikipedia.org/wiki/Pipeline_%28Unix%29



The exception messages seem to be printed to standard error. Try the redirection of stderr to stdout before the piping:



* * * * * www-data bin/console the:command 2>&1 | adddate.sh >> some.log






share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 16 '18 at 13:30









FaldonFaldon

1391




1391













  • How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

    – imclickingmaniac
    Nov 17 '18 at 9:29



















  • How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

    – imclickingmaniac
    Nov 17 '18 at 9:29

















How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

– imclickingmaniac
Nov 17 '18 at 9:29





How life becomes easier when you know how pipeline works. Thank you for your answer and for link to wiki. I should think about searching for that in first place.

– imclickingmaniac
Nov 17 '18 at 9:29




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53337856%2fsymfony-console-exception-not-logged-by-cron-output-file%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Florida Star v. B. J. F.

Danny Elfman

Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues