Menu

NCID Client Attempts Connect to 127.0.0.1 (which is not configured)

2021-09-26
2021-09-27
  • Dan Srebnick

    Dan Srebnick - 2021-09-26

    Hello:

    I am running the NCID client on Fedora 34 (using the packaged version).

    Every 15 seconds, the client tries to connect to a server on the local
    host. However, there is no server running on that host, it runs
    elsewhere.

    sourceforge.ncid.desktop[2690]: 127.0.0.1:3333 - couldn't open socket:
    connection refused

    A check of the ncid.conf shows that the only host configured it NOT
    127.0.0.1. And the client is properly communicating with the server.

    Bug or something I may have missed?

    Thanks for this great software.

     
    • Todd Andrews

      Todd Andrews - 2021-09-26

      Hi Dan,

      If the client is showing attempts to connect to 127.0.0.1:3333 but
      ncid.conf shows a different host, this could happen if ncid.conf is changed
      without restarting the client.

      If you go to the client and pick Server->Select NCID Server, what does it
      show as currently selected?

      And the client is properly communicating with the server.

      If it was properly communicating, it wouldn't be showing reconnect
      attempts. What are you seeing that indicates it is working ok?

      Edited to remove email reply text.

       

      Last edit: Todd Andrews 2021-09-26
  • Ed Attfield

    Ed Attfield - 2021-09-26

    If I were you, would be using "ps -ef | grep ncid" to see if there was more than one ncid running.
    The I would try "kill 2690" to see which one disappeared.

     
  • Dan Srebnick

    Dan Srebnick - 2021-09-27

    This is interesting, ncid shows as running even when it is not. If I explicitly start ncid, then there are 2. Something is autostarting the client in the background with no GUI display.

    It looks like net.sourceforge.ncid.desktop was dropped into my .config/autostart directory and it was being started in the background with the "On only desktop notifications" setting.

    I set autostart to Off and it seems to have eradicated the messages.

     

Log in to post a comment.