Hi, What is your platform (smartos) version?
Seb, On Tuesday, June 14, 2016, Gavin Ang <[email protected]> wrote: > Hi, > > I downloaded the (almost) latest Centos 7.2 LX zone Joyent image > (CentOS 7.2 20160601) and am evaluating if I can move my production stuff > onto this image. The host is running on ZFS RaidZ > > > > When I run ps –ef I see > > root 78880 1 0 Jun07 ? 00:00:00 /usr/bin/abrt-watch-log -F > BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected > ernel BUG at list_del corruption list_ > > > > In the /var/log/messages file I also see a fair amount of failed stuff. > > > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > Jun 7 10:07:55 localhost systemd: Started Load/Save Random Seed. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service has no holdoff > time, scheduling restart. > > Jun 7 10:07:55 localhost systemd: Starting udev Kernel Device Manager... > > Jun 7 10:07:55 localhost journal: Runtime journal is using 8.0M (max > allowed 305.6M, trying to leave 458.4M free of 2.9G available → current > limit 305.6M). > > Jun 7 10:07:55 localhost systemd: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-udevd: Function not implemented > > Jun 7 10:07:55 localhost systemd: Started Flush Journal to Persistent > Storage. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service: main process > exited, code=exited, status=226/NAMESPACE > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > Jun 7 10:07:55 localhost systemd: Started Configure read-only root > support. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service has no holdoff > time, scheduling restart. > > Jun 7 10:07:55 localhost systemd: Starting udev Kernel Device Manager... > > Jun 7 10:07:55 localhost systemd: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-udevd: Function not implemented > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service: main process > exited, code=exited, status=226/NAMESPACE > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service has no holdoff > time, scheduling restart. > > Jun 7 10:07:55 localhost systemd: Starting udev Kernel Device Manager... > > Jun 7 10:07:55 localhost systemd: Failed at step NAMESPACE spawning > /usr/lib/systemd/systemd-udevd: Function not implemented > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service: main process > exited, code=exited, status=226/NAMESPACE > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > Jun 7 10:07:55 localhost systemd: Started Rebuild Dynamic Linker Cache. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service has no holdoff > time, scheduling restart. > > Jun 7 10:07:55 localhost systemd: start request repeated too quickly for > systemd-udevd.service > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > > > Jun 7 10:07:55 localhost systemd: Failed to start udev Kernel Device > Manager. > > Jun 7 10:07:55 localhost systemd: Unit systemd-udevd-control.socket > entered failed state. > > Jun 7 10:07:55 localhost systemd: systemd-udevd.service failed. > > Jun 7 10:07:55 localhost systemd: Started udev Wait for Complete Device > Initialization. > > Jun 7 10:07:55 localhost systemd: Starting Activation of DM RAID sets... > > Jun 7 10:07:55 localhost systemd: plymouth-start.service: control process > exited, code=exited status=69 > > Jun 7 10:07:55 localhost systemd: Failed to start Show Plymouth Boot > Screen. > > Jun 7 10:07:55 localhost systemd: Unit plymouth-start.service entered > failed state. > > Jun 7 10:07:55 localhost systemd: plymouth-start.service failed. > > Jun 7 10:07:55 localhost systemd: Started Forward Password Requests to > Plymouth Directory Watch. > > Jun 7 10:07:55 localhost systemd: Started Dispatch Password Requests to > Console Directory Watch. > > Jun 7 10:07:55 localhost systemd: Starting Dispatch Password Requests to > Console Directory Watch. > > Jun 7 10:07:55 localhost rhel-dmraid-activation: ERROR: opening path > /sys/block > > Jun 7 10:07:55 localhost rhel-dmraid-activation: ERROR: failed to > discover devices > > > > Jun 7 10:07:56 localhost audispd: No plugins found, exiting > > Jun 7 10:07:56 localhost systemd: auditd.service: main process exited, > code=exited, status=1/FAILURE > > Jun 7 10:07:56 localhost augenrules: The audit system is disabled > > Jun 7 10:07:56 localhost systemd: Failed to start Security Auditing > Service. > > Jun 7 10:07:56 localhost systemd: Unit auditd.service entered failed > state. > > Jun 7 10:07:56 localhost systemd: auditd.service failed. > > > > Jun 7 10:07:56 localhost chronyd[78893]: chronyd version 2.1.1 starting > (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH) > > Jun 7 10:07:56 localhost chronyd[78893]: Fatal error : adjtimex() failed > > Jun 7 10:07:56 localhost rngd: Unable to open file: /dev/tpm0 > > Jun 7 10:07:56 localhost rngd: unable to adjust write_wakeup_threshold: > No such file or directory > > Jun 7 10:07:56 localhost rngd: RNDADDENTROPY failed: Inappropriate ioctl > for device > > Jun 7 10:07:56 localhost chronyd: adjtimex() failed > > > > Should I be concerned about any of this? > > > > *Gavin Ang* > > Global Mobility Laboratory > > > > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/26900931-98fbc364> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > -- Sebastien Perreault Partner Les Technologies Alesium Inc P: 514-298-7193 F: 514-221-3668 E: [email protected] ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
