Do you use Bloglines?
By adamg - 6/22/06 - 8:11 am
If so, could you let me know if you're having trouble with the Universal Hub feed? One reader reports Issues but as a FeedDemon user I'm not seeing any problems (so I might have to dig up my old Bloglines password and see if I can figure it out). If you do have problems, could you let me know the URL you're subscribed to (since the site offers both RSS and Atom)?
Thanks!
Comments
Bloglines
I don't read Universal Hub in Bloglines, but I have been having some problems with some of the other feeds I do read there. Even though I have the correct RSS feed, this is the error message I get:
The feed URL returns a page that does not look like an RSS feed. This can be caused by the feed URL being incorrect, or it can be caused by a configuration issue with the server hosting the feed. If this error continues, you should check the feed URL and, if it is wrong, subscribe to the correct URL.
I use Bloglines and I can't
I use Bloglines and I can't see UniversalHub updates either. :-( It says I'm subscribed to this: http://www.universalhub.com/node/feed
bloglines
I'm having trouble with
http://www.universalhub.com/node/feed
and I also checked out
http://www.universalhub.com/node/feed/atom
which seems ot be experiencing similar problems.
No whining here
I use the Atom feed (http://universalhub.com/atom/feed) via Bloglines and I haven't experienced any problems lately.
Bloglines
I have trouble with Bloglines in general and rarely use it.
It wasn't working for me,
It wasn't working for me, but I just subscribed with the atom feed and it seems to be back in business. I've noticed about 4 or 5 of my feeds in bloglines suddenly stop working.
some bloglines work, some don't
My bloglines is not picking up new items from http://www.universalhub.com/node/feed
So I went with cynical's idea and tried out http://www.universalhub.com/feed/atom
which seems to work fine. I'll stop my whining if that keeps working - but i'm still curious.
How do you like FeedDemon Adam?
Trouble
I tend to get tons at once, in clumps, rather than scattered throughout the day, and they are often very later.
---
http://proactivebusybody.com
OK, so seems to be a problem
Thanks all for the comments. I'll try to investigate this weekend, if I'm not too exhausted from making one last try to keep the weeds from overruning what's left of our grass and getting our daughter to clean up her room.
Who's having problems with www.universalhub.com/node/feed and who's having probems with www.universalhub.com/node/feed/atom?
Just wanted to let you know
Just wanted to let you know that the RSS feed on Bloglines seems to be back in business :-)
Possible reason for the Bloglines problem
Caution: Mind-numbing technical stuff to follow. Bottom line: I think the problem is fixed, but let me know if I'm wrong.
For the past few days, the UH server's been running extra hot - with server "loads" sometimes above 2 (way bad) and the database taking up 50-60% of the CPU time (not necessarily way bad, but an indication of something possibly going wrong). So it's possible the Bloglines aggregator tried to get a feed here, but it's a bit impatient, so when the feed didn't show up right away (since the server was basically running slow), it just gave up. This would explain why some people had problems while others didn't - just luck of the draw.
And why has the server been simulating a marathon? It would be great if it were because thousands of people had suddenly discovered how wonderful the site is - because then I'd talk to the Web host about upgrading the server. Alas, while traffic IS going up, it's not going up that much.
Turned out there's some stupid spider out there that doesn't understand what a "base href" tag is (which means it was written by an idiot), which means it was desperately trying to download thousands of pages that don't exist, causing the database to go into overload as it tried so eagerly to help the poor spider find those pages (every page on UH is built by the database).
Feh. I blocked the spider this morning. Server loads promptly dropped to around 0.30 and the database is now using maybe 2% of the CPU. Yay! Problem solved - until the next idiot spider hits.