• Upgrading 1.14 to 1.18.1 -- Cannot allocate memory?

    From lucas liu@21:1/5 to All on Wed Dec 30 22:36:13 2020
    在 2020年5月9日星期六 UTC+8 上午6:35:43,<Greg Hudson> 写道:
    On 5/8/20 3:18 PM, Leonard J. Peirce wrote:
    I am testing the upgrade from 1.14 to 1.18.1. I copy the database directory over and attempt to start krb5kdc and kadmind but both
    fail. Syslog shows for krb5kdc

    Cannot allocate memory - while creating main loop
    "while creating main loop" is a hint here, but unfortunately "Cannot allocate memory" probably doesn't speak to the true cause. If there any other KDC or kadmind log messages preceding that one, they may help.
    Since you built the sources yourself, you could try debugging through startup using gdb, particularly looking into loop_setup_network().
    strace is another option for collecting more information.

    There were significant changes to KDC and kadmind network configuration
    in 1.15. I haven't seen a report like this before, but it's possible
    that the changes interact badly with your specific configuration.
    ****************************************************************************************
    We are also show “Cannot allocate memory - while creating main loop”
    Any one can give me some ideas ? ================================================================
    [root@namenode ~]# cat /var/log/krb5kdc.log
    krb5kdc: Cannot allocate memory - while creating main loop
    krb5kdc: Cannot allocate memory - while creating main loop
    krb5kdc: Cannot find master key record in database - while fetching master keys list for realm HDFS.COM
    krb5kdc: Cannot find master key record in database - while fetching master keys list for realm HDFS.COM
    krb5kdc: Cannot find master key record in database - while fetching master keys list for realm HDFS.COM
    krb5kdc: Cannot allocate memory - while creating main loop
    krb5kdc: Cannot allocate memory - while creating main loop
    [root@namenode ~]# cat /var/log/kadmind.log
    Dec 31 11:52:49 namenode kadmind[74351](Error): Cannot allocate memory while initializing network, aborting

    Dec 31 13:55:25 namenode kdb5_util[75059](info): No dictionary file specified, continuing without one.
    Dec 31 14:22:36 namenode kadmind[75489](Error): Cannot allocate memory while initializing network, aborting

    [root@namenode ~]# c
    -bash: c: command not found
    [root@namenode ~]# ll /var/kerberos/krb5
    krb5/ krb5kdc/
    [root@namenode ~]# ll /var/kerberos/krb5kdc/
    total 24
    -rw------- 1 root root 18 Dec 31 14:14 kadm5.acl
    -rw------- 1 root root 431 Dec 30 19:08 kdc.conf
    -rw------- 1 root root 8192 Dec 31 14:20 principal
    -rw------- 1 root root 8192 Dec 31 14:15 principal.kadm5
    -rw------- 1 root root 0 Dec 31 14:15 principal.kadm5.lock
    -rw------- 1 root root 0 Dec 31 14:20 principal.ok
    [root@namenode ~]# cat /etc/krb5.conf
    [logging]
    default = FILE:/var/log/krb5libs.log
    kdc = FILE:/var/log/krb5kdc.log
    admin_server = FILE:/var/log/kadmind.log

    [libdefaults]
    dns_lookup_realm = false
    ticket_lifetime = 24h
    renew_lifetime = 7d
    forwardable = true
    rdns = false
    default_realm = HDFS.COM
    default_ccache_name = KEYRING:persistent:%{uid}

    [realms]
    HDFS.COM = {
    kdc = namenode
    admin_server = namenode
    }

    [domain_realm]
    .hdfs.com = HDFS.COM
    hdfs.com = HDFS.COM

    [kdc]
    profile = /var/kerberos/krb5kdc/kdc.conf

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)