AniDB

I know this is an old issue, but...

[15.02.2004 17:15:49] - Adding dropped files...
[15.02.2004 17:15:49] - Done adding dropped files.
[15.02.2004 17:16:08] - Trying to connect to AniDB...
[15.02.2004 17:16:09] - Done hashing (file1) with ed2k (...)
[15.02.2004 17:16:09] - Connected to AniDB.
[15.02.2004 17:16:10] - Executing new AniDB command.
[15.02.2004 17:16:11] ! AniDB reported internal server error, command queue halted.
[15.02.2004 17:17:07] - Adding dropped files...
[15.02.2004 17:17:07] - Done adding dropped files.
[15.02.2004 17:17:26] - Done hashing (file2) with ed2k (...)
(nothing)

The "command queue halted" is a bit annoying, especially when the auto-update on the next AoM-start forces the same thing to happen again, so it'd be good if this specific error could be handled other than by stopping any further commands.

Of course, it'd be even better to have the underlying problem solved instead ^^;

I also have been having this problem for the last 4-5 days. Unfortunately I have been too busy to report it. AOM will still hash and rename things, but talking to AniDB stops so I cannot add things to mylist.

Hey, wahaha, I know that you have a test users. If you set AOM to use that user, then restart, it should make the creq go through and then you can go back to your user and continue working with AOM. Could you try this and let me know if it works?

egg wrote:Hey, wahaha, I know that you have a test users. If you set AOM to use that user, then restart, it should make the creq go through and then you can go back to your user and continue working with AOM. Could you try this and let me know if it works?

It indeed does work... as I already had that account (though for other purposes), that's exactly the workaround I use at the moment. ^^;

Will ask EXP about that internal server error.

might be fixed now.

BYe!
EXP

Just re-tested it after brd529's bugreport: It still gives the same error.

For completeness' sake:
- Removed the md5-value from the last file I added to provoke an auto-creq
- Fresh AoM-database
- Activated "update known hashdata"
- Hashed the last file I added
-> Internal Server Error

- Restarted AoM
-> Internal Server Error

- Disabled "update known hashdata"
-> AoM works normally

I am also still having the same problem. AOM recently froze on me, and after an hour I killed it. Unfortunately I ended up with a corrupt database (everytime it was starting up, it crashed).

So I had to start fresh and hash my files again, and this caused it to try to creq a file again. So everytime I start up, I get this error. I even tried to have use another login, but this also has the error. I had previously used this login before to get around the problem, because the creq was created by a different user. Now, though, this user also gets the error, so recreqing, even if you are not the owner appears to cause problems.

Like, wahaha, I turned off update known hashdata, and it works fine. I would like to turn this back on, because there is at least one series I am downloading that does not have this data...

Hopefully new AOM won't corrupt it's database as easy.

might be fixed now.
please verify.

BYe!
EXP

exp wrote:might be fixed now.
please verify.

Yes, it works now. I was able to get past the point the problem occured, also I forced it to rehash some other files that I ran and it handled them propery.

Thanks.

Well, guess what, it's broken again. One of the features of the new creq system. Turning off the auto-creqs workaround still works.

OK, it works again. EXP fixed it just as I posted the problem in the forum... What great service!!!