HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Boot up sequence - Tru64UNIX
Operating System - Tru64 Unix
1828670
Members
2145
Online
109984
Solutions
Forums
Categories
Company
Local Language
back
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
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-02-2010 02:34 AM
12-02-2010 02:34 AM
Boot up sequence - Tru64UNIX
Hi,
I have an Alpha system that hangs on booting up.
It gets to "Starting environmental monitoring systems", and hangs.
I have tried control C, but this has no effect.
I understand the boot up sequence is defined in the directory rc3.d, but how can I find out where it is hanging.
Thanks
Andrew
I have an Alpha system that hangs on booting up.
It gets to "Starting environmental monitoring systems", and hangs.
I have tried control C, but this has no effect.
I understand the boot up sequence is defined in the directory rc3.d, but how can I find out where it is hanging.
Thanks
Andrew
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2010 12:00 AM
12-03-2010 12:00 AM
Re: Boot up sequence - Tru64UNIX
"environmental monitoring systems" refers to the envmon daemon wich you can see as an extension to errorlogger (man envmon).
possibly some logfiles have grown too large.
rc3.d is used for the "normal" multiuser environment (with networking and other services).
=> you can try booting to single user mode
>>> b -fl s
if this works you can inspect the system.
- start checking filespace on the basic system partitions using "df".
- mount other filesystems configured in fstab "using "bcheckrc"
- check filespace on the now mounted /var and /user partitions if used.
you can rename the script that starts the envmon daemon (so its name doesnt begin with S) then it will be skipped at startup and then reboot the system normally.
== Or you can execute startups in phases
(init 1; init 2; init 3)
== or execute scripts in the rc.d directories one-by-one.
They all start with "S"
execute them in order of sequence number.
rc1.d/S00....
rc1.d/S01....
rc1.d/S02....
rc1.d/S03....
....
rc2.d/S00....
rc2.d/S01....
rc2.d/S02....
...
rc3.d/S00....
rc3.d/S01....
rc3.d/S02....
...
possibly some logfiles have grown too large.
rc3.d is used for the "normal" multiuser environment (with networking and other services).
=> you can try booting to single user mode
>>> b -fl s
if this works you can inspect the system.
- start checking filespace on the basic system partitions using "df".
- mount other filesystems configured in fstab "using "bcheckrc"
- check filespace on the now mounted /var and /user partitions if used.
you can rename the script that starts the envmon daemon (so its name doesnt begin with S
== Or you can execute startups in phases
(init 1; init 2; init 3)
== or execute scripts in the rc
They all start with "S
execute them in order of sequence number.
rc1.d/S00....
rc1.d/S01....
rc1.d/S02....
rc1.d/S03....
....
rc2.d/S00....
rc2.d/S01....
rc2.d/S02....
...
rc3.d/S00....
rc3.d/S01....
rc3.d/S02....
...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2010 02:40 AM
12-03-2010 02:40 AM
Re: Boot up sequence - Tru64UNIX
Thanks you for your response.
We have now discovered that since we changed the IP interface name and address the startup of the "Environmental monitoring services" just hangs. I cannot even interrupt it with a CTRL/C.
I believe it is trying to poll the old IP interface name.
If I do not start the "Enviromental Monitoring services" ( I removed the startup script S55envmon from rc3.d) the system comes up correctly.
I have not had time to investigate where it still looks for the old IP interface name.
THanks
Andrew
We have now discovered that since we changed the IP interface name and address the startup of the "Environmental monitoring services" just hangs. I cannot even interrupt it with a CTRL/C.
I believe it is trying to poll the old IP interface name.
If I do not start the "Enviromental Monitoring services" ( I removed the startup script S55envmon from rc3.d) the system comes up correctly.
I have not had time to investigate where it still looks for the old IP interface name.
THanks
Andrew
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2010 09:37 PM
12-15-2010 09:37 PM
Re: Boot up sequence - Tru64UNIX
"Starting environmental monitoring systems"
After all these years would it not be a good idea to change this message, slightly and give some warnings, in the case it hangs....
Its not like it happens often.
Never seen it before.
After all these years would it not be a good idea to change this message, slightly and give some warnings, in the case it hangs....
Its not like it happens often.
Never seen it before.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP