kernel build fails

[Roger Baptiste]

Kirk,

This error occurs sometimes when the kernel parameters exceed limits. To make sure you are using within the limits, use SAM to rebuild the kernel. SAM will warn you in case the values are not correct.

Also, regarding your maxtsiz error, there is a maxtsiz
parameter in the kernel parm list. Check it up.

If you any have any further problems with this, pls post the kernel parms which you are changing and their sizes.

HTH
raj

[Kirk MacLean_2]

Thanks for your reply.

When using SAM and attempting to change a single parameter, we get the error:
"cpp: cannot open message catalog" and fails.
So we have resorted to the manual proceedure.

Below are the configureable parameters of the kernel.

bufpages 0
create_fastlinks 1
dbc_max_pct 25
fs_async 1
maxdsiz 2063806464
maxfiles 200
maxfiles_lim 2048
maxssiz (383*1024*1024)
maxswapchunks 4096
maxtsiz (1024*1024*1024)
maxuprc 200
maxusers 124
netmemmax 0

nfile 2800
ninode 15000
nproc 1024
npty 512

Regards,
Kirk

[Roger Baptiste]

<"cpp: cannot open message catalog" and fails. >>

Check
ll /usr/ccs/bin/cc
-> it should be a link to ./cc_bundled
Look at doc RCENKBRC00004680 for more reference.

<>

Also make sure you have the SAM/OBAM patch installed ( PHCO_22268)

When you do it manually, make sure you know what the dependencies are for the param you want change, through the equations shows in the SAM list and change the dependent params too.

But, i would still suggest that you correct the SAM issue and do it through SAM.

HTH
raj

[S.K. Chan]

One possible reason why you're getting the "cannot open message catalog" error is when you got inode table full situation.
Do a dmesg and see if you got inode full error. If yes close all other processes to free up the inode. If not just ignore this message.

[Kirk MacLean_2]

Hello and thanks for the suggestions,

Still experiencing the same problems after taking suggested actions.
One suggestion is reinstalling the OS, but I'd prefer not do this if it's avoidable.

Looking for additional feedback,

Kirk

> RajMan

> Check
> ll /usr/ccs/bin/cc
> -> it should be a link to ./cc_bundled
This link is in place.

> Look at doc RCENKBRC00004680 for more reference.
Searched for this number using the IRTC search. No results?

> Also make sure you have the SAM/OBAM patch installed ( PHCO_22268)
Installed this patch but results are the same.

> S.K. Chan

> Do a dmesg and see if you got inode full error.
> If yes close all other processes to free up the inode.
> If not just ignore this message.
There's no inode problem.

[Roger Baptiste]

Hi,

Here is the link to the docid i was referring to earlier:
http://us-support.external.hp.com/cki/bin/doc.pl/sid=abd28d680317bc8f7b/screen=ckiDisplayDocument?docId=200000054468440

Before you go for the drastic reinstall option, try out#
Use SAM and change just the maxusers parameter and see whether the kernel change is sucessful. This is just to test whether the kernel build operations work fine on the system.
Also, make sure you have all SAM related patches on the system. On a working 10.20 box do swlist -l product |grep -i sam
and compare it with the list on your box.

Look at sam log files to spot any errors

HTH
raj

[fjatu]

hi,kirk:
i see the value of maxdsiz,maybe it is too large(on hp_ux 11.0 it's max vuale is 2G(0x7B03A000)).
maybe you should reduce some value and test again.

good luck!

[Kirk MacLean_2]

Problem solved by booting off vmunix.prev, then building a new kernel.

Thanks for the help.

Kirk