error: cannot mmap()==MAP_FAILED

[IT Telecom Pomezia]

cd /sbin/rc2.d



# ./S416ldapclientd start

ldapclientd started with <0>

#

error: cannot mmap()==MAP_FAILED









# ps -ef | grep ldap

root 26634 1 210 17:44:59 ? 1:20 /opt/ldapux/bin/ldapclientd

root 27135 6739 0 17:46:20 pts/1 0:00 grep ldap






# /opt/ldapux/bin/ldapclientd -k

Error: Cache daemon is not running (or running but not ready)


Thanks in advance

[Steven E. Protter]

Shalom,

I have currently serious questions about the Q&A on this software (ldapux). Make sure you have the latest version released in late September.

http://software.hp.com


SEP

[IT Telecom Pomezia]

J4269AA B.04.10 LDAP-UX Integration

[Weltman, Ulf]

This is not an error we've seen during the extensive testing phase each version goes through, or heard it reported before. I'd like to help you resolve this, but I'll need some more information.

Did LDAP-UX ever work on the host where you're experiencing the problem? Did you change anything? What OS and platform are you running on? Any manual configuration changes, system crashes, or anything unusual that you can think of?

[SPGGPS]

Hi,

I have the same problem. I have hp-ux 11.23 and ladpux B.05.01. I do setup -l for use a local profile. The ldapux daemon run but nsquery not work.

Can you help me?

Thanks

[SPGGPS]

This is a debug error output

[Jul/22/2011 13:12:18  1:     daemon.c: 349:       clean_up_dead_sockets: client 67184800 is alive]
[Jul/22/2011 13:12:18  1:     daemon.c: 124:                   server_up: called]
[Jul/22/2011 13:12:18  1:     daemon.c: 141:                   server_up: random pass is 20185]
[Jul/22/2011 13:12:18  1:     daemon.c: 170:                   server_up: daemon_status_p=mmap()]

error: cannot mmap()==MAP_FAILED
[Jul/22/2011 13:12:18  1:     daemon.c: 180:                   server_up: error: cannot mmap()==MAP_FAILED]
[Jul/22/2011 13:12:18  1:application.c: 195:       application_exit_trap: called]
[Jul/22/2011 13:12:18  1:     daemon.c: 768:                     cleanup: called]

Thanks

[Dennis Handly]

You could use tusc to find the exact reason the syscall failed.

[LucaBerra]

happened to me today

using tusc /opt/ldapux/bin/ldapclientd -z i discovered it failed mmapping /var/spool/ldapcltd/status

removed the file and restarted ldapux, it works fine now.

[boukari]

The error can occurs when ldapclientd fails to memory map an existing status file /var/spool/ldapcltd/status . To solve the issue, remove the file before starting ldapclientd . The file will be newly created by ldapclientd .

[feeble]

LucaBerra, why you did not get kudos, i don't know. But you just saved my ass tonight. Many kudos to you.