Syslog errors

I see the following errors in the syslog all the time.
Leopard 10.5.3 Mac MIni PPC - all patches current.
Airport Extreme Base station 7.3.1
NAT box not checked in AEBS NAT screen
Connect to the internet via Verizon DSL, PPPoE, DCHP from Verizon.
Thu Jun 19 17:21:26 tommac mDNSResponder[21] <Error>: NAT gateway 192.168.1.1 rebooted
Thu Jun 19 17:21:29 tommac mDNSResponder[21] <Error>: Failed to obtain NAT port mapping 0080A41C from router 192.168.1.1 external address 151.199.19.28 internal port 4500 error 0
Thu Jun 19 17:21:29 tommac mDNSResponder[21] <Error>: Failed to obtain NAT port mapping 0004A4C4 from router 192.168.1.1 external address 151.199.19.28 internal port 5353 error 0
Thu Jun 19 17:21:35 tommac [0x0-0x66f66f].com.apple.airport.airportutility[26651] <Notice>: WirelessAttach: getInterfaceWithName failed
Thu Jun 19 17:21:35 tommac [0x0-0x66f66f].com.apple.airport.airportutility[26651] <Notice>: WirelessAttach: getInterfaceWithName failed
Firewall is on Set Access (option 3). I have allowed the following:
AFP
Printer Sharing
Screen Sharing
Airport Utility
Safari
iPhoto
ddnswriteconfig
I can use the web, VPN etc with no problems.
I have a new MB with the same except it is an Intel MAC with all the same setting, patch levels.
Any help would be appreciated.
Thank you

I read the mDNS info on several web sites. Seems like it is not a problem.

Similar Messages

WLC Syslog error message

Hi all,
I get a lot of the following syslog error messages from 3 of my 4 WLCs (two WiSMs).
Error message:
ethoip.c:342 ETHOIP-3-PKT_RECV_ERROR
I searched at cisco.com and I found the information to use the bug toolkit or open a tac case, but I didn't find a bug or any further information related to that problem.
I can not even recognize any differences in the WLC configs - for centralize configuration I use an WCS.
WiSM Software version: 5.0.148.0
WCS Software vesion: 5.0.56.0
Does anyone of you had the same problem?
Thank you for all information!
Best regards
Peter

Hi dennischolmes,
after your post I checked the mobility group configuration on all four controllers, and indeed, there was a inconsitency in the configuration. The WCS couldn't see the mismatch, because the settings between the WCS and the controllers were the same. As I looked on the controllers web pages i saw, that different mobility group memebers with various mobility group names were configured on every single controller, maybe caused by applying a new controller template, where i changed the mobility group name.
I started from scratch configuring the mobility groups and the syslog error messages were stopping.
Thank you very much!

[SOLVED]systemd-fstab-generator and syslog error?

here is the bootup error message:
Nov 2 07:27:58 localhost [ 9.207762] systemd-fstab-generator[151]: Failed to create unit file: File exists
Nov 2 07:27:58 localhost [ 10.119699] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited with exit status 1.
Nov 2 07:27:58 localhost [ 10.544789] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 07:27:58 localhost [ 10.544974] systemd[1]: Failed to listen on Syslog Socket.
and my fstab is here:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 /boot ext2 defaults 0 1
/dev/sdb5 / jfs defaults 0 1
/dev/sdb6 /home ext4 defaults,user_xattr 0 1
/dev/sdb7 /var reiserfs defaults 0 1
/dev/sdb8 /tmp reiserfs defaults 0 1
Last edited by frat (2012-11-02 03:21:07)

systemd-fstab-generator is fixed,thank you.
syslog errors still:
Nov 2 10:29:44 localhost [ 10.051816] systemd[1]: Socket service syslog.service not loaded, refusing.
Nov 2 10:29:44 localhost [ 10.052000] systemd[1]: Failed to listen on Syslog Socket.
#systemctl status syslog
syslog.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)
#systemctl status syslog.socket
syslog.socket - Syslog Socket
   Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
   Active: inactive (dead)
   Docs: man:systemd.special(7)
   http://www.freedesktop.org/wiki/Software/systemd/syslog
   CGroup: name=systemd:/system/syslog.socket
any advice?
Last edited by frat (2012-11-02 02:56:37)

Syslog errors while rebooting FI

