Sponsored Content
Special Forums Cybersecurity Datacenter Crash (Server Unreachable for About 17 minutes) Post 303044548 by vbe on Wednesday 26th of February 2020 07:42:07 AM
Old 02-26-2020
We had an outage last week I think, can't remember officially around half an hour but sure it was more as I got fed up and went to bed... Why I am mentionning is that it looks very similar, Swisscom had a router etc maintenance where no disruption was expected, finally maybe a third (if not a half...) of Switzerland was without TV phones using swisscom box and no 4G... many 24/24 alarm (police/hospitals...) were out of order... In other words a net issue that propagated bringing the whole datacenter down
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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
PLAN(4) 						     Kernel Interfaces Manual							   PLAN(4)

NAME
~/.dayplan - database file of plan(1) SYNOPSIS
DESCRIPTION
The ~/.dayplan file is read and written by the plan and pland programs. It can be edited manually, but it has not been designed for this. Generally, the format is annoyingly unmnemonic, and there is virtually no error checking. Use at your own risk. The only reason I didn't make this a binary file is that I dislike binary config files as a matter of principle. The type of every line depends on the first character of the line. The second character is always a single TAB character. All following characters are arguments. Comments and blank lines (which are ignored) can appear anywhere. "Header types" are all at the beginning of the file before the first "entry type". TYPES THAT CAN APPEAR ANYWHERE: # Comment line. The rest of the line is ignored. HEADER TYPES: o Options. The argument consists of 14 consecutive flag characters, and five numerical arguments. In order, the flags are: s sunday first a 12-hour (am/pm) mode m US date format mm/dd/yy d auto-delete past options j show julian dates w show week numbers n show the next three notes, rather than the first three - always a minus sign, not used (used to be warning popup mode) w show advance warnings graphically in week view u show file names next to note strings in week view b show appointments without time as full-width bar in week views - if "w", the first week of the year is the one with full seven days; if "t", the first Thursday controls which week is the first; otherwise, any partial week is first c use group color of other file appointments as the background color for the text of these appointments in the day boxes in the month view o turn the own-only flag in appointment entry menus on by default, and only show appointments from the main ~/.dayplan file. After the flags, there is a sequence of integers: - default early warning time in seconds - default late warning time in seconds - expiration time of notifier windows in seconds; 0 means notifiers never expire - beginning hour of week views, default is 8 (8:00 o'clock) - ending hour of week views, default is 20 (20:00 o'clock) - the number of days displayed in a week view, 1..28, default is 7 O More options. The argument consists of 24 consecutive flag characters, most of which are unused and reserved for future use. '-' means an option is off, everything else means the option is on. In order, the flags are: s use the main window for all views a resize windows if the contents change t Time adjustment parameters as defined with the Adjust Time popup. The five numeric parameters are the offset to the system clock in seconds, the timezone offset in seconds, the DST flag (0=always on, 1=always off, 2=automatic), and the Julian begin and end dates for automatic DST. e Early warning flags, l Late warning flags, and a alarm flags: These three have the same format. The first three argument chars are flags, as specified in the Alarm Options popup. '-' means the flag is off, everything else means the flag is on. In order, the flags are: w show a color-coded window when the warning/alarm triggers m send mail when the warning/alarm triggers x execute a command when the warning/alarm triggers The flags are followed by a single blank. The rest of the line is the command to execute when the warning/alarm triggers and the 'x' flag is on. y Year overview options. There are 10 consecutive flag characters and three numerical arguments. Only one flag is currently defined: s show single-day appointments too (those with a repeat-every count of 1) - nine unused flags that must be present, all '-' After the flags, there is a sequence of integers: - the number of months (zoom factor) that fills one screenful - The display mode is 0 for the default files as defined in the file list menu, 1 for all files, 2 for own appointments only, and 2 for the file defined by the following number. - the number of the file whose appointments are displayed if the previous number is 3. P The PostScript printing options. Ten flag characters, followed by a blank and the print mode: a omit all appointments from the printout p omit all private appointments from the printout - eight unused flags that must be present, all '-' - the mode: 0 for month, 1 for year, 2 for landscape week, and 3 for portrait week p The print spooling string. When printing a PostScript calendar, the PostScript code is sent to stdin of this command. m The mailer program, as specified in the Alarm Options menu. Up to one "%s" is allowed, it is replaced by the (quoted) note string. "%s" is typically used for a subject. U This code is obsolete since version 1.5. u One file in the file list. There are five arguments (the order is strange because the month flag has been added later in version 1.4): - the file (login) name - the file path - 0 if the file is shown in week views, 1 if the file is suspended - the color used in the week view, a number in the range 0..7 - 0 if the file is shown in month views, 1 if the file is suspended - 0 if appointments from this file are silent, 1 if they can trigger their alarms ENTRY TYPES: [0-9] Begins an entry. This is the only mandatory line, all others that follow are optional. All following lines that do not begin with a numeric digit are extra information for the entry. Unlike all other types, there is no TAB character in the second column, the first character is the first digit of the trigger date. The line consists of five date/time fields, seperated by at least one blank, and three flag characters that must be consecutive. As usual, flags are off if the character is '-', and on otherwise. The fields are: 1/2/3 trigger date, month/day/year. Year can be either 70..99,00..38, or 1970..2038. Do not enter appointments after 2037. If there is demand, I'll fix this bug in about 50 years. 1:2:3 trigger time, hour:minutes:seconds, in 24-hour format. 99:99:99 means that there is no alarm time ("-" in the time column). 1:2:3 length, hour:minutes:seconds, in 24-hour format 1:2:3 early-warning time, hour:minutes:seconds, in 24-hour format, 0:0:0 means there is no early warning 1:2:3 late-warning time, hour:minutes:seconds, in 24-hour format, 0:0:0 means there is no late warning S suspended (the green button at the left edge is off) P private (goes into the private dayplan file that has mode 0600) N no alarm (trigger warnings if nonzero, but no final alarm) M do not show this appointment in the month view Y do not show this appointment in the year view W do not show this appointment in the week view O do not show this appointment in the year overview D do not show this appointment in the day view t this is an active todo item, move to today if in the past - one unused flag, always '-' 0 appointment text color in month calendar: 0 is default, 1..8 are colors 0 show a warning this many days in advance: 0 means never, 1 means one day ahead, etc. E Add an exception date to the appointment. After the 'E', a tab and a date m/d/y on which the appointment will not trigger follow. There can be up to four 'E' lines for each appointment (see NEXC in conf.h). R Add repetition information to the current entry. There are five numeric fields, separated by at least one blank. This one is partic- ularly unsuited for human consumption, sorry. 1 trigger alarm every <1> days (in seconds) 2 delete alarm after this date (seconds since 1/1/70 0:00:00) 3 weekday bitmap and nth-week bitmap: bit0=sunday ... bit6=saturday bit8=first ... bit12=fifth, bit13=last 4 month day bitmap, bit0=last day of the month, bits 1..31=on that day of the month 5 if 1, the entry repeats every year; if 0, it doesn't. N Add a note string to the current entry. All characters that follow the TAB are part of the note string. M Add another line to the current entry's message. All characters that follow the TAB are part of the line. There can be multiple M lines, they all add to the message. S Add another line to the current entry's script. All characters that follow the TAB are part of the line. There can be multiple S lines, they all add to the script. G Reserved for group meetings, not currently used. PLAN(4)
All times are GMT -4. The time now is 02:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy