Hello, I don't know anything about programming, except batch files (I
understand this isn't really programming). Just a fair warning. Anyway I set
up RSSOwl for my father, it's an excellent RSS reader except that it keeps
breaking itself. He uses it for finding deals on a site called UsedVictoria,
this is time sensitive so if it stops working we can miss out. The feeds are
set to update ever minute and there is a maximum of 50 feeds. However, for no
reason, after some days of operation this error always shows itself: "An
internal error occurred during: "", uncaught exception. d4boengine closed".
The problem is this error sometimes doesn't display and in order to make it
display I must first click one of the feeds. This is a problem because it
means we can never be sure the program is still working properly in the
background. Sometimes we'll notice that there have been no updates for hours,
with no error message displayed. Quitting and reopening doesn't fix it.
Limiting the number of feeds displayed doesn't either.
Now if I go to Tools/Cleanup and run the optimizations it fixes this error,
that or moving to a backup of the old index file. Is there any way to:
A: Prevent this error from reoccurring.
B: Create a bat file that auto runs the clean command (I could set it on a
schedule). I have tried the -clean command to no avail.
Could anyone provide any insight?
starting RSSOwl with
-vmargs -Drssowl.reindex=true -Xmx1024m
command line parameters reindexes (and thus tries to fix) the database. This
functionality is part of the "Tools | Clean Up" feature.
For fixing your problem:
Thanks for the command line argument!!! That's exactly what I was searching
for. I'll make a bat file with the following:
cd C:\Program Files\RSSOwl
start rssowl.exe -vmargs -Drssowl.reindex=true -Xmx1024m
And set it to run every few hours to make sure everything is tidied up.
Oh and sorry for the confusion. I'm actually not updating 50 feeds, rather
maybe about 12-15. What I meant was the maximum number of news to keep is set
to 50 (I hoped this setting would help with the problem). Do you think this
setting is necessary or can I safely set it to a higher number? Oh and RSSowl
only takes about 4 seconds to update all the feeds.
About the log file, I'll wait til the error presents itself again, otherwise
you may have to sift through a lot of data. Since it happened a few days ago
Im not sure if the info in the log file would still be there (would it?)
Anyway thanks so much Genodeftest, that command run periodically may very well
be the solution to our problem, although its more of a quick fix than finding
the root cause.
reading this log file is not that complicated… ;)
The size is limited to ~1MB so it may date back one week or one year depending
a) how much RSSOwl is used
b) how much errors/debug messages are produced.
50 news (to keep) is no problem. Some users reported their database grow up to
2GB which is at least a million news…
Depending on your network latency and transfer rate 12 to 15 feeds updated per
minute may be too much. But that's really just a guess, I don't know for sure
if it could have caused the error without reading the log file.
I uploaded to zerobin since pastebin had a 500kb limit. Hope it still works :)
I see the error in the log file which is good, numerous times actually.
!MESSAGE An internal error occurred during: ""
So do you think it would be alright if I bumped the limit of news to keep to
150 news to keep is no problem to RSSOwl. Keep 100 000 news if you want.
There are two types of stack traces in your log file:
I got the error again, and the cleanup didn't fix it this time. Had to do the
manual restore to a backup of the index. I can turn this into a bat file, but
I can't automate it. Is there anyway to make RSSOwl do hourly backups? I guess
I could make a bat for that but if the application had the feature built in
somewhere that would be helpful.
Thanks for your help and time.
Sorry, if you need to make backups hourly there is something terribly wrong.
Some possible causes:
An error in some rarely used part of RSSOwl (will look this up when 1. to 3. are proven wrong)
more rare causes:
some sofware is defect (applications would crash – check by reinstalling e.g. RSSOwl or Windows)
Please report wether some of 1.-3. worked.
Hi, it's me (Sourceforge made me create a new account before I could post).
I'm thinking it may be two separate errors. One which produces the error message and requires me to move to a backup of the index, and another which makes the feeds stop updating without warning and requires me to run the cleanup tool.
(2). I'll have to get back to you on this, the computer is in use most of the time. If it were memory related, it would likely be causing troubles elsewhere, but everything else seems stable.
(3). I ran CrystalDisk info: Under "Reallocated Sectors count" it has a caution signal. The current is 199, the worst is 199, and the threshold is 140. I don't know what any of this means, but it's only a caution so Im guessing it's nothing catastrophic.
(5). Windows is a fresh install. RSSOwl never crashes, it just stops working. As in the app never closes itself. I could try reinstalling if you think it's necessary.
(6). No errors in other apps.
So far the index error hasn't reappeared, but I'm not confident it's gone. I did reinstall the program and created a new application folder. However one of the two errors still keeps cropping up, the one that stops RSSOwl from updating without warning until I run the cleanup tool. I ran Memtest within windows (not memtest86) and there were no errors. I don't know if it will be possible to run Memtest86 since the computer is in use all the time.
I'll see if there's someway I could run Memtest.
Right now I have the cleanup running every hour to hopefully fix one of the problems. I'll let you know if the index issue crops up.
Well the errors seemed to have slowed down, the only thing is I have to run the cleanup every once in awhile when the program stops working. Im not sure what changed, maybe it was the reinstall?
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.