Closed Bug 486176 Opened 16 years ago Closed 16 years ago

BES needs a kick? Not receiving email since ~23:30 Monday night

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: johnath, Assigned: sean)

Details

Beltzner spotted it, but Vlad and I aren't picking up BES traffic either.
And my calendar isn't syncing, whee.
Assignee: server-ops → sean
Status: NEW → ASSIGNED
This is all because I wrote a positive comment in bug 414858 and tempted fate, isn't it :(
--> major; this is not minor.
Severity: minor → major
I'll see your major and raise you.
Severity: major → critical
Disk was completely full, which made working on it even more of a pain than usual. I've moved things around and setup a script which will clear up some space every time the server reboots (which should be about monthly) to avoid this happening again. As of right now BES is showing all devices as working save for Beltzner -- expected? Might have to do a manual sync to get the device to reflect your actual inbox, but any new mail should be coming in now just fine. Can someone verify this?
I'm getting mail, woo. time for a nagios monitor on the disk space for that box? Calendar isn't synced, but I'll give it some time.
Apparently just such a nagios check already exists, but was broken at some point. I've filed a bug on it.
Ok, shows as working now for everyone. Shaver, how is calendar stuff looking now?
prompt and pleasant service, speedy reply, would buy again A+++++++
My email comes through Calendar still sits alone Maybe tomorrow?
Not to be a jerk, but this happened last time the BES died -- bug 475814.
What happened last time?
Followed up with Shaver and it looks like everything is sorted out now. Vlad feel free to ping me if that's not the case.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
The bug I linked was the last time the BES died, which was also due to the server being out of space; the same nagios thing was mentioned then. I'm just pointing it out because "out of space" seems to be a common problem, and it would be worth figuring out what's causing out of space and setting up an automated way of dealing with it.
Last bug mentions a check which was removed. In this bug I comment that that check was broken (or was never added back) and I've filed a bug about it, as well as setting up some a script which will clear space on boot. Hopefully that's sufficient.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.