On 8/10/07, Robert Cummings <robert@xxxxxxxxxxxxx> wrote:
> On Fri, 2007-08-10 at 17:39 +0100, Stut wrote:
> > Robert Cummings wrote:
> > > On Fri, 2007-08-10 at 11:48 -0400, Daniel Brown wrote:
> > >> On 8/10/07, Stut <stuttle@xxxxxxxxx> wrote:
> > >>> .... I get an email from each
> > >>> server containing the contents of the error log from the previous day
> > >>> and my first task each day is to go through that and track down any
> > >>> issues that usage has highlighted.
> > >> That's actually a good point there that I can take away from this.
> > >> I actually don't have anything set to send me a log of code issues,
> > >> only when an error is caused (and, of course, anything server-related,
> > >> but that's a different point entirely).
> > >
> > > Simple enough... put the following in a file, and add a cron job.
> > >
> > > #!/usr/bin/php -qC
> > > <?php
> > >
> > > if( !isset( $argv[1] ) || !isset( $argv[2] ) || !isset( $argv[3] ) )
> > > {
> > > echo "Usage: {$argv[0]} <subject> <email> <path>\n";
> > > exit( 1 );
> > > }
> > >
> > > $subject = $argv[1];
> > > $email = $argv[2];
> > > $path = $argv[3];
> > >
> > > $content = implode( '', file( $path ) );
> > >
> > > if( trim( $content ) === '' )
> > > {
> > > $content = 'NO ERRORS TODAY!!!';
> > > }
> > >
> > > mail( $email, $subject, $content );
> > >
> > > ?>
> >
> > I used to have something similar to this until someone uploaded a script
> > that started writing to the error log like mad. Overnight my poor little
> > script tried to load a 240meg log file into memory and email it to me. I
> > now use a simple bash script that pipes the log to the mail command -
> > much safer.
> >
> > Should probably say that it also renames the log file, graceful's
> > Apache, zips the old log and moves it to an archive file server. Rob's
> > script above, used without something that starts a new log will result
> > in ever-increasing emails.
>
> Oh yeah, that's true-- totally forgot to wipe the error log. I just
> whipped the above up :) I have something else on the server without
> command line params that I wrote ages ago :) As for a huge file, unless
> you set PHPs memory high it should just bail with a fatal memory
> exhaustion error. A better script would gzip the log file and attach it
> to an email.
>
> Cheers,
> Rob.
> --
> ...........................................................
> SwarmBuy.com - http://www.swarmbuy.com
>
> Leveraging the buying power of the masses!
> ...........................................................
>
Wouldn't it even be a worthwhile idea to simply include the first
$n lines of the daily log in an email? That's how I have my logs
emailed to me for the server things. I receive the first 300 lines of
the file, and if there's more than that (which, for server logs, there
always are, because I monitor everything), then I know to either hop
on the server and `vim` the log or download it and read it.
In any case, rotating and archiving would be a requirement.
Depending on the log, mine generally rotate daily or once every three
days, with backups being maintained for at least 30 days.
--
Daniel P. Brown
[office] (570-) 587-7080 Ext. 272
[mobile] (570-) 766-8107
Hey, PHP-General list....
50% off for life on web hosting plans $10/mo. or more at
http://www.pilotpig.net/.
Use the coupon code phpgeneralaug07
Register domains for about $0.01 more than what it costs me at
http://domains.pilotpig.net/.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
