Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Interface/Docker issue

MrMoosieMan
in General Support

Featured Replies

My unRAID interface is acting strangely.  I logged into today to find my Docker tab missing.  I rebooted the box and the tab came back but the containers are taking time to load and some of the applications never start.  I looked through my log and found the errors contained in the attached syslog file.  Do you mind taking a look and let me know what you think is wrong?

 

 

tower-diagnostics-20190218-1506.zip

syslog.txt

  • Quote
    52 minutes ago, MrMoosieMan said:

    some of the applications never start.

    Probably this: 

    time="2019-02-18T14:44:02.435435708-05:00" level=error msg="Handler for POST /v1.38/networks/create returned error: failed to allocate secondary ip address (server:10.10.14.0): Address already in use"

     

  • Quote
    • Author

    I beleive I corrected that issue.

     

    The problem I'm seeing is when I start the Docker process I start getting a ton of "kernel: ACPI Error" errors.  I have no idea what they mean or how to resolve them.  As a test I blew away my Docker instance and rebuilt it but I keep getting the errors once Docker starts.

     

    ErrorWarningSystemArrayLogin


    Feb 19 17:14:46 Tower rpcbind[21703]: connect from 10.10.10.5 to getport/addr(mountd)
    Feb 19 17:15:15 Tower ool www[21535]: /usr/local/emhttp/plugins/dynamix/scripts/emhttpd_update
    Feb 19 17:15:15 Tower emhttpd: req (47): cmdStatus=apply&csrf_token=****************
    Feb 19 17:15:15 Tower emhttpd: Starting services...
    Feb 19 17:15:15 Tower emhttpd: shcmd (778): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 40
    Feb 19 17:15:15 Tower root: Creating new image file: /mnt/user/system/docker/docker.img size: 40G
    Feb 19 17:15:16 Tower rpcbind[22142]: connect from 10.10.10.5 to getport/addr(mountd)
    Feb 19 17:15:16 Tower root: btrfs-progs v4.17 
    Feb 19 17:15:16 Tower root: See http://btrfs.wiki.kernel.org for more information.
    Feb 19 17:15:16 Tower root: 
    Feb 19 17:15:16 Tower root: Label: (null)
    Feb 19 17:15:16 Tower root: UUID: 71d890e8-8fff-4e82-803e-518e20daad64
    Feb 19 17:15:16 Tower root: Node size: 16384
    Feb 19 17:15:16 Tower root: Sector size: 4096
    Feb 19 17:15:16 Tower root: Filesystem size: 40.00GiB
    Feb 19 17:15:16 Tower root: Block group profiles:
    Feb 19 17:15:16 Tower root: Data: single 8.00MiB
    Feb 19 17:15:16 Tower root: Metadata: DUP 1.00GiB
    Feb 19 17:15:16 Tower root: System: DUP 8.00MiB
    Feb 19 17:15:16 Tower root: SSD detected: no
    Feb 19 17:15:16 Tower root: Incompat features: extref, skinny-metadata
    Feb 19 17:15:16 Tower root: Number of devices: 1
    Feb 19 17:15:16 Tower root: Devices:
    Feb 19 17:15:16 Tower root: ID SIZE PATH
    Feb 19 17:15:16 Tower root: 1 40.00GiB /mnt/disk4/system/docker/docker.img
    Feb 19 17:15:16 Tower root: 
    Feb 19 17:15:16 Tower kernel: BTRFS: device fsid 71d890e8-8fff-4e82-803e-518e20daad64 devid 1 transid 5 /dev/loop2
    Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): disk space caching is enabled
    Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): has skinny extents
    Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): flagging fs with big metadata feature
    Feb 19 17:15:16 Tower kernel: BTRFS info (device loop2): checking UUID tree
    Feb 19 17:15:16 Tower emhttpd: shcmd (780): /etc/rc.d/rc.docker start
    Feb 19 17:15:16 Tower root: starting dockerd ...
    Feb 19 17:15:18 Tower avahi-daemon[3199]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
    Feb 19 17:15:18 Tower avahi-daemon[3199]: New relevant interface docker0.IPv4 for mDNS.
    Feb 19 17:15:18 Tower avahi-daemon[3199]: Registering new address record for 172.17.0.1 on docker0.IPv4.
    Feb 19 17:15:18 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
    Feb 19 17:15:20 Tower root: Starting docker_load
    Feb 19 17:15:46 Tower rpcbind[24376]: connect from 10.10.10.5 to getport/addr(mountd)
    Feb 19 17:21:14 Tower kernel: eth0: renamed from veth72fd6b5
    Feb 19 17:21:14 Tower kernel: device br0 entered promiscuous mode
    Feb 19 17:21:16 Tower rpcbind[11535]: connect from 10.10.10.5 to getport/addr(mountd)
    Feb 19 17:21:18 Tower kernel: eth0: renamed from veth576a504
    Feb 19 17:21:22 Tower kernel: eth0: renamed from vethd1051bb
    Feb 19 17:21:26 Tower kernel: eth0: renamed from veth4c8653f
    Feb 19 17:21:30 Tower kernel: eth0: renamed from vethc32b208
    Feb 19 17:21:37 Tower kernel: eth0: renamed from veth71198f6
    Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516)
    Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338)
    Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516)
    Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130)
    Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._PMM, AE_NOT_EXIST (20180531/psparse-516)
    Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _PMM (20180531/power_meter-338)
    Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Region IPMI (ID=7) has no handler (20180531/exfldio-265)
    Feb 19 17:21:44 Tower kernel: ACPI Error: Method parse/execution failed \_SB.M111._GAI, AE_NOT_EXIST (20180531/psparse-516)
    Feb 19 17:21:44 Tower kernel: ACPI Error: AE_NOT_EXIST, Evaluating _GAI (20180531/power_meter-130)
    Feb 19 17:21:44 Tower kernel: ACPI Error: No handler for Region [POWS] (00000000701891e8) [IPMI] (20180531/evregion-132)
     

  • Quote
    • Author

    Does anyone have any idea how I can fix this?

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.