Hi Team ,
We rebooted Fabric interconnect yesterday & found below errors on FI console.
Pls suggest what is cause of it & how it can be rectified.
syslog[5182]: ERROR, mts_send failed, ERROR = -1, ERRNO = 22
syslog[5182]: ERROR, mts_send failed, ERROR = -1, ERRNO = 22
syslog[5182]: ERROR, mts_send failed, ERROR = -1, ERRNO = 22
syslog[5182]: ERROR, mts_send failed, ERROR = -1, ERRNO = 22

Any idea guys ?

Syslog errors on Wireless..

Folks - I am trying to determine if the huge amount of client side errors I see in our logs is normal. We setup WCS a couple of years ago, and I have been having a constant battle with trying to resolve alot of, what appear to me, client side errors. I have tried tweaking the controllers logging, but my syslog still gets hundreds of messages like those below - So, I am just curious - is this normal, or do I have a much much bigger issue?
2011-06-15 00:00:30
Local0.Error
10.1.1.151
WISM1: *dot1xMsgTask: Jun 15 00:00:30.306: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M5 retransmissions exceeded for client 00:23:15:47:54:28
2011-06-15 00:01:57
Local0.Error
10.1.1.151
WISM1: *dot1xMsgTask: Jun 15 00:01:57.906: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M3 retransmissions exceeded for client 00:23:4d:3e:6c:9b
2011-06-15 00:03:27
Local0.Error
10.1.1.151
WISM1: *dot1xMsgTask: Jun 15 00:03:27.708: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2914 Max EAP identity request retries (21) exceeded for client 00:24:d6:1d:55:b2
2011-06-15 00:03:54
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:03:55.061: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:23:15:62:7b:14
2011-06-15 00:05:15
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:05:15.139: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:23:15:61:e6:28
2011-06-15 00:05:15
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:05:15.139: %LOG-3-Q_IND: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:23:15:62:7b:14
2011-06-15 00:06:50
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:06:50.230: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:23:15:62:74:1c
2011-06-15 00:06:50
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:06:50.230: %LOG-3-Q_IND: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:23:15:61:e6:28
2011-06-15 00:06:50
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:06:50.235: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:23:15:62:72:38
2011-06-15 00:06:51
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:06:51.112: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:23:15:62:74:1c
2011-06-15 00:06:51
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:06:51.131: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 40, key type 1, client 00:23:15:62:72:38
2011-06-15 00:08:33
Local0.Error
10.1.1.151
WISM1: *Dot1x_NW_MsgTask_0: Jun 15 00:08:33.329: %DOT1X-3-INVALID_WPA_KEY_MSG_STATE: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:24:d6:1d:5d:1e
2011-06-15 00:09:30
Local0.Error
10.1.1.151
WISM1: *dot1xMsgTask: Jun 15 00:09:30.513: %LOG-3-Q_IND: 1x_eapkey.c:708 Received invalid EAPOL-key M2 msg in START state - invalid secure bit; len 24, key type 1, client 00:24:d6:1d:5d:1e
2011-06-15 00:09:30
Local0.Error
10.1.1.151
WISM1: *dot1xMsgTask: Jun 15 00:09:30.513: %DOT1X-3-MAX_EAPOL_KEY_RETRANS: 1x_ptsm.c:407 Max EAPOL-key M3 retransmissions exceeded for client 00:23:4d:3e:6f:39

This is roaming breaking because of possibly :
-bad coverage between APs
-interference/high load
Little you can do from a config perspective apart from analyzing where those happen and see if they are indeed related to coverage or whatsoever

Syslog error - WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_clean_tx_irq: Detected Tx Unit Hang

I am receiving this error in my syslog, every couple weeks or so. It causes a flap between our two inline WAEs. Have an idea what can be causing this? syslog is below, start from the bottom up.
2011-03-10 10:30:08 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth4: e1000bp_watchdog: NIC Link is Up 1000 Mbps Full Duplex
2011-03-10 10:30:06 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_watchdog: NIC Link is Up 1000 Mbps Full Duplex
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_watch.status <0>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: jiffies <2b900a9e1>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_watch <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: time_stamp <2b9008c71>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: buffer_info[next_to_clean]
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_clean <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: next_to_use <7e>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: TDT <7e>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: TDH <91>
2011-03-10 10:30:02 Kernel Warning 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-4-900000: Tx Queue <0>
2011-03-10 10:30:02 Kernel Error 10.0.100.26 2011 Mar 10 15: kernel: %WAAS-SYS-3-900000: e1000bp: eth5: e1000bp_clean_tx_irq: Detected Tx Unit Hang

