Skip to content

writePump error from slackarchive #26

@Tycho-S

Description

@Tycho-S

Hi! I'm trying to get SlackArchive running as well, and I ran into a few issues that I was able to solve with the help of the issues mentioned here on github. Especially the elasticsearch one. Thanks for that!

I'm still having 2 issues remaining so I'm logging 2 issues for this, I hope that's ok. This is the first one. I still don't see anything on the web interface:

image

Now, I think this is to do with the 2 problems I'm seeing. The first one seems to do with the bot interfacing to the slackarchive docker. I see this in the logs:

slackarchive-bot_1       | nlopes/slack2019/02/17 20:53:32 websocket_managed_conn.go:307: Incoming Event: {"type": "hello"}
slackarchive_1           | 2019/02/17 20:53:33 writePump error: %!(EXTRA string=write tcp 172.18.0.4:8080->172.18.0.5:50174: write: broken pipe)
slackarchive_1           | 2019/02/17 20:53:33 Connection closed

Is this a common problem perhaps? I did set up the network as instructed, and I also made sure the bot token is the same in both yaml files..

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions