mpt2sas posts in /var/log/vmkernel.log?

Similar Questions

• / var/log - safe to delete files

  Hi all

  On 1 of my hosts ESX file/var/log has grown to the point its me cause problems creating VM etc... look at the files in this folder are large size particularly sercure.1 and secure.2 (more than 200 MB) my question is, is - it safe to delete these files? I have also a lot of vmkernel.* is also safe to empty these files?

  Thank you

  The files that you see with le.1,.2,... extensions are newspapers archived resulting from the rotation of log files. Log files are usually shot based on their size, or when a host or VM is powered. You can remove these log files rotated if you want to free up disk space. I do not recommend you delete the files '.log', because they are usually the current criteria (except for virtual machine logs).

  However, if the log files have this size, there must be a reason for this. I would recommend that you first take a peek in log files to see if there is an issue that must be resolved before you delete.

  André

• Display of warning under/var/log/vmkwarning

  Please tell me the meaning of the newspapers showing under/var/log/vmkwarning

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.849 cpu11:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L113': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.850 cpu11:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L115': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.850 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L116': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.851 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L117': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.852 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L118': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.852 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L119': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.854 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L120': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.856 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L121': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.857 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L122': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 Protocol.

  6 February 20:43 DPE22 vmkernel: 0:00:15:42.857 cpu12:4119) WARNING: ScsiUid: 263: path 'vmhba3:C0:T0:L24': supports ANSI version 0 x 2 and a UID could not be extracted from the details of the INVESTIGATION. To be used with ESX, a device must support the SCSI 3 proto

  http://KB.VMware.com/kb/1005885

• Warning in the file/var/log/vmkwarning on an ESX Server:

  I ESX3.5 U2 set up with SAN, I get a warning message in the file/var/log/vmkwarning that says the following:

  VMkernel WARNING: Scsi id: 550: supports ANSI version ' SCSI-2' (0x2).» Be used with ESX a device must support the SCSI 3 Protocol.

  Should I be concerned and action?

  see this KB article

  http://KB.VMware.com/kb/1005885

  .. .and U4 seems to solve a difficulty

  http://KB.VMware.com/kb/1007971

