errors after 9.10 upgrade

Status
Not open for further replies.

borisattva

Dabbler
Joined
Apr 22, 2012
Messages
20
got prompted to update to 9.10, complied.

after a long update process the system rebooted into what seems like a list of errors.

i'm unclear if these are to be expected but i know that before the update the box was completely error free

including where i believe it starts.

Code:
Apr 6 01:29:06 N40L ipmi0: <IPMI System Interface> on isa0
Apr 6 01:29:06 N40L ipmi0: KCS mode found at mem 0x0 alignment 0x1 on isa
Apr 6 01:29:06 N40L ipmi0: couldn't configure I/O resource
Apr 6 01:29:06 N40L device_attach: ipmi0 attach returned 6
Apr 6 01:29:06 N40L hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> K8/4/48/0x1ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA>
Apr 6 01:29:06 N40L kernel: bge0: link state changed to DOWN
Apr 6 01:29:06 N40L kernel: bge0: link state changed to DOWN
Apr 6 01:29:06 N40L kernel: bge0: link state changed to UP
Apr 6 01:29:06 N40L kernel: bge0: link state changed to UP
Apr 6 01:29:06 N40L vboxdrv: fAsync=0 offMin=0x406 offMax=0x30a0
Apr 6 01:29:11 N40L GEOM_ELI: Device ada4p1.eli created.
Apr 6 01:29:11 N40L GEOM_ELI: Encryption: AES-XTS 128
Apr 6 01:29:11 N40L GEOM_ELI: Crypto: software
Apr 6 01:29:11 N40L GEOM_ELI: Device ada0p1.eli created.
Apr 6 01:29:11 N40L GEOM_ELI: Encryption: AES-XTS 128
Apr 6 01:29:11 N40L GEOM_ELI: Crypto: software
Apr 6 01:29:11 N40L GEOM_ELI: Device ada1p1.eli created.
Apr 6 01:29:11 N40L GEOM_ELI: Encryption: AES-XTS 128
Apr 6 01:29:11 N40L GEOM_ELI: Crypto: software
Apr 6 01:29:11 N40L GEOM_ELI: Device ada2p1.eli created.
Apr 6 01:29:11 N40L GEOM_ELI: Encryption: AES-XTS 128
Apr 6 01:29:11 N40L GEOM_ELI: Crypto: software
Apr 6 01:29:12 N40L GEOM_ELI: Device ada3p1.eli created.
Apr 6 01:29:12 N40L GEOM_ELI: Encryption: AES-XTS 128
Apr 6 01:29:12 N40L GEOM_ELI: Crypto: software
Apr 6 01:29:13 N40L root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Apr 6 01:29:20 N40L ntpd[1842]: ntpd 4.2.8p6-a (1): Starting
Apr 6 01:29:29 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: /usr/local/bin/net -d 0 getlocalsid
Apr 6 01:29:30 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: /usr/local/bin/net -d 0 setlocalsid S-1-5-21-1811421315-2323763608-1277229887
Apr 6 01:29:30 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Apr 6 01:29:30 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: mount
Apr 6 01:29:30 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: mount
Apr 6 01:29:30 N40L generate_smb4_conf.py: [common.pipesubr:61] Popen()ing: /usr/local/bin/net -d 0 getlocalsid
Apr 6 01:29:34 N40L smbd: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Apr 6 01:29:34 N40L mDNSResponder: mDNSResponder (Engineering Build) (Mar 25 2016 21:58:46) starting
Apr 6 01:29:34 N40L mDNSResponder: 8: Listening for incoming Unix Domain Socket client requests
Apr 6 01:29:34 N40L mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Apr 6 01:29:34 N40L mDNSResponder: CheckNATMappings: Failed to allocate port 5350 UDP multicast socket for PCP & NAT-PMP announcements
Apr 6 01:29:35 N40L mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801406D60 N40L.local. (Addr) that's already in the list
Apr 6 01:29:35 N40L mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000801407180 148.1.168.192.in-addr.arpa. (PTR) that's already in the list
Apr 6 01:33:00 N40L cron[3791]: _secure_path: /mnt/caviar/.login_conf is group writeable by non-authorised groups


please advise
 

borisattva

Dabbler
Joined
Apr 22, 2012
Messages
20
thank you for the quick response.

what about the last line:
Apr 6 01:33:00 N40L cron[3791]: _secure_path: /mnt/caviar/.login_conf is group writeable by non-authorised groups

i checked the permissions on the /caviar/ dataset and group write is unchecked so its confusing
 
D

dlavigne

Guest
That one I'm not sure about. If it worries you, create a ticket at bugs.freenas.org and post the issue number here.
 
Status
Not open for further replies.
Top