Here is the output from the show alarms hist, also there are no visual LED problem with the device.
     Op Sev Alarm ID             Module/Submodule     Instance
   1 C Mi servicedead          nodemgr              cms_ce
     Mar 7 15:00:41.435 EST, Processing Error Alarm, #000008, 2000:330004
     nodemgr: The cms_ce service died.
   2 R Mi servicedead          nodemgr              cms_ce
     Mar 7 15:00:31.233 EST, Processing Error Alarm, #000008, 2000:330004
     nodemgr: The cms_ce service died.
   3 C Mi servicedead          nodemgr              device_mgr
     Feb 2 11:31:45.484 EST, Processing Error Alarm, #000007, 2000:330004
     nodemgr: The device_mgr service died.
   4 R Mi servicedead          nodemgr              device_mgr
     Feb 2 11:31:35.282 EST, Processing Error Alarm, #000007, 2000:330004
     nodemgr: The device_mgr service died.
   5 C Mi servicedead          nodemgr              device_mgr
     Jan 22 20:39:47.480 EST, Processing Error Alarm, #000006, 2000:330004
     nodemgr: The device_mgr service died.
   6 R Mi servicedead          nodemgr              device_mgr
     Jan 22 20:39:37.276 EST, Processing Error Alarm, #000006, 2000:330004
     nodemgr: The device_mgr service died.

Syslog error 106023

Am getting the syslog messages flooded with error 106023. The recommended action says "could be port scanning or foot printing attempt". How to go about on this?

If the message specifies a source IP, I would shun that address on whichever interface it's arriving on.
HTH,

Syslog error: ERROR getting flow policy details

I just RMA'ed an inline wae-7371 and now both inline devices are throwing the below error. Traffic is being optimized if I look at active connections.
WAAS-STATS-3-600023: populate_flow_policy_details: ERROR getting flow policy details, Policy details have changed or are unavailable
Any help would be good, even a good listing of WAAS syslogs would be helpful, before calling TAC

Version is 4.1.3b we didnt upgrade with the RMAed device (but we are planing on upgrading to fix a AAA problem we are having with our ACS express)
Our policies have reciently been appied to the default device group and there are only 6 listed.
Application Policies
Classifier
Application
Action
Enabled
Type - Position
   NEODIN_Transactions-classifier
NEODIN_Transactions
Optimize(DRE,LZ)
Enabled
Basic 1
   DICOM_Classifier
DICOM
Optimize(DRE,LZ)
Enabled
Basic 2
   CIFS
WAFS
Optimize(DRE,LZ)
Enabled
Basic 3
   HTTP
Web
Optimize(DRE,LZ),Accelerate(HTTPAccelerator)
Enabled
Basic 4
   LDAP
Directory-Services
Optimize(DRE,LZ)
Enabled
Basic 5
   N/A
N/A
Optimize(DRE,LZ)
Enabled
Other 1
I thought this was strange, that our backups went from 24k to 4k after centrally managing the policies.
Are you saying that all the 162 polcies need to be listed, even if you dont have that type of traffic (IE Novell traffic)? We are currently just auditing the traffic we have between these two datacentres (95% of the traffic is our DICOM classifier on port 104) and are adding classifiers as needed.
I can try during our next "service window" to restore the default policies and add our two custom ones back (plus the http accelerator)
We are not using netflow on the devices.

Constant syslog errors

I installed archlinux on my laptop and after first boot i saw errors like
unable to enumerate USB device on port 2
unable to enumerate USB device on port 4
and that is couple of these errors a second so i couldn't see anything i wrote and output disappeared quite quickly in the flood of these errors. At first i wasn't to concern about that and i continued with post-installation work via ssh. But the problem remained. After some research i found that some users of Fedora and Debian have the same problem as is reported in these bugreports
https://bugzilla.redhat.com/show_bug.cgi?id=666563
http://lists.debian.org/debian-kernel/2 … 00576.html
It seems that it is actualy a NVIDIA problem. If i dont use prompt there is no discomfort, but the problem is that these errors fill my logs so that all log information is lost in the flood of these errors. What can i do to solve this. Is it appropriate to somehow block these errors and how would i do something like that.
Last edited by rokowsky (2012-09-18 09:25:22)

Bascially the MAC address is being seen on two different port-channels which is the cause for the flapping. You need to track down the MAC of the host that is flapping between ports and investigate. Issues could be NIC teaming issues. For example, I have seen issues where specific blade chassis that contain one more switches are split among a pair distro switches. Those then connect to a pair of core switches. If the the NIC teaming is set incorrectly on the server then the mac might show up via different paths to the root bridge. Might be the cause for the flapping.
Start with the host and work your way backward through the network.
Good Luck
- Mark

