Xebra error above my pay grade

    MIRAbeginnerbugs/issues
    dnealelo's icon
    dnealelo's icon
    dnealelo
    Jan 11 2017 | 1:31 am
    Hello Braintrust -- I keep getting this error popping up in my console when I'm running a patch with Mira in it:
    xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known
    The connection appears to work fine, but the error pops up every several seconds, so it interferes with using my console to track output while I'm problem solving the patch. I am running the latest versions of Max and Mira on OS X Yosemite 10.10.5 (it's a 2010 iMac, so I'm kind of done upgrading the OS) and iOS 9.3.5 on an iPad3.
    Can anyone direct me what to do to fix this error?
    • Bob's icon
      Bob's icon
      Bob
      Dec 08 2017 | 2:07 am
      I have the same issue with Max 7.3.4 on my mid-2015 MBP, El Capitain, with iOS 11.1.2 on an iPad Air 2, running MIRA 1.2.1 - it's probably trivial, but it would be good to know...
      Share
    • hanstutschku's icon
      hanstutschku's icon
      hanstutschku
      Feb 11 2023 | 1:37 pm
      Well, years and many Max versions later (currently 8.5.3) , I'm still getting this error: xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known
    • cahen's icon
      cahen's icon
      cahen
      Mar 18 2023 | 9:23 am
      same : xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known
      any possible explanation ?
      all OS/Max/libraries up to date !
    • sebastien ruiz's icon
      sebastien ruiz's icon
      sebastien ruiz
      Apr 18 2023 | 7:31 am
      xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known
      Same for me: Apple M1 Pro, Mac os: 12.6.4
      Also they appears after deleting the mira patch inside.
    • Bob's icon
      Bob's icon
      Bob
      Apr 18 2023 | 1:10 pm
      MIRA for me as an av performer and PhD researcher, has been one of THE most helpful and liberating software devs in MAX - because it allows us to move from numbers to gesture!
      Below is a what ChatGPT said in response to my question: “Is there any possible explanation for why this error appears in MAX/MSP: ‘xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known’? “The error message "xebra_global: XEBListeningConnection_ListenProc: Error accepting connection: 670008 nodename nor servname provided, or not known" in MAX/MSP's MIRA can occur for a few different reasons.
      One possible explanation is that the Xebra server is not running or is not installed properly. In this case, MAX/MSP is unable to establish a connection with the server and generates the error message.
      Another possibility is that there is an issue with the network settings or firewall configuration, preventing the connection from being established. This can include issues such as incorrect network addresses or port numbers, or firewalls blocking the connection.
      Additionally, the error message could also indicate a problem with the MAX/MSP or MIRA software itself, such as a bug or compatibility issue. In this case, the error message would likely appear consistently or in a particular set of circumstances.
      To troubleshoot this error, it's important to check the Xebra server status, network settings, and firewall configuration, and ensure that they are all set up correctly. It may also be helpful to consult the MAX/MSP and MIRA documentation, and to search online forums for similar issues and solutions.”