Fw: Fw: RPC: error 101
Ho un problema con bind e con nfs-kernel-server, funzionano correttamente solo se li faccio partire manualmente dopo il login,
durante il boot gli script provvedono ad avviarli ma restituiscono degli errori:
Apr 24 16:29:11 orangebud named[170]: starting BIND 9.2.1
Apr 24 16:29:11 orangebud named[170]: using 1 CPU
Apr 24 16:29:12 orangebud rpc.statd[177]: Version 1.0 Starting
Apr 24 16:29:12 orangebud named[172]: loading configuration from '/etc/bind/named.conf'
Apr 24 16:29:12 orangebud rpc.statd[178]: unable to register (statd, 1, udp).
Apr 24 16:29:12 orangebud named[172]: no IPv6 interfaces found
Apr 24 16:29:12 orangebud named[172]: ifiter_ioctl.c:218: REQUIRE(iter->pos < (unsigned int) iter->ifc.ifc_len) failed
Apr 24 16:29:12 orangebud named[172]: exiting (due to assertion failure)
Apr 24 16:29:17 orangebud nfsd[242]: nfssvc: Network is unreachable
Apr 24 16:29:25 orangebud xinetd[357]: xinetd Version 2.3.4 started with libwrap loadavg options compiled in.
Apr 24 16:29:25 orangebud xinetd[357]: Started working: 1 available service
Apr 21 11:20:19 orangebud kernel: RPC: sendmsg returned error 101
Apr 21 11:20:19 orangebud kernel: portmap: RPC call returned error 101
Apr 21 11:20:19 orangebud kernel: RPC: sendmsg returned error 101
Apr 21 11:20:19 orangebud kernel: portmap: RPC call returned error 101
Apr 21 11:20:19 orangebud kernel: RPC: sendmsg returned error 101
Apr 21 11:20:19 orangebud kernel: portmap: RPC call returned error 101
però se dopo il login avvio manualmente /etc/init.d/bind /etc/init.d/nfs-kernel-server funziona tutto perfettamente, ricordo che il problema si presentava anche con samba.
Reply to: