VM runs after reboot?

Similar Questions

• CF10 App running after reboot server. but website not available until the service restarts

  Hello, everyone.

  I recently returned from a work I've already had several months to another position.  On my return, I inherited someone another dev system (my old dev system, apparently, had been reimagee and given to someone else, after my departure).

  This system initially had CF9 server on it (the ColdFusion9 folder is still there) and now CF10.  By using the web server integrated (without IIS, no Apache)

  Whenever I have start/restart of the system, I can see in the computer management system Application Server is, in effect, running CF10.  But if I try to open the pages that I work, I get an error message cannot find the site.

  I'm in the computer management system, go to Services, right click on the application CF10 server, choose "Restart", wait until she finishes, and voila!, I get a page to work.

  Anyone know why this is happening or how to fix so that CF will work immediately after the start/restart without having to restart the service?

  Thank you

  Still don't know why CF showed that "started" when clearly he wasn't - but I found the culprit.  WebTrends.

  I have no idea why WebTrends has been installed on a system of dev (isolated from the internet), but that's it.

  I uninstalled WebTrends, restart the system, and (surprise!) the CF Server displays pages with no problems.

  Thank you, Alexander and Anit, for your help.

• My desktop icons will not run after a short period of time, with a reboot.

  My destop icons will not run after a short period of time, with a reboot

  Hello

  When did start to happening?

  You did any changes made to your PC?

  What HP PC model and operating system are you using?

• Can't use Firefox once after reboot my Mac, then he won't.

  After reboot or a total, followed by the setting stop running, I get use of Firefox. Once I close out of it, I can't hire back in.
  I checked and updated Firefox, no help. I am currently running Yosemite on my Mac.

  I tried a Force Quit on Firefox. Notice that the small point under the Firefox icon is missing. So, I then clicked on the Firefox icon and it has jumped up and down. Alto! I can now engage Firefox without having to restart my computer. So does that mean Firefox did not leave on its own? And why all of a sudden start. Inquiring minds. If with that I seem to be OK once more. How weird.

• The calendar settings reset after reboot

  Hello

  Could someone please check if you have the same problem on your phone?

  Sony calendar resets the settings after reboot.

  For example, if I put "week begins on ' = 'Monday' and restart the phone, this setting will return to 'Sunday' (which is the default).

  I am now running Calendar 20.0.A.2.5, but I think that this bug existed before as well (even on my old V Xperia I think)

  P.S. I found this subject, but I did not understand the solution correctly or it does not work for me... I tried to disable the calendar app, but it did not help somehow...

  There were improvements made on this subject and if you update the 23.4.A.0.546 phone and use the latest Google Calendar app I hope not to have this problem more.

• HP LaserJet CP1518ni - wireless installation, will now in offline mode after reboot

  I just install my printer wireless via my router and everything was fine - test pages, etc. I rebooted and after reboot, I can't use the printer.  It is "offline." Turn everything off and then does not solve the problem.  The printer is a Laserjet CP1518ni.  It is connected to my router and two computers use wireless. Don't know what to do. Help! Why is it keeps working after the first reboot?

  You can run printing HP and doctor Scan, and it can help with this problem.
  http://goo.GL/u3jDE

  It can also be a firewall or an antivirus which blocks. You can turn it off and try to print.

