- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: list_expander command 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
- 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
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
03-16-2009 06:04 AM
03-16-2009 06:04 AM
ERROR: The list_expander command failed. This could be due to a problem with the -x options specified - Check the existence of the included device(s).
03/16/09 14:44:23 MET make_net_recovery completed unsuccessfull
When I run list_expander I get this output:
n12904/:%~> /opt/ignite/lbin/list_expander
WARNING: The /dev/null file is not a character device file.
WARNING: The /dev/null file is not a character device file.
ERROR: 'all not': type 'all' not recognized.
What does it mean? How can solve the issue?
Ignite ver. C.7.4.157 on hp-ux 11.23
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2009 06:09 AM
03-16-2009 06:09 AM
Re: list_expander command failed
Can you provide the full command syntax you have given?
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2009 06:29 AM
03-16-2009 06:29 AM
Re: list_expander command failed
and
/opt/ignite/lbin/list_expander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2009 06:36 AM
03-16-2009 06:36 AM
SolutionThe /dev/null file is not a character device file.
Might be a real message.
file /dev/null
Post output.
An Ignite upgrade might help. I would decide that after confirming the message is not accurate.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2009 07:35 AM
03-16-2009 07:35 AM
Re: list_expander command failed
Solved with rm /dev/null ; mknod c 3 2 /dev/null ; chmod go+w /dev/null
Now it's character file again and ignite is running fine. Thanks!
file /dev/null
/dev/null: character special (3/2)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2009 06:15 PM
03-16-2009 06:15 PM
Re: list_expander command failed
This is a fairly common root user problem. Only root can remove files in the /dev directory and once it is removed, the /dev/ directory may grow extremely large as data sent to /dev/null turns into a real file. The list_expander is particularly good at finding problem files and filenames.
> ERROR: 'all not': type 'all' not recognized.
This is probably a file that was created with a space in the name. You can find it by enclosing the name with double ", but if it does not show up, there may be some control characters imbedded in the file name. You can use the ll -b option to show special characters in filenames.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2009 03:54 AM
03-17-2009 03:54 AM