Title: Message

I should just release something. I’ve already written this for Both VOPRadius and Modusmail and includes right-click menus for any web-based user database (such as Rodopi).

 

In MS SQL you can do a simple “delete from <tablename> where ldatetime < dateadd(hour, -24, current_timestamp)” to delete entries older than 24 hours. To get rid of entries you don’t want (like watchdog entries) you would just do “delete from <tablename> where errormessage like ‘Cleaning Up Port%’ “. Obviously you would want to schedule these lines in a stored procedure that runs at an interval of your choosing and include in the schedule steps to shrink the db to get rid of empty lines (from the delete above) and control transaction log growth.

 

Brad Johnson

  Systems Administrator

    Local Link Network Operations

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Global Net, LLC
Sent: Tuesday, August 17, 2004 4:35 PM
To: [EMAIL PROTECTED]
Subject: [VOPRadius] (Interim Processing) Cleaning up port (UPDATE STILL PROBLEM)

 

I have a errorlog every renew 24 hours, so you can tell what a mess that can be.

 

I would be interested on how you done the hour parse, if your willing to share.

 

Jeff

----- Original Message -----

Sent: Tuesday, August 17, 2004 5:00 PM

Subject: [VOPRadius] (Interim Processing) Cleaning up port (UPDATE STILL PROBLEM)

 

I did that once and found the radius logs filled up way to much.

 

What kind of house cleaning do you do?

 

I have a program split the radius text file logs up every hour which gives us a 24 hour window so the techs can look at any errors at any hour they want.  These are Rolling logs though and overwrite every 24 hours.  I then have a few asp pages that parse the log files for specific things like password errors and various others.

 

 

Tony D. Koehn
Director of Networks
Pixius Communications, LLC
316-219-8569
Amateur:  N0LVY

 

 

----- Original Message -----

From: Brad Johnson

Sent: Tuesday, August 17, 2004 2:42 PM

Subject: [VOPRadius] (Interim Processing) Cleaning up port (UPDATE STILL PROBLEM)

 

I used the log to DB functionality to send error logs to an SQL database (access would work to). I then display only what I want my techs to see on an asp page. They even have the ability to search for entries just for a particular user. Its nice.

 

Brad Johnson

  Systems Administrator

    Local Link Network Operations

 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Global Net, LLC
Sent: Tuesday, August 17, 2004 2:14 PM
To: [EMAIL PROTECTED]
Subject: [VOPRadius] (Interim Processing) Cleaning up port (UPDATE STILL PROBLEM)

 

Ok, I did what you said and I am still getting the (Interim Processing) Cleaning up port in the error log

I  even restarted the radius server, and am still getting them.??

 

Jeff

----- Original Message -----

Sent: Tuesday, August 17, 2004 2:00 PM

Subject: [VOPRadius] (Interim Processing) Cleaning up port

 

Jeff,

 

Under Logs Tracking, uncheck Log WatchDog Packets.

 

 

Tony D. Koehn
Director of Networks
Pixius Communications, LLC
316-219-8569
Amateur:  N0LVY

 

 

----- Original Message -----

Sent: Monday, August 16, 2004 11:40 PM

Subject: [VOPRadius] (Interim Processing) Cleaning up port

 

Is their a way to stop the error log from filling up with

(Interim Processing) Cleaning up port

Since I am using watchdog

And not loose it gathering invalid login attempts, and simultaneous attempts????

 

Jeff

Reply via email to