Closed baughmann closed 5 years ago
Very odd. It's like redis keeps restarting or something like that. Does your system have memory upwards of 4GiB?
The react bug should be fixed in develop
, I hope to make a new release today.
Very odd. It's like redis keeps restarting or something like that. Does your system have memory upwards of 4GiB?
The react bug should be fixed in
develop
, I hope to make a new release today.
Oh yes, I'm running on 32gb.
The log is actually misleading. I will trim it down. I restarted the container a few times after making some changes in my attempt to track the problem. The restart was from me. The OSError: Connection closed by server.
occurred every time the container was restarted.
Just bizarre. I'm trying to dig around to figure out where it might be getting held up, but I've had no luck so far (likely since I didn't write it lol).
It might be worth putting a watch
on docker-compose -f docker-compose.dev.yml ps
to see if anything is happening over there. Otherwise I'd also recommend doing a make stop
to shut down all services and then starting again.
@pudo I've actually done a docker system prune
and docker system prune --volumes
several times, even going so far as to re-pull the images after ensuring that docker is wiped clean. I've also tried on other OSes.
What version of Docker are you using? Maybe I can rollback to yours just to see.
What's in your aleph.env
, if I may ask?
I'm on 2.1.0.1 on OS X
What's in your aleph.env, if I may ask?
@pudo Just the default (minus adding my email to the admin list). I added the default aleph.env
that I'm using to my original post just for completeness.
I'm on 2.1.0.1 on OS X
I guess that settles the Docker version debate then haha.
The other possibility is that the docker networking isn't connecting things as it should. It may be worth entering the ingest-file
container and trying to ping redis
, see if that works. Also what the actual env var for REDIS_URL
in that container is.
@pudo The REDIS_URL
is redis://redis:6379/0
.
I was also able to successfully ping redis
:
# ping redis
PING redis (172.20.0.3) 56(84) bytes of data.
64 bytes from aleph_redis_1.aleph_default (172.20.0.3): icmp_seq=1 ttl=64 time=0.053 ms
64 bytes from aleph_redis_1.aleph_default (172.20.0.3): icmp_seq=2 ttl=64 time=0.081 ms
64 bytes from aleph_redis_1.aleph_default (172.20.0.3): icmp_seq=3 ttl=64 time=0.040 ms
64 bytes from aleph_redis_1.aleph_default (172.20.0.3): icmp_seq=4 ttl=64 time=0.055 ms
^C
--- redis ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 134ms
rtt min/avg/max/mdev = 0.040/0.057/0.081/0.015 ms
Technology makes no sense, I'm going into gardening.
@pudo Were there any additional steps I needed to take when getting setting up the developer environment on OS X, besides setting up the max_map_count
? Docker is usually just plug 'n play.
Technology makes no sense, I'm going into gardening.
That's a good move. I hear landscaping is where the big money is these days.
Well, the good news is I figured out how to correctly install the Mac OS dependencies. The page with the instructions on the wiki is poorly formatted.
Once homebrew is installed, you simply perform the following commands:
brew install leveldb
brew install icu4c
env CFLAGS=-I/usr/local/opt/icu4c/include
(or set it permanently in your .bash_profile
)
env LDFLAGS=-L/usr/local/opt/icu4c/lib
(ditto above)
PATH=$PATH:/usr/local/opt/icu4c/bin
(or set it permanently in usr
)
pip install pyicu
(or pip3 install pyicu
)
This, of course, does not resolve the upload freezing issue, but it does make me feel better.
Well, the good news is I figured out how to correctly install the Mac OS dependencies. The page with the instructions on the wiki is poorly formatted.
Once homebrew is installed, you simply perform the following commands:
brew install leveldb
brew install icu4c
env CFLAGS=-I/usr/local/opt/icu4c/include
(or set it permanently in your.bash_profile
)env LDFLAGS=-L/usr/local/opt/icu4c/lib
(ditto above)PATH=$PATH:/usr/local/opt/icu4c/bin
(or set it permanently inusr
)pip install pyicu
(orpip3 install pyicu
)
Thanks! I've added this to our newly growing documentation!
https://docs.alephdata.org/developers/ftm#optional-enhanced-transliteration-support
I'm gonna close this as "can't reproduce". Please let us know if you have further information, or if upgrading to a newer version removes the issue. Sorry not to be able to solve.
I am having the same problem. Docker 2.1.0.3 on Mac OSX 10.14.6. Cloned today, running make all
, the containers seems to spin up fine, uploading a document, and I can see log entries of the document being added in aleph_ingest-file_1
container. But in the UI it seems to be stuck on 25% update progress. Docker has 7GB of memory available.
@anderser Are you running this in production or development mode? In development mode you need to manually run the aleph worker, i.e. make shell
, them aleph worker
to commence indexing.
@pudo Well, that solved it. Was running dev mode yes. Thanks!
Same problem.
freezes at a certain percentage point. All the files have completed upload in-GUI and with the client, its just this processing part where things stop up.
Going to see how redis might be poked to improve this...
Can you try this again with the latest release, 3.8.5? There was a bug in the backend in 3.8.4.
Also check out: https://app.gitbook.com/@aleph/s/docs/developers/technical-faq#my-import-is-stuck-at-67-whats-wrong
I cannot seem to complete uploading a document (via the UI) or crawling a directory (via the CLI). It reaches a point always less than "30%" complete and completely freezes. I've been truing to trace the issue to no avail.
I'm running Docker 2.1.0.1 on Mac OS 10.14.6 (but I've also tried on an Ubuntu 18.04 VM). I'm following the "Developer Setup" guide (https://github.com/alephdata/aleph/wiki/Developer-setup). I attempted to follow the macOS instructions (here: https://github.com/alephdata/aleph/wiki/Running-on-macOS) but really cannot follow them because Homebrew complains that it's not a valid command. I've also increased the
max_map_count
on the host using Docker'sscreen
feature.For what it's worth, in order to avoid hitting the
catch
on line 79 ofDocumentUploadDialog.jsx
in the UI, I had to actually return something from theingestDocument.COMPLETE
reducer at line 21 ofcollectionStatus
in the UI (I changed() => {}
tostate => state
). This allowed me to use the UI without error.Below are the log outputs from the container
aleph_ingest-file_1
. There did not seem to be any interesting logs from the API, ElasticSearch, Redis, or ConvertDocument containers.aleph_ingest-file_1:
My
aleph.env
file:I'm still trying to trace this myself, but I'm just sort-of taking shots in the dark here. Could this be an error with my Docker version or something simple like that that I may have overlooked in the documentation?