This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-18
Channels
- # admin-announcements (1)
- # beginners (4)
- # boot (18)
- # cider (4)
- # cljsrn (17)
- # clojure (77)
- # clojure-austin (6)
- # clojure-greece (6)
- # clojure-spec (81)
- # clojure-uk (6)
- # clojurescript (32)
- # code-art (2)
- # core-async (12)
- # cursive (1)
- # datomic (1)
- # emacs (15)
- # funcool (1)
- # hoplon (108)
- # om (9)
- # onyx (83)
- # planck (1)
- # re-frame (3)
- # reagent (4)
- # specter (6)
- # spirituality-ethics (4)
- # yada (9)
Getting another error:
peer_1 | Caused by: org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /onyx/1/ledgers/cookies/172.17.0.4:3196
that's the only error I can find... This is using the https://github.com/onyx-platform/onyx-twitter-sample example
@aaelony: Did the peer fail to start up due to that exception?
peer_1 | 16-Jun-18 00:11:12 5c9dcffe2327 INFO [onyx.log.failure-detector] - Starting peer failure detector
peer_1 | 16-Jun-18 00:11:12 5c9dcffe2327 INFO [onyx.log.failure-detector] - Starting peer failure detector
peer_1 | 16-Jun-18 00:11:12 5c9dcffe2327 FATAL [onyx.system] -
peer_1 | twit.core.main
peer_1 | ...
peer_1 | twit.core/-main core.clj: 69
peer_1 | twit.core/-main core.clj: 79
peer_1 | lib-onyx.peer/start-peer peer.clj: 9
peer_1 | onyx.api/start-env api.clj: 316
peer_1 | onyx.api/start-env api.clj: 319
peer_1 | onyx.system.OnyxDevelopmentEnv/start system.clj: 88
peer_1 | onyx.system/rethrow-component system.clj: 80
peer_1 | onyx.system.OnyxDevelopmentEnv/fn system.clj: 89
peer_1 | com.stuartsierra.component/start-system component.cljc: 163
peer_1 | ...
peer_1 | com.stuartsierra.component/update-system component.cljc: 129
peer_1 | com.stuartsierra.component/update-system component.cljc: 135
peer_1 | clojure.core/reduce core.clj: 6544
peer_1 | ...
peer_1 | com.stuartsierra.component/update-system/fn component.cljc: 139
peer_1 | com.stuartsierra.component/try-action component.cljc: 117
peer_1 | clojure.core/apply core.clj: 648
peer_1 | ...
peer_1 | com.stuartsierra.component/fn/G component.cljc: 5 (repeats 2 times)
peer_1 | onyx.state.bookkeeper.BookieServers/start bookkeeper.clj: 108
peer_1 | clojure.core/mapv core.clj: 6618
peer_1 | clojure.core/reduce core.clj: 6544
peer_1 | ...
peer_1 | clojure.core/mapv/fn core.clj: 6627
peer_1 | onyx.state.bookkeeper.BookieServers/fn bookkeeper.clj: 109
peer_1 | onyx.state.bookkeeper.BookieMonitor/start bookkeeper.clj: 75
peer_1 | onyx.state.bookkeeper.Bookie/start bookkeeper.clj: 37
peer_1 | org.apache.bookkeeper.proto.BookieServer.<init> BookieServer.java: 87
peer_1 | org.apache.bookkeeper.proto.BookieServer.<init> BookieServer.java: 95
peer_1 | org.apache.bookkeeper.proto.BookieServer.newBookie BookieServer.java: 107
peer_1 | org.apache.bookkeeper.bookie.Bookie.<init> Bookie.java: 466
peer_1 | org.apache.bookkeeper.bookie.Bookie.checkEnvironment Bookie.java: 362
peer_1 | org.apache.bookkeeper.bookie.Cookie.writeToZooKeeper Cookie.java: 213
peer_1 | org.apache.zookeeper.ZooKeeper.create ZooKeeper.java: 783
peer_1 | org.apache.zookeeper.KeeperException.create KeeperException.java: 51
peer_1 | org.apache.zookeeper.KeeperException.create KeeperException.java: 119
peer_1 | org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /onyx/1/ledgers/cookies/172.17.0.4:3197
peer_1 | code: -110
peer_1 | path: "/onyx/1/ledgers/cookies/172.17.0.4:3197"
peer_1 | org.apache.bookkeeper.bookie.BookieException$InvalidCookieException: org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /onyx/1/ledgers/cookies/172.17.0.4:3197
peer_1 | code: 0
peer_1 | clojure.lang.ExceptionInfo: Error in component :bookkeeper in system onyx.system.OnyxDevelopmentEnv calling #'com.stuartsierra.component/start
peer_1 | component: #<Bookie Servers>
peer_1 | function: #'com.stuartsierra.component/start
peer_1 | reason: :com.stuartsierra.component/component-function-threw-exception
peer_1 | system: <#C051WKSP3>.system.OnyxDevelopmentEnv{:monitoring #<NoOp Monitoring Agent>, :logging-config #<Logging Configuration>, :bookkeeper #<Bookie Servers>, :log #<ZooKeeper Component>}
peer_1 | system-key: :bookkeeper
peer_1 |
peer_1 | Exception in thread "main" org.apache.bookkeeper.bookie.BookieException$InvalidCookieException: org.apache.zookeeper.KeeperException$NodeExistsException: KeeperErrorCode = NodeExists for /onyx/1/ledgers/cookies/172.17.0.4:3197
peer_1 | at org.apache.bookkeeper.bookie.Bookie.checkEnvironment(Bookie.java:366)
peer_1 | at org.apache.bookkeeper.bookie.Bookie.<init>(Bookie.java:466)
peer_1 | at org.apache.bookkeeper.proto.BookieServer.newBookie(BookieServer.java:107)
peer_1 | at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:95)
peer_1 | at org.apache.bookkeeper.proto.BookieServer.<init>(BookieServer.java:87)
peer_1 | at onyx.state.bookkeeper.Bookie.start(bookkeeper.clj:37)
peer_1 | at onyx.state.bookkeeper.BookieMonitor.start(bookkeeper.clj:75)
peer_1 | at onyx.state.bookkeeper.BookieServers$fn__16430.invoke(bookkeeper.clj:109)
peer_1 | at clojure.core$mapv$fn__6953.invoke(core.clj:6627)
peer_1 | at clojure.lang.PersistentVector.reduce(PersistentVector.java:341)
peer_1 | at clojure.core$reduce.invokeStatic(core.clj:6544)
peer_1 | at clojure.core$mapv.invokeStatic(core.clj:6618)
peer_1 | at clojure.core$mapv.invoke(core.clj:6618)
peer_1 | at onyx.state.bookkeeper.BookieServers.start(bookkeeper.clj:108)
peer_1 | at com.stuartsierra.component$fn__6831$G__6825__6833.invoke(component.cljc:5)
peer_1 | at com.stuartsierra.component$fn__6831$G__6824__6836.invoke(component.cljc:5)
peer_1 | at clojure.lang.Var.invoke(Var.java:379)
peer_1 | at clojure.lang.AFn.applyToHelper(AFn.java:154)
peer_1 | at clojure.lang.Var.applyTo(Var.java:700)
peer_1 | at clojure.core$apply.invokeStatic(core.clj:648)
peer_1 | at clojure.core$apply.invoke(core.clj:641)
@aaelony: https://github.com/onyx-platform/onyx/blob/e4f432364c9ce3c7b75271f04c8bbbf21fb487d4/doc/user-guide/faq.md#cookie-exception
It's on your docker host
Your using docker-compose up right?
On Linux?
Where are your containers running
Ok yea then you can clear the /tmp directory on your docker-machine host
Coming home from the gym, I can help more in a few minutes
$ docker-machine ssh aa-machine
## .
## ## ## ==
## ## ## ## ## ===
/"""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\_______/
_ _ ____ _ _
| |__ ___ ___ | |_|___ \ __| | ___ ___| | _____ _ __
| '_ \ / _ \ / _ \| __| __) / _` |/ _ \ / __| |/ / _ \ '__|
| |_) | (_) | (_) | |_ / __/ (_| | (_) | (__| < __/ |
|_.__/ \___/ \___/ \__|_____\__,_|\___/ \___|_|\_\___|_|
Boot2Docker version 1.11.2, build HEAD : a6645c3 - Wed Jun 1 22:59:51 UTC 2016
Docker version 1.11.2, build b9f10c9
docker@aa-machine:~$ ls -hl /tmp
lrwxrwxrwx 1 root root 13 Jun 17 23:00 /tmp -> /mnt/sda1/tmp/
docker@aa-machine:~$ df -kh /tmp
Filesystem Size Used Available Use% Mounted on
/dev/sda1 17.9G 3.3G 13.7G 19% /mnt/sda1
Your using an unmodified clone of the onyx Twitter sample?
basically, just cloned the repo then did:
Set your twitter API keys in docker-compose.yaml
lein do clean, uberjar; docker build -t peerimage .
docker-compose up
docker-compose run --entrypoint=java peer "-cp" "/opt/peer.jar" "twit.core" "submit-job" "trending-hashtags" "-p" ":docker"
try docker-compose rm -v
then docker-compose up
-v
drops the volumes
$ docker-compose rm -v
WARNING: Not including one-off containers created by `docker-compose run`.
To include them, use `docker-compose rm --all`.
This will be the default behavior in the next version of Compose.
No stopped containers
docker-compose kill
first
$ docker-compose kill
Killing onyxtwittersample_peer_1 ... done
Killing onyxtwittersample_mysql_1 ... done
Killing onyxtwittersample_zookeeper_1 ... done
alright then drop the containers and their volumes
that’ll get you into a clean state
docker-compose rm -v
That's a clean start.
so the peers booted up?
now you have to submit a job, the cluster is currently in a waiting state
docker-compose run --entrypoint=java peer "-cp" "/opt/peer.jar" "twit.core" "submit-job" "trending-hashtags" "-p" ":docker”
Yea if you cancel the window with docker compose the containers will come down
for future reference, -d
starts the docker-compose setup in “daemon” mode
so once that comes back, you should see a job id if everything was successful
then you can look in the Trending
table in the onyx
db that was started up
if your on a mac, mycli
is pretty good
brew install mycli
mycli -h 192.168.99.101 -u admin -p “mypass"
uhh try it with 192.168.99.100
i dont know where your docker machine is
$ docker-machine ls
NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS
aa-machine * virtualbox Running v1.11.2
And your peer logs look fine?
No this is a docker-compose thing
docker-compose logs
Ah gotcha
$ docker-compose logs | grep error peer_1 | # A fatal error has been detected by the Java Runtime Environment: peer_1 | # An error report file with more information is saved as:
Can I get the output from that, that’s most likely my problem