Errors booting into multiuser mode

[dictum9]

this is Itanium rx2620 running 11.23

I get these errors in /etc/rc.log, what do they mean?
I just installed patches (ran swainv to get inventory.xml file to upload), could this have something to do with booting problems?



/sbin/rc[67]: Syntax error at line 166 : `"' is not matched.
/sbin/rc2.d/S130pfilboot[5]: Syntax error at line 166 : `"' is not matched.
/sbin/rc2.d/S131ipfboot[6]: Syntax error at line 166 : `"' is not matched.
/sbin/rc2.d/S590Rpcd[30]: Syntax error at line 166 : `"' is not matched.
/sbin/rc2.d/S606runner[21]: Syntax error at line 166 : `"' is not matched.
Wed Dec 6 16:54:45 EST 2006 /sbin/rc2.d/S606runner: ERROR: 127 returned from LogError invocat
ion
Wed Dec 6 16:54:45 EST 2006 /sbin/rc2.d/S606runner: ERROR: Originial Returned Value: 2 Origin
al Error: error returned from sourcing rc.config
/sbin/rc2.d/S700acct[39]: Syntax error at line 166 : `"' is not matched.
/sbin/rc3.d/S823hpws_apache[46]: Syntax error at line 166 : `"' is not matched.
/sbin/rc3.d/S823hpws_tomcat[46]: Syntax error at line 166 : `"' is not matched.
/sbin/rc3.d/S823hpws_webmin[45]: Syntax error at line 166 : `"' is not matched.
/sbin/rc3.d/S823hpws_webproxy[44]: Syntax error at line 166 : `"' is not matched.
/sbin/rc3.d/S823hpws_xmltools[42]: Syntax error at line 166 : `"' is not matched.

HP-UX Start-up in progress

[dictum9]

Once it comes after along time out the following, I have the system name set to "unknown" and the routing table blank. No changes to any files were made, just the patch bundle.

Could it be I installed a bad patch?


Configure HP Fibre Channel Tachyon TL/TS Mass Storage interfaces ........... OK
...........................................................................

[Ivan Krastev · Accepted solution]

See what you have in scripts on this lines:

/sbin/rc3.d/S823hpws_apache[46]:
/sbin/rc3.d/S823hpws_tomcat[46]:
/sbin/rc3.d/S823hpws_webmin[45]:


maybe they all pointed to same sript/command when error raise. I think this is an error in network config parameters after patch.


regards,
ivan

[Bill Hassell]

Most likely there is a rogue file in the /etc/rc.config.d directory. This is the one directory that you never have any temporary or junk files. Every file in that directory is sourced prior to every startup script.

To decode the above message, the line number is in [ ] brackets. For example, the acct script shows that line [39] is:

. /etc/rc.config

and /etc/rc.config does not have 166 lines (it's just 15 lines long), so the problem is in the files rc.config is sourcing.

[dictum9]

They are all trying to do this:

. /etc/rc.config


The file is still there, same size, ownership and permissions as a functional system. why would it cause problems?

[dictum9]

Bill H,

Just a quick look into the /etc/rc.config.d directory doesn't show anything abnormal, or any strange file names, or even anything with recent time stamp.

[dictum9]

Is it a good idea to try to source that /etc/rc.config file manually to see where it breaks?

[Bill Hassell]

It's not a problem with the rc.config file, it's with the files it is sourcing. Just trace the rc.config file by hand:

sh -x /etc/rc.config

This script just creates a bunch of env variables. You can slowdown all the steps like this:

sh -x /etc/rc.config 2>&1 | more

[dictum9]

Interesting, the only file that is 166 lines long in that directory is

/etc/rc.config.d/netconf

and the last entry is

DEFAULT_INTERFACE_MODULES=""

I wonder if that "" is what's causing issues.

[Ivan Krastev]

Maybe you have unclosed brackets in previous lines and this show error in last one.


ivan

[dictum9]

I did /sbin/init.d/net stop and start
and it showed clearly it was having issues with netconf file.

I re-counted all the " double quotes and found a quote that was not matched!

Thanks for showing the right direction here!



( Moral of the story - when editing netconf file, don't enclose the IP address in quotes, or if you do, make sure they are matched. )

[Bill Hassell]

Because the /etc/rc.config.d files never get run until bootup, it's a good idea to always test them after any edits are made. This is particularly easy because these files simply set env variables in the current shell. That means you can run any or all of the files at any time without affecting the running system. The reason 166 is reported is the missing " cause all the trailing lines to look like part of a multi-line string.

[Dennis Handly]

To follow up what Bill said about testing scripts for syntax errors, you can use: sh -n script