- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Not able to execute commands......
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
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
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
02-19-2010 03:51 AM
02-19-2010 03:51 AM
I am having HP-UX B.11.00 U PA-RISC system,
I am facing following issues,
(1)Not able to execute # vgdisplay , #ioscan …. I have also tried with giving its entire path “ /usr/sbin “ but not giving any o/p…..But I can execute #bdf cmd
(2) when I am trying to execute # /usr/sbin/sam it giving me following msg
(a) Superuser(root) does not belong to group "sys". Proceeding with SAM │
│ when superuser(root) does not belong to group "sys" will result in │
│ files and directories getting created with a wrong group ID. Do you │
│ want to change the group to "sys" and continue?
(b) If I continue . then ….
Superuser's(root) group successfully changed from group "users" with │
│ GID "20" to group "sys" with GID "3"
(c) Giving me error
The command, pd_ioparser, has failed while trying to retrieve
information about the device class, CTL. The stderr output from the
command was:-------
(3) This is o/p of my passwd file
root:pWLMcyBm77Gyk:0:3::/:/sbin/sh
and /etc/group is
root::0:root
sys::3:root,uucp
(4) I have installed the sudo-1.7.2 utility from http://www.gratisoft.us/sudo/install.html
I went to source dir , ran ./configure script and then “ make install … I can see visudo and sudoers file but it is not showing in /var/adm/sw/product database …
Please let me know , can we correlate this issue with sudo installation and if yes how I can remove it as I am not able to execute #swremove
Thank in advance!!!!
Regards,
Subodh.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 04:10 AM
02-19-2010 04:10 AM
Re: Not able to execute commands......
See if you can (as root) run:
# swverify \*
This will take some time but will read the IPD ('/var/adm/sw') database and match the expected permisssions, ownerships and modification times of its objects with the actual files and directories.
I'm not sure that your 'sudo' package even uses the standard SD tools for installation. If not, then nothing would be viewable in a 'swlist'.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 04:30 AM
02-19-2010 04:30 AM
Re: Not able to execute commands......
I have tried #swverify as you mentioned,
But still not able to execute the vgdisplay, ioscan with its complete path and even from sam it is not listing vg, lv , fs. it is giving error as mentioned in my previous text....through sam
i can see the group, user etc...
Regards,
Subodh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 04:38 AM
02-19-2010 04:38 AM
Re: Not able to execute commands......
> I have tried #swverify as you mentioned,
But you don't say what if any errors you saw.
If there are errors you can try to fix them thusly:
# swverify -F \*
Too, do your LVM files have non-zero sizes or have they been corrupted? Do you have any filesystems that are full?
By the way, login directly as 'root' and perform the above.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 04:53 AM
02-19-2010 04:53 AM
Re: Not able to execute commands......
Can you please post the output for this command:
set
Horia.
Horia.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 06:13 AM
02-19-2010 06:13 AM
Re: Not able to execute commands......
Please find attached o/p of set and swverify..
(1)some of the error of swverify are
ERROR: 110 of 2161 filesets had Errors.
WARNING: 40 of 2161 filesets had Warnings.
* 2011 of 2161 filesets had no Errors or Warnings.
ERROR: The Analysis Phase had errors and warnings. See the above
output for details.
======= 02/19/10 18:24:49 IST END verify
(2)ERROR: File "/sbin/reboot" should have mtime "893841302" but the
actual mtime is "1266504135".
ERROR: File "/sbin/reboot" should have size "192512" bytes but the
actual size is "0" bytes.
ERROR: Fileset "PHCO_14777.UX-CORE,l=/,r=1.0" had file errors.
ERROR: File "/usr/sbin/getx25" should have mtime "877939200" but the
actual mtime is "1266504134".
ERROR: File "/usr/sbin/getx25" should have size "20480" bytes but the
actual size is "0" bytes.
ERROR: File "/usr/sbin/uucpd" should have mtime "877939200" but the
actual mtime is "1266504136".
ERROR: File "/usr/sbin/uucpd" should have size "20480" bytes but the
actual size is "0" bytes.
Regards,
Subodh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 06:17 AM
02-19-2010 06:17 AM
Re: Not able to execute commands......
The short excerpt you just posted indicates files that have been truncated to a 0 byte size.
You need to closely look at the swverify output and if there are lots of files that are of '0' size, then you may need to restore your system from a recent Ignite/UX backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 06:19 AM
02-19-2010 06:19 AM
Re: Not able to execute commands......
> ERROR: File "/sbin/reboot" should have size "192512" bytes but the
actual size is "0" bytes.
This error (and others like it) is very bad. Without even opening your attached (non-text) file, I suspect that the sizes of your LVM executables are probably zero too. You should verify that with a simple 'ls /sbin/vg*' for example.
I suspect that some very catastrophic damage has been done.
I hope you have an Ignite recovery tape. Deploying that might be the fastest recovery method.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 06:58 AM
02-19-2010 06:58 AM
Re: Not able to execute commands......
I don't have ignite backup with me...
Is there any other solution like any patches (lvm, Co) which can fix this rather than going for cold installation,
Command patches like
PHCO_19479 1.0 LVM commands cumulative patch
PHCO_27369 1.0 LVM commands (VA7410 HWE) cumulative patch
PHCO_33244 1.0 LVM commands cumulative patch
Regards,
Subodh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2010 07:08 AM
02-19-2010 07:08 AM
Re: Not able to execute commands......
> I don't have ignite backup with me...
But the real question is, do you even have one?
> Is there any other solution like any patches (lvm, Co) which can fix this rather than going for cold installation,
In the absence of an Ignite backup, if the damage is as widespread as it appears to be, a cold-install might be the faster route to a viable system. To try to reapply various products (base file sets) and their patches would probably be more time-consuming. You may then be struggling with problems for months.
Regards!
...JRF...