Amazon ist bekannt für seinen (teuren) Onlineshop, aber es gibt noch eine weitere (ebenso teure) Seite: Amazon AWS bietet - einfach gesagt - verschiedene "managed services" an. Einer davon nennt sich SES und dient dem Email-Versand. Allerdings sind SES-Fehlermeldungen nicht immer das, was sie zu sein scheinen.
Suchergebnisse mit Tag „error“
Error messages should be simple, clear and easy to understand. But there are differences: A developer writing some sourcecode will think of something different as "easy to understand" than a user who doesn't know the source or internals. MongoDB reports a "DBClientCursor::init call() failed" on connect errors. Do you know what this message means?
Some errors are really hard to find: They appear only sometimes or only on live systems or within complex source that can't run manually using a debugger. Adding debug output might help, but might also be confusing as the DBI error code 4 "statement contains no result" does.
Gearman is a great tool for farmed or distributed work. It's some kind of basic cloud handling: Many Worker processes (usually running on many different servers) are waiting for jobs to process and there's (hopefully) always another worker taking over if one worker (server) should ever die. But what happens, if a single job dies and should be repeated?
I tried MovableType just before setting up WordPress for this blog. It didn't offer the features I wanted (okay, WordPress still doesn't have them, but it promised to have them and so it won). After trying out MT again, I want to have it. But what about my existing articles, comments, settings? That's (the only reason) why I'm still using WordPress.
Look at the title and you're done. No need to add a text to this post if everything is said in the title. Not really? France is too small to hold half of the world's population? No way! My computer told me that 4.294.967.296 people live in France - and computers don't fail, you know?
mySQL servers have their own mind and sometimes just disappear. They go away from a client leaving it alone if the complete server is dying, if a client is doing unexpected things and sometimes even without any known reason.
I joined a commercial project lately which has been growing for years. Adding a "use" for a module which was called in source but not loaded by "use" before suddenly led some old coding sins show up. Torben and I spent two hours on finding and fixing this bug.
