auto_parms.log messages older than rc.log startup

[Laurent Laperrousaz]

One of our system crashed today and rebooted ok.
When checking the logs, it appears that auto_parms.log mesags are timestamped before rhe startup message in rc.log.

Does it means that auto_parms is started before init?
and why such a difference: 10mn !! that's a long time...

Thanks

Laurent

here are the evidences:
mySystem:/etc# more rc.log
Old /etc/rc.log moved to /etc/rc.log.old

**************************************************
HP-UX Start-up in progress
Tue Oct 5 10:20:32 METDST 2004
**************************************************

Configure system crash dumps
Output from "/sbin/rc1.d/S080crashconf start":
----------------------------
EXIT CODE: 0

Update kernel and loadable modules
Output from "/sbin/rc1.d/S100kmbuild start":
----------------------------
"/sbin/rc1.d/S100kmbuild start" SKIPPED

Initialize loadable modules
Output from "/sbin/rc1.d/S100kminit start":
----------------------------
"/sbin/rc1.d/S100kminit start" SKIPPED

Mount file systems
Output from "/sbin/rc1.d/S100localmount start":
----------------------------
checking quotas

Setting hostname
Output from "/sbin/rc1.d/S320hostname start":

etc...

auto_parms.log:
more auto_parms.log
Oct 05 10:10:08: DHCP is disabled for: lan0

[Sridhar Bhaskarla]

Hi,

auto_parms script is run prior to rc scripts. So, auto_parms.log file will get created before rc.log.

rc.log will have the time stamp of the last activity. If any of the rc scripts take a long time to start (like database startup etc.,), then the time difference between rc.log and auto_parms.log can be long.

-Sri

[Laurent Laperrousaz]

the timestamp I mentionned is the one that appears in the first message of rc.log:
HP-UX Start-up in progress
Tue Oct 5 10:20:32 METDST 2004
while auto_parms.log last message is:
Oct 05 10:10:08: DHCP is disabled for: lan0
this is long!

[Marlou Everson]

Besides database startups, the clean_ex (recover editor crash files) can take 5 minutes and configuring software after a reboot by swinstall can add time too.

You can edit the /sbin/rc.utils file to add the date to each step.

Change the two lines in /sbin/rc.utils
from
echo "----------------------------" >> $LOGFILE
to
echo "----------------------------"$(date) >> $LOGFILE

Then after a reboot you can look at rc.log and see how long each step took. Naturally, you want to be very careful with the changes since it is used during booting. You also want to save the customization to a file (rc.utils.local) since a patch can change this file which means you get to edit it again!

Marlou

[Sridhar Bhaskarla]

Hi,

You are right. I would temporarily (if you want permanently) move /sbin/auto_parms as /sbin/auto_parms.old and then see if it was due to DHCP timeouts. Create a one liner script called auto_parms under /sbin directory with 'exit 0'. If the system comes up faster than it was before, then you would need to ensure that DHCP_ENABLE is set to 0 for all the interfaces in your netconf file. Also see if you have any information logged into /tmp/dhcpclient.log file.

-Sri