Elefantito

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Posts posted by Elefantito

    [REPO] dmaxwell351 repo - Air Video HD, splunk

    in Docker Containers

    Posted

    7 hours ago, dmaxwell351 said:

    It's interesting because I have $SPLUNK_HOME defined after a vanilla install of splunk...

     

    Either way, it's set in the Dockerfile now, so the command to append the optimistic file locking setting should work!

     

    I was thinking the same thing, the variable definition is part of the instalation so I'm not sure why it isnt showing up.

    If you still have that vanilla install, can you check if $SPLUNK_DB is defined? 

    [REPO] dmaxwell351 repo - Air Video HD, splunk

    in Docker Containers

    Posted · Edited by Elefantito
    confirming

    7 hours ago, scloutier said:

    on github I see this in the dockerfile: 

     

    RUN echo "OPTIMISTIC_ABOUT_FILE_LOCKING = 1" >> $SPLUNK_HOME/etc/splunk-launch.conf

     

    I think $SPLUNK_HOME isn't defined

     

    ------------

     

    Since the $SPLUNK_HOME variable isn't defined (not sure why, but you can check by doing echo $SPLUNK_HOME) ,

    RUN echo "OPTIMISTIC_ABOUT_FILE_LOCKING = 1" >> $SPLUNK_HOME/etc/splunk-launch.conf creates a file in the /root/etc directory which is not read by Splunk.

     

    We either need to save that string in /opt/splunk/etc/splunk-conf or append a "SPLUNK_HOME=/opt/splunk" to the dockerfile before the echo string.

     

    [REPO] dmaxwell351 repo - Air Video HD, splunk

    in Docker Containers

    Posted · Edited by Elefantito

    On 4/3/2017 at 8:05 PM, dmaxwell351 said:

    Got splunk updated to 6.5.3! I haven't tested if it fixes the BTRFS issue yet, but hopefully that will do it since they do say it is supported now...

     

    Thanks for the update!

    I gave the docker a try, but even though the docker is up and running, the WEBUI was not available (connection refused)

     

    Looking at the logs, I still saw the dreaded " validating databases (splunkd validatedb) failed with code '1'. If you cannot resolve the issue(s) above after consulting documentation, please file a case online at http://www.splunk.com/page/submit_issue " error message , which is kind of strange, since I thought my data drives were formatted in XFS and not in BTRFS?

     

    Anyway, Google recommended adding this :

     

     

    Quote

    You'll want to append the following configuration option to $SPLUNK_HOME/etc/splunk-launch.conf:

     

     

     

    1. OPTIMISTIC_ABOUT_FILE_LOCKING = 1

     

     

     

     

     

    Once I did that, then restarted the splunk service and the webui came up.

    is it possible to add this fix to the docker so I don't have to add it everytime the docker restarts?

    Thanks

    [Support] brettm357 - UniFi

    in Docker Containers

    Posted

    On 4/2/2017 at 6:43 PM, brettm357 said:

    I would delete image and container restart Unraid and reinstall 

     

    update: just deleted my image and container and reinstalled tried both firefox and chrome without issues

     

    Did that and it worked =)

    Thanks!!

    [Support] brettm357 - UniFi

    in Docker Containers

    Posted · Edited by Elefantito

    10 hours ago, brettm357 said:

    What internet browser are you using?

     

    Chrome v57

     

    went into the docker, and I see an error in the server.log at /var/lib/unifi/logs# 

     

    [2017-04-02 10:41:09,724] <db-server> ERROR system - [exec] error, rc=14
    [2017-04-02 10:41:09,724] <db-server> INFO  db     - DbServer stopped
    [2017-04-02 10:41:09,724] <db-server> WARN  db     - DbServer not shutdown cleanly and need repairing on next startup
     

    Looks like there is something with the DB going on

     

    [Support] brettm357 - UniFi

    in Docker Containers

    Posted

    I'm having a hard time launching the web ui, I get a "connection refused" message.

    Logs are empty, but I see that the docker is running : 

     

    96d4cc145a79        brettm357/unifi         "/run.sh"              4 minutes ago       Up 4 minutes        0.0.0.0:6789->6789/tcp, 0.0.0.0:8080-8081->8080-8081/tcp, 0.0.0.0:8443->                                                                               8443/tcp, 0.0.0.0:8843->8843/tcp, 0.0.0.0:8880->8880/tcp   Unifi
     

    root@xxxx:~# netstat -apn | grep docker
    tcp        0      0 0.0.0.0:8843            0.0.0.0:*               LISTEN      29381/docker-proxy
    tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      29411/docker-proxy
    tcp        0      0 0.0.0.0:8880            0.0.0.0:*               LISTEN      29371/docker-proxy
    tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      29401/docker-proxy
    tcp        0      0 0.0.0.0:8337            0.0.0.0:*               LISTEN      22775/docker-proxy
    tcp        0      0 0.0.0.0:8443            0.0.0.0:*               LISTEN      29391/docker-proxy
    tcp        0      0 0.0.0.0:6789            0.0.0.0:*               LISTEN      29421/docker-proxy
     

     

    Any idea on where to look for clues on why this isnt working?

    Thanks