Syslog errors after upgrade to 10.5.5

I cannot find a solution to the following errors that are posted to the system log every 10 seconds:
org.openldap.slapd[318]: Unrecognized database type (netinfo)
com.apple.launchd[1] (org.openldap.slapd[318]): Exited with exit code: 1
com.apple.launchd[1] (org.openldap.slapd): Throttling respawn: Will start in 10 seconds
com.apple.launchd[1] (org.apache.httpd-1.3[321]): Exited with exit code: 1
com.apple.launchd[1] (org.apache.httpd-1.3): Throttling respawn: Will start in 10 seconds
org.apache.httpd[325]: Syntax error on line 2230 of /private/etc/apache2/httpd.conf:
org.apache.httpd[325]: Invalid command 'Spotlight', perhaps misspelled or defined by a module not included in the server configuration
com.apple.launchd[1] (org.apache.httpd[325]): Exited with exit code: 1
com.apple.launchd[1] (org.apache.httpd): Throttling respawn: Will start in 10 seconds
Web services are not turned on. It is a stand-alone OD server. (Although it was connected to an AD while at 10.4.) I don't see the "Spotlight" reference in line 2230 of the httpd.conf. I can't even start the web server. It was never configured under 10.4 that I know of.
I'd appreciate any assistance or documentation reference.
Thanks.
-cf
Craig Flowers
Champaign, Illinois
[email protected]

To fix the Apache errors, I did the following:
1) Enabled the Spotlight module in the Web - Settings window using Server Admin.
2) Followed a tip I found on another Apple discussion thread to turn off the launchd for Apache 1.3. That tip is from Mikael Lofgren and is included below.
Thank you Mikael.
-cf
Craig
Re: Upgrade to Apache 2.2 fails
Posted: Dec 20, 2007 6:47 AM in response to: John Wallrodt
Great that worked! =)
For this sounds like a launchdaemon is trying to start your old Apache
"com.apple.launchd[1] (org.apache.httpd-1.3) Throttling respawn: Will start in 10 seconds"
Try to download "Lingon"
http://lingon.sourceforge.net/ and have a look at
System Daemon->org.apache.httpd-1.3
My file says this command:
/usr/sbin/httpd-1.3 -F -D LAUNCHD
and if i run it like this in terminal:
sudo /usr/sbin/httpd-1.3 -F -D LAUNCHD
it look likes it tries to start the old sites. So maybe try to
uncheck "Run it when it is loaded by the system (at startup or login)"
and see what happends.

WAAS syslog error: nscd: %WAAS-UNKNOWN-5-899999: 5317: Handled cache clean up for SIGHUP

Hi All,
Can anyone tell me what this syslog message relates to? I'm seeing it on a whole lot of WAEs. Is it something I need to worry about or not?
nscd: %WAAS-UNKNOWN-5-899999: 5317: Handled cache clean up for SIGHUP
Thanks
Claire

Hi Claire,
Getting this message can be normal.
Since it is generated by the nscd process that takes care of the dns caching (and that is it generated when the cache is flushed), I would maybe verify the DNS config on those devices and if it is properly configured, I wouldn't worry about it.
If you want, the test self-diagnostic basic should test your DNS settings for you.
Regards,
Nicolas

Message about Error binding socket....journal/syslog

I do not have a systemd archlinux. I was only following the new suggestions about initscripts.
However, at boot, I see a message error like this:
Error binding socket; addr='AF_UNIX(/run/systemd/journal/syslog)', error='No such file or directory (2)'
etc.
There is another post about this, but it is related to a systemd arch installation.
Last edited by hifi25nl (2012-10-21 10:38:41)

I see (man pacman):
The current file is the same as the original but the new one differs. Since the user did not ever modify the file, and the new one may contain improvements or bugfixes, install the new file.
Makes sense.
Shame on me, for never reading or overseeing this...
Thanks for the pointer.
Last edited by rebootl (2012-10-21 18:30:03)

Limit of 10 000 messages for syslog"s

I am using LMS 3.2 as syslog server.
I have set purge settings. Ther is enaughe free space on a disk. But when the nmber of syslog messeges increases up to 10 000. it stops to collect them.
So all messages will be lost if it is fool.
How can I change 10 000 limit for about 100 000 ???

