After about 12 hours running on an ADSL 750k line, the cpu usage is running between 40-60% (P III 866 256 RAM), The database file is 600MB. Deleting the file manually, reduces cpu usage to 30-40% and after 30 minutes log file is already 30mb and running.
UPDATE: after about an hour, op_data.mdb is standing on 102MB.
Originally posted by Paranoid2000
I've been running a Freenet node for 2 days and my op_data.mdb file is only 75MB.
Only 75 MB? That is the understatement of the year IMHO. I can think of no reason why a logfile should be that large. Don't know any (home)application besides Outpost V2 that generates these enormous logfiles. My virusscanner logfile for example is restricted to 2 MB right now, and covers 2 months in time. More then enough.
Anyway, I've heard that this problem will be fixed in the next update. Until then my logging is and will be manually disabled.
Hi LoctOut,
I would call this a design oversight rather than an error. This should be an issue with all Outpost PRO v2.0 and later releases. The only other option would be to use the FREE version which is not so bad. Outpost in it's current form was not designed to operate on systems acting as servers and generating a great deal of traffic log information.
However, I do believe that there is some remedy on the way for this. I believe that log size control and compacting is on the near horizon, but I do not have enough information to be specific. I understand this is an issue for many and I will be the first to celebrate when some relief for people like yourself finally comes.
Sorry I do not have better news.
Have a good day. :)
Hi,
As soon as I switched on my PC today, there was an enourmous lag, as Outpost started consuming my CPU resources.
The situation was so bad that it was impossible to even show the Outpost window. Even after a restart, the problem continued.
Then, I opened the Outpost log viewer and chose the 'Repair Database' option. I chose 'Mark DB as corrupt and delete and create new on next boot'.
Then, (without restarting) I tried running Outpost. Voila! The problem was instantly solved.
See if this works for anyone else. If it does, the lag is probably due to a damaged DB.
Wild Thing
Hi LoctOut,
A new version of Outpost with Logging Control features is in late Alpha and should be released as Beta shortly. Hopefully, that will be combined with some good core updates that will fix this issue. That is the best information that I can provide for you at the moment.
Have a good day. :)
I'm having the same problems but I'm not running emule. I am running waste.
My CPU usage goes to 100% I use GoBack for recovery purposes, but this logging bug in outpost pro causes goback to shut down and wipe out all history.
Which prior version of outpost pro was safe as far as not having this bug? and is this going to be fixed or do we have to live with it?
Thanks for posting this Robbin - this should be a good point to add to the V2 FAQ.
Robbin, I have a similar problem. I run eMule and after a day or so the whole system slows to an unacceptable level.
When I restart Outpost is is alright again.
Do I have the same problem? Is the log file rebuilt after restarting Outpost?
Thanks
thanks Dave....... can I volunteer to be a beta tester?
Hello,
I've got the same problem I think.
After eMule was running about 14h, my CPU load was at 89-99%.
Just to rename or delete "op_data.dll" sounds good but which feature will be lost temporaley? Only the "Log-Function"... but I am rather interested in my logfiles...(Attacks e.g.)...
Try my Zantac 75. It works on the spicy Cajun Food. :D
Thanks for the fast answer Robbin!
Yes, I got my system virtually frozen too a couple of times.
I delete the log file every day, or every second day. Tt is not perfect solution, but it works for now.
I hope there is a solution for this problem soon, because it is annoying.
thanks David,
I't's just been driving me crazy trying to figure out what was going on. I finally just deleted outpost and installed norton Internet security. Not my first choice, but....
Already took a Zantac. Not that the food was spicy, it was just a lot of strange seafood. Let's keep this OT stuff short. :)
Hi LoctOut,
I can't blame you for that. You have to use what works and Symantec makes some pretty good stuff. I would check back here maybe once a week to see if a new public version has been released and if it has more logging control. You should only need to check the Announcements forum to verify this. So, it should not take much time.
Sorry that this issue has put you in such a position. Hopefully in the near future, Agnitum will give you and others with the logging problems a reason to come back to Outpost soon. :)
Near 100% CPU usage when using forum?: Sling Community::
19 postsHi Is anyone else having problems with their CPU usage when browsing this forum? Please log in or register to participate in this community! Log In
http://www.slingcommunity.com/forum/thread/18248/Near-100--CPU-usage-when-using-forum-/HOME |
A 3D Lesson v2.2 by Peter Wilson::
16 posts - Last post: Feb 17, 2005use 100% CPU? RAM help. By MazterzDemon on 1/1 A 3D Lesson v2.2 Note: Due to the size or complexity of this submission,
http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=58876&lngWId=1HOME |
Have a nice day LoctOut. :)
GoonMan, you are too late. Take typing lessons. :D
Bumping this to see if any progress has been made to actually "fix" this issue by some means other than deleting files or stopping logging
Presumably you are running a file-sharing application that attracts a lot of traffic. I've been running a Freenet node for 2 days and my op_data.mdb file is only 75MB. However, I rarely see CPU usage above 3% (1Ghz PIII) with Outpost and it has only taken 15 minutes CPU time so far.
One possibility, if your op_data.mdb file is that big, odds are that it's going to be pretty badly fragmented. Disconnecting from the network, shutting Outpost down and doing a defrag may help matters.
Greater control over log file size is supposed to be on the Todo list - but can be set in Outpost v1. If you find the defragging does not help, then using v1 may be a better option.
Your more then welcome, just happy I could give back to this great board.
Originally posted by LoctOut
Bumping this to see if any progress has been made to actually "fix" this issue by some means other than deleting files or stopping logging
LoctOut the logging issue is suppose to be fixed in Version 2.1 so that you can control log file size.
As of yet we do not know when the release will be, this is my guess it will be late January or February.
Randy
LOL David you and I are burning the late nite oil and posting at the same time. Oh well time for my ugly sleep.:D ;)
Well, I deleted the op_data.mdb file 10 hours ago (take or leave 1 hour). Now the file is 47,8 MB while running under emule. So 75 MBs for 2 days are quite "good" actually. :)
Hi LoctOut,
Originally posted by LoctOut
thanks Dave....... can I volunteer to be a beta tester?
You may certainly apply to be a Beta Tester. Any user has the possibility of doing this. Please visit this link:
Outpost Beta Tester Application (http://www.agnitum.com/products/outpost/betatest.html)
Fill out the information and you should receive a reply. That reply will ask several questions that you should answer. After processing of the application, you may be accepted or denied based your answers, the unique problem that you may be having, and whether Agnitum needs additional testers based added to the current pool of participants. Also, I would like to point out that the forum leaders have little or no influence over Agnitum regarding Beta Tester decisions. We are an independent forum and staffed with volunteers, including myself. We are not employees of Agnitum.
Finally, please keep in mind that high CPU usage is generally associated with operating Outpost in a server type environment. Most often for home users, this includes operating P2P (Peer to Peer File Sharing) applications. Generally, the effects of P2P applications can be mitigated by properly configuring those applications so that they do not generate so much traffic.
I hope that my comments have helped.
Have a good day. :)
Goonman, yes we are here late this evening. I attented a wedding with my wife and endured nine courses of Vietnamese foods. I will be up for a while. :D
A temp solution:
I renamed op_data.dll, doing this cancels the writing capabilities of the database system, this reduced the cpu usage to 6-12% and kept memory usage from round 25MB to round 5MB. It is a very crude solution but one that allows me to keep using version 2 until an update for disabling/limiting the database size/usage, would be available.
Originally posted by Whistler
Hello,
I've got the same problem I think.
After eMule was running about 14h, my CPU load was at 89-99%.
Just to rename or delete "op_data.dll" sounds good but which feature will be lost temporaley? Only the "Log-Function"... but I am rather interested in my logfiles...(Attacks e.g.)...
Do you really investigating your log file for anything you did not mentioned here ?
Almost all IT staff people I know in my company are afraid of looking too deeply into a log file (except when an error occured without any hint for the reason). Better you think about a correct and (almost) complete configuration of your network traffic/of the OP rules and stop logging.
Btw: I had a similar case of CPU usage (almost 100%) by defining rules which blocks too much (even DNS requests). But relaxing firewall rules because the product you are using is not stable enough for a greater amount of network traffic (e.g. using emule) is not the best way of solving similar problems.
So it should be released a newer version of OP 2.0 asap, the current version is too buggy/unstable to use it in a corporate environment !
Unfortunately I didn't read anything about a new release date...
Regards
Peter
all I have running is emule, which wasn't a problem with cpu usage under version 1, defragmantation, reboots and clean installs didn't help, after one hour i am touching 100MB again with about 30% cpu usage, i think it has to do more with the number of threads emule keeps live then the number of downloader's. Back to version 1 unfortunately.
Hello Michael, yes it does sound like the same issue, what I suggest you do is follow the instruction posted above, that is renaming op_data.dll. What unfortunately I found out is that in a prolong running time of Outpost +emule, the CPU usage will eventually grind your system to a halt. I got to 80% at one point. I tried endless scenarios: running emule in totally trusted mode, thinking this would reduce its trafficking tracking, canceling all the plug-ins, and so on and on including all the ones proposed by the FAQ, to no luck. Eventually I was forced to revert to version 1, while I eagerly await a more permanently solution by Agnitum.
 Nortel Unveils Vision, Strategy for Israeli High-Performance Net
 Busy Friday Leads to Strong Close for Net Stocks
|
PRINT
Add to favorites