Beautiful! I am now able to see my logs again and it *appears* as though I am rotating properly! I will confirm at midnight when I re-run the rotate, checking for just two days worth of logs as well as a sane DB.
Thank you, and sorry for the poking... .vp >From: Joel <[EMAIL PROTECTED]> >Reply-To: Joel <[EMAIL PROTECTED]> >To: Vadim Pushkin <[EMAIL PROTECTED]>, >[email protected] >CC: [EMAIL PROTECTED] >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code >Date: Mon, 17 Jul 2006 07:57:34 -0700 (PDT) > >Ah.. the joy of having someone poke holes in your well thought out plan. >:-) > >I forgot when you leverage this method you have to edit your config file to >use the new format. > >/var/www/html/phpsyslogng/scripts/config/config.php > >I replaced the defaultlogtable line with this, so that it matches and >always uses my new tablename format. > >// DEFAULTLOGTABLE is the name of the table where new syslog entries are >stored. >$customdate = logs.date("Ymd", mktime(0, 0, 0, date("m"), date("d"), >date("Y") )); >define('DEFAULTLOGTABLE', $customdate); > > >----- Original Message ---- >From: Vadim Pushkin <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED]; [email protected] >Cc: [EMAIL PROTECTED] >Sent: Monday, July 17, 2006 10:21:22 AM >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code > >Thanks Joel, > >I've edited the file and removed the one that no longer exists in my DB. >That error no longer exists. > >The only problem that I am having now is that the default method is to look >at logs, but with your recommendations, syslog-ng is now shoving into >logsYEARDATE. I am no longer seeing anything at all when I do a search or >tail. Am I supposed to now select the currecnt date whenever I wish to do a >search? > >.vp > > > >From: Joel <[EMAIL PROTECTED]> > >Reply-To: Joel <[EMAIL PROTECTED]> > >To: Vadim Pushkin > ><[EMAIL PROTECTED]>,[email protected] > >CC: [EMAIL PROTECTED] > >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code > > >edit the all_logs.MRG file manually, check the line listing vs what's in > >the directory. > > > >----- Original Message ---- > >From: Vadim Pushkin <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > >[email protected] > >Cc: [EMAIL PROTECTED] > >Sent: Monday, July 17, 2006 9:55:58 AM > >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code > > > >By the way, I just ran manually and got: > > > >Starting logrotate > >2006-07-17 09:49:49 > >PHP Notice: Use of undefined constant logs - assumed 'logs' in > >/var/www/html/phpsyslogng2.9.2/scripts/logrotate.php on line 17 > >no logs20060718 table created. May already exist. > >Getting list of log tables. > >Query failed: Can't find file: 'all_logs.MRG' (errno: 2) > >[root scripts]# > > > >Login via the GUI also shows the same error. > > > >Am I missing something? all_logs *is* a valid tablename. > > > >.vp > > > > > > >From: "Vadim Pushkin" <[EMAIL PROTECTED]> > > >To: [EMAIL PROTECTED], [email protected] > > >CC: [EMAIL PROTECTED] > > >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest >Code > > > > > > >Hi Joel; > > > > > >I remember your post, in fact I had asked for a copy as an attachment >:) > >I > > >had seen a post by Clayton that he had a new logrotate.php, which fixed > > >some > > >issues with that function. > > > > > >The bigger problem here is why it was not properly added into the >latest > > >build, and what else was potentially left out? This is a big problem > >since > > >all rollouts must have as tight a build as possible. > > > > > >Clayton, is there a reason for the non-change to logrotate.php? > > > > > >Lastly, I applaud Clayton for all of his efforts in helping to maintain > >the > > >project, but does anyone know what Claus' involvement is now? Are >there > > >two > > >or more branches to this project? > > > > > >Thanks all, > > > > > >.vp > > > > > > > > > > > > >From: Joel <[EMAIL PROTECTED]> > > > >Reply-To: Joel <[EMAIL PROTECTED]> > > > >To: Vadim Pushkin > > > > > > > > >Well, if it's never been touched there was an error in logrotate.. >but > >I > > > >was hoping one of guys had corrected. > > > > > > > >I would say to search the archives.. but .. here it is, I'll repost. > >In > > > >this logrotate you'll note that there is one code section that I > > > >duplicated. > > > > > > > > The logrotate snippet that drops the old logs is right before the > > >snippet > > > >to create the > > > >merge table. The array that feeds both is not updated between. I'll > > >paste > > > >my updated > > > >logrotate in below, but I've hacked my logrotate to heck in order to > > >figure > > > >everything out. > > > > > > > >Anyway, this version uses logsDATE and is meant to run ahead of time, > > > >creating each days log file just prior to use. (I run mine at 23:55) > >This > > > >way the log files never get renamed, it just seems to be a really >clean > > >way > > > >to do it. > > > > > > > >-------------------------- > > > > > > > > I think I've found the root cause for the issue with logrotate in >the > > >2.8 > > > >code. > > > > > >[...SNIP...] ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Php-syslog-ng-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/php-syslog-ng-support
