Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
Recently I found errors in my mediatomb.log saying "ERROR: AbstractHash::search() failed, maximal number of iterations exceeded: h:15863 h2:29 size:9689".
By searching the web I came directly into the part of the mediatomb src that gives that log message and found there was a hardcoded hash_max value, which I have exceeded.
The question would be if the max value is in any way configurable and what might be the consequences of that error? It seems that at least using the webinterface I'm able to play/download any of my songs, no matter if the song is ordered on the beginning or the end in the filesystem. (I'm assuming the hashing is done in some sort of lexicographical order.)
thanks for your help,
Interesting… can you tell us what exactly you are doing when this error comes? How to reproduce it?
I'll talk to Leo, we'll check the code, I do not remember right now where it is used, I'll get back to you.
I'm sorry, I can't. I've installed mediatomb on a kubuntu lucid server as it was delivered by ubuntu. I fixed a few permission issues in my music folder, though it seems in my video folder there are still some problems, but the logmsg about the permission error was about 3 hours before the max iterations error.
So all I see in the logfile is the startup info and one permission error ("Inotify thread caught exception: Permission denied") and 3 hours later i get two max iterations messages in the same second:
2010-01-30 12:29:56 ERROR: AbstractHash::search() failed, maximal number of iterations exceeded: h:15863 h2:29 size:9689
2010-01-30 12:29:56 ERROR: AbstractHash::search() failed, maximal number of iterations exceeded: h:15863 h2:29 size:9725
I don't think my only upnp client (Philips Streamium) was active at that time and nobody accessed the server. So I think this hashing has been triggered by the periodic update check on my shared folders.
Are there any settings I can change so the logging is more verbose or are there any scripts to check if everything is setup correctly, which might give you some useful information?
I have been having this problem. I have just rebuilt everything and have these messages in mediatomb.log:
2011-12-18 10:59:36 ERROR: AbstractHash::search() failed, maximal number of iterations exceeded: h:9193 h2:29 size:9859
2011-12-18 10:59:36 ERROR: AbstractHash::search() failed, maximal number of iterations exceeded: h:8439 h2:29 size:9883
Mediatomb 0.12~svn2018-6ubuntu2, Ubuntu 10.04.3 LTS.
My photos folder contains 1776 folders and 46776 files.
My videos folder contains 51 folders and 668 files.