Elefantito

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Elefantito's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Is it possible to use CA to install something like this ? I mean, can we use it to search in github?
  2. Confirmed, this fixed it. I can now run my pi hole docker again. TY bonienl
  3. Looks like you nailed it. I See the option now. Will test & report back
  4. root@Tower:~# docker network ls NETWORK ID NAME DRIVER SCOPE 97230223115a bridge bridge local f4da55d9d85d host host local b87989e7dca0 none null local I believe I used to have a "Custom Br0" option that allowed me to manually select an IP Address from within my network for this specific container.
  5. I'm in the same boat, the option to select "custom : br0" in the docker template is gone, so I can't assign specific containers their own IP addresses :(
  6. 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?
  7. 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.
  8. Hmmm just updated but I still don't see that string
  9. 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 : 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
  10. 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
  11. 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