Results 1 to 2 of 2

Thread: named mit chroot geht nicht - mmap returns with EACCESS

  1. #1

    Default named mit chroot geht nicht - mmap returns with EACCESS


    SuSE 12.1

    vielleicht kann mir mal irgendjemand helfen:
    rcnamed start
    laueft kein named!

    wenn ich es per Hand starte:
    named -t /var/lib/named -u named -g
    28-Nov-2011 16:59:42.267 starting BIND 9.8.1-P1 -t /var/lib/named -u named -g
    28-Nov-2011 16:59:42.267 built with '--prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib64' '--includedir=/usr/include/bind' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-openssl' '--enable-threads' '--with-libtool' '--enable-runidn' '--with-libxml2' '--with-dlz-mysql' '--with-dlz-ldap' 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNO_VERSION_DATE -fno-strict-aliasing' 'LDFLAGS=-L/usr/lib64'
    28-Nov-2011 16:59:42.267 adjusted limit on open files from 4096 to 1048576
    28-Nov-2011 16:59:42.267 found 4 CPUs, using 4 worker threads
    28-Nov-2011 16:59:42.269 using up to 4096 sockets
    28-Nov-2011 16:59:42.274 initializing DST: openssl failure
    28-Nov-2011 16:59:42.274 exiting (due to fatal error)

    Dem bin ich nachgegangen:
    strace named -t /var/lib/named -u named -g
    open("/lib64/engines/", O_RDONLY) = 9
    read(9, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0000t\0\0\0\0\0\0"..., 832) = 832
    fstat(9, {st_mode=S_IFREG|0555, st_size=97312, ...}) = 0
    mmap(NULL, 2192400, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 9, 0) = -1 EACCES (Permission denied)


    was muss im System geaendert werden, damit named auch mit chroot funktioniert.
    Ohne chroot geht es naemlich

    Aber bitte nicht das system aufmachen - named sollte unter chroot laufen


  2. #2

    Default Re: named mit chroot geht nicht - mmap returns with EACCESS

    from the English thread - treat it as solved

    Hi P.V.,

    thanks for answering.

    problem was not a missing file like in the mandriva bug.
    All of the files are in place.

    But I found a solution - it's the configuration of appamor


Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts