PHP and System Management Homepage

[T-h-i-j-s]

There's a problem with HP SMH when running on a Windows system with a system-wide PHP installation (eg for IIS). As soon as the PHPRC environment variabele or the PHP registry entry is set, de HP SMH doesn't work anymore, because the PHP module of SMH tries to load te wrong php.ini (because no explicit path is set). The solution is to add the proper path in smhpd.conf (e.g.: PHPIniDir "C:/hp/hpsmh/bin")

Problem is that the contents of that file are hard-coded in smhstart.exe

I managed to fix it with a workaround (don't use smhstart.exe, but call hpsmhd.exe with the proper switches), but it would be useful if this could be fixed in a proper way.

[Scott Klassen]

Could you possibly provide me with more details on getting the SMH PHP (version4 I believe) to work properly with a system-wide PHP install (PHP5 in my case)?

I'm having a heck of a time when they are both loaded at bootup. The extension modules for PHP5 try to load with the SMH php giving me a popup error for each one.

Any help would be appreciated. Thanks.

[T-h-i-j-s]

Sure:

1. Stop the System Management Homepage Service.

2. copy the smhpd.conf (C:\hp\hpsmh\conf\smhpd.conf) to httpd.conf (C:\hp\hpsmh\conf\httpd.conf)

3. Edit httpd.conf, add:

PHPIniDir "C:/hp/hpsmh/bin"

(adjust path if needed)

4. Adjust the System Management Homepage Service using regedit:

change the 'command' ([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysMgmtHp]
"ImagePath") to: "C:\hp\hpsmh\bin\hpsmhd.exe" -k runservice

5. Start the System Management Homepage Service.


check hpsmhd.exe /?
for more commandline options. It looks for httpd.conf by default, so you don't *have* to specify it.

You might have to take care of rotating the logfiles; i haven't looked into that yet.

[Scott Klassen]

Sorry to bother you again. This mostly fixed my problem. On reboot, I got a couple of failed services with the following messages in the log:

Event Type: Error
Event Source: cpqvcagent
Event Category: Service
Event ID: 608
Date: 4/6/2006
Time: 9:37:52 PM
User: N/A
Computer: machine1
Description:
The service cannot start because one or more OpenSSL libraries are missing on this system. "C:\hp\hpsmh\bin\ssleay32.dll "C:\hp\hpsmh\bin\libeay32.dll


Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date: 4/6/2006
Time: 9:37:56 PM
User: N/A
Computer: machine1
Description:
The Apache service named reported the following error:
>>> [Thu Apr 06 21:37:56 2006] [warn] (OS 2)The system cannot find the file specified. : No installed ConfigArgs for the service "HP System Management Homepage", using Apache defaults. .

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The dll is definately in that path.
Should the imagepath in the registry ("C:\hp\hpsmh\bin\hpsmhd.exe" -k runservice)be in quotes? Any other advise would be great. Thanks.

[MTardiff]

Does anyone know if this problem still exists in support pack 7.50? We're currently running 7.40B and it's preventing us from running the SMH on all of our IIS servers.

[Matthew Pinkston]

I find it rather disturbing that HP would create an executable to start the service that in effect locks down files from being modified. Not only, do they make their install non-standard, they make it unmanageable to a system administrator (their customer). And of course you can't just modify the .exe meant to start the service without having a doctorate in reverse engineering.

And here we are 2 years later, and as far as I can tell the issue has not been addressed and still persists in their product. If this is not the case, I apologize.

That out of the way, I had the same exact problem as the original poster, and am now up and running without any php conflict. I would urge HP to allow purchasers of their product to have the capability of modifying the .conf file, without having to hack their services.

-Matt P.

[Rich Purvis]

While I have not encountered this issue, it is my understanding that it was corrected in one of the releases this past year. You might try the latest release, as of yesterday 2.1.12, on one of your systems to see if it behaves properly without the work around.

-Rich