Visit The New, Modern Unix Linux Community


Datacenter Crash (Server Unreachable for About 17 minutes)


 
Thread Tools Search this Thread
Special Forums Cybersecurity Datacenter Crash (Server Unreachable for About 17 minutes)
# 15  
Thanks for sharing your miseries....


This has been a real PITA.....

I have written some very stern lectures to S4Y, telling them what I think about not notifying customers about data center upgrades; and for doing this during the week and not during the weekend, etc.

Their sales teams have expressed similar frustration, as I was not the only customer in the data center to be outraged at these two unschedule, unannounced, outages within 24 hours.

What the "heck" were they thinking?

What they said was "we did not think there would be a problem, sorry"; but when I used to run data centers back in the old days, we approached upgrades as
  1. Anything that can go wrong will"
  2. Schedule for the weekends and plan well in advance and
  3. Notify all customers who might be effected many days in advance.

I thought this was standard practice in all data centers!

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #985
Difficulty: Medium
386BSD and FreeBSD were both derived from BSD releases.
True or False?

10 More Discussions You Might Find Interesting

1. AIX

System p 9115-505: Server and HMC unreachable

Hi there I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports. Does anybody know that problem? Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies

2. Red Hat

how to configure netdump to copy the crash in the server itself??

hi, i would like to configure netdump, but saving the var/crash in the server itself, not in another server. could anybody tell me if this is possible? thanks (4 Replies)
Discussion started by: pabloli150
4 Replies

3. Programming

Client accidently close when the server crash

The steps to test the problem 1. Open TCP Server 2. Open TCP Client 3. TCP Client sends data to Server. 4. Close TCP Server and the client also crash without any notification Second wonderful test: 1. Comment the following statement in Client.c (at line 168) and compile it Writen(... (1 Reply)
Discussion started by: sehang
1 Replies

4. SCO

Crash error on my unix server

Hi there. Well i have a really bad problem with my server: UnixWare Version 5 Release 7 The system crash :wall: and show the error: Panic: Kernel-mode address fault on user address 0x00000004 :eek: If anyone knows about the reason of this error please give me a help Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies

5. Programming

Client/Server Socket Application - Preventing Client from quitting on server crash

Problem - Linux Client/Server Socket Application: Preventing Client from quitting on server crash Hi, I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64. I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies

6. Linux

crash dump server for red hat ent 4

Is it true that you can't have the crash dump server/client on the same server? I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump. if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies

7. UNIX for Dummies Questions & Answers

Notification if server unreachable?

Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'? Or if its easier have one server that monitors the other five and then sends an alert. If so how would this be done? Thanks (3 Replies)
Discussion started by: Sepia
3 Replies

8. UNIX for Advanced & Expert Users

Solaris Server Crash

We have had a server (Solaris 2.6) hardisk crash. When booting the server we get: ok> boot -S Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0 short read 0x2000 chars read disk read error The only way we can get into the console is to ok> boot cdrom whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies

9. UNIX for Dummies Questions & Answers

server crash

Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday.. Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies

10. UNIX for Advanced & Expert Users

linux server crash

Hi I faced a problem while booting linux which is as follows;- ************************************************* Inode 146180 has illegal block(s) xauth:error in locking authority file /home/root/.Xauthority Fatal Server Error: Could not create lock file in /tmp/tXo-lock ... (1 Reply)
Discussion started by: Abhishek
1 Replies
DOVEADM-LOG(1)							      Dovecot							    DOVEADM-LOG(1)

NAME
doveadm-log - Locate, test or reopen Dovecot's log files SYNOPSIS
doveadm [-Dv] log errors doveadm [-Dv] log find [directory] doveadm [-Dv] log reopen doveadm [-Dv] log test DESCRIPTION
The doveadm log commands are used to locate and reopen the log files of dovecot(1). It's also possible to test the configured targets of the *log_path settings. OPTIONS
Global doveadm(1) options: -D Enables verbosity and debug messages. -v Enables verbosity, including progress counter. COMMANDS
log errors doveadm log errors The log errors command is used to show the last - up to 1,000 - errors and warnings. If no output is generated, no errors have occurred since the last start. log find doveadm log find [directory] The log find command is used to show the location of the log files, to which dovecot(1) sends its log messages. If dovecot(1) logs its messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd writes its log files. log reopen doveadm log reopen This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings. These settings are configured in /etc/dovecot/conf.d/10-logging.conf. This is for example useful after manually rotating the log files. log test doveadm log test This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files. The used prior- ities are: debug, info, warning, error and fatal. EXAMPLE
This example shows how to locate the log files used by dovecot(1). doveadm log find Looking for log files from /var/log Debug: /var/log/dovecot.debug Info: /var/log/mail.log Warning: /var/log/mail.log Error: /var/log/mail.log Fatal: /var/log/mail.log REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail- able at: http://dovecot.org/bugreport.html SEE ALSO
doveadm(1) Dovecot v2.1 2012-02-22 DOVEADM-LOG(1)

Featured Tech Videos