Detect a fatal shutdown
Hi,
Is it possible to do a particular treatment when a fatl shut down is done ( PC fatally shut down, database server fatally shut down ... ).
Is it possible to catch this event in FORMS ?
thanks.
Romeo
Here is the forum for you.
Similar Messages
-
we are using CISCO ASR 9006 . and we configured aaa authentication and commit changes after that i am able to login ASR with local user but
no any command execute and get error.
Command authorization failed - 'AAA API' detected the 'fatal' condition 'No method could process the authorisation request'
% Incomplete command.
please help.Hi Anop
How did you get over this problem? I am having the same issue.
Regards
Rohan -
How to detect client socket shutdowns in server socket
Hi,
Hoping to get some help with this. I am writing this program that implements a socket server that accepts a single client socket (from a third-party system). This server receives messages from another program and writes them to the client socket. It does not read anything back from the client. However, the client (which I have no control over) disconnects and reconnects to my server at random intervals. My issue is I cannot detect when the client has disconnected (normally or due to a network failure), hence am unable to accept a fresh connection from the client. Here's my code for the server.
ServerSocket serverSocket = null;
Socket clientSocket = null;
PrintWriter out = null;
BufferedReader in = null;
try{
if (serverSocket == null){
serverSocket = new ServerSocket(4511);
clientSocket = serverSocket.accept();
System.out.println("Accepted client request ... ");
out = new PrintWriter(clientSocket.getOutputStream(), true);
in = new BufferedReader(new InputStreamReader(clientSocket.getInputStream()));
System.out.println("Input / Output streams intialized ...");
while (true){
System.out.println("Is Client Socket Closed : " + clientSocket.isClosed());
System.out.println("Is Client Socket Connected : " + clientSocket.isConnected());
System.out.println("Is Client Socket Bound : " + clientSocket.isBound());
System.out.println("Is Client Socket Input Shutdown : " + clientSocket.isInputShutdown());
System.out.println("Is Client Socket Output Shutdown : " + clientSocket.isOutputShutdown());
System.out.println("Is Server Socket Bound : " + serverSocket.isBound());
System.out.println("Is Server Socket Closed : " + serverSocket.isClosed());
messageQueue = new MessageQueue(messageQueueDir+"/"+messageQueueFile);
//get Message from Queue Head (also removes it)
message = getQueueMessage(messageQueue);
//format and send to Third Party System
if (message != null){
out.println(formatMessage(message));
System.out.println("Sent to Client... ");
//sleep
System.out.println("Going to sleep 5 sec");
Thread.sleep(5000);
System.out.println("Wake up ...");
}catch(IOException ioe){
System.out.println("initSocketServer::IOException : " + ioe.getMessage());
}catch(Exception e){
System.out.println("initSocketServer::Exception : " + e.getMessage());
}I never use the client's inputstream to read, although I have declared it here. After the client is connected (it enters the while loop), it prints the following. These values stay the same even after the client disconnects.
Is Client Socket Closed : false
Is Client Socket Connected : true
Is Client Socket Bound : true
Is Client Socket Input Shutdown : false
Is Client Socket Output Shutdown : false
Is Server Socket Bound : true
Is Server Socket Closed : false
So, basically I am looking for a condition that detects that the client is no longer connected, so that I can bring serverSocket.accept() and in and out initializations within the while loop.
Appreciate much, thanks.Crossposted and answered.
-
Detect and Prevent SHUTDOWN ABORT
Hello all,
Is there any way to pre-detect the database when (for some reason) it is about to shutdown with the abort option?
My concern, is whether there exist any way that can be used to notify the user (even the sysdba) that such event happenedHello back,
This is what I've found the day the db went down, and the trigger was not fired
Wed Jul 27 04:32:38 2011
Errors in file d:\oracle\admin\db_name\bdump\db_name_lgwr_1988.trc:
ORA-00345: redo log write error block 180877 count 2
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\db_name\REDO01.LOG'
ORA-27072: skgfdisp: I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
Wed Jul 27 04:32:40 2011
Errors in file d:\oracle\admin\db_name\bdump\db_name_lgwr_1988.trc:
ORA-00340: IO error processing online log 1 of thread 1
ORA-00345: redo log write error block 180877 count 2
ORA-00312: online log 1 thread 1: 'D:\ORACLE\ORADATA\db_name\REDO01.LOG'
ORA-27072: skgfdisp: I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
LGWR: terminating instance due to error 340
Wed Jul 27 04:32:43 2011
Errors in file d:\oracle\admin\db_name\bdump\db_name_pmon_7312.trc:
ORA-00340: IO error processing online log of threadI do not know what the real reason could be.
I just thought, that "ringing a bell" when the db goes down would have been a solution while looking at the source
cousing the error. -
Detect if shutdown input is active PCI-733x
Is there a way to detect if the shutdown input of a PCI-7334 controller is active?
I'm using LabVIEW 2011 SP1 and NI-Motion 8.3.0.3 and there doesn't seems to be a function that read the state of this input. The setup controls 4 stepper motors and include an UMI-7774. An emergency stop pushbutton is connected to the global stop input of the UMI. No feedback devices are used, the steppers are in open-loop.
Basically what I want to do is make sure that the emergency stop pushbutton is not pressed before starting a test, if so the start test command is cancelled and popup message is displayed asking to check the state of the pushbutton.
The controller shutdown is activated by a rising edge on this input, so if a test is running it will immediately stop but if the pushbutton is already pressed when the test start the controller will send the steps and direction signal to the drivers. Note that the motors will not run because the drivers are disabled by the emergency stop pushbutton and that the controller will eventually stop on a programmed error condition but it is a non-negligible waste of time.
A possible workaround is to also connect the pushbutton to a digital or analog input on the UMI but it seems odd to me that the state of this input can't be read.
Any other suggestion?
Ben64Greetings;
After some preliminary search, I have not come across any VI that would simply check the value of the Shutdown line on a 7334. While I came across a few articles on implementing an Emergency stop, nothing popped up for that particular matter.
My initial thoughts are that the best way to go about it would be to simply split the wire into both the Shutdown line as well as any DIO input and check it therein. I will, however, do some more research and inform you of my findings.
Cordially;
Simon P.
National Instruments
Applications Engineer -
Xorg-No Device Detected-ATI Radeon [solved]
I keep getting errors while trying to start the X server- EE No Deviced Detected. I'm usting a dell inspiron 600m laptop with an ATI Radeon 9000 mobility.
I used the fglrx driver which loaded perfectly, it's just not working when i start X.
Here is my /var/log/Xorg.0.log
X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: UNKNOWN
Current Operating System: Linux derek-laptop 2.6.21-ARCH #1 SMP PREEMPT Sun May 6 18:33:47 CEST 2007 i686
Build Date: 08 April 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 2 21:02:08 2007
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Xorg Configured"
(**) |-->Screen "aticonfig-Screen[0]" (0)
(**) | |-->Monitor "aticonfig-Monitor[0]"
(**) | |-->Device "aticonfig-Device[0]"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbRules" "xorg"
(**) XKB: rules: "xorg"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(WW) Option "XkbLayout" requires an string value
(WW) Option "XkbVariant" requires an string value
(==) Keyboard: CustomKeycode disabled
(**) |-->Input Device "USB Mouse"
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/75dpi").
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/75dpi").
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/100dpi").
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/100dpi").
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ttf/western" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
Entry deleted from font path.
(**) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/misc
(**) RgbPath set to "/usr/share/X11/rgb"
(**) ModulePath set to "/usr/lib/xorg/modules"
(**) Option "AllowMouseOpenFail" "true"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Loader magic: 0x81c44a0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 1.1
X.Org XInput driver : 0.7
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(--) using VT number 7
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,3340 card 1028,01be rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,3341 card 0000,0000 rev 03 class 06,04,00 hdr 01
(II) PCI: 00:1d:0: chip 8086,24c2 card 1028,01be rev 01 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,24c4 card 1028,01be rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,24c7 card 1028,01be rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,24cd card 1028,01be rev 01 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev 81 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,24cc card 0000,0000 rev 01 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,24ca card 1028,01be rev 01 class 01,01,8a hdr 00
(II) PCI: 00:1f:5: chip 8086,24c5 card 1028,01be rev 01 class 04,01,00 hdr 00
(II) PCI: 00:1f:6: chip 8086,24c6 card 14f1,5422 rev 01 class 07,03,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4c66 card 1028,01be rev 02 class 03,00,00 hdr 00
(II) PCI: 02:00:0: chip 14e4,170c card 1028,8127 rev 02 class 02,00,00 hdr 00
(II) PCI: 02:01:0: chip 1217,7113 card d001,0000 rev 20 class 06,07,00 hdr 82
(II) PCI: 02:01:1: chip 1217,7113 card d801,0000 rev 20 class 06,07,00 hdr 82
(II) PCI: 02:03:0: chip 8086,4223 card 8086,1020 rev 05 class 02,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Intel Bridge workaround enabled
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,7), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b]
[1] -1 0 0x0000c400 - 0x0000c4ff (0x100) IX[b]
[2] -1 0 0x0000c800 - 0x0000c8ff (0x100) IX[b]
[3] -1 0 0x0000cc00 - 0x0000ccff (0x100) IX[b]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xfc000000 - 0xfdffffff (0x2000000) MX[b]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[b]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:30:0), (0,2,10), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 2 I/O range:
[0] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
[1] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[b]
[2] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[3] -1 0 0x0000dc00 - 0x0000dcff (0x100) IX[b]
[4] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[b]
[5] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
[6] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[b]
[7] -1 0 0x0000ec00 - 0x0000ecff (0x100) IX[b]
(II) Bus 2 non-prefetchable memory range:
[0] -1 0 0xf6000000 - 0xfbffffff (0x6000000) MX[b]
(II) Bus 2 prefetchable memory range:
[0] -1 0 0x50000000 - 0x57ffffff (0x8000000) MX[b]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-CardBus bridge:
(II) Bus 3: bridge is at (2:1:0), (2,3,6), BCTRL: 0x0580 (VGA_EN is cleared)
(II) Bus 3 I/O range:
[0] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
[1] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[b]
(II) Bus 3 prefetchable memory range:
[0] -1 0 0x50000000 - 0x53ffffff (0x4000000) MX[b]
(II) PCI-to-CardBus bridge:
(II) Bus 7: bridge is at (2:1:1), (2,7,10), BCTRL: 0x0580 (VGA_EN is cleared)
(II) Bus 7 I/O range:
[0] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[b]
[1] -1 0 0x0000dc00 - 0x0000dcff (0x100) IX[b]
(II) Bus 7 prefetchable memory range:
[0] -1 0 0x54000000 - 0x57ffffff (0x4000000) MX[b]
(--) PCI:*(1:0:0) ATI Technologies Inc Radeon R250 [Mobility FireGL 9000] rev 2, Mem @ 0xe8000000/27, 0xfcff0000/16, I/O @ 0xc000/8
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) PCI Memory resource overlap reduced 0xe0000000 from 0xe7ffffff to 0xdfffffff
(II) Active PCI resource ranges:
[0] -1 0 0xfaffd000 - 0xfaffdfff (0x1000) MX[b]
[1] -1 0 0xfaffe000 - 0xfaffffff (0x2000) MX[b]
[2] -1 0 0xf4fff400 - 0xf4fff4ff (0x100) MX[b]
[3] -1 0 0xf4fff800 - 0xf4fff9ff (0x200) MX[b]
[4] -1 0 0x58000000 - 0x580003ff (0x400) MX[b]
[5] -1 0 0xf4fffc00 - 0xf4ffffff (0x400) MX[b]
[6] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[7] -1 0 0xfcff0000 - 0xfcffffff (0x10000) MX[b](B)
[8] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[b](B)
[9] -1 0 0x0000b080 - 0x0000b0ff (0x80) IX[b]
[10] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[b]
[11] -1 0 0x0000bc40 - 0x0000bc7f (0x40) IX[b]
[12] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[b]
[13] -1 0 0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
[14] -1 0 0x00000374 - 0x00000374 (0x1) IX[b]
[15] -1 0 0x00000170 - 0x00000177 (0x8) IX[b]
[16] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[b]
[17] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[18] -1 0 0x0000bf20 - 0x0000bf3f (0x20) IX[b]
[19] -1 0 0x0000bf40 - 0x0000bf5f (0x20) IX[b]
[20] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[b]
[21] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b](B)
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xfaffd000 - 0xfaffdfff (0x1000) MX[b]
[1] -1 0 0xfaffe000 - 0xfaffffff (0x2000) MX[b]
[2] -1 0 0xf4fff400 - 0xf4fff4ff (0x100) MX[b]
[3] -1 0 0xf4fff800 - 0xf4fff9ff (0x200) MX[b]
[4] -1 0 0x58000000 - 0x580003ff (0x400) MX[b]
[5] -1 0 0xf4fffc00 - 0xf4ffffff (0x400) MX[b]
[6] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[7] -1 0 0xfcff0000 - 0xfcffffff (0x10000) MX[b](B)
[8] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[b](B)
[9] -1 0 0x0000b080 - 0x0000b0ff (0x80) IX[b]
[10] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[b]
[11] -1 0 0x0000bc40 - 0x0000bc7f (0x40) IX[b]
[12] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[b]
[13] -1 0 0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
[14] -1 0 0x00000374 - 0x00000374 (0x1) IX[b]
[15] -1 0 0x00000170 - 0x00000177 (0x8) IX[b]
[16] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[b]
[17] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[18] -1 0 0x0000bf20 - 0x0000bf3f (0x20) IX[b]
[19] -1 0 0x0000bf40 - 0x0000bf5f (0x20) IX[b]
[20] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[b]
[21] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0xfaffd000 - 0xfaffdfff (0x1000) MX[b]
[5] -1 0 0xfaffe000 - 0xfaffffff (0x2000) MX[b]
[6] -1 0 0xf4fff400 - 0xf4fff4ff (0x100) MX[b]
[7] -1 0 0xf4fff800 - 0xf4fff9ff (0x200) MX[b]
[8] -1 0 0x58000000 - 0x580003ff (0x400) MX[b]
[9] -1 0 0xf4fffc00 - 0xf4ffffff (0x400) MX[b]
[10] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
[11] -1 0 0xfcff0000 - 0xfcffffff (0x10000) MX[b](B)
[12] -1 0 0xe8000000 - 0xefffffff (0x8000000) MX[b](B)
[13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[14] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
[15] -1 0 0x0000b080 - 0x0000b0ff (0x80) IX[b]
[16] -1 0 0x0000b400 - 0x0000b4ff (0x100) IX[b]
[17] -1 0 0x0000bc40 - 0x0000bc7f (0x40) IX[b]
[18] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[b]
[19] -1 0 0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
[20] -1 0 0x00000374 - 0x00000374 (0x1) IX[b]
[21] -1 0 0x00000170 - 0x00000177 (0x8) IX[b]
[22] -1 0 0x000003f4 - 0x000003f4 (0x1) IX[b]
[23] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[b]
[24] -1 0 0x0000bf20 - 0x0000bf3f (0x20) IX[b]
[25] -1 0 0x0000bf40 - 0x0000bf5f (0x20) IX[b]
[26] -1 0 0x0000bf80 - 0x0000bf9f (0x20) IX[b]
[27] -1 0 0x0000c000 - 0x0000c0ff (0x100) IX[b](B)
(II) LoadModule: "ddc"
(II) Loading /usr/lib/xorg/modules//libddc.so
(II) Module ddc: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.1
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 7.2.0, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 7.1.0, module version = 8.37.6
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.0
(II) LoadModule: "keyboard"
(II) Loading /usr/lib/xorg/modules/input//keyboard_drv.so
(II) Module keyboard: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 7.2.0, module version = 1.1.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.7
(II) Primary Device is: PCI 01:00:0
(II) ATI Proprietary Linux Driver Version Identifier:8.37.6
(II) ATI Proprietary Linux Driver Release Identifier: LGDr8.37g1
(II) ATI Proprietary Linux Driver Build Date: May 25 2007 14:25:03
(II) ATI Proprietary Linux Driver Build Information: autobuild-rel-r6-8.37.1.1.2.3-driver-lnx-x86-x86_64-346145
(--) Assigning device section with no busID to primary device
(EE) No devices detected.
Fatal server error:
no screens found
and my /etc/X11/xorg.conf:
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "ServerLayout"
# PS/2 Mouse not detected
# Serial Mouse not detected
Identifier "Xorg Configured"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" ""
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
Identifier "Monitor0"
HorizSync 28.0 - 96.0
VertRefresh 50.0 - 75.0
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection
Section "Screen"
Identifier "Screen0"
Device "aticonfig-Device[0]"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Last edited by DrRootabega (2007-07-03 02:58:08)I think Flgrx simply does not support cards that are that old anymore. Use an older version or use xf86-video-ati which probably will be the better choice for you card anyways.
Last edited by kth5 (2007-07-03 01:37:02) -
Shutdown of the server and problems with some reports
Hello,
A fatal shutdown of the ERP server arrived. Now we have some errors and dumps for some transactions.
Dumps examples :
A RAISE statement in the program "CL_GUI_ALV_TREE===============CP" raised the
exception
condition "DP_ERROR".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
exception
condition "CNTL_ERROR".
How we can resolve these errors ? Kernel problems or other ideas ?
Thanks a lot
Rewards given.
Regards,Hi
Checkout for SAP notes with the Dump error such as DP_ERROR and the transaction for which dump occerred, you will get more relevant information, as program error could not be just interpreted looking at the dump.
Still if you are unable to find the reason, raising a message with SAP would be advisable.
Rahul -
Athlon XP-M detection for Delta-L
http://forum.clubedohardware.com.br/lofiversion/index.php/t140979.html\
if you scroll down it has 5.8 modded bios for Delta-L wwith Athlon XP-M detection and CPU shutdown
anyone cares to try it out?http://translate.google.com/translate?hl=en&sl=pt&u=http://forum.clubedohardware.com.br/lofiversion/index.php/t140979.html&prev=/search%3Fq%3Dhttp://forum.clubedohardware.com.br/lofiversion/index.php/t140979.html%26hl%3Den%26lr%3D%26sa%3DG
there you go here is the translated version....
if you mean the bios then....
arent most bioses english? -
Powering down USB on machine shutdown
When I shut my pc down the pc itself goes off but it leaves power to any usb devices attached, this means my mouse and usb hub continue to glow but worse, my external hdd doesn't detect the machine shutdown and so doesn't turn off itself.
I've read about this problem on a couple of other distro forums but no one has any solutions.
Does this affect anyone else and if so, how can I get usb to go down with the machine?This happens on two PCs, neither have windows on so I don't know if it is distro, OS or pc related.
In a thread on the the ubuntu forums people are saying that they have machines which do shutdown completely in Windows but not in ubuntu.
Did you get a solution?
I'll try to remember to check the BIOS next time I reboot and I'll try to dig out the motherboard manuals to see if they mention anything.
A similar thing, to get my PC to do wake on lan I had to run some software to set some flags, I assume in the bios, before it would work. This is even though I set the BIOS to do wake on lan in its own config editor. Could this be the same? -
[SOLVED] X11 Fatal server error: no screens found
Hello everyone!
I have just installed Arch x86_64 and I'm using a nVidia Corporation NV18 [GeForce4 MX 4000].
I'm running the command nvidia-xconfig to set up my xorg. Then I uncommented the line exec gnome-session in my .xinitrc. When run the command startx I get the following:
[root@work ~]# startx
xauth: creating new authority file /root/.serverauth.16103
xauth: creating new authority file /root/.Xauthority
xauth: creating new authority file /root/.Xauthority
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux work 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 06:42:43 UTC 2009 x86_64
Build Date: 28 May 2009 08:24:17PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 15:08:09 2009
(==) Using config file: "/etc/X11/xorg.conf"
(EE) Failed to load module "type1" (module does not exist, 0)
(EE) Failed to load module "freetype" (module does not exist, 0)
(EE) No devices detected.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
And looking at the log:
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.1.901 (1.6.2 RC 1)
Release Date: 2009-5-8
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux work 2.6.29-ARCH #1 SMP PREEMPT Wed May 20 06:42:43 UTC 2009 x86_64
Build Date: 28 May 2009 08:24:17PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 16 15:03:08 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0x3540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@1:0:0) nVidia Corporation NV18 [GeForce4 MX 4000] rev 193, Mem @ 0xe0000000/16777216, 0xd8000000/134217728, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded by default.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(WW) Warning, couldn't open module freetype
(II) UnloadModule: "freetype"
(EE) Failed to load module "freetype" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 180.51 Fri Apr 17 00:35:49 PDT 2009
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 180.51 Fri Apr 17 00:15:00 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.6.1.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(WW) NVIDIA(0): The NVIDIA GeForce4 MX 4000 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 96.43.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information. The 180.51 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU. Continuing probe...
(EE) No devices detected.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Aaand my xorg.conf is:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Fri Apr 17 00:40:10 PDT 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Files"
EndSection
Section "Module"
Load "dbe"
Load "extmod"
Load "type1"
Load "freetype"
Load "glx"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
Something weird is that if I remove the file xorg.conf I can start Gnome normally. Can anyone please tell me what is wrong?
Last edited by kdjtar (2009-06-17 15:59:17)Problem solved! I just noticed that I hadn't check which nvidia version I was using, as the log says:
(WW) NVIDIA(0): The NVIDIA GeForce4 MX 4000 GPU installed in this system is
(WW) NVIDIA(0): supported through the NVIDIA 96.43.xx Legacy drivers.
(WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
(WW) NVIDIA(0): more information. The 180.51 NVIDIA driver will ignore
(WW) NVIDIA(0): this GPU. Continuing probe...
And in fact I was using the 180.51 driver. Then I did the following:
# pacman -Rd nvidia nvidia-utils
Then:
# pacman -S nvidia-96xx nvidia-96xx-utils
And it's working now!
Thank you guys -
ASR9001 module A9K-MPA-20X1GE issue
Hi all!
Who knows, what does these messages mean?
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)'
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error) : pkg/bin/lda_server : (PID=40990) : -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
Is this hardware or software issue? What do you think?
I think we have faced with hardware issue of module A9K-MPA-20X1GE.
More outputs:
RP/0/RSP0/CPU0:asr9001#sh ver
Tue Oct 22 10:53:46.186 UTC
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 2.01(20130627:172232) [ASR9K ROMMON],
asr9001 uptime is 6 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-4.3.2/0x100000/mbiasr9k-rp.vm"
cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
P4040 processor at 1500MHz, Revision 2.0
ASR-9001 Chassis
2 Management Ethernet
4 TenGigE
4 DWDM controller(s)
4 WANPHY controller(s)
219k bytes of non-volatile configuration memory.
2880M bytes of hard disk.
3932144k bytes of disk0: (Sector size 512 bytes).
Configuration register on node 0/RSP0/CPU0 is 0x102
Boot device on node 0/RSP0/CPU0 is disk0:
Package active on node 0/RSP0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
Built on Sun Sep 1 19:23:39 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
Built on Sun Sep 1 19:21:14 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
Built on Sun Sep 1 19:21:14 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
Built on Sun Sep 1 19:21:19 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
Built on Sun Sep 1 19:21:22 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
Built on Sun Sep 1 19:21:16 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
Built on Sun Sep 1 19:27:30 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-mgbl, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-mgbl-4.3.2
Built on Sun Sep 1 19:28:25 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-supp-4.3.2
Built on Sun Sep 1 19:28:25 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-px-4.3.2
Built on Sun Sep 1 19:28:37 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-4.3.2
Built on Sun Sep 1 19:29:15 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-px-4.3.2
Built on Sun Sep 1 19:29:40 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9K-doc-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9K-doc-supp-4.3.2
Built on Sun Sep 1 19:29:07 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-doc-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-doc-px-4.3.2
Built on Sun Sep 1 19:29:14 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
Boot device on node 0/0/CPU0 is mem:
Package active on node 0/0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
Built on Sun Sep 1 19:23:39 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
Built on Sun Sep 1 19:21:14 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
Built on Sun Sep 1 19:21:14 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
Built on Sun Sep 1 19:21:19 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
Built on Sun Sep 1 19:21:22 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
Built on Sun Sep 1 19:21:10 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
Built on Sun Sep 1 19:21:16 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
Built on Sun Sep 1 19:27:30 UTC 2013
By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#sh log
Tue Oct 22 10:54:22.823 UTC
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level warnings, 44 messages logged
Monitor logging: level debugging, 0 messages logged
Trap logging: level informational, 0 messages logged
Buffer logging: level debugging, 148 messages logged
Log Buffer (307200 bytes):
RP/0/RSP0/CPU0:Oct 22 10:47:29.090 : init[65540]: %OS-INIT-7-MBI_STARTED : total time 8.814 seconds
RP/0/RSP0/CPU0:Oct 22 10:47:29.113 : imio[64]: %PLATFORM-IMIO-3-OPERATION_NOTIFY : imio_main: cold start
RP/0/RSP0/CPU0:Oct 22 10:48:42.672 : sysmgr[96]: %OS-SYSMGR-5-NOTICE : Card is COLD started
RP/0/RSP0/CPU0:Oct 22 10:48:50.075 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 89.801 seconds
RP/0/RSP0/CPU0:Oct 22 10:48:51.803 : sysmgr[407]: %OS-SYSMGR-6-INFO : Backup system manager is ready
RP/0/RSP0/CPU0:Oct 22 10:48:52.088 : sc_reddrv[376]: imio_lance2_init_interrupts:
RP/0/RSP0/CPU0:Oct 22 10:48:58.262 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : node set to DSC
RP/0/RSP0/CPU0:Oct 22 10:49:04.763 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-SYSTEM_COLD_START : System cold start detected. Resetting Line Cards.
RP/0/RSP0/CPU0:Oct 22 10:49:06.487 : pwr_mgmt[360]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM1/SP failure condition raised : Module input voltage out of range
RP/0/RSP0/CPU0:Oct 22 10:49:07.565 : online_diag_rsp[427]: %DIAG-DIAG-6-RUN_MINIMUM : ASR9001-RP 0/RSP0/CPU0: Running Minimum Diagnostics...
RP/0/RSP0/CPU0:Oct 22 10:49:09.369 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM : Fan tray RPM warning on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:49:12.761 : bpe[144]: %PLATFORM-BPE-5-INFO : successfully retrieved i2c eeprom
RP/0/RSP0/CPU0:Oct 22 10:49:12.969 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-7-CAN_INFO : Can API: slot 0 online event.
RP/0/RSP0/CPU0:Oct 22 10:49:12.991 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-3-POWER_SUPPLY_REDUNDANCY : Power Supply Failures are not protected.
RP/0/RSP0/CPU0:Oct 22 10:49:13.624 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/FT0/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.780 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM0/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.788 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM1/SP, state: FAILED
RP/0/RSP0/CPU0:Oct 22 10:49:13.789 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM1/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.800 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/RSP0/CPU0, state: IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:49:18.393 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_ERROR : Failed in envmon lwmconnect.message channel connection failed!,-1 error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511)
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in envmon_fantray_alarms.7076, error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511)
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-2-ENV_CONDITION : Outstanding environmental condition exists in the chassis
RP/0/RSP0/CPU0:Oct 22 10:49:19.815 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:20.816 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:21.817 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:22.843 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/RSP0/CPU0 inserted
RP/0/RSP0/CPU0:Oct 22 10:49:27.313 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
RP/0/RSP0/CPU0:Oct 22 10:49:32.838 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_DISCOVERY : Node State Discovery complete
RP/0/RSP0/CPU0:Oct 22 10:49:32.854 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.905 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FT0/SP FAN TRAY state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.957 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/CPU0 inserted
RP/0/RSP0/CPU0:Oct 22 10:49:35.224 : syslog_dev[94]: hsbi_fpd_agent[240]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:49:37.310 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to IOXR in state default
RP/0/RSP0/CPU0:Oct 22 10:49:48.759 : syslog_dev[94]: netio[327]: > WARNING (BM) [/ws/akgoswam-bgl/hellhound/nto6.4-XR/cisco/lib/3rdparty/netcomm/NetCommSw/Peripherals/BM/bm.h:352 BmBpidGet]: No Ipc - can't validate bpid.^M
RP/0/RSP0/CPU0:Oct 22 10:50:02.721 : ipodwdm[275]: %L2-G709-6-INFO : /harddisk:/ipodwdm_log Already present
RP/0/RSP0/CPU0:Oct 22 10:50:03.698 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/0/CPU0, RomMon Version: 2.1
RP/0/RSP0/CPU0:Oct 22 10:50:04.481 : shelfmgr[381]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : Remote location 0/0/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.3.2/lc/mbiasr9k-lc.vm validated
RP/0/RSP0/CPU0:Oct 22 10:50:04.499 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-BOOTING
RP/0/RSP0/CPU0:Oct 22 10:50:07.632 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to ACTV in state default
RP/0/RSP0/CPU0:Oct 22 10:50:14.758 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
RP/0/RSP0/CPU0:Oct 22 10:50:14.764 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED
RP/0/RSP0/CPU0:Oct 22 10:50:29.223 : placed[346]: LR-PLANE-READY DECLARATION
RP/0/RSP0/CPU0:Oct 22 10:50:31.360 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM_CLEAR : Fan tray RPM warning cleared on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:50:33.247 : ifmgr[242]: %PKT_INFRA-LINK-5-CHANGED : Interface MgmtEth0/RSP0/CPU0/1, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.257 : cfgmgr-rp[158]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/RSP0/0' has been restored.
RP/0/RSP0/CPU0:Oct 22 10:50:35.006 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM1/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.012 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM0/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.588 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:50:35.589 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED
RP/0/RSP0/CPU0:Oct 22 10:51:23.316 : dsc[181]: %PLATFORM-DSC_CTRL-6-RACK_STATE : Rack 1 is now Down
RP/0/RSP0/CPU0:Oct 22 10:51:23.321 : gsp[239]: gsp_rack_down_handler: for node:0x1
RP/0/RSP0/CPU0:Oct 22 10:51:25.396 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-RUNNING
LC/0/0/CPU0:10: init[65540]: %OS-INIT-7-MBI_STARTED : total time 5.152 seconds
LC/0/0/CPU0:Oct 22 10:51:57.119 : sysmgr[91]: %OS-SYSMGR-5-NOTICE : Card is COLD started
LC/0/0/CPU0:Oct 22 10:51:57.524 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 38.219 seconds
LC/0/0/CPU0:Oct 22 10:51:58.119 : sysmgr[341]: %OS-SYSMGR-6-INFO : Backup system manager is ready
RP/0/RSP0/CPU0:Oct 22 10:52:11.473 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 UNKNOWN state:UNPOWERED
RP/0/RSP0/CPU0:Oct 22 10:52:11.896 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:POWER UP
LC/0/0/CPU0:Oct 22 10:52:12.716 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing
RP/0/RSP0/CPU0:Oct 22 10:52:13.786 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:INITIALIZED
LC/0/0/CPU0:Oct 22 10:52:25.265 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
LC/0/0/CPU0:Oct 22 10:52:25.273 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
LC/0/0/CPU0:Oct 22 10:52:25.402 : lda_server[65]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : fpga3 instance 0 is down-rev (V0.07), upgrade to (V0.08). Use the "upgrade hw-module fpd" CLI in admin mode.
LC/0/0/CPU0:Oct 22 10:52:25.632 : sysmgr[91]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
LC/0/0/CPU0:Oct 22 10:52:27.651 : syslog_dev[89]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:52:37.663 : exec[65727]: %MGBL-exec-3-LOGIN_AUTHEN : Login Authentication failed. Exiting...
RP/0/RSP0/CPU0:Oct 22 10:52:43.079 : exec[65727]: %SECURITY-login-6-AUTHEN_SUCCESS : Successfully authenticated user 'shopik' from 'console' on 'con0_RSP0_CPU0'
RP/0/RSP0/CPU0:Oct 22 10:52:46.558 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.578 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.583 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 inserted
LC/0/0/CPU0:Oct 22 10:52:58.858 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/6, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/4, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/0, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:53:00.041 : upgrade_fpd_cli[65763]: %PLATFORM-UPGRADE_FPD-6-STATUS : FPD upgrade started.
LC/0/0/CPU0:Oct 22 10:53:01.800 : lda_server[65]: %PLATFORM-SCC-2-BAD_ID_HW : Failed Identification Test in 0/130/0 [5/0] The module in 0/130/0 in this router may not be a genuineCisco product. Cisco warranties and support programs onlyapply to genuine Cisco products. If Cisco determines thatyour insertion of non-Cisco SPA cards or other modules into aCisco product is the cause of a support issue, Cisco maydeny support under your warranty or under a Cisco supportprogram such as SmartNet.
RP/0/RSP0/CPU0:Oct 22 10:53:09.746 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:53:09.755 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: IOS XR RUN
LC/0/0/CPU0:Oct 22 10:53:31.822 : lda_server[65]: %PLATFORM-LDA-4-MPA_OIR_QUICK_BACK_TO_BACK_ERROR : OIR operation was performed on MPA in bay:0 while the system is initializing. Recommend waiting for two minutes after EP initialized.
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)'
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error) : pkg/bin/lda_server : (PID=40990) : -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#show inventory
Tue Oct 22 11:01:32.251 UTC
NAME: "module 0/RSP0/CPU0", DESCR: "ASR 9001, Route Switch Processor with 8GB memory"
PID: ASR9001-RP, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/CPU0", DESCR: "ASR 9001, Modular Line Card"
PID: ASR9001-LC, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/0", DESCR: "ASR 9000 20-port 1GE Modular Port Adapter"
PID: A9K-MPA-20X1GE, VID: V00, SN: FOC1522XXXX
NAME: "module 0/0/2", DESCR: "ASR 9000 Virtual Module"
PID: A9K-MODULEv, VID: N/A, SN: N/ABryan,
We checked the "show hw-module fpd location all" and there is no "yes" in the last column.
http://pastebin.com/W1wuqYks
RP/0/RSP0/CPU0:asr9001#sh hw-module fpd location all
Thu Oct 24 13:40:19.487 UTC
===================================== ==========================================
Existing Field Programmable Devices
==========================================
HW Current SW Upg/
Location Card Type Version Type Subtype Inst Version Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 ASR9001-RP 1.0 lc fpga2 0 1.14 No
lc cbc 0 22.114 No
lc rommon 0 2.01 No
0/FT0/SP ASR-9001-FAN 1.0 ft cbc 7 24.114 No
0/0/CPU0 ASR9001-LC 1.0 lc cbc 0 23.114 No
lc fpga2 0 1.18 No
lc fpga4 0 2.07 No
lc rommon 0 2.01 No -
When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
When FMLE stopped,Remote RTMP stream to FMS 4.5 with rtmfp?
edit "applications/multicast/main.asc" ?
HELP ME !!! THANKS!!!
* File: main.asc
* The server-side portion of the multicast sample application.
* This app accepts publish and unpublish requests from FMLE, and republishes
* the live stream from FMLE into a target Flash Group.
// General Constants
// "Constants" representing multicast event types.
var TYPE_FUSION = 1;
var TYPE_IP = 2;
var TYPE_P2P = 3;
// StreamContext Description, Constants and Functions
* Type: StreamContext
* This application tracks the context for live streams published to the server
* that are being republished into a Flash Group. The StreamContext "type" used
* for this is just an Object containing the following members:
* client - The encoding/publishing client.
* streamName - The source Stream name as published by the client.
* type - The multicast event type.
* groupspec - The groupspec identifying the Flash Group and capabilities.
* address - IP multicast address (optional for pure P2P events).
* netConnection - A loopback NetConnection used for the mcastNetStream.
* mcastNetStream - The NetStream used to republish the source Stream into
* the Flash Group.
* netGroup - An (optional) NetGroup handle for the target Group.
* Only present for Fusion or P2P events.
* state - One of the state constants defined immediately below
* this comment.
var STATE_INIT = 0; // Starting state for a StreamContext.
var STATE_CONNECTING = 1; // Establishing loop-back connection.
var STATE_CONNECTED = 2; // Connection established.
var STATE_PUBLISH_PENDING = 3; // Attempting to publish.
var STATE_REPUBLISHING = 4; // Actively republishing to multicast.
var STATE_UNPUBLISHING = 5; // Shutting down multicast republish.
var STATE_UNPUBLISHED = 6; // Unpublished successfully.
var STATE_DISCONNECTING = 7; // Shutting down loopback connection.
var STATE_DISCONNECTED = 8; // Connection shut down. Done.
* Registers a source Stream published by the specified client, along with the
* context for the multicast event, as a StreamContext Object.
* @param client - The Client publishing the stream.
* @param streamName - The source Stream name.
* @param params - The parameters resulting from parsing the source Stream's
* query string.
* @return The new StreamContext Object for the registered Stream.
function registerStream(client, streamName, params)
var streamContext = { "client": client,
"streamName": streamName,
"type": params["fms.multicast.type"],
"groupspec": params["fms.multicast.groupspec"] };
if (params["fms.multicast.interface"])
streamContext["interfaceAddress"] = params["fms.multicast.interface"];
if (params["fms.multicast.address"])
streamContext["address"] = params["fms.multicast.address"],
streamContext.state = STATE_INIT;
updateStreamContextLookups(streamContext);
trace("Registered multicast context for source stream: " + streamName);
return streamContext;
* Updates the indexed lookups installed for the passed StreamContext Object
* with the application.
* @param streamContext - The StreamContext Object to (re)index.
function updateStreamContextLookups(streamContext)
application.streamTable[streamContext.streamName] = streamContext;
if (streamContext.netConnection)
application.netConnTable[streamContext.netConnection] = streamContext;
if (streamContext.mcastNetStream)
application.mcastNetStreamTable[streamContext.mcastNetStream] = streamContext;
if (streamContext.netGroup)
application.netGroupTable[streamContext.netGroup] = streamContext;
* Provides access to the StreamContext Object for a registered source Stream
* by name.
* @param streamName - A registered source Stream name.
* @return The associated StreamContext Object; undefined if the source Stream
* name is not registered.
function getStreamContextForSourceStream(streamName)
return application.streamTable[streamName];
* Provides access to the StreamContext Object for a given server-side
* NetConnection hosting a multicast NetStream.
* @param netConnection - A server-side NetConnection.
* @return The associated StreamContext Object; undefined if the passed
* NetConnection is not indexed to a StreamContext.
function getStreamContextForNetConnection(netConnection)
return application.netConnTable[netConnection];
* Provides access to the StreamContext Object for a given multicast NetStream.
* @param netStream - A multicast NetStream.
* @return The associated StreamContext Object; undefined if the passed
* NetStream is not indexed to a StreamContext.
function getStreamContextForMulticastNetStream(netStream)
return application.mcastNetStreamTable[netStream];
* Provides access to the StreamContext Object for a given NetGroup associated
* with a multicast NetStream.
* @param netGroup - A NetGroup.
* @return The associated StreamContext Object; undefined if the passed
* NetGroup is not indexed to a StreamContext.
function getStreamContextForNetGroup(netGroup)
return application.netGroupTable[netGroup];
* Unregisters the StreamContext from the application.
* @param streamContext - The StreamContext Object to unregister.
function unregisterStreamContext(streamContext)
if (streamContext.netConnection)
delete application.netConnTable[streamContext.netConnection];
if (streamContext.mcastNetStream)
delete application.mcastNetStreamTable[streamContext.mcastNetStream];
if (streamContext.netGroup)
delete application.netGroupTable[streamContext.netGroup];
trace("Unregistered multicast context for source stream: " +
streamContext.streamName);
// Application callback functions
* Initializes global StreamContext lookup tables.
application.onAppStart = function()
application.streamTable = {};
application.netConnTable = {};
application.mcastNetStreamTable = {};
application.netGroupTable = {};
* Handles a publish event for the application by validating the request
* and bridging the published stream into a target Flash Group. Invalid
* publish requests are ignored and the publishing client's connection
* is closed.
* @param client - The publishing client.
* @param stream - The published stream.
application.onPublish = function(client, stream)
//trace("Handling publish request for source stream: " + stream.name);
var params = parseQueryString(stream.publishQueryString);
if (!validateStreamParams(params))
application.disconnect(client);
return;
var prevContext = getStreamContextForSourceStream(stream.name);
if (prevContext)
forceCloseStreamContext(prevContext);
// Register source Stream, and kick off the async process that will
// eventually wire-up the associated multicast NetStream.
var streamContext = registerStream(client, stream.name, params);
openMulticastConnection(streamContext);
* Handles an unpublish event for the application by shutting down
* any associated multicast NetStream.
* @param client - The unpublishing client.
* @param stream - The source stream being unpublished.
application.onUnpublish = function(client, stream)
trace("Handling unpublish request for source stream: " + stream.name);
var streamContext = getStreamContextForSourceStream(stream.name);
if (streamContext && (streamContext.state <= STATE_REPUBLISHING))
destroyStreamContext(streamContext);
// Callback functions for NetConnection and multicast NetStream/NetGroup wiring.
* First step in setting up a republished multicast NetStream; open the loopback
* connection it requires.
* @param streamContext - The StreamContext Object for the publish event.
function openMulticastConnection(streamContext)
var nc = new NetConnection();
nc.onStatus = netConnectionStatusHandler;
streamContext.netConnection = nc;
updateStreamContextLookups(streamContext);
streamContext.state = STATE_CONNECTING;
nc.connect(resetUriProtocol(streamContext.client.uri, "rtmfp"));
* Status event handler for the loopback NetConnection used by the multicast
* NetStream. Advances setup upon successful connection, or triggers or advances
* tear-down as a result of connection loss or an unpublish and clean shutdown.
* @param info - The status info Object.
function netConnectionStatusHandler(info)
var streamContext = getStreamContextForNetConnection(this);
trace("Multicast NetConnection Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."));
if (streamContext)
switch (info.code)
case "NetConnection.Connect.Success":
streamContext.state = STATE_CONNECTED;
// If event type is Fusion or P2p, wire up a NetGroup for neighbor
// bootstrapping and maintenance ahead of (re)publishing the stream.
var type = streamContext.type;
if (type == TYPE_FUSION || type == TYPE_P2P)
initNetGroup(streamContext);
else
initMulticastNetStream(streamContext);
break;
case "NetConnection.Connect.Failed":
case "NetConnection.Connect.Rejected":
case "NetConnection.Connect.AppShutdown":
trace("MULTICAST PUBLISH ERROR: Failed to establish server-side NetConnection for use by multicast NetStream. " +
"Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
streamContext.streamName);
streamContext.state = STATE_DISCONNECTED;
destroyStreamContext(streamContext);
break;
case "NetConnection.Connect.Closed":
if (streamContext.state < STATE_DISCONNECTING)
trace("MULTICAST PUBLISH ERROR: Unexpected server-side NetConnection close. " +
"Status code: " + info.code + ", description: " + info.description + ", Source stream: " +
streamContext.streamName);
streamContext.state = STATE_DISCONNECTED;
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* Initializes the multicast NetGroup following a successful connection of its
* underlying loopback NetConnection. This hook is optional and only runs for
* event types of Fusion and pure P2P.
* @param streamContext - The StreamContext Object for the multicast publish.
function initNetGroup(streamContext)
var ng = null;
try
ng = new NetGroup(streamContext.netConnection, streamContext.groupspec);
catch (e)
trace("MULTICAST PUBLISH ERROR: Failed to construct NetGroup. Error: "
+ e.name + (e.message ? " " + e.message : "") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
ng.onStatus = netGroupStatusHandler;
streamContext.netGroup = ng;
updateStreamContextLookups(streamContext);
* Status event handler for the multicast NetGroup. Advances to initializing the
* multicast NetStream upon successful NetGroup connect. Otherwise, triggers
* shut down.
* @param info - The status info Object.
function netGroupStatusHandler(info)
var streamContext = getStreamContextForNetGroup(this);
trace("Multicast NetGroup Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
if (streamContext)
switch (info.code)
case "NetGroup.Connect.Success":
initMulticastNetStream(streamContext);
break;
case "NetGroup.Connect.Failed":
case "NetGroup.Connect.Rejected":
trace("MULTICAST PUBLISH ERROR: Failed to connect multicast NetGroup. " +
"Status code: " + info.code + ", description: " + info.description +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
break;
case "NetGroup.MulticastStream.UnpublishNotify":
// At this point, multicast publishers will be notified;
// continue shut down.
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* Initializes the multicast NetStream following a successful connection of its
* underlying loopback NetConnection.
* @param streamContext - The StreamContext Object for the multicast publish.
function initMulticastNetStream(streamContext)
var ns = null;
try
ns = new NetStream(streamContext.netConnection, streamContext.groupspec);
catch (e)
trace("MULTICAST PUBLISH ERROR: Failed to construct multicast NetStream. Error: " +
e.name + (e.message ? " " + e.message : "") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
var type = streamContext.type;
if (type == TYPE_FUSION || type == TYPE_IP)
var iAddr = (streamContext.interfaceAddress) ? streamContext.interfaceAddress : null;
try
trace("Multicast NetStream will publish to IP address: " + streamContext.address +
" on interface address: " + ((iAddr) ? iAddr : "default") +
", Source stream: " + streamContext.streamName);
ns.setIPMulticastPublishAddress(streamContext.address, iAddr);
catch (e2)
trace("MULTICAST PUBLISH ERROR: Failed to assign IP multicast address and port for publishing. Address: "
+ streamContext.address + " on interface address: " + ((iAddr) ? iAddr : "default") +
", Source stream: " + streamContext.streamName);
destroyStreamContext(streamContext);
return;
ns.onStatus = netStreamStatusHandler;
streamContext.mcastNetStream = ns;
updateStreamContextLookups(streamContext);
streamContext.state = STATE_PUBLISH_PENDING;
* Status event handler for the multicast NetStream. Advances state upon successful
* connect and publish, or upon successful unpublish. Triggers tear-down if we fail
* to attach to a source Stream to republish.
* @param info - The status info Object.
function netStreamStatusHandler(info)
var streamContext = getStreamContextForMulticastNetStream(this);
trace("Multicast NetStream Status: " + info.code +
(streamContext ? ", Source stream: " + streamContext.streamName : ", Not associated with a source stream."))
if (streamContext)
switch (info.code)
case "NetStream.Connect.Success":
if (!this.attach(Stream.get(streamContext.streamName)))
trace("MULTICAST PUBLISH ERROR: Failed to attach multicast NetStream to source. Source stream: " +
streamContext.streamName);
destroyStreamContext(streamContext);
//var stream;
//stream = Stream.get("liveStream");
//return;
}else{
this.publish(streamContext.streamName, "live");
break;
case "NetStream.Publish.Start":
streamContext.state = STATE_REPUBLISHING;
break;
case "NetStream.Unpublish.Success":
streamContext.state = STATE_UNPUBLISHED;
// Wait for unpublish notify event if the context has a NetGroup;
// otherwise continue shut down now.
if (!streamContext.netGroup)
destroyStreamContext(streamContext);
break;
default:
// Ignore.
* The common tear-down hook. Other functions that manage or shut down
* the StreamContext Object delegate to this function upon detecting a fatal
* error or during shut down.
* @param streamContext - The StreamContext Object for the source Stream and
* (potentially wired-up) multicast NetStream.
function destroyStreamContext(streamContext)
// Unregister by Stream name immediately; lookups by NetConnection, NetGroup
// and multicast NetStream remain in place until tear-down is complete.
delete application.streamTable[streamContext.streamName];
switch (streamContext.state)
case STATE_REPUBLISHING:
streamContext.mcastNetStream.attach(false);
streamContext.mcastNetStream.publish(false);
streamContext.state = STATE_UNPUBLISHING;
return;
case STATE_CONNECTING:
case STATE_CONNECTED:
case STATE_PUBLISH_PENDING:
case STATE_UNPUBLISHED:
// Delete status handler callbacks and cleanup in case we arrived here
// as a result of a force close.
if (streamContext.netGroup)
delete streamContext.netGroup.onStatus;
if (streamContext.mcastNetStream)
streamContext.mcastNetStream.attach(false);
delete streamContext.mcastNetStream.onStatus;
streamContext.netConnection.close();
streamContext.state = STATE_DISCONNECTING;
return;
default:
// Fall-through.
// At this point, we either never got to the republishing state or we've
// proceeded through the clean shut down steps above. Everything for this
// StreamContext can go away.
unregisterStreamContext(streamContext);
* Utility function used to force close a StreamContext in the event that we
* start handling a republish of a Source stream before the context for its
* prior incarnation has been torn down.
* @param streamContext - The StreamContext Object for the source Stream.
function forceCloseStreamContext(streamContext)
trace("Force closing previous multicast context for source stream: " + stream.name);
prevContext.state = STATE_UNPUBLISHED;
destroyStreamContext(prevContext);
// Client callback functions
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onPublish.
* @param streamName - The name of the stream being published.
Client.prototype.FCPublish = function(streamName)
this.call("onFCPublish",
null,
{code:"NetStream.Publish.Start", description:streamName});
* A no-op. Answers the RPC in the fashion expected by encoders, but the real
* work happens in application.onUnpublish.
* @param streamName - The name of the stream being unpublished.
Client.prototype.FCUnpublish = function(streamName)
this.call("onFCUnpublish",
null,
{code:"NetStream.Unpublish.Success", description:streamName});
* If the client invoker's ip matches what was captured for a currently publishing
* stream, assume it's the same client and reset the stream. Otherwise, ignore.
* @param streamName - The name of the stream being released.
Client.prototype.releaseStream = function(streamName)
var streamContext = getStreamContextForSourceStream(streamName);
if (streamContext &&
(streamContext.client.ip == this.ip) &&
(streamContext.state <= STATE_REPUBLISHING))
// Only tear-down an orphaned stream if it's not
// already shutting down (see state check above).
destroyStreamContext(streamContext);
// Helper functions
* Validates that a newly published stream has correct metadata (e.g. query
* string parameters) to republish into a Flash Group. This function also
* writes a message to the application log for any validation failures.
* @param params - The quiery string parameters for the source Stream.
* @return true if valid; otherwise false.
function validateStreamParams(params)
var empty = true;
for (var param in params)
empty = false;
break;
if (empty)
trace("MULTICAST PUBLISH ERROR: Stream query string is empty.");
return false;
if (!params["fms.multicast.type"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.type'.");
return false;
var type = params["fms.multicast.type"];
if (type != 1 && type != 2 && type != 3)
trace("MULTICAST PUBLISH ERROR: 'fms.multicast.type' has invalid value: " + type);
return false;
if (!params["fms.multicast.groupspec"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.groupspec'.");
return false;
// Fusion and IP require an address:port.
if ((type == 1 || type == 2) &&
!params["fms.multicast.address"])
trace("MULTICAST PUBLISH ERROR: Stream query string does not specify a 'fms.multicast.address'.");
return false;
// No obvious validation issues.
return true;
* Parses the supplied query string, and if valid, returns an Object populated
* with the name-value pairs contained in the query string. The simple processing
* here does not preserve multiple name-value pairings having the same name; the
* last value seen wins. Parameters with no value are mapped to "" (empty String)
* in the returned Object.
* @param queryString - A query string portion of a URI, not including the leading
* '?' character.
* @return An Object containing a key-value mapping for each name-value parameter
* defined in the query string; Object is empty if the query string is
* invalid.
function parseQueryString(queryString)
var result = {};
var decoded = "";
try
decoded = decodeURIComponent(queryString);
catch (e) // Invalid URI component; return empty result.
return result;
if (decoded.length)
var params = decoded.split('&');
for (var i in params)
var pair = params[i];
var sepIndex = pair.indexOf('=');
if (sepIndex != -1)
var name = pair.substr(0, sepIndex);
result[name] = pair.substr(sepIndex + 1);
else
result[pair] = "";
return result;
* Utility function used to swap out the protocol (scheme) portion
* of a given URI with an alternate.
* @param uri - The full URI.
* @param desiredProtocol - The replacement protocol.
* @return The URI with its protocol replaced.
function resetUriProtocol(uri, desiredProtocol)
var sepIndex = uri.indexOf("://");
return desiredProtocol + uri.substr(sepIndex);HELP ME !!! THANKS!!!
-
Directory Server SMF tripping over itself (crosspost)
I've posted this question in the SMF related forum too, so if replies could go there, that would be handy: [http://forums.sun.com/thread.jspa?messageID=10940406]
We have a working instance of DSEE6.3.1 under Solaris 10 managed via SMF (using the manifest generated by dsadm/dscfg -- I forget which).
# svcs -a | grep ldap-user
online 10:47:08 svc:/application/sun/ds:ds--data-ldap-user-instanceAfter a forced shutdown, DSEE starts up and does a self-recovery (as it should). When that's complete, the slapd process is running and the startup script exits with status 221 (ie. Not 0) -- however slapd is running.
SMF notices that it's !0 and tries to restart DSEE... by issuing another start. This second start then exits almost immediately saying "slapd already running" but this time exits with 0 -- are we ok? No... cos SMF then notices that all the processes it just started have gone away so it calls "stop" followed by another "start".
This is where it gets a bit hazy as it looks like DSEE never shut down cleanly again so the whole process repeats itself ad infinitum (although I suspect that's a separate issue). :-(
I guess what I'm asking is -- is there a way to stop SMF from doing that: perhaps treat exit=221 as non-fatal and perform a service check?
Log file below:
[ Feb 26 21:40:42 Enabled. ]
[ Feb 26 21:40:50 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Failed to start Directory Server instance '/data/ldap/user/instance'
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Directory Server instance '/data/ldap/user/instance' has detected a disorderly shutdown or a change in cache
size
Recovery phase is starting, this may take a while...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
ns-slapd wrote the following lines in the error log (/data/ldap/user/instance/logs/errors):
##[26/Feb/2010:22:00:07 +0000] - Sun-Java(tm)-System-Directory/6.3.1 B2008.1121.0156 (64-bit) starting up
##[26/Feb/2010:22:00:09 +0000] - WARNING<20488> - Backend Database - conn=-1 op=-1 msgId=-1 - Detected Diso
rderly Shutdown last time Directory Server was running, recovering database.
##[26/Feb/2010:22:01:38 +0000] - Database recovery is 0% complete.
##[26/Feb/2010:22:01:51 +0000] - Database recovery is 100% complete.
##[26/Feb/2010:22:01:59 +0000] - WARNING<20805> - Backend Database - conn=-1 op=0 msgId=-1 - search is not
indexed base='cn=changelog' filter='(replicationcsn>=4b87f656000000000000)' scope='sub'
[ Feb 26 22:02:17 Method "start" exited with status 221 ]
[ Feb 26 22:02:17 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Directory Server instance '/data/ldap/user/instance' is already running (pid: 352)
[ Feb 26 22:02:18 Method "start" exited with status 0 ]
[ Feb 26 22:02:18 Stopping because all processes in service exited. ]
[ Feb 26 22:02:18 Executing stop method ("/opt/SUNWdsee/ds6/bin/dsadm stop --exec /data/ldap/user/instance")
Directory Server instance '/data/ldap/user/instance' stopped
[ Feb 26 22:02:20 Method "stop" exited with status 0 ]
[ Feb 26 22:02:20 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Failed to start Directory Server instance '/data/ldap/user/instance'
.......................... repeat ........................Well, one way around it is to write your own start script and manage the exit codes yourself.
I have some doubts about the autorestart configuration of DS, especially in a case like this where the server seems to be crashing. Realistically, you can end up worse off if your server has crashed by automatically restarting it. Your data may be corrupt, and the process may eventually stay up (especially if you work around the current issue), but the DS is not really healthy and it does need an administrator to investigate what's wrong with it. It may also return inconsistent or simply bad data to clients. All in all, I would prefer an instance in such a state to stay down and trigger alarms, assuming it has failover peers that can take on its workload. -
Directory Server SMF tripping over itself
We have a working instance of DSEE6.3.1 under Solaris 10 managed via SMF (using the manifest generated by dsadm/dscfg -- I forget which).
# svcs -a | grep ldap-user
online 10:47:08 svc:/application/sun/ds:ds--data-ldap-user-instanceAfter a forced shutdown, DSEE starts up and does a self-recovery (as it should). When that's complete, the slapd process is running and the startup script exits with status 221 (ie. Not 0) -- however slapd is running.
SMF notices that it's !0 and tries to restart DSEE... by issuing another start. This second start then exits almost immediately saying "slapd already running" but this time exits with 0 -- are we ok? No... cos SMF then notices that all the processes it just started have gone away so it calls "stop" followed by another "start".
This is where it gets a bit hazy as it looks like DSEE never shut down cleanly again so the whole process repeats itself ad infinitum (although I suspect that's a separate issue). :-(
I guess what I'm asking is -- is there a way to stop SMF from doing that: perhaps treat exit=221 as non-fatal and perform a service check?
Log file below:
[ Feb 26 21:40:42 Enabled. ]
[ Feb 26 21:40:50 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Failed to start Directory Server instance '/data/ldap/user/instance'
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Directory Server instance '/data/ldap/user/instance' has detected a disorderly shutdown or a change in cache
size
Recovery phase is starting, this may take a while...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
Waiting for Directory Server instance '/data/ldap/user/instance' to start...
ns-slapd wrote the following lines in the error log (/data/ldap/user/instance/logs/errors):
##[26/Feb/2010:22:00:07 +0000] - Sun-Java(tm)-System-Directory/6.3.1 B2008.1121.0156 (64-bit) starting up
##[26/Feb/2010:22:00:09 +0000] - WARNING<20488> - Backend Database - conn=-1 op=-1 msgId=-1 - Detected Diso
rderly Shutdown last time Directory Server was running, recovering database.
##[26/Feb/2010:22:01:38 +0000] - Database recovery is 0% complete.
##[26/Feb/2010:22:01:51 +0000] - Database recovery is 100% complete.
##[26/Feb/2010:22:01:59 +0000] - WARNING<20805> - Backend Database - conn=-1 op=0 msgId=-1 - search is not
indexed base='cn=changelog' filter='(replicationcsn>=4b87f656000000000000)' scope='sub'
[ Feb 26 22:02:17 Method "start" exited with status 221 ]
[ Feb 26 22:02:17 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Directory Server instance '/data/ldap/user/instance' is already running (pid: 352)
[ Feb 26 22:02:18 Method "start" exited with status 0 ]
[ Feb 26 22:02:18 Stopping because all processes in service exited. ]
[ Feb 26 22:02:18 Executing stop method ("/opt/SUNWdsee/ds6/bin/dsadm stop --exec /data/ldap/user/instance")
Directory Server instance '/data/ldap/user/instance' stopped
[ Feb 26 22:02:20 Method "stop" exited with status 0 ]
[ Feb 26 22:02:20 Executing start method ("/opt/SUNWdsee/ds6/bin/dsadm start --exec /data/ldap/user/instance
Failed to start Directory Server instance '/data/ldap/user/instance'
.......................... repeat ........................Well, one way around it is to write your own start script and manage the exit codes yourself.
I have some doubts about the autorestart configuration of DS, especially in a case like this where the server seems to be crashing. Realistically, you can end up worse off if your server has crashed by automatically restarting it. Your data may be corrupt, and the process may eventually stay up (especially if you work around the current issue), but the DS is not really healthy and it does need an administrator to investigate what's wrong with it. It may also return inconsistent or simply bad data to clients. All in all, I would prefer an instance in such a state to stay down and trigger alarms, assuming it has failover peers that can take on its workload. -
Hi folks.
I'm deploying BNG at ASR9k with IOS XR 4.3.1 and have some problems with RADIUS exchange. My current config is:
radius source-interface Loopback220 vrf default
radius-server host x.y.z.198 auth-port 1812 acct-port 1813
key test
aaa attribute format USERNAME
format-string length 253 "%s" outer-vlan-id
aaa attribute format NAS_PORT_FORMAT
circuit-id plus remote-id separator .
aaa radius attribute nas-port format e SSSSAAPPPPPVVVVVVVVVVVVVVVVVVVVV
aaa radius attribute nas-port-id format NAS_PORT_FORMAT
aaa group server radius BNG
server x.y.z.198 auth-port 1812 acct-port 1813
source-interface Loopback220
aaa accounting subscriber default group BNG
aaa authorization subscriber default group BNG
aaa authentication subscriber default group BNG
aaa authentication ppp default group BNG
dhcp ipv4
vrf INTERNET proxy profile IPV4_GROUP
profile IPV4_GROUP proxy
class INTERNET
match vrf INTERNET
helper-address vrf INTERNET x1.y1.z1.77 giaddr x2.y2.z2.129
limit lease per-remote-id 150
relay information option vpn
relay information option
relay information policy keep
relay information option allow-untrusted
interface TenGigE0/1/0/0.1 proxy profile IPV4_GROUP
Radius server is reachable from BNG with loopback220 source IP address.
interface TenGigE0/1/0/0.1
ipv4 point-to-point
ipv4 unnumbered Loopback200
service-policy type control subscriber IP_POLICY_BASIC
encapsulation dot1q 145 second-dot1q 1960
ipsubscriber ipv4 l2-connected
initiator dhcp
dynamic-template
type ipsubscriber IP_BASIC
ipv4 unnumbered Loopback200
class-map type control subscriber match-any DHCP
match protocol dhcpv4
end-class-map
policy-map type control subscriber IP_POLICY_BASIC
event session-start match-first
class type control subscriber DHCP do-until-failure
10 activate dynamic-template IP_BASIC
20 authorize aaa list default format USERNAME password test
end-policy-map
Radius debug info:
LC/0/1/CPU0:Aug 1 00:19:41.493 FET: radiusd[322]: ENTERING 'handle_nas_req'
LC/0/1/CPU0:Aug 1 00:19:41.493 FET: radiusd[322]: ENTERING 'radiusd_get_nas_identifier'
LC/0/1/CPU0:Aug 1 00:19:41.493 FET: radiusd[322]: ENTERING 'build_radius_pkt'
LC/0/1/CPU0:Aug 1 00:19:41.493 FET: radiusd[322]: EXITTING 'radiusd_get_nas_identifier'
LC/0/1/CPU0:Aug 1 00:19:41.493 FET: radiusd[322]: ENTERING 'build_radius_pkt_from_list'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: ENTERING 'radiusd_get_prepend_nas_id_to_session_id'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING 'radiusd_get_prepend_nas_id_to_session_id'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING 'build_radius_pkt_from_list'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING 'build_radius_pkt'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: ENTERING 'radius_send_request_message'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: ENTERING 'radius_get_next_server'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: Server x.y.z.198/1812/1813 is UP & Quarantined: NO
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: radius_get_next_server: Setting the preferred server handle to NULL
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: Sending request to x.y.z.198:1812, with retry_limit: 3 and delay: 5
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING 'radius_get_next_server'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: ENTERING 'radius_set_ident_sock'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING 'radius_set_ident_sock'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: ENTERING 'radius_ctx_db_insert_rctx'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: EXITTING (value 1) 'radius_ctx_db_insert_rctx'
LC/0/1/CPU0:Aug 1 00:19:41.494 FET: radiusd[322]: Sending request with id : 14/1347259508
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: ENTERING 'send_radius_packet'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: ENTERING 'radius_add_mand_attrs'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: EXITTING 'radius_add_mand_attrs'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: ENTERING 'radius_get_nas_ip_address'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Calling best local address using daemon address=x.y.z.198
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: ENTERING 'get_ip_addr_from_fib'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Address x.y.z.198 does not have a source address
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Got IP address: 0.0.0.0
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: IP source address aaa util format: 0.0.0.0
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: EXITTING 'get_ip_addr_from_fib'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: NAS best local address = 0.0.0.0
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: EXITTING 'radius_get_nas_ip_address'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Reencoding NAS-IP prev 0.0.0.0 new 0.0.0.0
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: ENTERING 'radius_get_next_server'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Server x.y.z.198/1812/1813 is UP & Quarantined: NO
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Failed aaa_sg_server_get_next_server with error 'qos-ea' detected the 'fatal' condition 'set exp imposition in egress is not permitted' rc = AFDF1600
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: EXITTING 'radius_get_next_server' with error [A247C800] 'Subsystem(1167)' detected the 'fatal' condition 'Code(36)'
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: NAS-IP-Address not found, Moving to next server in the server group
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Nas-IP-Address not found, dropping request
LC/0/1/CPU0:Aug 1 00:19:41.495 FET: radiusd[322]: Failed to send the request
Any workaround or recommendation to solve the issue?a have same problem on 5.1.1 software
aaa accounting system default start-stop group BNG
aaa group server radius BNG
server-private XX.XXX.XXX.8 auth-port 1812 acct-port 1813
key 7 000500140D551F031D324D5A490D000406
source-interface Loopback1
aaa authentication ppp default group BNG
aaa authentication login default local
dynamic-template
type ppp PPP_TPL
ppp authentication chap
ppp ipcp dns 8.8.8.8
ipv4 unnumbered Loopback2
interface Loopback1
ipv4 address 10.254.254.254 255.255.255.255
interface Loopback2
ipv4 address 10.254.254.253 255.255.255.255
interface MgmtEth0/RSP0/CPU0/0
ipv4 address 10.252.0.90 255.255.255.0
interface MgmtEth0/RSP0/CPU0/1
shutdown
interface TenGigE0/0/2/1.556
ipv4 address 10.56.0.1 255.255.255.0
service-policy type control subscriber PPP_PM
pppoe enable bba-group pppoe
encapsulation dot1q 556
aaa attribute format NAS_PORT_FORMAT
circuit-id plus remote-id separator .
aaa radius attribute nas-port format e SSAAPPPPQQQQQQQQQQVVVVVVVVVVUUUU type 32
aaa radius attribute nas-port format e SSAAPPPPQQQQQQQQQQVVVVVVVVVVUUUU
aaa radius attribute nas-port-id format NAS_PORT_FORMAT
aaa accounting subscriber default group BNG
aaa authorization subscriber default group BNG
aaa authentication subscriber default group BNG
pppoe bba-group pppoe
service selection disable
class-map type control subscriber match-any PPP
match protocol ppp
end-class-map
policy-map type control subscriber PPP_PM
event session-start match-first
class type control subscriber PPP do-until-failure
1 activate dynamic-template PPP_TPL
event session-activate match-first
class type control subscriber PPP do-until-failure
1 authenticate aaa list default
end-policy-map
Radius -server sends Access-Accept but on its router it isn't visible
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Send Access-Request to XX.XXX.XXX.8:1812 id 169, len 220
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: authenticator D3 8C BA E1 87 32 81 3C - E7 47 78 79 20 C1 AC 57
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Vendor,Cisco [26] 41
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Cisco AVpair [1] 35 client-mac-address=000e.0c75.b6d9
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Acct-Session-Id [44] 10 0400003b
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: NAS-Port [5] 6 2701140681
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: NAS-Port-Id [87] 3 .
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Vendor,Cisco [26] 9
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: cisco-nas-port [2] 3 .
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: User-Name [1] 11 user1
LC/0/0/CPU0:Mar 6 15:48:32.499 : radiusd[327]: RADIUS: Service-Type [6] 6 Framed[0]
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: CHAP-Password [3] 19 *
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: CHAP-Challenge [60] 18 r^K d ^BZ-^E^B^_^S^Xd^U)
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: Unsuppoted attribute.
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: Vendor,Cisco [26] 33
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: Cisco AVpair [1] 27 connect-progress=LCP Open
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: Framed-Protocol [7] 6 PPP[0]
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: NAS-Port-Type [61] 6 PPPoEoVLAN[0]
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: Event-Timestamp [55] 6 1394102897
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: Nas-Identifier [32] 14 asr9k_pppoe
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: RADIUS: NAS-IP-Address [4] 6 XX.XXX.XXX.9
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: Updating last used server
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: EXITTING 'send_radius_packet'
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: Got global deadtime 0
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: Using global deadtime = 0 sec
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: ENTERING 'start_dead_detect_timer'
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: EXITTING 'start_dead_detect_timer'
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: ENTERING 'radius_timer_update'
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: EXITTING 'radius_timer_update'
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: Updated timer thread rad_ident 169 remote_port 1812 remote_addr 0x30fb908c, socket 1342480676 rctx 0x5015b530
LC/0/0/CPU0:Mar 6 15:48:32.500 : radiusd[327]: ENTERING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: ENTERING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: ENTERING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: ENTERING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_timer_set_addl_context'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: Successfully sent packet and started timeout handler for rctx 0x5015b530
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_send_request_message'
LC/0/0/CPU0:Mar 6 15:48:32.501 : radiusd[327]: EXITTING 'radius_timeout_handler'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_timeout_handler'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_timer_get_addl_context'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_timer_get_addl_context'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_timer_get_addl_context'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_timer_get_addl_context'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: Timeout happened for req rad_ident 169 remote_port 1812 remote_addr 0x50 socket 1342480676 rctx 5015b530
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_ctx_db_get_and_remove_rctx'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: rctx found is 0x5015b530
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: EXITTING 'radius_ctx_db_get_and_remove_rctx'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_send_request_message'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: Reached retry count for the server 3,Trying to move to next server
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'radius_get_next_server'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: Server XX.XXX.XXX28/1812/1813 is UP & Quarantined: NO
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: EXITTING 'radius_get_next_server' with error [A247C800] 'Subsystem(1167)' detected the 'fatal' condition 'Code(36)'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: EXITTING 'radius_send_request_message' with error [A247C800] 'Subsystem(1167)' detected the 'fatal' condition 'Code(36)'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: ENTERING 'rad_nas_reply_to_client'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: rad_nas_reply_to_client: Received response from id : 169,packet type 1
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: rad_nas_reply_to_client: Sending failover message to client
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: EXITTING 'rad_nas_reply_to_client'
LC/0/0/CPU0:Mar 6 15:48:37.508 : radiusd[327]: EXITTING 'radius_timeout_handler'
I tried with group of radius and without it and different source-interface interfaces doesn't help
There are thoughts where to look?
Maybe you are looking for
-
ACS 5.4 Access Policies Problem
Hi Gents, I've been trying to troubleshoot this for a long time but I'm out of ideas now. here is the topo. I've got a Cisco ACS 5.4 VM used for Radius Network Authentication with a Cisco WLC 7.0, I've done the initial setup and all the rules, everyt
-
How to set Legislation rule for Enhanced Retro
how to set Legislation rule for Enhanced Retro How can i setup Enhanced Retro for Global HR International. Iam implementing HR/Payroll on latest 12i. I am using HR International. when i execute the following query , there is no records select * from
-
SMS id shows 759-73; so no one can reply to an SMS...
I have the caller id set to my cell number but when I send an SMS the receiver gets 759-73 as the sender. They can not respond to my SMS or figure who it is from? What good is that? HELP
-
Adding Selected value in JTable
hi , I want to put the file selected via the filechooser browse dialog and put it in the table.can someone help me plz?
-
"System Adm has set policies to prevent this installation" error message
I have always installed previous upgrade versions of iTunes with no problem. I'm the single user and the administrator of this stand-alone computer (not in a network). When I try to install iTunes 8 I get the "System Administrator has set policies to