I've just bought a HP DL360 gen8 server, but the issue is when i shutdown the server it do all its prosess but the led still glows and after 15-20 sec the server automatically starts again, can you guide me for that?
RHEL 5.x has an entropy-generation problem (held-over from kernel 2.4). Following directions from here has produced little-to-no results:
How to increase entropy pool on a 2.6 kernel RHEL/Fedora system without keyboard/mouse.
A good source of entropy is needed for random number generation. This affects services that go via SSL amongst other things. In 2.6 kernels the entropy sources of a system are keyboard, mouse and some IRQ interrupts. There are two random number sources on linux - /dev/random and /dev/urandom. /dev/random will block if there is nothing left in the entropy bit bucket. If your system does not have keyboard and mouse, you can use 'rngd' daemon to perform the task. You can see the entropy valu using following command.
#cat /proc/sys/kernel/random/entropy_availNow, start the 'rngd' daemon using following command and monitor the entropy on the system.
#rngd -r /dev/urandom -o /dev/random -f -t 1 #watch -n 1 cat /proc/sys/kernel/random/entropy_avail
What other fixes are available for this issue?
background
There is a known issue (on HP's side) with one component in the current version of Server Automation that takes a long time to startup due to a small entropy pool on RHEL 5. I'm trying to find a workaround until/unless it's fixed on the vendor's part.
I'm trying to get a list of patches contained in a Patch Policy in HPSA -- I can get what I need via the Twister web interface (under PatchPolicy.getPatches(), give it an ID, and it happily returns a list of patches contained.) -- I'm having a hard time getting this to work via the Pytwist interface, though... I haven't used the Pytwist interface for much besides some very basic Device manipulation, and Python is.. not my forte. I create the TwistServer object, then a PatchPolicy object from that (which I think is working..), but can't figure out how/where to call the getPatches() method from in Python-land.
If there's a way to dig this out of the database itself, that would work, too, but I can't seem to find much in there along these lines besides the vendor-recommended patching stuff, and we use custom policies.
Is there a known fix (other than upgrading from 5.1) to fix /etc/hosts from being replaced on reboot?
I discovered this behavior when running HP's Server Automation tools. HPSA sets-up a variety of local aliases for itself to use for different components to communicate wit each other.
However, after reboot, the hosts files is reverted to a quasi-plain-vanilla version: all lines above the entry for localhost are removed. Manually re-adding those needed lines below the entries for localhost works, but is non-ideal.
Is there a fix for this behavior?
I do realize that RHEL 5u1 is not officially supported for HPSA 7.8, but the hosts file resetting is not good for a variety of other reasons, too.
I am running HP Server Automation v7.8 in a lab environment on VMware ESXi, managed via vSphere 4.
On the same host I have several small VMs for OS provisioning testing (512MB RAM, 10GB hdd, one NIC on the same vSwitch that HPSA is running on).
DHCP is configured to hand-out addresses in the 192.168.10.151-200 range. On boot of the VM, it receives an IP (eg 192.168.10.198) within seconds.
However, after it receives its IP, a PXE-E11: ARP Timeout error occurs in trying to boot from the DHCP server.
I do not know if this is a HPSA-specific error, as I have seen reports of the PXE-E11 error on various forums. Proposed solutions I have seen so far (changing VLAN settings, for example) have not been applicable to my environment.
Are there any pointers/troubleshooting steps that can be taken to resolve this?