If you're referring to the "SLCA0131: There are more than 10000 records generated for this date range.
Only 10000 records are being displayed, starting with the records generated on the end date." message when generating a syslog report, I don't think the answer has changed since this thread below:
http://supportforums.cisco.com/message/638820#638820Re: Cisco works cant display more then 10k of syslog error
Your syslogs are not being lost though. You can still view them in the raw syslog_info file(s) on the CLI.

WAAS - Disk Space Error

Hi all,
Is this Syslog Error Message affecting statistics in % Compression?
What is the cause of this ? It is tunned, or should be automaticaly resolved?
Best Regards,
Bruno PetrÃ³nio
*** Output ***
2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (74488:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x51e7e008, 65536, 68485120): No space left on device
2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (74673:2) FileMgr failed in writing data-segment start at id=834779, error=0xfffffc09--Disk is full
2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690464: (112823:2) RE File Manager error: filemgr_state::do_io (segments) call pwrite(90, 0x5140e008, 65536, 69271552): No space left on device
2009 Jul 30 11:33:13 wae so_dre: %WAAS-RE-3-690432: (112995:2) FileMgr failed in writing data-segment start at id=834791, error=0xfffffc09--Disk is full
wae#show disks details
Physical disk information:
disk00: Present WD-WCANY3489733 (h02 c00 i00 l00 - Int DAS-SATA)
238472MB(232.9GB)
disk01: Present WD-WCANY3489714 (h02 c00 i01 l00 - Int DAS-SATA)
238472MB(232.9GB)
Mounted file systems:
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
/sw internal /dev/md0 991MB 912MB 79MB 92%
/swstore internal /dev/md1 991MB 459MB 532MB 46%
/state internal /dev/md2 5951MB 191MB 5760MB 3%
/local/local1 SYSFS /dev/md4 11903MB 601MB 11302MB 5%
.../local1/spool PRINTSPOOL /dev/data1/spool 991MB 32MB 959MB 3%
/obj1 CONTENT /dev/data1/obj 125975MB 1013MB 124962MB 0%
/dre1 CONTENT /dev/data1/dre 59515MB 59514MB 1MB 99%
/ackq1 internal /dev/data1/ackq 1189MB 32MB 1157MB 2%
/plz1 internal /dev/data1/plz 2379MB 65MB 2314MB 2%
Software RAID devices:
DEVICE NAME TYPE STATUS PHYSICAL DEVICES AND STATUS
/dev/md0 RAID-1 NORMAL OPERATION disk00/00[GOOD] disk01/00[GOOD]
/dev/md1 RAID-1 NORMAL OPERATION disk00/01[GOOD] disk01/01[GOOD]
/dev/md2 RAID-1 NORMAL OPERATION disk00/02[GOOD] disk01/02[GOOD]
/dev/md3 RAID-1 NORMAL OPERATION disk00/03[GOOD] disk01/03[GOOD]
/dev/md4 RAID-1 NORMAL OPERATION disk00/04[GOOD] disk01/04[GOOD]
/dev/md5 RAID-1 NORMAL OPERATION disk00/05[GOOD] disk01/05[GOOD]
Disk encryption feature is disabled.
wae# sho disks failed-disk-id
Disk location Serial Number
wae# sho disks failed-sectors
disk00
=========
(none)
disk01
=========
(none)
wae#

Thank You very much Zach,
It seems to be the case.
It was a Demo in a client, which in some time we decide to upgrade the memory, cause a persistent tfo limition alarm.
The final results were not good about % of Optimization and Compression/Traffic Reduction.
But, what the hell, we are always learning !
Thanks a lot.
Bruno PetrÃ³nio

Syslog logging in CF801

How to enable syslog error logging in CF801?
Its old & documented bug #47314 [http://www.adobe.com/support/coldfusion/releasenotes/mx/knownissues_mx_j2ee_p2.html]
In the ColdFusion MX Administrator,on the Debugging & Logging > Logging Settings page, the Use operating system logging facilities option does not work. If you select it, restarting your application server throws the following error:
log4j:ERROR No syslog host is set for SyslogAppender named "null".
I got the same error.
Are there any solutions to enable it? Can I setup it by hands(edit some files)??
thanks

no such feature outthere, there is a field in the tables that will tell you the time a record was last updated cross reference that to your webserver access logs .. maybe that helps
we use SVN as a source depository for any code. The only way to promote the code form Dev to QA is to have it checked in, hence somewhat being able to identify who changed what

Syslog errors

Similar Messages

Maybe you are looking for