|
qfshadfhad
|
| |
adfhadfhadfhadfhadfhadfhadfhad fhadfhadfhadfh
|
|
Pulse services may need to be restarted
|
| |
There was an IT outage this morning that impacted many Mozilla servers, including pulse, see [link]. This problem has been resolved and pulse is working normally again, but individual publishers/consumers may need to be restarted.
Jonathan
|
|
Pulse transition complete
|
| |
Dustin just changed the DNS for pulse.mozilla.org to point to the new servers. Please check your consumers and publishers if necessary, as they may need to be restarted. RabbbitMQ on the old server has been stopped to force clients to disconnect.
If you have any issues, please let us know.... more »
|
|
pulse: transition to new hardware
|
| |
Currently, pulse is running on an unmanaged VM with limited capacity. Dustin has been working hard to bring up a new managed cluster for pulse in the PHX datacenter, which will provide us with some redundancy, puppetization, better capacity, the ability to implement nagios monitoring, and some other IT goodies.... more »
|
|
Free web hosting
|
| |
Unlimited web hosting web hosting made easy and affordable unlimited
disk space unlimited bandwidth free site builder easy control panel
one click script installs. Bing: free web hosting register or transfer
domain name registration own your corner of the web transfer domain
includes a free one year extension bulk domain name registration.... more »
|
|
buildbot step detail useful?
|
| |
Does anybody use the per-step messages that we're currently generating? I imagine we could cut down the # of messages by at least 10x if we didn't send messages when steps started and stopped.
|
|
Is Pulse down?
|
| |
My Pulse connections fell down at 3:35AM PST, can't seem to reconnect.
Web page says Status: Running.
If it is down, can we fix the fact that the status lies?
Geo
|
|
is pulse ok?
|
| |
We're finding it very slow to push messages to pulse today.
|
|
Pulse is fixed, you may need to restart your listeners
|
| |
Pulse is fixed. Depending on the library you are depending on you may need to restart your listeners. Details: The web interface spins up a queue (via node.js). I also have it optionally spinning up an eventsource queue via django/python. Unfortunately, with the django side I can't detect when a client disconnects so the queue is never deleted (unlike the node side).... more »
|
|
|