• Windows Update will not install after reboot required.

  Update of security for Microsoft Visual C++ 2005 Service Pack 1 (KB2538242).

  I'm running Windows 7 x 64.

  I have a Windows update that requires the closing down to install.   This is not, and after reboot, I have a slower computer.

  At this point, even removing the offending program would be useful.

  Thank you for your expertise.

  Hello

  Try the methods provided below and see if they help to resolve the issue.

  Method 1:

  In the case where you are not able to install specific updates then, try the troubleshooting provided in the link below steps to fix the problem.

  You cannot install some programs or updates

  http://support.Microsoft.com/kb/822798

  Method 2:

  You can also try to reset the Windows Update components and check if that helps.

  Click on the link provided below for more information about resetting Windows Update components.

  How to reset the Windows Update components?

  http://support.Microsoft.com/kb/971058

  Method 3:

  Start the computer in a clean boot state and then try to download the updates manually.

  Put your boot system helps determine if third-party applications or startup items are causing the problem. If so, you need to maybe contact the manufacturer of the program for updates or uninstall and reinstall the program.

  See the following article in the Microsoft KB for more information on how to solve a problem by performing a clean boot in Windows Vista or Windows 7:

  How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

  http://support.Microsoft.com/kb/929135

  Note:

  After troubleshooting, be sure to set the computer to start as usual as mentioned in step 7 in the above article.

  Download the updates manually from the link provided below.

  MFC Package security update Microsoft Visual C++ 2008 Service Pack 1

  http://www.Microsoft.com/download/en/details.aspx?displaylang=en&ID=26368

  MFC Package security update Microsoft Visual C++ 2005 Service Pack 1

  http://www.Microsoft.com/download/en/details.aspx?ID=26347

  I hope this helps.

• BlackBerry smartphones my new favorite 9970 "BOLD" and no progress after reboot

  Hi all

  Your guys need help, my new favorite 9970 "BOLD" and no progress after reboot. I have a open the case and remove the batery and reinstall and still no improvement. Please asist.

  Hi abdulkader2002,

  Welcome to the community,

  Please take control of your applications do not install unwanted applications. Install only those who you most need. Please press on and press and hold the Menu for a few seconds, it will appear a screen that will display all the programs running in the background, usually five will always look here (home, BBM, Message, phone, browser), appropriate to other applications. are running.

• Can not connect to vcenter after reboot

  Hello VMware,

  I can not connect to vcenter after reboot with the error «Failed to connect to the Vmware research service»

  

  I tried to follow below doc but no help.

  http://www.myvmwareblog.com/2012/11/28/lookupservicesdk-SSL-certificate-verification-failed/

  I tried to play with the Vcenter screen underneath, but no luck.

  
  

  To resolve this problem, replace the VCSA IP with hostname VCSA in the search service configuration file, ls_url.txt file.

  To replace the VCSA IP address with the host VCSA name in the ls_url.txt file:

  1. Connect to the VCSA via ssh under the root user
  2. Go to the directory/etc/vmware-sso using the command:

     CD/etc/vmware-sso

  3. Make a backup copy of the file ls_url.txt using the command:

     CP ls_url.txt ls_url.txt.bak

  4. Open the file ls_url.txt using a text editor
  5. Replace the VCSA IP address with the host name of the VCSA. For example:

     https:// Lookupservice/XXXXXXXXXX/sdk

     Where XXXXXX is the host name of the VCSA.

     Note: It is usually the host name of the domain the VCSA FULL name. Make sure it matches the common name (CN) in the certificate name.

  6. Restart the VCSA services by running the command:

     restart the /etc/init.d/VMware-vpxd
     restart the /etc/init.d/VMware-SSO
     restart the /etc/init.d/VMware-InventoryService

     Or

     Restart the VCSA.

  Alternatively, you can use this workaround to regenerate the certificates for the vCenter Server Appliance.To to regenerate the certificates for the vCenter Server Appliance:

  1. Temporarily change the IP address of the vCenter Server Appliance to a different IP address, not used
  2. Restart the vCenter Server Appliance
  3. Change the IP address of the vCenter Server Appliance to the originating IP address
  4. Restart the vCenter Server Appliance
  5. Connect to vCenter Server Appliance, https://vcenterserveripmanagement Web page: 5480
  6. Click the Administration tab, and then select Yes to certificate enabled regeneration
  7. Click send to save the changes
  8. Restart the vCenter Server Appliance

