Hi Joel;
Where does it state to use DBNAME? (I am just guessing). My DBNAME should
be syslog, and it fails to create the table with tomorrows date. My DB has
no table named logs20060719 , and fails to create one.
Here is the output that logrotate.php gives:
Starting logrotate
2006-07-18 10:33:02
PHP Notice: Use of undefined constant logs - assumed 'logs' in
/var/www/html/phpsyslogng2.9.2/config/config.php on line 6
PHP Notice: Use of undefined constant logs - assumed 'logs' in
/var/www/html/phpsyslogng2.9.2/scripts/logrotate.php on line 17
no logs20060719 table created. May already
exist.
Getting list of log tables.
Searching for tables to drop.
Getting list of log tables.
Creating merge table.
2006-07-18 10:33:02
All done!
------------------------------
Line 6 in /var/www/html/phpsyslogng2.9.2/config/config.php is:
$customdate = logs.date("Ymd", mktime(0, 0, 0, date("m"), date("d"),
date("Y") ));
Thank you,
.vp
>From: Joel <[EMAIL PROTECTED]>
>Reply-To: Joel <[EMAIL PROTECTED]>
>To: Vadim Pushkin <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
>[EMAIL PROTECTED]
>Vadim, not sure why that's not working for you, I haven't looked beyond 2.8
>and the modifications I made, so I don't know how it will compare with the
>version that's out there now. I do know with my version of the logrotate
>one of the upsides of that approach is that you can run it at any time,
>unlike the "stock" version that came with it. So run it as often as needed
>until you find out what's not working.
>
>There shouldn't be any dependancies other than the config.php file.. I'm
>trying to think about how they are related.. you may want to create a .php
>file that just creates the log file for testing purposes.
>
>Advantages of this approach vs the built-in apprach.
>Log rotate can be run at any time
>data doesn't truncate between days based on when the logrotate is run
>no damage if the logrotate is run ahead of time or multiple times for
>testing, unlike the built in version that can only be run 1x/day
>Data doesn't move between files, so it's more efficient because the data
>always stays in the file it was put
>opinion: logsDATE is more intuitive than "logs"
>
>I would love to see this approach moved into the main build.
>
>----- Original Message ----
>From: Vadim Pushkin <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]; [email protected]
>Sent: Tuesday, July 18, 2006 9:00:33 AM
>Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code
>
>Clayton, sorry to bother you, please lift a pint for us all.
>
>All others, last night, via cron at 23:45, I tested the modified logrotate
>to no sucess in actually creating the new log file (logs20060718). I see
>that in the php script that it is using the +1 name, but it never actually
>gets created. I will dig deeper and try to figure out why, but I suspect
>that it is because the db is not declared on the "CREATE" portion.
>
>.vp
>
>
> >From: "Clayton Dukes" <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: "Freeman, Michael" <[EMAIL PROTECTED]>
> >CC: "Vadim Pushkin" <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
> >[email protected]
> >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest Code
>
> >Hi guys,
> >Without reading this long thread completely, I'll just add that I
> >didn't make any changes to logrotate since I don't use it -- sorry, I
> >should have been more thorough.
> >I'm in Ireland this week and have very limited access to email, but
> >will try to help out where needed when I can.
> >
> >
> >On 7/17/06, Freeman, Michael <[EMAIL PROTECTED]> wrote:
> >>Hey Guys,
> >>
> >>Clayton is out of town for a little while but I think I may be able to
> >>answer some of these questions.
> >>
> >>There are no longer two different branches, Clayton's changes have been
> >>merged back into HEAD (trunk), and we're all working out of the same
> >>repository. I'm not too familiar with the logrotate.php stuff for the
>new
> >>code as I haven't yet tried it myself, so I have no idea what is
>working
> >>or what is not.
> >>
> >>As for not making it into the latest build, I don't think anyone should
>be
> >>surprised 8). What we really need to do and I think Claus is onboard
>with
> >>this, is make a 'stable' branch or tag off a release from 2.8.1 code,
>and
> >>create a seperate branch for the bleeding edge stuff we're working on
>and
> >>call it un-stable.
> >>
> >>
> >>-----Original Message-----
> >>From: [EMAIL PROTECTED] on behalf of
> >>Vadim Pushkin
> >>Sent: Mon 7/17/2006 8:07 AM
> >>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
> >> ><[EMAIL PROTECTED]>,[email protected]
> >> >CC: [EMAIL PROTECTED]
> >> >Subject: Re: [Php-syslog-ng-support] Errors Upon Login, Using Latest
> >>Code
> >>
> >> >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...]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Php-syslog-ng-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/php-syslog-ng-support
