Hello,
the MEME-suite website is down since at least two days ago. Does anyone have any information?
•
written
by
Anima Mundi
I can also access the site without problems.
In situations like this, I can highly recommend to use the following tool to quickly tell if the web site is really down, or if the problem is likely to be at your end:
http://www.downforeveryoneorjustme.com/
It is much faster than asking others to check if they can access the site that you cannot ;-)
It is a useful tool, thanks. Since I saw the problem in two different machine behind different routers on Monday, I mistakenly took for granted it was a general problem.
If problems persist, best course of action is to contact the maintainer or the author. You can try meme@nbcr.net or contact Tim Bailey (email address at bottom of page). Just politely explain the issue and ask if there are any known problems at the moment.
I (and others) are getting to the site without problems, so the issue is likely at your end.
I will follow your hint, thank you.
That page loads for me when I try it now.
It redirects to http://meme.sdsc.edu/meme4_6_0/intro.html.
Are you getting some kind of error message?
Thanks for the help. I am getting a network timeout error.
Maybe there is a DNS issue. Try the IP address and see what happens: http://198.202.74.226
Even contacting directly the IP address, the problem remains.
Strange. Try http://198.202.74.226/meme4_6_0/intro.html
Unfortunately nothing changes.
I also tried with wget from another machine behind the same router. That machine here is executing scripts, so I cannot reset the router. Time ago, I made many requests to the site, could my IP have been blocked? If Mary is experiencing the same problem, could it be due to bandwidth consuming requests too?
Resetting the router (scripts are terminated) does not fix the problem, even if my IP is changed.
From wget I get several timeouts, this is the output:
--2011-03-16 00:45:39-- http://198.202.74.226/
Connecting to 198.202.74.226:80... failed: Connection timed out.
Retrying.
--2011-03-16 00:46:01-- (try: 2) http://198.202.74.226/
Connecting to 198.202.74.226:80...
•
written
by
Anima Mundi
It appears strange to me too. I cannot access the site from different and distant locations, about 50 Km (with different machines). This range should be relatively broad, and would cut off different university guests. Thanks again.
I had the answer: the problem is general, and depends on network issues regarding MEME's machine room. They expect to solve it by tomorrow.
Oh, wow. I am going to reward myself ;).
I'm one of the MEME developers in Tim Bailey's lab in Brisbane, Australia.
The NBCR server meme.nbcr.net and meme.sdsc.edu are both the same site) had a hardware failure and we're currently trying to redirect everyone to one of the alternate sites. The NBCR admins have put in place redirects to the EBI site in Australia but they haven't given us an ETA on when they'll have a server we can use at NBCR.
The working alternate sites are http://meme.ebi.edu.au/meme/intro.html which is based in Brisbane, Australia and http://tools.genouest.org/tools/meme/intro.html which is based in France.
One of our US developers is also working on getting a MEME server we can directly control based on Amazon's services.
Unfortunately none of the alternate servers are yet running release 4.9.0 but you can download it and install it from EBI's FTP site. ftp://ftp.ebi.edu.au/pub/software/MEME/r4.9.0/
We moved the MEME forums to google groups recently so that's another location you can contact us https://groups.google.com/forum/#!forum/meme-suite as well as the contact email meme@nbcr.net which thankfully still works.
Hello James, it was an old issue (the post is today 19 month old). Thank you anyway!
Yep, I realised that afterwards. I figured it might still be of use.
I see, in that case in my opinion it would have been better to start a new post (i.e. as a news). It would have been also more visible (maybe you can still do this, if you want). The message however, I think, is relevant from many of us. Thanks again. bye!
Log in to answer this question.
