- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Who is cluttering /var/tmp with char dev files rds...
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
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
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
тАО08-09-2007 12:20 AM
тАО08-09-2007 12:20 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
I now added this line to the disabled_instances, and hope this will keep the agents from playing with the dvd drive.
# tail -1 /var/stm/data/tools/monitor/disabled_instances
/storage/events/disks/default/0_0_1_0.1.0
Must the diagnostic stuff be restarted?
Probably won't hurt anyway...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 12:26 AM
тАО08-09-2007 12:26 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
I'm not completely convinced this will work... se the following entry in the disabled_instances file:
# NOTE: entries in this file do NOT cause a monitor to stop polling an
# instance or stop the PSM monitor from marking an instance as DOWN, it
# just stops the notification of events based on entries in the *.sapcfg
# files for this instance.
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 12:39 AM
тАО08-09-2007 12:39 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
Have been a bit too hasty.
The diagmond seemed unimpressed by my futile disabling attempt anyway,
and keeps merrily churning out further devices
# ll /var/tmp/rdsk*|grep -c 0x001000
20
So what else could I do?
Pull the DVD drive from its slot seems a bit too drastic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 12:49 AM
тАО08-09-2007 12:49 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
for some advice in this matter.
This thread's subject has long been answered.
And so I should not delay the promotion of Duncan on his way to Olympia any longer.
Many thanks for your patience and help to all!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 12:55 AM
тАО08-09-2007 12:55 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
Does diskinfo work OK for the DVD-ROM device?
diskinfo /dev/rdsk/c0t1d0
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 01:03 AM
тАО08-09-2007 01:03 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
# diskinfo /dev/rdsk/c0t1d0
SCSI describe of /dev/rdsk/c0t1d0:
vendor: HP
product id: DVD-ROM 305
type: CD-ROM
size: 3442336 Kbytes
bytes per sector: 2048
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 01:06 AM
тАО08-09-2007 01:06 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
# mount -r /dev/dsk/c0t1d0 /cdrom
# bdf /cdrom
Filesystem kbytes used avail %used Mounted on
/dev/dsk/c0t1d0 3442336 3442336 0 100% /cdrom
Must be some application SW DVD
# head /cdrom/DVD_TABLE_OF_CONTENTS
HP9000 Series 9000/IA
HP-UX Application Software
DVD Part Number - 5013-4959
1 of 1 DVDs
DVD CONTENT LIST
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 01:58 AM
тАО08-09-2007 01:58 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
I think this process is supposed to report back to STM in the local map log.
Does:
echo lml | cstm
turn up anything intersting?
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 06:36 PM
тАО08-09-2007 06:36 PM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
sorry for the belated reply.
I must had left office already yesterday when your last posting was submitted.
I had a look at the localmaplog in cstm.
Among other messages especially these two appear repeatedly which refer to the DVD drive I suppose:
Thu Aug 9 14:25:19 2007: Tool completed with exit_status PROD_NOT_SUPPORTED
(3) indicating the tool exited because the product
identifier is not supported by this tool.
Thu Aug 9 14:25:20 2007: Identify routine (scsi_arry) for hardware at path
(0/0/1/0.1) indicated hardware path is not supported.
A subsequent identify routine should support the
hardware.
Thu Aug 9 14:25:20 2007: Hardware at path (0/0/1/0.1) and driver name (tgt) is
being ignored as entry in id_mod_xref file indicated
it should be ignored. This hardware will not appear
in the map.
But as similar messages apear for other HW paths as well, I am not quite sure if this is evidence enough for some abnormality?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 11:36 PM
тАО08-09-2007 11:36 PM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
I filed an SW case with HP Support
and was instantly supplied with a howto that seems to have fixed this (I still have to observe for a longer period, say until Monday).
This Howto lists the steps necessary how EMS can be restarted thoroughly, meaning by removing of certain files that require EMS to regenerate a new set of config and state files.
I am not sure if I am allowed to cite the procedure here?
Maybe you will even find it in the knowledge base?
I will have to ask the support engineer next week.
Have a nice weekend guys
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-10-2007 12:14 AM
тАО08-10-2007 12:14 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
I have nothing to contribute to the EMS dialog, but wanted to add a "thanks" for the Perl "digression" as you called it. I'd hardly call you a rookie as you applied the moniker to yourself! I agreed with your comments surrounding the code and also wonder about the quality of the binaries that we can't see if indeed the Perl is representative!
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2007 09:23 PM
тАО08-15-2007 09:23 PM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
sorry, for the late response.
This piece of Oracle Perl code is even worse than I thought at first sight.
Well, it does compile if you leave off the strict pragma
# perl -c -Mwarnings -Mlib=/app/oracle/grid/agent10g/bin /app/oracle/grid/agent10g/bin/emwd.pl <
Unquoted string "cp" may clash with future reserved word at /app/oracle/grid/agent10g/bin/emwd.pl line 187.
main::printDebugMessage() called too early to check prototype at /app/oracle/grid/agent10g/bin/emwd.pl line 223.
main::printDebugMessage() called too early to check prototype at /app/oracle/grid/agent10g/bin/emwd.pl line 245.
Name "main::CONSOLE_START_TIME" used only once: possible typo at /app/oracle/grid/agent10g/bin/emwd.pl line 207.
Name "main::AGENT_START_TIME" used only once: possible typo at /app/oracle/grid/agent10g/bin/emwd.pl line 208.
/app/oracle/grid/agent10g/bin/emwd.pl syntax OK
But it terribly fails when put under strict.
Such code is unmaintainable and should be indented six feet under and covered with dirt (to take up a quote from Damian Conway's "Perl Best Practices").
Even the real masters never get tired of emphasing the great relief strict introduces for even the seemingly most trivial of scripts to save the programmer's sanity.
For distributed code which needs to be maintained this failing to compile is unforgivable.
# perl -cw -Mstrict -Mlib=/app/oracle/grid/agent10g/bin /app/oracle/grid/agent10g/bin/emwd.pl
Useless use of a variable in void context at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 121.
Useless use of a variable in void context at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 129.
Useless use of a variable in void context at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 130.
Use of uninitialized value in concatenation (.) or string at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 136.
Use of uninitialized value in string eq at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 178.
Use of uninitialized value in string eq at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 178.
Use of uninitialized value in string eq at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 178.
Use of uninitialized value in string eq at /app/oracle/grid/agent10g/bin/EmctlCommon.pm line 178.
Scalar value @_[0] better written as $_[0] at /app/oracle/grid/agent10g/bin/EMAgent.pm line 573.
Scalar value @lines[$deleteCount-1] better written as $lines[$deleteCount-1] at /app/oracle/grid/agent10g/bin/EMAgent.pm line 614.
Bareword found in conditional at /app/oracle/grid/agent10g/bin/nfsPatchPlugin.pm line 101.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 386.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 392.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 392.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 429.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 434.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 451.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 455.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 467.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 481.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 482.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 489.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 492.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 495.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 495.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 497.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 524.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 524.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 526.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 536.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 549.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 556.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 559.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 562.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 563.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 563.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 570.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 573.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 601.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 611.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 617.
Variable "@processExit" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 831.
Variable "$signal" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 962.
(Did you mean &signal instead?)
Variable "$signal" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 963.
(Did you mean &signal instead?)
Variable "$signal" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 977.
(Did you mean &signal instead?)
Variable "$signal" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 981.
(Did you mean &signal instead?)
Variable "$signal" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 986.
(Did you mean &signal instead?)
Variable "@comps" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 1013.
Variable "@comps" is not imported at /app/oracle/grid/agent10g/bin/emwd.pl line 1024.
main::printDebugMessage() called too early to check prototype at /app/oracle/grid/agent10g/bin/emwd.pl line 223.
main::printDebugMessage() called too early to check prototype at /app/oracle/grid/agent10g/bin/emwd.pl line 245.
Bareword "cp" not allowed while "strict subs" in use at /app/oracle/grid/agent10g/bin/emwd.pl line 187.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 202.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 203.
Global symbol "$PROCESS_EXIT_SIGNAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 204.
Global symbol "$PROCESS_DUMPED_CORE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 205.
Global symbol "$CONSOLE_START_TIME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 207.
Global symbol "$AGENT_START_TIME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 208.
Global symbol "$EMWD_MONITOR_WAIT_TIME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 210.
Global symbol "$EMWD_PROCESS_CHECK_FACTOR" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 211.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 220.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 221.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 223.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 225.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 228.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 232.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 236.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 240.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 243.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 245.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 247.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 247.
Global symbol "$component" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 255.
Global symbol "$moduleName" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 256.
Global symbol "$component" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 256.
Global symbol "$reqPkg" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 257.
Global symbol "$moduleName" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 257.
Global symbol "$reqPkg" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 258.
Global symbol "$obj" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 260.
Global symbol "$moduleName" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 260.
Global symbol "$refComponents" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 262.
Global symbol "$obj" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 262.
Global symbol "$exitCode" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 263.
Global symbol "$refComponents" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 263.
Global symbol "$exitCode" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 274.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 326.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 328.
Global symbol "$EMWD_MONITOR_WAIT_TIME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 336.
Global symbol "$EMWD_PROCESS_CHECK_FACTOR" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 336.
Global symbol "$EMWD_PROCESS_CHECK_FACTOR" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 338.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 355.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 355.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 355.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 355.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 355.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 360.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 373.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 386.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 386.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 392.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 392.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 429.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 429.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 434.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 434.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 451.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 451.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 455.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 455.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 467.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 467.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 472.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 481.
Global symbol "$PROCESS_EXIT_SIGNAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 481.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 482.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 489.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 489.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 492.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 495.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 495.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 497.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 508.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 524.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 524.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 526.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 533.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 536.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 549.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 556.
Global symbol "$PROCESS_EXIT_SIGNAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 556.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 559.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 562.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 563.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 563.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 570.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 573.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 585.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 601.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 601.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 605.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 611.
Global symbol "$PROCESS_DUMPED_CORE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 611.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 617.
Global symbol "$message" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 668.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 669.
Global symbol "$message" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 670.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 677.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 701.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 704.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 711.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 732.
Global symbol "$i" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 736.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 776.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 782.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 785.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 786.
Global symbol "$EMHOME" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 799.
Global symbol "@processExit" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 831.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 831.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 880.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 880.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 894.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 894.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 905.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 915.
Global symbol "$PROCESS_EXIT_SIGNAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 919.
Global symbol "$PROCESS_DUMPED_CORE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 924.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 929.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 950.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 954.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 954.
Global symbol "$PROCESS_EXIT_NORMAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 958.
Global symbol "$signal" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 962.
Global symbol "$PROCESS_EXIT_SIGNAL" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 963.
Global symbol "$signal" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 963.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 970.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 970.
Global symbol "$signal" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 977.
Global symbol "$PROCESS_DUMPED_CORE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 981.
Global symbol "$signal" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 981.
Global symbol "$PROCESS_OK" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 986.
Global symbol "$signal" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 986.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1005.
Global symbol "$numComponents" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1005.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1005.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1007.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1007.
Global symbol "$baseCtr" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1008.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1008.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1009.
Global symbol "$numComponents" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1009.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1013.
Global symbol "@comps" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1013.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1015.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1018.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1019.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1024.
Global symbol "@comps" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1024.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1026.
Global symbol "$objRef" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1029.
Global symbol "$numCols" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1030.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1049.
Global symbol "$NOHUP_FILE" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1052.
Global symbol "$buf" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1055.
Global symbol "$buf" requires explicit package name at /app/oracle/grid/agent10g/bin/emwd.pl line 1056.
/app/oracle/grid/agent10g/bin/emwd.pl had compilation errors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2007 04:26 AM
тАО08-23-2007 04:26 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
Did you get an answer to this problem? Which version of OnlineDiags do you have installed? (Running 'cstm' shows this.)
disk_em used to create these files for EVA type devices, but that was a year or more ago, current versions should not be showing this problem. AM60Srvr has also been seen to do something very similar, but again the current version should not.
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2007 10:13 PM
тАО08-23-2007 10:13 PM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
yes I did get an answer (as I wrote, but probably too distractingly long a thread)
by a Support Engineer colleague of yours.
I don't know if I may name her without having asked for her approval?
From the solution I was provided I fabricated a script which I called emsflush.sh that you may find attached.
It's more of a proposal because I haven't tested it fully for publication and it still may contain some bugs or be downright appalling
or even havoc wreaking.
You have been warned.
At least it worked fine for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2007 10:23 PM
тАО08-23-2007 10:23 PM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
$ /usr/sbin/swlist -l bundle OnlineDiag|tail -2
OnlineDiag B.11.11.19.01 HPUX 11.11 Support Tools Bundle, June 2007
$ echo version|/usr/sbin/cstm
Running Command File (/usr/sbin/stm/ui/config/.stmrc).
-- Information --
Support Tools Manager
Version A.57.00
Product Number B4708AA
(C) Copyright Hewlett Packard Co. 1995-2007
All Rights Reserved
Use of this program is subject to the licensing restrictions described
in "Help-->On Version". HP shall not be liable for any damages resulting
from misuse or unauthorized use of this program.
cstm>version
Support Tools Manager
Version A.57.00
Product Number B4708AA
(C) Copyright Hewlett Packard Co. 1995-2007
All Rights Reserved
Use of the individual support tools provided by this program is subject to the
licensing restrictions for each tool described by the "Tools-->toolname-->Info"
command. HP shall not be liable for any damage resulting from misuse or
unauthorized use of these tools.cstm>#.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2007 01:11 AM
тАО08-24-2007 01:11 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
Thanks for the update; I'll have a look at the script when I've got time and see if I learn anything from it.
The problem shouldn't be happening with A.57.00, but it obviously is. If running the script hasn't fixed it for good, can you ask HP support to elevate the issue when you go back to them?
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2007 01:21 AM
тАО08-24-2007 01:21 AM
Re: Who is cluttering /var/tmp with char dev files rdskAAA* ?
which last took place on the 13th of Aug,
seems to have fixed this.
Since that last EMS monitors' restart no new device files appeared apart from these:
# UNIX95= ps -C disk_em -o stime,args
STIME COMMAND
Aug 13 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
# find /var/tmp -xdev -type c -name rdskAAA\* -exec ll {} +
crw------- 1 root root 203 0x001000 Aug 13 15:51 /var/tmp/rdskAAAa29848
crw------- 1 root root 203 0x001000 Aug 13 15:51 /var/tmp/rdskAAAa29973
- « Previous
-
- 1
- 2
- Next »