Segfault on linux alpine #8
Comments
|
I presume you downloaded the latest GitHub version? There are a couple of
fixes in there for old segfaults already.
Assuming that you did, are you able to run a debug (un-stripped) version
under GDB, and show me a back-trace of the crash? This assumes that the
previous sentence makes any sense to you at all?
Sadly I do not currently have an environment to run docker as it breaks my
LAN setup.
:)
Steve
…On Mon, 6 Mar 2017 at 15:29 Pascal Deschênes ***@***.***> wrote:
Trying to get astmanproxy up&running within a Linux alpine docker
container. Compilation performs perfectly, so does install, and actual
launch but it segfault while trying to establish AMI connection to upstream.
Not clear what could be the issue at this stage but I could share my
docker image if there's need to.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA5a47kFz78XjHcQyC4s3huTeT6Dj8oks5rjCZAgaJpZM4MUS13>
.
|
|
I’m onto v1.28.2 since this is the last release, which works perfectly on CentOS. I haven’t tried on master HEAD.
I’ll give it a shot with the latest and report back with a backtrace.
Pascal
… On Mar 6, 2017, at 10:33 AM, Steve Davies ***@***.***> wrote:
I presume you downloaded the latest GitHub version? There are a couple of
fixes in there for old segfaults already.
Assuming that you did, are you able to run a debug (un-stripped) version
under GDB, and show me a back-trace of the crash? This assumes that the
previous sentence makes any sense to you at all?
Sadly I do not currently have an environment to run docker as it breaks my
LAN setup.
:)
Steve
On Mon, 6 Mar 2017 at 15:29 Pascal Deschênes ***@***.***>
wrote:
> Trying to get astmanproxy up&running within a Linux alpine docker
> container. Compilation performs perfectly, so does install, and actual
> launch but it segfault while trying to establish AMI connection to upstream.
>
> Not clear what could be the issue at this stage but I could share my
> docker image if there's need to.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#8>, or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAA5a47kFz78XjHcQyC4s3huTeT6Dj8oks5rjCZAgaJpZM4MUS13>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJV2IAW7bKWW20-fHvg31xga6kRtSB7ks5rjCdHgaJpZM4MUS13>.
|
|
1.28.2 was the latest version, but I just pushed a patch which I thought
was already available on Github. Perhaps it will help?
Cheers,
Steve
On Mon, 6 Mar 2017 at 15:57 Pascal Deschênes <[email protected]>
wrote:
… I’m onto v1.28.2 since this is the last release, which works perfectly on
CentOS. I haven’t tried on master HEAD.
I’ll give it a shot with the latest and report back with a backtrace.
Pascal
> On Mar 6, 2017, at 10:33 AM, Steve Davies ***@***.***>
wrote:
>
> I presume you downloaded the latest GitHub version? There are a couple of
> fixes in there for old segfaults already.
>
> Assuming that you did, are you able to run a debug (un-stripped) version
> under GDB, and show me a back-trace of the crash? This assumes that the
> previous sentence makes any sense to you at all?
>
> Sadly I do not currently have an environment to run docker as it breaks
my
> LAN setup.
>
> :)
> Steve
>
> On Mon, 6 Mar 2017 at 15:29 Pascal Deschênes ***@***.***>
> wrote:
>
> > Trying to get astmanproxy up&running within a Linux alpine docker
> > container. Compilation performs perfectly, so does install, and actual
> > launch but it segfault while trying to establish AMI connection to
upstream.
> >
> > Not clear what could be the issue at this stage but I could share my
> > docker image if there's need to.
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#8>, or mute the
thread
> > <
https://github.com/notifications/unsubscribe-auth/AAA5a47kFz78XjHcQyC4s3huTeT6Dj8oks5rjCZAgaJpZM4MUS13
>
> > .
> >
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <
#8 (comment)>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/AAJV2IAW7bKWW20-fHvg31xga6kRtSB7ks5rjCdHgaJpZM4MUS13
>.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA5azv4vF9BGp55mbH-QTQwR_NL2FYZks5rjCzngaJpZM4MUS13>
.
|
|
Is there a docker container available for astmanproxy? I'd appreciate to know whether someone managed to got it up'n running ... |
|
I've certainly not done one yet. I see no reason why it should not be a
trivial task since it is just connecting and listening on the LAN, and has
only 2 basic config files.
I will leave it to someone who understands containers properly though :)
…On Thu, 17 Jan 2019 at 23:17, Florian Taeger ***@***.***> wrote:
Is there a docker container available for astmanproxy? I'd appreciate to
know whether someone managed to got it up'n running ...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA5a4ts6hsgcIejzK28w7eyX9cJJQ3kks5vEQRtgaJpZM4MUS13>
.
|
|
FYI: I've build a quick'n dirty docker container for astmanproxy: https://github.com/ftaeger/docker-astmanproxy and also published it on docker hub https://hub.docker.com/r/ftaeger/astmanproxy Enjoy. Works like a charme on a x86 docker host (not Raspberry ready yet, will work on that soon) |
|
And davies147: could you maybe push a new release with your latest patches, so I could adopt this version in my docker container ;-) I don't like to ship docker containers based on a "work-in-progress" repo rather than a frozen release version ... |
|
I'll make a note to do this for you.
I am travelling a lot the next 2 weeks, but feel free to remind me!
…On Fri, 8 Feb 2019 at 23:57, Florian Taeger ***@***.***> wrote:
And davies147: could you maybe push a new release with your latest
patches, so I could adopt this version in my docker container ;-) I don't
like to ship docker containers based on a "work-in-progress" repo rather
than a frozen release version ...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA5axG9wOiPPEdJyg4MlnuukOPexs3sks5vLg7RgaJpZM4MUS13>
.
|
|
I've tagged 1.28.3 as a release - let me know if there is a problem with
it. I also plan to add a slightly-more-experimental update with all my
newest changes.
Would you be okay if I linked to your Docker repo from an updated README
file?
Thanks,
Steve
…On Fri, 8 Feb 2019 at 23:57, Florian Taeger ***@***.***> wrote:
And davies147: could you maybe push a new release with your latest
patches, so I could adopt this version in my docker container ;-) I don't
like to ship docker containers based on a "work-in-progress" repo rather
than a frozen release version ...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAA5axG9wOiPPEdJyg4MlnuukOPexs3sks5vLg7RgaJpZM4MUS13>
.
|
|
Sure. Feel free. I'll spin up a 1.28.3 container during the next days and will upload it to the repo... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to get astmanproxy up&running within a Linux alpine docker container. Compilation performs perfectly, so does install, and actual launch but it segfault while trying to establish AMI connection to upstream.
Not clear what could be the issue at this stage but I could share my docker image if there's need to.
The text was updated successfully, but these errors were encountered: