AniDB

Hello,

I can't seem to be able to connect to anidb.ath.cx at port 9000 using UDP.

I tried using PING with netcat, like: So, no response. After this I did an one-port port scan, and the port seemed to be closed.

I began wondering that perhaps the software listening to that port isn't running? Has this perhaps something to do with the database update?

indeed, it should be up again now.

BYe!
EXP

Yep, works now. Thanks

Last time the API was online: 13th March 2005
Its now 3 days not reachable.
All requests are timing out.

Please check if the API is up
or if the Frirewall rules have changed.

please try again now.

BYe!
EXP

runs fine again, Thanks.

Last time the API was online: 28th March 2005
Its now 3 days not reachable.
All requests are timing out.

Please check if the API is up

dinoex wrote:Last time the API was online: 28th March 2005
Its now 3 days not reachable.
All requests are timing out.

Please check if the API is up

grml,

actually it is up, but looking at the auto restart script which checks it once every 30mins and kills it if it is no longer responding it's down a lot indeed.
I'll set the checkintervall lower.

doesn't anyone have any experience with java UDP sockets under linux? why do they keep dying on me?

BYe!
EXP

exp wrote: actually it is up, but looking at the auto restart script which checks it once every 30mins and kills it if it is no longer responding it's down a lot indeed.
I'll set the checkintervall lower.

Thanks but this did not help.

exp wrote: doesn't anyone have any experience with java UDP sockets under linux? why do they keep dying on me?

I don't use Java, cuase it is hard to build on BSD.
But the restart script may suffer from a general problem.

I noticed That even a 30 second timeout on the socket is sometimes not enough.

I have seen this effect a couple of times:

AUTH user=dinoex

[Timeout: 30s]

AUTH user=dinoex

dinoex 200 xxxxx LOGIN ACCEPTED

MYLIST xxxxxxx

dinoex 200 xxxxx LOGIN ACCEPTED

In such a case i see the same "Session" code from the Server
There might be a load problem.

dinoex wrote:Last time the API was online: 28th March 2005
Its now 3 days not reachable.
All requests are timing out.

Please check if the API is up

Still no response from anidb.info, port 9000
anidb.info has address 64.202.105.188

Its now 3 days not reachable.
Blocked by firewall?

works here.

BYe!
EXP