• ESXi 5.5 build 2456374 is unable to reconnect to the vcenter after reboot

  Hello

  Have been hitting my head against it for the past few weeks. A host that has worked very well to a previous 5.5 build fails to reconnect to the vcenter after reboot once upgraded to build the 2456374. This also happens to the newly built guest. When a reconnection is started manually, it produces up to 80% (data of the host processing), then dies with a "general system error: internal error. I tried to remove the vpxa account, resetting the config network via the console, Cup NIC of the vswitch, removal of additional interfaces vkernel. The network via the console configuration reset allows me to reconfigure the net and tie vcenter and complete the host host configuration. However, as soon as I restart the host, is no longer, it reconnects to vcenter and I'm back where I started.

  Unfortunately, this is not a 100% event. If I rebuild a host enough times, one of the new buildings will finally works correctly.

  any ideas on how to solve this problem would be appreciated.

  Elmārs

  QUESTION REOLVED!

  Ok. so that was the easy part. Open a folder with vmware to identify the cause for this. After much digging, friction, pull hair, we found a clue in the hostd.log on the ESXi host.

  2015-04 - T 02, 04: 49:05.481Z [23381 B 70 error 'Hostsvc.NetworkProvider' user opID=HB-host-185064@917-1d029f4d-d2 = vpxuser] an error occurred during extraction of stack instance configuration: incompatible value of ccalgo for the Netstack instance: defaultTcpipStack.

  In my network performance test I did recently, I have significantly improved network iSCSI performance from the cubes NewReno network congestion control algorithm. For each of these hosts, as part of the installation procedure I now set the control algorithm of congestion on cube through the web interface. Finally, it is a little bug with that VMware believed fixed. Is not.

  To confirm doubling you encounter this problem, connect to the host (ssh or remote cli) and run the following command:

  list of esxcli ip network netstack

  You should get a message saying that there is an inconsistency in the netstack configuration.

  To fix, run the following command:

  esxcli network ip put netstack defaultTcpipStack cubic n - c

  the netstack from above list command should now display detailed information and will now be able to connect to vcenter.

  If I understand correctly, an article will be published on this in the near future.

