Jump to content

diehard2k9

Members
  • Posts

    39
  • Joined

  • Last visited

Posts posted by diehard2k9

  1. 53 minutes ago, ChatNoir said:

    I see several things repeating in the log that do not seem normal :

    Sep 18 13:48:13 KRAKEN  zed[6752]: Diagnosis Engine: error event 'ereport.fs.zfs.deadman'
    Sep 18 13:48:13 KRAKEN  zed[6752]: Missed 25 events
    Sep 18 13:48:13 KRAKEN  zed[6752]: Bumping queue length to 2147483647
    Sep 18 13:48:13 KRAKEN  zed[6752]: Diagnosis Engine: error event 'ereport.fs.zfs.deadman'
    Sep 18 13:48:13 KRAKEN  zed[6752]: Missed 20 events
    Sep 18 13:48:13 KRAKEN  zed[6752]: Bumping queue length to 2147483647
    Sep 18 13:48:13 KRAKEN  zed[6752]: Diagnosis Engine: error event 'ereport.fs.zfs.deadman'

     

    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 task abort SUCCESS!! scmd(0x000000008d67e782)
    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 CDB: opcode=0x0 00 00 00 00 00 00
    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 OCR is requested due to IO timeout!!
    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 SCSI host state: 5  SCSI host busy: 1  FW outstanding: 0
    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 scmd: (0x000000008d67e782)  retries: 0x0  allowed: 0x5
    Sep 18 13:48:22 KRAKEN kernel: sd 1:2:12:0: [sdg] tag#7259 CDB: opcode=0x8a 8a 00 00 00 00 05 e6 f5 d8 60 00 00 00 b0 00 00
    Sep 18 13:48:22 KRAKEN kernel: megaraid_sas 0000:13:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
    Sep 18 13:48:22 KRAKEN kernel: megaraid_sas 0000:13:00.0: megasas_enable_intr_fusion is called outbound_intr_mask:0x40000000
    Sep 18 13:48:32 KRAKEN kernel: sd 1:2:12:0: Power-on or device reset occurred

     

    The first one seem to be related to ZFS, so I would suggest asking in the support thread for the plugin.

     

    The second seem to be sdg being reset. I'd guess that this device is part of a ZFS file system ? You should check the drive connections (data and power).

    Note that RAID controllers are not recommended even if that's maybe not the cause of your issue.

    the connection data and power are ok, unless it's in the backplan.  the slow speed is happening on both the controller and on the motherbard sata ports.  I dont have a clue why the transfer speed would run slow in KB/s when I have a big pipe for it to at high speed.  I have shut it down because I have to replace one of the new drives and dont want my data to get lost on that mirror. So as soon as I get the new drives I will test the speed again.

  2. Hello, I have started to notice that the transfer speed at time we very slow as in the KB/s and I would get a pop mesg when opening a fold from another computer. telling me to wait for it to open or cancel it and this waitr could take mins.  So I went to upgrade the system with new hard drives and files system.  on the transfer from the old hard drive at times it would be really 180MB/s but then it would take longer time like all days for  some folders with smaller files in them. I would see the copying file stuck for mins, then the rest of the files fly by and them stops again for 10 mins or more on a 3 meg file.  I dont know if the old hard drive are slow because it's almost full got like 3 - 30 gb left on them.   What I notice is that trying to access the new hard drives with the new file system is just as bad. I cant copy files across the network it would time out and streaming now working.  Lots of room on the new hard drives and computer is a beast.  So if anyone has some ideas that will help me solve these slow proformance please let me know what I can do.

     

    p.s. after i move all my data half the hard drive and ssd will be removed

    kraken-diagnostics-20220918-1356.zip

  3. Hello after I have update to the latest unraid my plex server was not working and now thaat I do have it working my media are not playable!  When looking for the shares on plex to map I dont see the areas where all my media is stored. Would someone please help me with that, thanks in advance!

  4. On 8/24/2022 at 11:57 AM, dlandon said:

     

    In my case:

    Screenshot 2022-08-24 105557.png

     

    Click on the 'Testing' text when the drive is unmounted and change that to 'TEAM4TB'.

    OK DUDE YOU ROCK!

    I was ok let me change this real quick just to say I did it and it didnt work.  Thanks alot man it's back up and running. Too bad I have to tear everything down now to add new file system and hard drives!

  5. On 8/24/2022 at 11:57 AM, dlandon said:

     

    In my case:

    Screenshot 2022-08-24 105557.png

     

    Click on the 'Testing' text when the drive is unmounted and change that to 'TEAM4TB'.

    I will try that but I have to upgrade the UNRAID server. I got new hard drives and I have to change the setup and move all the files and data to XFS raid10 if I can get it to work.  As for changing that label to "TEAM4TB"  I think I just tried to point it to the "unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099'" where I can see my files but PLEX would not show up. it was running but no metadata or my files was there.  I will have to do a teardown now that I got the new hard drives and am changing the filke system and putting it into a new box.

  6. On 8/22/2022 at 10:58 PM, dlandon said:

    You have the wrong mapping of the drive.  You're referring to the drive in the docker mounted at /mnt/disks/TEAM4TB, but the drive is actually mounted at:

    Aug 22 21:57:10 KRAKEN unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099'

    Do the following:

    • Stop the plex docker container.
    • Unmount the UD drive.
    • Click on the UD mount point and change it to 'TEAM4TB'.
    • Mount the UD drive.
    • Start the plex docker container.

    Hello, thanks for all the help but I'm not sure what I';m doing anymore. You reply let me find that all my info is there.  I dont know why it all stoped working. I created a link to UD back when I installed the NVME for plex andd file. so when you say to do "Click on the UD mount point and change it to 'TEAM4TB'." not sure how this is done or where it is. I see now what the problem is my link that was create might have gotten changed after the upgrade that cchanged something.  I will try and see if I can change it back!

  7. 8 hours ago, dlandon said:

     

    I don't think this is the solution to your problem, but your log is being spammed with this:

    Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152573,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   process_local_master_announce: Server GIGABYTE at IP 10.0.0.120 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
    Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152691,  0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success)
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   Samba name server KRAKEN has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
    Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
    Aug 20 20:54:12 KRAKEN  nmbd[74745]: [2022/08/20 20:54:12.727010,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
    Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****
    Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
    Aug 20 20:54:12 KRAKEN  nmbd[74745]:   Samba name server KRAKEN is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
    Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
    Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****

    The local master browser election is bouncing back and forth causing a lot of log messages.  It makes it hard to analyze your log when it's filling with those messages.  Not sure what your LAN configuration is, but maybe install the local master plugin to make Unraid always win the election for master browser.

     

    Once you've solved that, unmount and remount the UD drive you use for plex and post new diagnostics.

     

    Also post a screen shot of the mapping of the drive to the plex docker container.

    Hi I'm not very good with the whole linux thing. It's hard for me to understtand what to do.  I have the local master plug installed.

    I am weeks away from upgrade and this happens.  I just know that the folders in the UD are not showiung up for the system to find what it need to run plex or show my files.  I reaally dont know what I need to do and I dont want to start from the beginning so any help would be great!

    lan.png

    local.png

    plex1.png

    kraken-diagnostics-20220822-2157.zip

  8. On 8/20/2022 at 9:44 PM, wgstarks said:

    Go to the docker tab and click the name of your plex docker. This will open the configuration window. Click the edit button for the path associated with the UD device and you will see a popup window similar to this-

    18672744_ScreenShot2022-08-20at9_39_12PM.thumb.png.c731fd2903ef60fda31483b46b7d761b.png

     

    Set the access mode to Read/Write - Slave and click "Save".

    Hello, Yeah I found and understand what I needed to do but that didnt fix my problem!  I still cant see what on the drive so my plex server still isnt working. When conneccted threw the network all my file are not displaying. But unraid main page see the drive and that I have used up 2.4TB and have 1.5Tb free but under the unassign devices no files are showing up

  9. Hello, just updateto the lastest unraid6.11.0-rc3 Now the plex server is broken. I have a link or share in unassigned device with the plexe data. Only problem is that unraid doesnt see my files on it. It doesnt need all the videos either.  It know that 2TB has been used and there is 1.4TB free but I cant see any of the files . "

     

    Due to how Docker works, if you have an disk or share being mounted by Unassigned Devices and that device or share is being passed through to a docker container under certain circumstances the docker app may not always see the files present within it.

     

    The solution here is to edit the docker app in question, and next to the path that you're mapping to the container hit EDIT.  On the popup window that appears, for the access mode select one of the Slave access modes

    " I do not understand what I need to do when is says"for the access mode select one of the Slave access modes"

    so I dont know what I need to do if that will fix the problem.  I get this error "

    This site can’t be reached

    10.0.0.17 refused to connect.

    Try:

    Checking the connection

    Checking the proxy and the firewall

    ERR_CONNECTION_REFUSED"

    any help wouuld be great!

    kraken-diagnostics-20220820-2101.zip

  10. 33 minutes ago, trurl said:

    Not clear, but your docker configuration is less than ideal.

     

    Why do you have 200G docker.img? 20G is often more than enough. Also, system share has files on the array.

     

    Syslog being spammed with these. Install dynamix local master plugin

    Jan  3 16:17:37 KRAKEN nmbd[13398]: [2022/01/03 16:17:37.264825,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   process_local_master_announce: Server GIGABYTE at IP 10.0.0.25 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
    Jan  3 16:17:37 KRAKEN nmbd[13398]: [2022/01/03 16:17:37.264986,  0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success)
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   *****
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   Samba name server KRAKEN has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   
    Jan  3 16:17:37 KRAKEN nmbd[13398]:   *****
    Jan  3 16:17:54 KRAKEN nmbd[13398]: [2022/01/03 16:17:54.282261,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
    Jan  3 16:17:54 KRAKEN nmbd[13398]:   *****
    Jan  3 16:17:54 KRAKEN nmbd[13398]:   
    Jan  3 16:17:54 KRAKEN nmbd[13398]:   Samba name server KRAKEN is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
    Jan  3 16:17:54 KRAKEN nmbd[13398]:   
    Jan  3 16:17:54 KRAKEN nmbd[13398]:   *****
    Jan  3 16:28:27 KRAKEN nmbd[13398]: [2022/01/03 16:28:27.151854,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
    Jan  3 16:28:27 KRAKEN nmbd[13398]:   process_local_master_announce: Server LAPTOP at IP 10.0.0.50 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
    Jan  3 16:28:27 KRAKEN nmbd[13398]: [2022/01/03 16:28:27.152028,  0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success)
    

     

    Ok, I have installed dynamix local master plugin.

    The reason for the 200G is that it was telling me it was running out of space.

    I increased it to 200G so I would never run out and I didnt know that might be too much cause 20G wasnt enough.

    Will the about install get plex to work ?

  11. Hi, thanks for the respond! I'm not sure that you thought it was an easy fix but I have no clue on how to fix it even after going threw read me first and the other stuff.

    The SSL was already disable.  So right now my plex is not working before the upgrade to 6.10.0.RC2

    Any help on how to get connected back to it is is apreciate!

    Checked the other dockers and they using the same IP and what I think the server is, dont know if that helps.

  12. Hello I thought I would upgrade to 6.10.0. rc2 last night and didnt test if everything was working.

    Today I went to connect to plex and I get this error." This site can’t be reached

    10.0.0.17 refused to connect." I have gotten this error before in the pass and all I had to do was removed the s from the hppts:// to http://. I would get a warning about the site not being safe but it would connect and work.  Today that doesnt work and I cant get my plex info. The docker work and unraid says it's running but I can't get my date when on the computer or phone.  The phone willl have the app running but not of my info is there to view and the computer just gives me "This site can’t be reached 10.0.0.17 refused to connect."  I would really like to know why I run into this error when it was working fine but not after an upgrade.  You guys really need to do a better job of not having the dockers break after an upgrade.  It is very confusing to know what to do since unraid linux is not my first language and I really dont know how to fix stuff but I know how to set it up. I have a feeling that someone has already post a solution but I was not able to find it.

    plex_DIA.zip

  13. Hello, I just update my deluge and now it doesnt work, it got broken. I'm nost usre how to fix it.

    It starts up but it wont download anything. It also look like it still trying to boot. Would someone Please help me?

    Here is the log.

    ErrorWarningSystemArrayLogin



    2019-03-30 15:58:55,949 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 auth-token received, disabling auth-nocache for the authentication token

    2019-03-30 15:58:55,950 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 TUN/TAP device tun0 opened

    2019-03-30 15:58:55,950 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
    Sat Mar 30 15:58:55 2019 /usr/bin/ip link set dev tun0 up mtu 1500

    2019-03-30 15:58:55,953 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 /usr/bin/ip addr add dev tun0 local 10.2.10.10 peer 10.2.10.9

    2019-03-30 15:58:55,955 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 /root/openvpnup.sh tun0 1500 1558 10.2.10.10 10.2.10.9 init

    2019-03-30 15:58:55,965 DEBG 'start-script' stdout output:
    Sat Mar 30 15:58:55 2019 Initialization Sequence Completed

    2019-03-30 15:58:56,069 DEBG 'watchdog-script' stdout output:
    [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.2.10.10 different, marking for reconfigure

    2019-03-30 15:58:56,069 DEBG 'privoxy-script' stdout output:
    [info] Configuring Privoxy...

    2019-03-30 15:58:56,076 DEBG 'watchdog-script' stdout output:
    [info] Deluge not running

    2019-03-30 15:58:56,083 DEBG 'watchdog-script' stdout output:
    [info] Deluge Web UI not running

    2019-03-30 15:58:56,088 DEBG 'start-script' stdout output:
    [info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82...

    2019-03-30 15:58:56,099 DEBG 'privoxy-script' stdout output:
    [info] All checks complete, starting Privoxy...

    2019-03-30 15:58:56,100 DEBG 'privoxy-script' stderr output:
    2019-03-30 15:58:56.100 1504b96e1100 Info: Privoxy version 3.0.26
    2019-03-30 15:58:56.100 1504b96e1100 Info: Program name: /usr/bin/privoxy

    2019-03-30 15:58:56,396 DEBG 'start-script' stdout output:
    [info] Successfully retrieved external IP address 172.98.67.35

    2019-03-30 15:58:56,464 DEBG 'start-script' stdout output:
    [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

    2019-03-30 15:58:56,546 DEBG 'start-script' stdout output:
    [info] List of PIA endpoints that support port forwarding:-

    2019-03-30 15:58:56,546 DEBG 'start-script' stdout output:
    [info] ca-toronto.privateinternetaccess.com
    [info] ca-montreal.privateinternetaccess.com
    [info] ca-vancouver.privateinternetaccess.com
    [info] de-berlin.privateinternetaccess.com
    [info] de-frankfurt.privateinternetaccess.com
    [info] sweden.privateinternetaccess.com
    [info] swiss.privateinternetaccess.com
    [info] france.privateinternetaccess.com
    [info] czech.privateinternetaccess.com
    [info] spain.privateinternetaccess.com
    [info] ro.privateinternetaccess.com
    [info] israel.privateinternetaccess.com

    2019-03-30 15:58:56,557 DEBG 'start-script' stdout output:
    [info] Attempting to curl http://209.222.18.222:2000/?client_id=5fad20a37ef6474a2f91611aef507dc0a350af29c0ff76e2efcc74eafbc6643b...

    2019-03-30 15:58:57,397 DEBG 'start-script' stdout output:
    [info] Curl successful for http://209.222.18.222:2000/?client_id=5fad20a37ef6474a2f91611aef507dc0a350af29c0ff76e2efcc74eafbc6643b, response code 200

    2019-03-30 15:58:57,493 DEBG 'watchdog-script' stdout output:
    [info] Deluge incoming port 6890 and VPN incoming port 22146 different, marking for reconfigure

    2019-03-30 15:58:57,494 DEBG 'watchdog-script' stdout output:
    [info] Attempting to start Deluge...
    [info] Removing deluge pid file (if it exists)...

    2019-03-30 15:58:57,675 DEBG 'watchdog-script' stdout output:
    [info] Deluge listening interface currently defined as 0.0.0.0
    [info] Deluge listening interface will be changed to 0.0.0.0
    [info] Saving changes to Deluge config file /config/core.conf...

    2019-03-30 15:58:57,896 DEBG 'watchdog-script' stdout output:
    [info] Deluge process started
    [info] Waiting for Deluge process to start listening on port 58846...

    2019-03-30 16:00:19,267 WARN received SIGTERM indicating exit request
    2019-03-30 16:00:19,268 DEBG killing privoxy-script (pid 151) with signal SIGTERM
    2019-03-30 16:00:19,268 INFO waiting for start-script, watchdog-script, privoxy-script to die
    2019-03-30 16:00:19,268 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 23302974950864 for <Subprocess at 23302974949352 with name privoxy-script in state STOPPING> (stdout)>
    2019-03-30 16:00:19,269 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 23302974951152 for <Subprocess at 23302974949352 with name privoxy-script in state STOPPING> (stderr)>
    2019-03-30 16:00:19,269 INFO stopped: privoxy-script (terminated by SIGTERM)
    2019-03-30 16:00:19,269 DEBG received SIGCLD indicating a child quit
    2019-03-30 16:00:19,269 DEBG killing watchdog-script (pid 150) with signal SIGTERM
    2019-03-30 16:00:19,270 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 23302974950576 for <Subprocess at 23302974949640 with name watchdog-script in state STOPPING> (stderr)>
    2019-03-30 16:00:19,270 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23302974950288 for <Subprocess at 23302974949640 with name watchdog-script in state STOPPING> (stdout)>
    2019-03-30 16:00:19,270 INFO stopped: watchdog-script (terminated by SIGTERM)
    2019-03-30 16:00:19,270 DEBG received SIGCLD indicating a child quit
    2019-03-30 16:00:19,270 DEBG killing start-script (pid 149) with signal SIGTERM
    2019-03-30 16:00:19,271 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23302974949712 for <Subprocess at 23302974949496 with name start-script in state STOPPING> (stdout)>
    2019-03-30 16:00:19,271 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23302974950000 for <Subprocess at 23302974949496 with name start-script in state STOPPING> (stderr)>
    2019-03-30 16:00:19,271 INFO stopped: start-script (terminated by SIGTERM)
    2019-03-30 16:00:19,271 DEBG received SIGCLD indicating a child quit
    Created by...
    ___. .__ .__
    \_ |__ |__| ____ | |__ ____ ___ ___
    | __ \| |/ \| | \_/ __ \\ \/ /
    | \_\ \ | | \ Y \ ___/ > <
    |___ /__|___| /___| /\___ >__/\_ \
    \/ \/ \/ \/ \/
    https://hub.docker.com/u/binhex/

    2019-03-30 16:03:25.720649 [info] Host is running unRAID
    2019-03-30 16:03:25.750854 [info] System information Linux 4af33b83e174 4.14.49-unRAID #1 SMP Mon Jun 11 16:21:07 PDT 2018 x86_64 GNU/Linux
    2019-03-30 16:03:25.788137 [info] PUID defined as '99'
    2019-03-30 16:03:25.834642 [info] PGID defined as '100'
    2019-03-30 16:03:25.916297 [info] UMASK defined as '000'
    2019-03-30 16:03:25.952626 [info] Permissions already set for volume mappings
    2019-03-30 16:03:25.998000 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
    2019-03-30 16:03:26.033826 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
    2019-03-30 16:03:26.068968 [info] VPN_ENABLED defined as 'yes'
    2019-03-30 16:03:26.128143 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/Netherlands.ovpn
    dos2unix: converting file /config/openvpn/Netherlands.ovpn to Unix format...
    2019-03-30 16:03:26.193627 [info] VPN remote line defined as 'remote nl.privateinternetaccess.com 1198'
    2019-03-30 16:03:26.229486 [info] VPN_REMOTE defined as 'nl.privateinternetaccess.com'
    2019-03-30 16:03:26.264624 [info] VPN_PORT defined as '1198'
    2019-03-30 16:03:26.307750 [info] VPN_PROTOCOL defined as 'udp'
    2019-03-30 16:03:26.344735 [info] VPN_DEVICE_TYPE defined as 'tun0'
    2019-03-30 16:03:26.377915 [info] VPN_PROV defined as 'pia'
    2019-03-30 16:03:26.413241 [info] LAN_NETWORK defined as '10.0.0.0/24'
    2019-03-30 16:03:26.449264 [info] NAME_SERVERS defined as '209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4'
    2019-03-30 16:03:26.483984 [info] VPN_USER defined as 'p7'
    2019-03-30 16:03:26.519129 [info] VPN_PASS defined as '90210'
    2019-03-30 16:03:26.552178 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS)
    2019-03-30 16:03:26.587060 [info] STRICT_PORT_FORWARD defined as 'yes'
    2019-03-30 16:03:26.618852 [info] ENABLE_PRIVOXY defined as 'yes'
    2019-03-30 16:03:26.654262 [info] Starting Supervisor...
    2019-03-30 16:03:26,929 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing
    2019-03-30 16:03:26,929 INFO Set uid to user 0 succeeded
    2019-03-30 16:03:26,933 INFO supervisord started with pid 7
    2019-03-30 16:03:27,936 INFO spawned: 'start-script' with pid 149
    2019-03-30 16:03:27,938 INFO spawned: 'watchdog-script' with pid 150
    2019-03-30 16:03:27,939 INFO spawned: 'privoxy-script' with pid 151
    2019-03-30 16:03:27,939 INFO reaped unknown pid 8
    2019-03-30 16:03:27,945 DEBG 'start-script' stdout output:
    [info] VPN is enabled, beginning configuration of VPN

    2019-03-30 16:03:27,945 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2019-03-30 16:03:27,945 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2019-03-30 16:03:27,946 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
    2019-03-30 16:03:27,953 DEBG 'watchdog-script' stderr output:
    dos2unix: converting file /config/core.conf to Unix format...

    2019-03-30 16:03:27,965 DEBG 'start-script' stdout output:
    [warn] Password contains characters which could cause authentication issues, please consider changing this if possible

    2019-03-30 16:03:28,059 DEBG 'start-script' stdout output:
    [info] Default route for container is 172.17.0.1

    2019-03-30 16:03:28,067 DEBG 'start-script' stdout output:
    [info] Adding 209.222.18.222 to /etc/resolv.conf

    2019-03-30 16:03:28,073 DEBG 'start-script' stdout output:
    [info] Adding 37.235.1.174 to /etc/resolv.conf

    2019-03-30 16:03:28,077 DEBG 'start-script' stdout output:
    [info] Adding 8.8.8.8 to /etc/resolv.conf

    2019-03-30 16:03:28,084 DEBG 'start-script' stdout output:
    [info] Adding 209.222.18.218 to /etc/resolv.conf

    2019-03-30 16:03:28,090 DEBG 'start-script' stdout output:
    [info] Adding 37.235.1.177 to /etc/resolv.conf

    2019-03-30 16:03:28,096 DEBG 'start-script' stdout output:
    [info] Adding 8.8.4.4 to /etc/resolv.conf

    2019-03-30 16:03:28,206 DEBG 'start-script' stdout output:
    [info] Docker network defined as 172.17.0.0/16

    2019-03-30 16:03:28,213 DEBG 'start-script' stdout output:
    [info] Adding 10.0.0.0/24 as route via docker eth0

    2019-03-30 16:03:28,214 DEBG 'start-script' stdout output:
    [info] ip route defined as follows...
    --------------------

    2019-03-30 16:03:28,216 DEBG 'start-script' stdout output:
    default via 172.17.0.1 dev eth0
    10.0.0.0/24 via 172.17.0.1 dev eth0
    172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2

    2019-03-30 16:03:28,216 DEBG 'start-script' stdout output:
    --------------------

    2019-03-30 16:03:28,222 DEBG 'start-script' stdout output:
    iptable_mangle 16384 1
    ip_tables 24576 3 iptable_mangle,iptable_filter,iptable_nat

    2019-03-30 16:03:28,223 DEBG 'start-script' stdout output:
    [info] iptable_mangle support detected, adding fwmark for tables

    2019-03-30 16:03:28,417 DEBG 'start-script' stdout output:
    [info] iptables defined as follows...
    --------------------

    2019-03-30 16:03:28,420 DEBG 'start-script' stdout output:
    -P INPUT DROP
    -P FORWARD ACCEPT
    -P OUTPUT DROP
    -A INPUT -i tun0 -j ACCEPT
    -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
    -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
    -A INPUT -s 10.0.0.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT
    -A INPUT -s 10.0.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT
    -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT
    -A INPUT -i lo -j ACCEPT
    -A OUTPUT -o tun0 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT
    -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT
    -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT
    -A OUTPUT -d 10.0.0.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT
    -A OUTPUT -s 172.17.0.0/16 -d 10.0.0.0/24 -o eth0 -p tcp -j ACCEPT
    -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
    -A OUTPUT -o lo -j ACCEPT

    2019-03-30 16:03:28,420 DEBG 'start-script' stdout output:
    --------------------

    2019-03-30 16:03:28,422 DEBG 'start-script' stdout output:
    [info] Starting OpenVPN...

    2019-03-30 16:03:28,475 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:28 2019 WARNING: file 'credentials.conf' is group or others accessible
    Sat Mar 30 16:03:28 2019 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018

    2019-03-30 16:03:28,475 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:28 2019 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10

    2019-03-30 16:03:28,476 DEBG 'start-script' stdout output:
    [info] OpenVPN started

    2019-03-30 16:03:28,476 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:28 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

    2019-03-30 16:03:28,477 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:28 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]46.166.190.219:1198
    Sat Mar 30 16:03:28 2019 UDP link local: (not bound)
    Sat Mar 30 16:03:28 2019 UDP link remote: [AF_INET]46.166.190.219:1198

    2019-03-30 16:03:28,927 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:28 2019 [de6130aaccbd799fd05c50e178d01bd5] Peer Connection Initiated with [AF_INET]46.166.190.219:1198

    2019-03-30 16:03:30,293 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:30 2019 auth-token received, disabling auth-nocache for the authentication token

    2019-03-30 16:03:30,293 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:30 2019 TUN/TAP device tun0 opened

    2019-03-30 16:03:30,293 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:30 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
    Sat Mar 30 16:03:30 2019 /usr/bin/ip link set dev tun0 up mtu 1500

    2019-03-30 16:03:30,296 DEBG 'start-script' stdout output:
    Sat Mar 30 16:03:30 2019 /usr/bin/ip addr add dev tun0 local 10.32.10.6 peer 10.32.10.5

    ,654 DEBG 'start-script' stdout output:
    Sat Mar 30 16:23:08 2019 SIGINT[hard,] received, process exiting

    2019-03-30 16:23:30,793 DEBG 'start-script' stdout output:
    [warn] OpenVPN process terminated, restarting OpenVPN...

     

    not sure if this part is in the posted log!


    2019-03-30 18:31:07,023 DEBG 'start-script' stdout output:
    [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200

    2019-03-30 18:31:07,103 DEBG 'start-script' stdout output:
    [warn] PIA endpoint 'nl.privateinternetaccess.com' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow
    [info] Please consider switching to one of the endpoints shown below

    2019-03-30 18:31:07,103 DEBG 'start-script' stdout output:
    [info] List of PIA endpoints that support port forwarding:-
    [info] ca-toronto.privateinternetaccess.com
    [info] ca-montreal.privateinternetaccess.com
    [info] ca-vancouver.privateinternetaccess.com
    [info] de-berlin.privateinternetaccess.com
    [info] de-frankfurt.privateinternetaccess.com
    [info] sweden.privateinternetaccess.com
    [info] swiss.privateinternetaccess.com
    [info] france.privateinternetaccess.com
    [info] czech.privateinternetaccess.com
    [info] spain.privateinternetaccess.com
    [info] ro.privateinternetaccess.com
    [info] israel.privateinternetaccess.com

    2019-03-30 18:31:07,114 DEBG 'start-script' stdout output:
    [info] Attempting to curl http://209.222.18.222:2000/?client_id=4c0079a3c8b77219f56d2b0ee70770a2301ba397ef3aab907654588370706880...

    2019-03-30 18:31:07,228 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 12 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:31:17,345 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 11 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:31:27,462 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 10 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:31:37,579 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 9 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:31:47,694 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 8 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:31:57,812 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 7 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:07,928 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 6 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:18,045 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0

    2019-03-30 18:32:18,045 DEBG 'start-script' stdout output:
    [info] 5 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:18,045 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0

    2019-03-30 18:32:18,045 DEBG 'start-script' stdout output:
    [info] 5 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:28,164 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 4 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:28,164 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 4 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:38,279 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 3 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:48,394 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 2 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:32:58,513 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx
    [warn] Exit code 7 from curl != 0
    [info] 1 retries left
    [info] Retrying in 10 secs...

    2019-03-30 18:33:08,628 DEBG 'start-script' stdout output:
    [warn] Response code 000 from curl != 2xx, exhausted retries exiting script...

    2019-03-30 18:33:08,629 DEBG 'start-script' stdout output:
    [warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...

    2019-03-30 18:33:08,631 DEBG 'start-script' stdout output:
    Sat Mar 30 18:33:08 2019 event_wait : Interrupted system call (code=4)

    2019-03-30 18:33:08,640 DEBG 'start-script' stdout output:
    Sat Mar 30 18:33:08 2019 /usr/bin/ip addr del dev tun0 local 10.4.10.6 peer 10.4.10.5

    2019-03-30 18:33:08,652 DEBG 'st

     

     

     

     

     

     

     

     

     

     

     

     

     



     

  14. Hello, went to do some stuff on the computer and none of the apps or VM are showing anymore.

    Everything has disappear, what do I do now?

    I dont really want to start from the beginning, It took me sometime to understand how to get them 

    setup and running the way I wanted it to work. I still didnt get then  working correctly but now everything is gone but the files!

  15. 12 hours ago, John_M said:

     

    What is the "it" here? What are you trying to achieve?

    There is a lot of freezing, programs not responding.

    Like when watching youtube videos it would hang for 10 sec before resuming. I have a GPU passthrough card.

    When I come back to the computer it would be none responsive for 2- 15 sec.

    When starting programs it would take alot longer to boot.

    the everyday running on a OS is not smooth. 

  16. 1 hour ago, John_M said:

    Clearly you do have a processor installed! The lack of information in the System Information window is just cosmetic because your CPU is correctly detailed in the lscpu.txt file in your diagnostics so it will be something simple like its identification string not being recognised.

     

    VMs only report base clock speeds.

     

    In your Windows file copy example you are copying a lot of very small files. 10 remaining (50.8 KB) so an average of 5 KB each and each carries a significant network and file system overhead. Try copying one or two very large files (10 GB or so) instead.

     

    Your syslog is full of this:

    
    Apr 25 22:54:53 KRAKEN root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token

    Close all stale browser windows and reopen just one.

     

    And this:

    
    Apr 25 22:37:36 KRAKEN rc.diskinfo[9525]: PHP Warning: Use of undefined constant byte11h - assumed 'byte11h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662

    I recommend that you uninstall the Preclear plugin. Then your syslog will be a lot more readable.

     

    Okay I have done the copy with 7 files 10GB total and the speed goes up and down sometime even going real slow to look like it stop. each file is no less than 1GB and one that is 2GB

    I have also uninstalled preclear.

     

    Last is the slow to run apps and the freezing any help for those?

    unraid04.jpg

    unraid05.jpg

    unraid06.jpg

  17. Hello, I'm a newbie to UNRAID and and trying it for the first time. I have been trying to get UNRAID up and running but keep running into one problem or another.

    I have come a long way and feel I'm almost there but not sure what to do about these small problems that are happening.

     

    1)- First problem is that UNRAID say my CPU is not installed and I am unsure how to fix this as showed in the photo below marked unraid02.jpg

    I am not seeing the CPU boost to 2.55GHz or 3.0 GHz. it stays at 2.0 GHz even if the cpuc is being used 100%. I am wondering if this is because the CPU driver or

    whatever needs to be installed. Photo unraid03.jpg

     

    2)-2nd I'm getting FREEZING when in the GUI LINUX/WINDOWs, it will become unresponsive for sometime and then respond. I notice it when I return to the GUI to run a program or use the VM.

    I would really like to find out what is going on with it so that I can fix it.

     

    3)- Slow. sometime it's slow to load programs and slow to transfer files. 

    I am copying from from the share or loading a app but it is very slow I feel considering the NVME cache, the hard drives and the system.

    I'm not sure if it's because it's a VM, since this is the first time I'm running all my apps in a VM. Photo unraid01.jpg

    I tried to get a better photo to post but that one show how it starts off fast then goes much slower.

    On some transfer it drops down to KBs and I'm not sure why.

     

    I am almost ready to go live with this build but the slow performance and other stuff are stopping me from doing to and I am loving UNRAID but if I can't get these freezing, slow down  correct I

    will have to go to windows only and I really dont want to do that.

    If anyone can help me with these problem that would be total great!

    unraid02.jpg

    unraid03.jpg

    unraid01.jpg

    kraken-diagnostics-20180426-1206.zip

  18. On 4/22/2018 at 9:03 AM, John_M said:

    The best explanation of the tendency to freeze when idle that I've read is here:

    In particular this:

     

     

    So to ensure stability under light load there's a desire to avoid entering the C6 state. Some BIOSes have the option to disable C6 while others only have the option to disable all C states, which is a bit drastic.  So the zenstates utility was written.

    Yeah the EYPC is that you can only disable C-STATES and that's what I have done and I have not had any reboots or system crashes since then.

    THX,everyone for there help on this, I would have had a hard time finding that out!

  19. On 4/20/2018 at 6:22 PM, John_M said:

    The Ryzen specific tweak is in the post that johnnie.black linked:

     

     

    Hello, I have not done that yet but I have turned off C-STATES in my bios.

    I have also copied 2TB of data to the UNRAID array and the system has not crashed.

    I have more data to copy over to the array, I should be done by monday and if no more crashes then that might be the solution to the problem.

    Why do I need to do that and what is the difference.

    kraken-diagnostics-20180422-0449.zip

  20. 5 hours ago, John_M said:

    The syslog snippet was useless because it only covers a period of 20 seconds. Your more recently posted diagnostics look much better, though still spammed by the Preclear plugin. There's nothing in there to suggest a cause for any crashing. Try johnnie.black's suggestion. I don't know if Epyc is affected by the C6 states issue that affects Ryzen but it's worth a try. Also consider updating to unRAID 6.5.1-rc6 as it uses a newer kernel and fixes a couple of issues present in 6.5.0.

    Where do you find the update, I looked but I can't seem to find it, I will try the ryzen fix if I can that one too.

    You got to love this stufff!! :)

  21. 1 hour ago, John_M said:

    What is the syslog snippet meant to show? Everything in it is network related. Nothing to do with disks at all.

    it's meant to show that removing the Icydock hard drive bay shows no errors, but when I us it I get ata7, ata6, ata5 erorrs and it saying that it was frozen.

    I also posted it so that if there is something there that anyone can see.

    I am still getting system crashes, this time I have new cables and there are plugged into the hard drives.

    I dont know what else to do??!!!

    If it crashes again with the new cables I dont know what else to try!

    kraken-diagnostics-20180420-0034.zip

  22. Hey, thx for the tip and I have tried the new hard drive holder and there is no erros but it still crashed the system.

    So now I will try the new cable I have two set.

    If that doesn't work it might just be the unassign hard drive that might be cause the crash and I will replace it with another hard drive with data and see If I still get 

    a system crash.  there are no system crash running the system, or copying files from the unraid drives. Only from USB drive to UNRAID.

     

    Apr 19 22:14:22 KRAKEN avahi-daemon[9920]: New relevant interface vethb05fcc5.IPv6 for mDNS.
    Apr 19 22:14:22 KRAKEN avahi-daemon[9920]: Registering new address record for fe80::dc3c:2eff:fe18:653b on vethb05fcc5.*.
    Apr 19 22:14:24 KRAKEN kernel: docker0: port 3(veth6345fdf) entered blocking state
    Apr 19 22:14:24 KRAKEN kernel: docker0: port 3(veth6345fdf) entered disabled state
    Apr 19 22:14:24 KRAKEN kernel: device veth6345fdf entered promiscuous mode
    Apr 19 22:14:24 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth6345fdf: link is not ready
    Apr 19 22:14:24 KRAKEN kernel: docker0: port 3(veth6345fdf) entered blocking state
    Apr 19 22:14:24 KRAKEN kernel: docker0: port 3(veth6345fdf) entered forwarding state
    Apr 19 22:14:24 KRAKEN kernel: docker0: port 3(veth6345fdf) entered disabled state
    Apr 19 22:14:25 KRAKEN kernel: eth0: renamed from veth2916362
    Apr 19 22:14:25 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6345fdf: link becomes ready
    Apr 19 22:14:25 KRAKEN kernel: docker0: port 3(veth6345fdf) entered blocking state
    Apr 19 22:14:25 KRAKEN kernel: docker0: port 3(veth6345fdf) entered forwarding state
    Apr 19 22:14:26 KRAKEN avahi-daemon[9920]: Joining mDNS multicast group on interface veth6345fdf.IPv6 with address fe80::40bf:d9ff:fe70:aa26.
    Apr 19 22:14:26 KRAKEN avahi-daemon[9920]: New relevant interface veth6345fdf.IPv6 for mDNS.
    Apr 19 22:14:26 KRAKEN avahi-daemon[9920]: Registering new address record for fe80::40bf:d9ff:fe70:aa26 on veth6345fdf.*.
    Apr 19 22:14:28 KRAKEN kernel: docker0: port 4(veth7596926) entered blocking state
    Apr 19 22:14:28 KRAKEN kernel: docker0: port 4(veth7596926) entered disabled state
    Apr 19 22:14:28 KRAKEN kernel: device veth7596926 entered promiscuous mode
    Apr 19 22:14:28 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth7596926: link is not ready
    Apr 19 22:14:28 KRAKEN kernel: docker0: port 4(veth7596926) entered blocking state
    Apr 19 22:14:28 KRAKEN kernel: docker0: port 4(veth7596926) entered forwarding state
    Apr 19 22:14:28 KRAKEN kernel: docker0: port 4(veth7596926) entered disabled state
    Apr 19 22:14:29 KRAKEN kernel: eth0: renamed from vethf3d48bc
    Apr 19 22:14:29 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7596926: link becomes ready
    Apr 19 22:14:29 KRAKEN kernel: docker0: port 4(veth7596926) entered blocking state
    Apr 19 22:14:29 KRAKEN kernel: docker0: port 4(veth7596926) entered forwarding state
    Apr 19 22:14:30 KRAKEN avahi-daemon[9920]: Joining mDNS multicast group on interface veth7596926.IPv6 with address fe80::50d1:93ff:fee0:d4e5.
    Apr 19 22:14:30 KRAKEN avahi-daemon[9920]: New relevant interface veth7596926.IPv6 for mDNS.
    Apr 19 22:14:30 KRAKEN avahi-daemon[9920]: Registering new address record for fe80::50d1:93ff:fee0:d4e5 on veth7596926.*.
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered blocking state
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered disabled state
    Apr 19 22:14:32 KRAKEN kernel: device veth3ffeeea entered promiscuous mode
    Apr 19 22:14:32 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth3ffeeea: link is not ready
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered blocking state
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered forwarding state
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered disabled state
    Apr 19 22:14:32 KRAKEN kernel: eth0: renamed from veth2473925
    Apr 19 22:14:32 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3ffeeea: link becomes ready
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered blocking state
    Apr 19 22:14:32 KRAKEN kernel: docker0: port 5(veth3ffeeea) entered forwarding state
    Apr 19 22:14:33 KRAKEN avahi-daemon[9920]: Joining mDNS multicast group on interface veth3ffeeea.IPv6 with address fe80::1097:a0ff:fe2f:3b5d.
    Apr 19 22:14:33 KRAKEN avahi-daemon[9920]: New relevant interface veth3ffeeea.IPv6 for mDNS.
    Apr 19 22:14:33 KRAKEN avahi-daemon[9920]: Registering new address record for fe80::1097:a0ff:fe2f:3b5d on veth3ffeeea.*.
    Apr 19 22:14:36 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered blocking state
    Apr 19 22:14:36 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered disabled state
    Apr 19 22:14:36 KRAKEN kernel: device veth2a3ea73 entered promiscuous mode
    Apr 19 22:14:36 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth2a3ea73: link is not ready
    Apr 19 22:14:36 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered blocking state
    Apr 19 22:14:36 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered forwarding state
    Apr 19 22:14:36 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered disabled state
    Apr 19 22:14:37 KRAKEN kernel: eth0: renamed from vethd5a7391
    Apr 19 22:14:37 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2a3ea73: link becomes ready
    Apr 19 22:14:37 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered blocking state
    Apr 19 22:14:37 KRAKEN kernel: docker0: port 6(veth2a3ea73) entered forwarding state
    Apr 19 22:14:39 KRAKEN avahi-daemon[9920]: Joining mDNS multicast group on interface veth2a3ea73.IPv6 with address fe80::6c3e:7ff:fe0b:da1c.
    Apr 19 22:14:39 KRAKEN avahi-daemon[9920]: New relevant interface veth2a3ea73.IPv6 for mDNS.
    Apr 19 22:14:39 KRAKEN avahi-daemon[9920]: Registering new address record for fe80::6c3e:7ff:fe0b:da1c on veth2a3ea73.*.
    Apr 19 22:14:40 KRAKEN kernel: docker0: port 7(veth470405d) entered blocking state
    Apr 19 22:14:40 KRAKEN kernel: docker0: port 7(veth470405d) entered disabled state
    Apr 19 22:14:40 KRAKEN kernel: device veth470405d entered promiscuous mode
    Apr 19 22:14:40 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth470405d: link is not ready
    Apr 19 22:14:40 KRAKEN kernel: docker0: port 7(veth470405d) entered blocking state
    Apr 19 22:14:40 KRAKEN kernel: docker0: port 7(veth470405d) entered forwarding state
    Apr 19 22:14:40 KRAKEN kernel: docker0: port 7(veth470405d) entered disabled state
    Apr 19 22:14:41 KRAKEN kernel: eth0: renamed from veth1205ba2
    Apr 19 22:14:41 KRAKEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth470405d: link becomes ready
    Apr 19 22:14:41 KRAKEN kernel: docker0: port 7(veth470405d) entered blocking state
    Apr 19 22:14:41 KRAKEN kernel: docker0: port 7(veth470405d) entered forwarding state
    Apr 19 22:14:42 KRAKEN avahi-daemon[9920]: Joining mDNS multicast group on interface veth470405d.IPv6 with address fe80::2413:25ff:feca:a54.
    Apr 19 22:14:42 KRAKEN avahi-daemon[9920]: New relevant interface veth470405d.IPv6 for mDNS.

×
×
  • Create New...