Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    looks like ipv6 on a ipv4 network
    metalefty
    @metalefty
    I also tried that.
    xrdp-sesrun silently finishes and no sessions created.
    I'll look into it later
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    and $? = 0
    metalefty
    @metalefty
    yep $?=0
    xrdp-sesrun utility not well-maintained because few users use it.
    however, you're certainly the one. it is a good chance to fix it.
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    90 if (g_tcp_connect(sck, argv[1], g_cfg.listen_port) == 0)
    the port, should that have a htons()?
    metalefty
    @metalefty
    wait 1m
    nope
    the port should be char*
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    ok, I am getting the code to build and see if I can resolve this
    metalefty
    @metalefty
    sorry, i'm leaving. laters.
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    I now have a better feel for where to look than yesterday, plus sleep, so maybe it will be fixed tonight
    matt335672
    @matt335672
    @shh-Its-a-Secret - are you saying your machine doesn't have ::1 on any interface?
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    it does not, no
    ipv6 is completely disabled on that network. sysctl disabled so its easy to turn on for those boxes if its relaly needed
    matt335672
    @matt335672

    There are definitely some issues in this area - see #1596.

    Could you try 127.0.0.2 ? Sounds barmy I know, but there's code which for reasons I don't fully understand looks for the string 127.0.0.1

    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    ok, and I know that linux for a long time has dealt with 127/8 differently
    same
    matt335672
    @matt335672
    Does the connect fail immediately, or does it take a while?
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    near immediate. I get the following (two log fails)
    The log reference is NULL - log not initialized properly
    connect error
    The log reference is NULL - log not initialized properly
    its not a timeout condition
    matt335672
    @matt335672
    OK - ta. I'll try to reproduce this here by dropping ::1 off a local box.
    No luck so far - working for me with no ::1. I'll have a step into the code.
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    just brought ipv6 up
    same, I think ipv6 is a red herring
    matt335672
    @matt335672

    The code I've just stepped through is pretty clean in terms of what it's doing.

    What does getent hosts localhost say on your box? Also nmap -p 3350 localhost?

    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    now with ipv6 reenabled getent is ::1
    it is also binding to ::1 3350 which is the port specified in sesman.ini
    matt335672
    @matt335672
    Have you got a firewall running on lo?
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    but it still does not want to work :/
    no
    matt335672
    @matt335672
    What does the nmap say, or can't you install it?
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    closed which is odd. that appears ot be where the problem is
    matt335672
    @matt335672
    Any containers involved maybe?
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    no snaps, this is not run in a netns
    any other containers I should look for?
    matt335672
    @matt335672
    Nothing I can think of.
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    trying something
    first hurdle overcome. I changed the bind addr to 0.0.0.0 to see if localhost was resolving weird or something. that worked (wont stay that way but it works)
    Xorg now starts
    matt335672
    @matt335672
    On my box, I've got sesman running on PID 16590. This shows both sesman and my local process are using the same network namespace:-
    $ lsns -p $$ | grep net
    4026531992 net         8  4792 mjb  /lib/systemd/systemd --user
    $ sudo lsns -p 16590 | grep net
    4026531992 net       197   1 root /sbin/init splash
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    so it appears that "ListenAddress=127.0.0.1" was the issue. ignore the resolv thing because it was an IP
    I also verified that the session is started properly, the GUI auto ran as it was configured to do. it was literally just the ListenAddress line in sesman.ini which was refusing connections. xubuntu 20.04
    thanks for your help
    matt335672
    @matt335672
    Thanks for the interesting chat!
    Ghost
    @ghost~5fc7898ad73408ce4ff57f45
    its ok, you can say time wasting :P
    matt335672
    @matt335672
    For info, just opened PR #1741 on this.