Hey guys, the site crash about two hours ago, right? I could still ping it, but whatever... I… - Feed Post by Mangan
Hey guys, the site crash about two hours ago, right? I could still ping it, but whatever... I think it might have been me who crashed the site when I did the 40th vocabulary chapter test (Im level 5 now, jippi!!!). I just answered the first question which had お礼 as answer, got an error, and when I reloaded it came up the standard 503 Service Unavailable. I just thought I should share this so it might help the developer (beeant <3) figure out why the site is crashing :)
posted by Mangan
Comments 12
The site was down all morning and all afternoon yesterday (Saturday Pacific Time USA).
Although I think that action is very unlikely to have caused the crash, I think it's good to mention any little thing, no matter how seemingly insignificant. Anything to help the site get fixed quicker. :)
You say the site crashed about two hours before your post, right? Your post was written nearly 5 hours ago now, so the site crashed roughly 7 hours ago?
Well, in my email inbox I have an email notification saying someone replied to a feed I'd posted in on JCJP. I recieved this notification email almost exactly 8 hours ago (20:08 JST, it is now 06:16 JST).
What is interesting about this is that even though the email says what feed it was written in, who wrote it, and what was written, I've checked and refreshed the site several times and there is nothing there!
It is possible the site crashed at the exact moment that the comment was written, so it never made it onto the site, but the notification still got sent. This seems more likely to have caused the crash, however this is about an hour earlier than the time you reckoned the crash had happened.- * Typo: should say that the notification email was received at "22:08" JST (not 20:08). ^^;
Yeah, your right, it probably dident crash because of me. Btw, is beeant the only one working on this site? It seems like a lot of work, so why doesn't he get someone to help out? I dont know really, but I think there would be a lot of people willing to help out. I would, but web programming isnt really my field so i might not be able to do much...- (im not implying that he does a bad job, he does a great job)
The site crashes a lot, it's just general traffic. It's only on the bandwidth he can afford.- @Mangan, Yes, beeant is the only developer and also the only admin on this site. He's the only person who works on this site, and as the owner he has to pay for the server if donations and advertising don't cover the running costs.
The server cost stated on the "Donate" page is probably out-of-date, as that value was written when JCJP was on a previous server.
The current server still costs at least €60 a month (£48 / $75 / 8700円).
@jimhaku, I'm sure high traffic often makes up a lot of the reason why the site crashes. The way the site runs is fairly dynamic, so it's understandable that it is likely to get overloaded if lots of people are online.
However, sometimes the site crashes with barely anyone in the online user list. Even when lots of people are online, the site can run very quick and smoothly, and then all-of-a-sudden it crashes. The current server doesn't seem like it should be quite that flimsy, so there's probably more to it.
The Readings bug which was fixed recently would crash the site even if only that one user was online (as far as I'm aware). There could still be other bugs of this kind which need finding. ^^ - That's interesting. Should probably make an option to donate monthly.
User caused crashes are pretty rare, don't flatter yourself.- Users reporting anything about the site crashing seems pretty rare too, considering how often the site does go offline.
I think it's strange saying "user caused crashes are pretty rare", as I'd expect most crashes are linked to the fact that users are using the site. If no users used the site for a week, then the site would probably stay online for a whole week! :P
The site goes down daily, at least 4 times in the last 48 hours.
The site going offline is definitely not due to the webserver's network being offline. I've never noticed this happen.
The server itself stays online too, as you can still ping it and stuff, so it hasn't completely died or lost connectivity.
It is possible that beeant might be doing something on the server where the site needs to be taken off air, but this is very unlikely to be something which happens often (if ever).
So the site itself is most definitely crashing regularly. Probably things like websocket faults, server hardware possibly being stretched, definitely specific bugs too. However, none of these things are triggered without users actually using the site. ^^ - To elaborate: the chance that him specifically causing the site crash, at that very moment, is pretty low.
Of course that site load can and probably does have a hand in the recent site blackouts, and of course I don't know the specifics. - Yeah, sorry, I knew what you meant but I was being a little bit pedantic at the time. :P
However, the site has now gone down at least 9 times in the last four days.
This morning the site crashed just as I had completed a readings quiz (getting 100% correct). The site crashed at the same point it did before the bug was fixed.
Just after this crash I checked the network the server is on, and one of the machines enroute to the server was playing up a bit, but it settled down after a few minutes. If nobody had completed a Readings quiz at that time, the site probably would have been far less likely to have crashed at all. However because I did, it's possible just my action crashed the server, due to what seems like an issue where the site gives up on life if things go slightly outside of plan for those few seconds (seems to have no plan B)...
