- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- what is vmunix: DM_ENGINE_BO: PN_GET failed
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 07:20 AM
07-31-2004 07:20 AM
And idea where are those error messages coming from? I keep seeing them in my syslog.log. I am running HP11i.
Thanks
------------------------------------------
Jul 26 18:58:09 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 26 18:58:09 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Jul 26 19:00:24 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 26 19:00:24 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Jul 30 07:02:42 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 30 07:02:42 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Jul 30 07:02:48 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 30 07:02:48 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Jul 30 12:57:43 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 30 12:57:43 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Jul 30 12:59:29 websvr vmunix: chown_pre: resolve_path failed:
Jul 30 12:59:33 websvr vmunix: engine_env_pre: pn_resolve failed.
Jul 30 12:59:34 websvr vmunix: chown_pre: resolve_path failed:
Jul 30 12:59:33 websvr vmunix: DM_ENGINE_BO: PN_GET failed
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 07:45 AM
07-31-2004 07:45 AM
Re: what is vmunix: DM_ENGINE_BO: PN_GET failed
If I had to guess, some application is trying to resolve a pathname component (pn_resolve) and failing. Also, the fact that a chown(1) command is failing with "resolve_path failed" tells me that some application is trying to resolve a pathname component for a file/directory and failing.
What 3rd party applications are running on this system? Any "ps -ef" output returning a program called "engine" or "dm"?
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 10:20 AM
07-31-2004 10:20 AM
Re: what is vmunix: DM_ENGINE_BO: PN_GET failed
I did a search of dm or pn but the closest one that I got is:
/usr/dmi/bin/dmisp
/var/dmi/bin/hpuxci
/var/dmi/bin/swci
/usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
/usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
/usr/sbin/stm/uut/bin/tools/monitor/dm_stape
/usr/sbin/stm/uut/bin/tools/monitor/dm_memory
I have also attahed the entire output of ps -ef just in case.
%ps -ef
UID PID PPID C STIME TTY TIME COMMAND
root 0 0 0 19:55:55 ? 0:07 swapper
root 8 0 0 19:55:55 ? 0:00 supsched
root 9 0 0 19:55:55 ? 0:00 strmem
root 10 0 0 19:55:55 ? 0:00 strweld
root 11 0 0 19:55:55 ? 0:00 strfreebd
root 2 0 0 19:55:55 ? 0:00 vhand
root 3 0 0 19:55:55 ? 0:21 statdaemon
root 4 0 0 19:55:55 ? 0:01 unhashdaemon
root 12 0 0 19:55:55 ? 0:00 ttisr
root 13 0 0 19:55:55 ? 0:00 ioconfigd
root 1 0 0 19:55:55 ? 0:00 init
root 19 0 0 19:55:55 ? 0:00 lvmkd
root 20 0 0 19:55:55 ? 0:00 lvmkd
root 21 0 0 19:55:55 ? 0:00 lvmkd
root 22 0 0 19:55:55 ? 0:00 lvmkd
root 23 0 0 19:55:55 ? 0:00 lvmkd
root 24 0 0 19:55:55 ? 0:00 lvmkd
root 25 0 0 19:55:55 ? 0:00 lvmschedd
root 26 0 0 19:55:55 ? 0:00 smpsched
root 27 0 0 19:55:55 ? 0:00 smpsched
root 28 0 0 19:55:55 ? 0:00 smpsched
root 29 0 0 19:55:55 ? 0:00 smpsched
root 30 0 0 19:55:55 ? 0:00 sblksched
root 31 0 0 19:55:55 ? 0:00 sblksched
root 808 1 0 19:56:44 ? 0:00 /usr/sbin/rpc.lockd
root 37 0 0 19:55:56 ? 1:06 vxfsd
root 515 1 0 19:56:23 ? 0:00 /usr/sbin/syslogd -D
root 496 1 0 19:56:22 ? 0:02 ipmon -sD
root 518 1 0 19:56:23 ? 0:00 /usr/sbin/ptydaemon
root 394 1 0 19:56:18 ? 0:01 /usr/sbin/syncer
root 755 1 0 19:56:43 ? 0:00 /usr/sbin/rpcbind
root 779 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 735 1 0 19:56:43 ? 0:00 /opt/ssh/sbin/sshd
root 760 0 0 19:56:43 ? 0:00 nfskd
root 780 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 781 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 782 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 783 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 784 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 785 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 786 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 787 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 788 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 789 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 790 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 791 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 792 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 793 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 794 1 0 19:56:43 ? 0:00 /usr/sbin/biod 16
root 834 1 0 19:56:45 ? 0:05 /usr/sbin/inetd
root 802 1 0 19:56:44 ? 0:00 /usr/sbin/rpc.statd
root 1691 1 0 19:57:46 ? 0:02 cclogd
root 1106 1 0 19:56:47 ? 0:15 sendmail: accepting connections on port 25
root 1151 1 0 19:56:48 ? 0:00 /usr/sbin/fddi4subagt
root 1179 1 0 19:56:53 ? 0:02 /usr/dmi/bin/dmisp
root 1250 1 0 19:56:59 ? 0:02 /usr/sbin/xntpd
root 1165 1 0 19:56:48 ? 0:02 /opt/dce/sbin/rpcd
root 1188 1 0 19:56:58 ? 0:00 /var/dmi/bin/hpuxci
root 1260 1 0 19:56:59 ? 0:03 /usr/sbin/pwgrd
root 1203 1 0 19:56:59 ? 0:00 /var/dmi/bin/swci
root 1215 1 0 19:56:59 ? 0:01 scrdaemon
root 1235 1 0 19:56:59 ? 0:00 /usr/sbin/rbootd
root 1305 1 0 19:57:04 ? 0:00 /usr/sbin/envd
root 1323 1 0 19:57:04 ? 0:00 /usr/sbin/swagentd -r
root 1693 1 0 19:57:46 ? 0:00 memlogd
root 1276 1 0 19:57:00 ? 0:00 /usr/sbin/cron
root 1692 1 0 19:57:46 ? 0:00 diaglogd
root 1491 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1694 1 0 19:57:46 ? 0:17 psmctd
root 1336 1 0 19:57:05 ? 0:05 /usr/contrib/sbin/prngd /var/run/egd-pool
root 2197 1 0 19:58:38 ? 0:11 /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em
root 1612 834 0 19:57:24 ? 0:01 bootpd
root 1749 1 0 19:58:18 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
root 1700 834 0 19:57:47 ? 0:00 /etc/opt/resmon/lbin/registrar
root 1352 1 0 19:57:05 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 1529 1 0 19:57:11 ? 0:00 /sbin/krsd -i
root 1369 1 0 19:57:05 ? 0:00 /usr/local/bin/rsync --daemon --config=/usr/local/etc/rsyncd.co
root 1487 1 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
patrol 2902 2825 0 20:00:02 ? 1:59 /opt/patrol/PATROL3.5/HPUX-V11-64/lib/psl/HPUX-V11-64/INETClien
root 1420 1 0 19:57:07 ? 0:02 /opt/VRTSob/bin/vxsvc -r /etc/vx/isis/Registry
root 1526 1 0 19:57:11 ? 0:00 /sbin/sh /usr/dt/bin/dtrc
root 1489 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 3822 1 0 20:13:51 ? 0:00 ./uxwdog -d /home/iplanet/servers/https-admserv/config
root 1471 1 0 19:57:08 ? 0:00 /usr/sbin/rpc.mountd
root 1490 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1486 1 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1492 1490 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1493 1491 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1494 1490 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1495 1491 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1531 1 0 19:57:11 ? 0:00 /usr/sam/lbin/samd
root 1497 1490 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1530 1 0 19:57:11 ? 0:00 /sbin/sfd
root 1540 1 0 19:57:11 ? 0:01 /etc/opt/resmon/lbin/p_client
root 1500 1491 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1501 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1502 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1503 1487 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1513 1489 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1514 1489 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 1515 1489 0 19:57:08 ? 0:00 /usr/sbin/nfsd 16
root 2236 1 0 19:58:39 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em
root 1577 1526 0 19:57:14 ? 0:00 /usr/dt/bin/dtlogin
root 5927 0 0 23:53:41 ? 0:00 nfsktcpd
root 1839 1 0 19:58:20 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
patrol 3245 2974 0 20:01:21 ? 0:52 bgscollect -I noInstance -M /opt/patrol/PATROL3.5//HPUX-11-11-6
root 1866 1 0 19:58:20 ? 0:04 /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
patrol 2974 2825 0 20:00:25 ? 0:31 /opt/patrol/PATROL3.5//HPUX-11-11-64/best1/bgs/bin/dcm -f /opt/
patrol 2971 2825 0 20:00:19 ? 0:00 /opt/patrol/PATROL3.5/unix/HPUX-V11-64/bin/logd
root 2145 1 0 19:58:22 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
root 2060 1 0 19:58:21 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
patrol 2825 1 2 19:59:55 ? 5:23 PatrolAgent -p 3181
$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2004 11:11 AM
07-31-2004 11:11 AM
SolutionThese could be from the stm tools, but if that were the case I would have thought one of the printfs would have shown up in my source code search.
I hate to say this, but unless someone else recognizes these messages (I didn't see them in google, news, groups, etc.) you might be down to a process of elimination - i.e. stop an application and see if the logging messages continue.
Since I cannot find a reference to these messages in the HP-UX knowledge databases, I'm guessing they are generated by a 3rd party tool, so you might want to begin with some of those, like:
patrol3.5
/usr/contrib/sbin/prngd /var/run/egd-pool
uxwdog
etc.
Good luck, and if you are able to identify the application generating these messages I'd be curious to know which one it was.
Regards,
Dave
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2004 10:22 AM
08-05-2004 10:22 AM
Re: what is vmunix: DM_ENGINE_BO: PN_GET failed
Thanks for your info. It was from a NAI product called Entercept. I disabled it and those error messages disappeared.
Thanks a lot for your help.