• / var/log is full. Best practices?

  One of the score of the newspaper of our host is 100% full. I'm not the practice administrator for this host, but manage/deploy the virtual machines it for others to use.

  I was wondering what's the best practice to deal with a more complete log partition? I found an article that mentioned editing the file /etc/logrotate.d/vmkernel/ so that files

  be compressed more often and saved for less often, but there was no real clear instructions on what to change and how.

  Is the only way to investigate on the console itself or the directory/var/log via putty? No there is no way to see VIC?

  Thank you

  Hello

  To solve the immediate problem, I would transfer to any newspaper in/var/log with a number at the end is dire.1,.2, etc. to a temporary storage outside the ESX host location. You could run something similar to the following command of the scp to do:

  scp /var/log/*.[0-9]* /var/log/*/*.[0-9]* host:TemporaryDir
  

  Or you can use winscp to transfer of the ESX host in a windows box. A you get the files from existing logs from the system for later playback, use the following to clear the space:

  cd /var/log; rm *.[0-9]* */*.[0-9]*
  

  I would therefore consist logrotation thus directed by hardening for VMware ESX.

  Best regards, Edward L. Haletky VMware communities user moderator, VMware vExpert 2009
  "Now available on Rough Cuts: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security' VMware vSphere (TM) and Virtual Infrastructure Security: ESX security and virtual environment ' [url]
  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]
  [url =http://www.astroarch.com/wiki/index.php/Blog_Roll] SearchVMware Pro [url] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links Top security virtualization [url] links | URL = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcast Virtualization Security Table round Podcast [url]

• 5.2 Server postfix logging is more to /var/log/mail.log

  I would like to know if anyone else has this problem?

  After update macOS Sierra and Server 5.2, I get no message Postfix in /var/log/mail.log (aka SMTP Log).  I've never had a problem to see messages from postfix here before.  I defining all postfix mail log "info".

  I do not process messages greylisting Policy logging /var/log/mail.log.  Thus, the file seems to work in general.  But, no tricks postfix.

  Does anyone else have this problem?

  Same here, tried changing in debugging without result. Tried to change with the Terminal using serveradmin settings messaging or (I know you shouldn't do) editing the main.cf, also changed the com.apple.mail in the directory/etc/asl of notices info or debug nada!

  so, if anyone finds the solution? Please share

• WARNING: The system file "/ var/log ' reached out to space

  I have a DMM version 5.2.

  When entering the DMM via SSH or console shows me the following sentence:

  WARNING: The system file "/ var/log ' reached out to space

  How can I fix this error?

  I await your comments.

  Concerning

  Hi Aurelius,

  If the newspapers of cleaning did not help them (which I expect to). You can run in a known defect, this problem occurs because as the access_log does not turn properly after we reach the limit of size.

  The Cisco default is #.

  CSCti86040 - Access_log not turning or delete when erasing logs on DMM

  This default is set in point 5.2.2 release of code, but you can open a TAC case and we can remove the access_log journal and apply the workaround for the same thing.

  Thank you

  Sagar Dhanrale

• Directory to the/var/log/apache2 vRA device is not even after installing successfully

  VMware KB: Log locations for VMware vRealize Automation 7.x

  

  Installation of vRA succeeded him, but there is no ' / var/log/apache2 / * "vRA device." So I can't check if the apache is working properly. Everyone sees this directory?

  Apache is more used than the reverse proxy (we now use HAProxy), that the document should be updated.

  Thank you shouting it!

  Grant

• At all times the value/var/log/messages * mode 644

  What process constantly changes/var/log/messages * mode back to the 640? I want to disable that. Thank you.

  I'd guess logrotate.  Have you checked /etc/logrotate.d/syslog?  It does not specify a particular permission?

  If not specified, logrotate should retain the existing file permissions.

  Marc

• /var/log/boot.gz

  I guess that this file is created at startup and then gzip'd for archival purposes.

  So, question:

  -Is this file crashed every time you start it gets archived/moved/saved for historical reference, or is it just added/joint at each start-up phase?

  THX.

  Guardian1234 wrote:

  -Is this file crashed every time you start it gets archived/moved/saved for historical reference, or is it just added/joint at each start-up phase?

  I did two reboots of a 5.1 ESXi host and the boot.gz was that 30506 bytes in the first case and after the second reboot 30416 bytes. A large amount of new lines has been added, but the size was still a few bytes less. This strongly tells me that the file is overwritten each time you start. (Server on a persistent storage as well).

  You could read the file with zcat /var/log/boot.gz | more.

• Is it safe to delete the log file in/private/var/log/vnetlib?

  [Fusion 4.1.2 / Lion 10.7.4]

  My vnetlib log file is greater than 22 MB in size and has > K 250 lines of entries dating back to September 2011. Is it safe to delete this log file? A planning at startup, remove the file and then do a restart immediately after to restart VMWare network components - and we hope to recreate a new empty file. I tried erasing the contents of the file via the Terminal but do not have sufficient permissions, even with sudo - guess it was because the VMWare networking processes running at the time.

  Thank you

  John

  If you do not experience network problems, then it is safe to delete.

  I had no problem to remove in a Terminal (while VMware Fusion is running) by using the following command in (although I would recommend VMware Fusion of closing first and it doesn't have to be done in safe mode).

  sudo rm -f /var/log/vnetlib
  

  Just curious, what the big problem is why you want to delete, 22 MB is not that big a deal.

• vmware var log base file

  Hello

  Trying to do a cleaning on our box ESX3.  There are a lot of old log files accumulate so we removed most of them.  Can someone explain the "core" file/s in/var/log/vmware /?  There are much more like core.1234, core.8793 etc and we are not really sure what they are since then, except that they were 2007 unlike the one below;

  # ls - lh, / var/log/vmware

  total of 206 M

  -rw - 1 root root 163M 13 April 2009 core

  service console core dumps unannounced? You can remove...

  Duncan

  VMware communities user moderator | VCP | VCDX

  -

• ACS 5.5/var logs

  Hello
  I received a call today from our team of data statement 100% cpu on a Cisco ACS VM 5.5.0.46 Center (this machine virtual ACS is configured as a primary, but not as a newspaper collector) running. They also had a report indicating that the folder/var on this virtual machine was out of space (1 MB free)

  The CLI on the VM, I ran the command show disks and found the available disk space seemed ok:

  Internal file systems:
  ..
  / var: 80% used (10315944 7783116)
  ..
  all internal file systems have enough free space

  To the virtual machine restarts, showed the output:

  Internal file systems:
  ..
  / var: 5% used (10315944 442856)
  ..
  all internal file systems have enough free space

  If the incident recurs, what commands can I use to view the logs (and size) in / var and they appear in the annex of logrotate ACS?

  Thank you
  Andy

  Andy,

  You can't remove them, but ACS should prune them over time because it manages disk space.

  Javier Henderson

  Cisco Systems

• How to disable journaling documented in vmkernel.log in ESXi 5.5 u2

  Hello community!

  I'm trying to disable debug logging vmkernel.log but so far nothing helps. My vmkernel.log is watered by something like this:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.051Z cpu0:32866) 0 x

  00000000

  00001e00

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0 x 16] "" H2: 0xD7 command == 0 ".

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0x0f] ' H2: 0xD7 PETE:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.051Z cpu0:32866) 0 x

  00000000

  00000080

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.051Z cpu0:32866) [0x1c] ' H2: 0xD8 notification processor.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.052Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.052Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.055Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.055Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.350Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.350Z cpu0:32866) [0 x 17] ' H2: 0xD6 ME WP! = ME PR'

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.350Z cpu0:32866) [0 x 19] ' H2: 0xD6 Message header:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  0000000080040011

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0 x 26] "H2: 0xD6 TState:PState:SeqNo:Command:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  00000000

  00001f00

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0 x 16] "" H2: 0xD7 command == 0 ".

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0x0f] ' H2: 0xD7 PETE:

  [Debug ACPI]  (Integer 2015 - 06-30T 07: 17:08.351Z cpu0:32866) 0 x

  00000000

  00000080

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.351Z cpu0:32866) [0x1c] ' H2: 0xD8 notification processor.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.352Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.352Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0 x 28] ' H2: 0xD0 enter Manager SCI for HECI-2.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0x2d] ' H2: 0xD1 host interrupt status set to 1.

  [Debug ACPI]  (Chain 2015 - 06-30T 07: 17:08.353Z cpu0:32866) [0 x 24] ' H2: 0xD3: bits4 CSR_HA set to 0.

  [Debug ACPI]  Chain 2015-06-30 T 07: 17:08.353Z cpu0:32866) [0 x 19] ' H2: CSR_HA 0xD4 Bit3-> 0.

  What I did:

  1. updated the file config.xml in/etc/vmware/hoistd. Currently, section < Journal > looks like this:

  < Log >

  < Directory >/var/log/vmware/< / book >

  Info < level > < / level >

  < maxFileNum > 8 < / maxFileNum >

  < > 524288 maxFileSize < / maxFileSize >

  pass < name > < / name >

  < outputToConsole > false < / outputToConsole >

  < outputToFiles > false < / outputToFiles >

  < outputToSyslog > true < / outputToSyslog >

  < syslog >

  local4 < Setup > < / installation >

  < ident > go < / ident >

  < logHeaderFile > /var/run/vmware/hostdLogHeader.txt < / logHeaderFile >

  < / syslog >

  < / log >

  For the record, I changed < level > (was verbose)

  2. changes to the advanced settings:

  Verbose for info Config.HostAgent.log.level

  Vpx.Vpxa.config.log.level verbose for info.

  No results even after reboot of the host.

  I missed something?

  This ESXi is Lenovo custom image.

  Hello

  I met exactly same problem with our brand new Lenovo x 3650 M5 machines. Unfortunately, VMware was not able to say where these newspapers come as there is not a hardware problem.

  If you feel comfortable, you can decrease vmkernel loging level by:

  core of the system settings set - setting = acpiDbgLevel - value = 1 esxcli

  Then, you will need to reboot your host.

  I hope it helps.

• Registration of the VMWare Tools? No created log file

  Hello

  I have SuSE Linux with VMWare Tools.

  I add in the /etc/vmware-tools/tools.conf

  [record]

  Journal = true

  log.file="/var/log/VMwareTools.log".

  log. Level = Debug

  But the file does not create or write.

  What I did wrong?

  Is it a problem that the 'free' VMWareTools was insalled before?

  I would like to know why the Scripts:

  / usr/sbin/pre-freezescript and/usr/sbin/postthaw-script

  are not start if I run a snapshot

  Thank you

  You configuration in /etc/vmware-tools/tools.conf should look like this:

  [record]
  Journal = true
  vmtoolsd. Level = debug
  vmtoolsd. Handler = file

  vmtoolsd. Data = /var/log/vmtoolsd.log

  See the following article:

  Enabling debug logging for VMware Tools within a guest operating system

  With these settings, I can get logging to work in a prompt of SuSe VM.

  I would like to know why the Scripts:

  / usr/sbin/pre-freezescript and/usr/sbin/postthaw-script

  are not start if I run a snapshot

  To start the file names must be:

  usr/sbin/pre-antifreeze-script

  usr/sbin/post-thaw-script

  These files must also be executable with 0755 permissions and owner root. Make sure that it is set to script files.

  Also you can check the file vmware.log of the VM on the data store that records messages related to the VM of ESXi host point of view.