in reply to flush error in modperl on system commands

What does the system call do?

Redirect stdout and stderr to nul?

Launch in background with Proc::Background?

Did you try running apache with strace?

Are you running a proxy?

  • Comment on Re: flush error in modperl on system commands

Replies are listed 'Best First'.
Re^2: flush error in modperl on system commands
by barsh (Novice) on Jan 21, 2012 at 18:50 UTC
    It happens on multiple system calls. One example is running ps2pdf12 to create a pdf from ps file, in that instance I am not capturing stdout or stdin. In other instances where this error occurs I am capture both (running using backticks and redirecting stderr to stdout in the command).

    Have not tried proc::background, or strace, so will try that. Also read Apache::SubProcess might be worth trying so I will also attempt that today. Will report back if anything works.

    Also read last night that including Test::MockObject was creating a similar type of error for somebody: http://www.apache-httpd.com/list/39/962672.html. I was not including that module but did have Test::More, although I tried removing Test::More and it hasn't helped.

    Thanks!

[reply]
      One more follow up: removing Test::More solved the problem on my production server (I stress tested it with 10000 consecutive queries) but did not solve the error on my dev server (and yes, both servers exhibit the error when Test::More is included). Nothing else on the dev server is using any Test package that I could find. For the time being, since the production server is working this is satisfactory for me so I am no longer actively seeking a solution, although it is still very curious to me.

      I won't call this solved, but for any seekers of perl wisdom with this issue in the future I recommend checking libraries you are including, especially any library from the Test package.

[reply]

In Section Seekers of Perl Wisdom