• WebLogic Admin server fails to start after reboot

  Hi gurus,
  
  WebLogic Admin server starts after a reboot of the server. Note that weblogic has graciously stopped before restarting.
  
  Also note that the following files have been accidentally deleted after reboot (but I don't think that that should cause a problem..):
  / opt/Shared/Apps/Hyperion/Oracle/middleware/user_projects/Domains/EPMSystem/Servers/adminserver/Data/Store/default/_WLS_ADMINSERVER000000. DAT
  / opt/Shared/Apps/Hyperion/Oracle/middleware/user_projects/Domains/EPMSystem/Servers/adminserver/Data/Store/Diagnostics/WLS_DIAGNOSTICS000000. DAT
  
  
  Looking at the AdminServer.log:
  
  
  * # < 11 October 2012 11:27:53 CEST > < critical > < WebLogicServer > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969273846 > < BEA-000386 > < server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException: *.
  java.lang.AssertionError: weblogic.management.provider.EditFailedException:
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON. < init > (DomainRuntimeServiceMBeanImpl.java:79)
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON.getInstance (DomainRuntimeServiceMBeanImpl.java:68)
  at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
  at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
  to weblogic.management.deploy.internal.DeploymentManagerImpl. < init > (DeploymentManagerImpl.java:83)
  at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
  at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
  at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
  at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
  Caused by: weblogic.management.provider.EditFailedException:
  at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
  at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON. < init > (DomainRuntimeServiceMBeanImpl.java:76)
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON.getInstance (DomainRuntimeServiceMBeanImpl.java:68)
  at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
  at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
  to weblogic.management.deploy.internal.DeploymentManagerImpl. < init > (DeploymentManagerImpl.java:83)
  at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
  at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
  at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
  at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
  Caused by: org.xml.sax.SAXParseException: premature end of file.
  at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
  at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
  at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
  at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
  to com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ PrologDriver.next (XMLDocumentScannerImpl.java:1059)
  at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
  at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
  at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
  at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
  at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
  at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
  at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
  at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
  at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
  at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
  to weblogic.management.provider.internal.ConfigReader. < init > (ConfigReader.java:70)
  to weblogic.management.provider.internal.ConfigReader. < init > (ConfigReader.java:64)
  at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
  at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
  at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
  at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON. < init > (DomainRuntimeServiceMBeanImpl.java:76)
  to weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$ SINGLETON.getInstance (DomainRuntimeServiceMBeanImpl.java:68)
  at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
  at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
  to weblogic.management.deploy.internal.DeploymentManagerImpl. < init > (DeploymentManagerImpl.java:81)
  at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
  at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
  at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
  at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
  
  
  # < 11 October 2012 11:27:54 AM EDT > < opinion > < WebLogicServer > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274051 > < BEA-000365 > < changed failed State Server >
  # < 11 October 2012 11:27:54 AM EDT > < error > < WebLogicServer > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274053 > < BEA-000383 > < is not an essential service. The server will shut down >
  # < 11 October 2012 11:27:54 AM EDT > < opinion > < WebLogicServer > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274069 > < BEA-000365 > < server status changed to FORCE_SHUTTING_DOWN >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMX > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274138 > < BEA-149513 > < JMX Connector Server stopped at service: jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMX > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274140 > < BEA-149513 > < JMX Connector Server stopped at service: jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMX > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274141 > < BEA-149513 > < JMX Connector Server stopped at service: jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < WebService > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274146 > < BEA-220028 > < Web Service reliable agents are suspended. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < WebService > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274153 > < BEA-220029 > < Web Service reliable agents are shut down. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < MessagingBridge > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274318 > < BEA-200001 > < messaging bridge has shut down successfully. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMS > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274426 > < BEA-040308 > < service JMS suspends >.
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMS > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274506 > < BEA-040107 > < 8 cancelled by default connection factories. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JMS > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274510 > < BEA-040015 > < stop JMS is done >.
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JDBC > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274530 > < BEA-001144 > < Force suspending the JDBC service. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JDBC > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274536 > < BEA-001146 > < Force suspend the JDBC service finished >.
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JDBC > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274538 > < BEA-001147 > < JDBC service stop. >
  # < 11 October 2012 11:27:54 AM EDT > < Info > < JDBC > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274552 > < BEA-001149 > < stopping the completed JDBC service >.
  # < 11 October 2012 11:27:54 AM EDT > < Info > < WebLogicServer > < tnsq08041.energy.ge.com > < AdminServer > < main Thread > < < WLS Kernel > > <><>< 1349969274694 > < BEA-000236 > < stop run > discussions.
  .....
  
  
  Kindly guide me with this. Thank you!
  
  Published by: Kent Pawar. October 11, 2012 08:51

  It is:

  Caused by: weblogic.management.provider.EditFailedException:

  A likely reason may be a few changes in the config.xml file. If you have a previous backup of the config.xml file, then try to replace the config.xml file, and then restart the server.
  Another reason for this exception maybe it were completely a few changes to the configuration through the administration Console that were not activated and the server administrator has been restarted. According to this scenario, weblogic will create a dir /pendig and have a config.xml file is created with the changes unchecked.

  a solution of workaround that you can try to restore the management server:

  Under domain dir.
  \pending directory - take backup and delete the directory.

  Under Dir Admin Server:
  data\store - take backup and delete the directory.

  Thank you
  Sandeep

• Install PRE &amp; PSE V12 fails repeatedly even after reboot

  I have a working installation of

  • 5.3 Lightromm
  • Photoshop elements V11
  • First Elements V11

  on a PC running Windows 7 SP1.

  After the purchase of a new licenses of PSE & PRE V12 succesfully downloaded and unpacked all the files.

  but Setup process fails even after reboot and recovery point.

  

  Hello

  Please try to install the software with a new administrator account. A new local administrative account can exclude network strategies, corrupt profiles and configure administrative accounts: http://windows.microsoft.com/en-us/windows/create-user-account#create-user-account=windows-7

  If the error continues to appear, restart Windows in modified mode, and try again to install 12 elements: http://helpx.adobe.com/x-productkb/global/restart-windows-modified-mode-windows.html

  Concerning

  O´Neill_SG1

• Ping IP of ESXi host fails after reboot? Newbie

  VMWare ESXi 4.0.0 ReleaseBuild 171294 - HP ProLiant DL360 G4

  The server turned craps so we got a used that even make and model and shared disks.  Now we cannot connect with the customer and we cannot ping, ping times out.  When we ping from the console we get inconsistent results, can ping ok, the first IP addy and then fails on the second ping, or it connects to the second IP addy, but fails to ping first that it resolve the hostname constantly.  We stopped and started the management network and Management Agents a couple of times but no joy.

  I have the Articles KB 1008446 ping to the ESXi host IP fails after reboot, 1003490 restart the Management Agents on an ESX or ESXi Server and 1003677 Tech Support Mode of emergency support.

  What must we do to recover the server to an operational state? If there is other information needed to help us please let me know.

  And, what distro and version is ESXi 4.0.0 inspires?  I read that it is Redhat, but I couldn't find the version.

  I have worked with Soloris, Linux and Aix over the years, so I am comfortable working from the cmd line if need be.

  Thank you

  ESXi is not Linux. The VMkernel is VMware. The small console that runs the VMkernel is busybox. ESX has a VM management based on RedHat 5, but here again the VMkernel is all VMware.

  I would check that the embedded NICs are working properly. Start with a linux rescue disk and test.

  If all extracted would reset the system configuration from the yellow Console screen. Your configuration will be lost, but your machines virtual etc. will be OK. You will need to add to the inventory.

• Ubuntu 9.10 and more recent vmware server 2. Will never run after restart of ubuntu.

  Hello

  I installed VMware server on my box of ubuntu 9.10 (32 bit, P - IV 2.4 GHz, 2 GB RAM). The problem is that he never runs after a reboot, even if the demons are actually being run. If I run the file vmware - config.pl, it does not work because it tells me the vmci, vmmon and vmnet modules are not standard. I then remove these modules, re-run vmware - config.pl and then it works until the next reboot of the computer.

  Does anyone have a solution for this problem?

  Hello

  OK maybe that you have upgraded the kernel version recently?

  If you use the standard kernels provided with Ubuntu 9.10, always use this one:

  2.6.31 - 15-Generic

  Make the installation of vmware server with the kernel version above following the directions I told before. Then, you ALWAYS start ubuntu 9.10 with this kernel version and never use another more recent.

  At the moment (as I know), it is the only way to run a vmware server 2 on ubuntu 9.10.

  A saludo/best regards,.

  Pablo

  If upon mi respuesta ayuda, por favor puntuarla considered como correcta o util. MUCHAS gracias! - If you have found this information useful, please consider awarding points for the answers 'OK' or 'useful '. Thank you!!

• El Capitan keyboard does not not after reboot

  I have a Macbook Pro 13 inch with OS X El Capitan 10.11.6

  After one of the recent improvements, I met a problem, if I take my mac, the keyboard and the trackpad to respond enough lag (if I constantly try to move the cursor, he'll have a time and then for like half an hour it will completely stop responding and after this the other repeats). It only happens after reboot and only on the login screen. So if I put my mac to sleep and then wake up, everything will work perfectly. Same thing if I managed somehow to connect, once the keyboard and trackpad respond correctly. The only button that works fine after reboot is the power button, but it doesn't help much, because it charges does not solve the problem somehow: as soon as the user selection screen, keyboard and mouse stops responding again (or should I say "start answering from time to time").

  I saw lots of questions here on the keyboard does not not after waking up, but as you can see, this isn't my situation.

  Try again in Safe Mode.

  Start up all by holding down the SHIFT key. It takes five minutes longer because it is a disk first aid on the way up, and you MUST provide your user name and password, even if you normally the automatic connection.