C-gate Server crashing in Linux

Discussion in 'C-Bus Toolkit and C-Gate Software' started by skarotech, Apr 12, 2020.

  1. skarotech

    skarotech

    Joined:
    Apr 12, 2020
    Messages:
    1
    Likes Received:
    0
    I am starting out with C-Gate, and managed to get it up and running all ok on Windows (using the Toolkit) and then via telnet can open and start a project. However the same setup/project file in Linux (both ARM & x64) seems to crash whenever connecting to the CNI with the following error.

    Clipsal C-Gate(TM) v2.11.5 (build 3255)
    Logging to file: logs/event.txt
    java.lang.NullPointerException
    at bG.aC(ProGuard:9177)
    at bG.a(ProGuard:106)
    at com.clipsal.cgate.project.Project.g(ProGuard:5103)
    at hW.a(ProGuard:204)
    at ir.a(ProGuard:53)
    at ha.a(ProGuard:1066)
    at com.clipsal.cgate.cmd.Command.c(ProGuard:229)
    at hk.a(ProGuard:62)
    at com.clipsal.cgate.cmd.Command.c(ProGuard:229)
    at gV.a(ProGuard:177)
    at gR.run(ProGuard:4502)
    at java.lang.Thread.run(Thread.java:745)

    The logs from my C-gate session are (you will see the error #e# 20200412-121903 903 sys Critical Server Exception) and it just hangs....anyone have any ideas ??

    project start VOICE
    #e# 20200412-121903 761 cmd1 - Command: project start VOICE
    #e# 20200412-121903 758 //VOICE/254 - Network parameters: sync-time=3600, startup-delay=0, cbus-application=56, response-delay=5500, network.retries=2, network.error.commands-failed=3, network.retries.pci-check=1, cbus-tx-delay=250, report-new-objects=false, auto-reopen=true, reopen-delay=15000, speed-write=true, pci-flow-control=true, local-flow-control=false, sync-fast-pci=true, comms-debug=false, use-queue-sweeper=true, allow-fast-start=false, network.application-connect=true, network.simultaneous-identifies=5, network.pci.poll-interval=60000
    #e# 20200412-121903 755 //VOICE/254 - InterfaceState=opening, TargetState=running
    #e# 20200412-121903 757 //VOICE/254 - State=new Previous=(unchanged) Reason=Interface Opening
    #e# 20200412-121903 903 sys Critical Server Exception: refer exception.info for details
    #e# 20200412-121903 758 //VOICE/254 - Network parameters: sync-time=3600, startup-delay=0, cbus-application=56, response-delay=5500, network.retries=2, network.error.commands-failed=3, network.retries.pci-check=1, cbus-tx-delay=250, report-new-objects=false, auto-reopen=true, reopen-delay=15000, speed-write=true, pci-flow-control=true, local-flow-control=false, sync-fast-pci=true, comms-debug=false, use-queue-sweeper=true, allow-fast-start=false, network.application-connect=true, network.simultaneous-identifies=5, network.pci.poll-interval=60000
    #e# 20200412-121903 757 //VOICE/254 - State=new Previous=(unchanged) Reason=starting threads
    #e# 20200412-121903 790 //VOICE/254 - rx thread init
    #e# 20200412-121903 899 sys Debug: New Command Context: cc002 = Network 254 pci reset
    #e# 20200412-121903 735 //VOICE/254 - cc002 sent cmd: ||
    #e# 20200412-121903 734 //VOICE/254 - response: || processed by network.
    #e# 20200412-121903 735 //VOICE/254 - cc002 sent cmd: @1A2001
    #e# 20200412-121904 765 //VOICE/254 - got packet confirm: l.
    #e# 20200412-121904 734 //VOICE/254 - response: 8220F965 accepted as short form by command: @1A2001
    #e# 20200412-121904 899 sys Debug: New Command Context: cc003 = Network 254 connection check
    #e# 20200412-121904 735 //VOICE/254 - cc003 sent cmd (fastpci): \46F9002101g (254: \46F9002101g)
    #e# 20200412-121904 765 //VOICE/254 - got packet confirm: g.
    #e# 20200412-121904 734 //VOICE/254 - response: 890150434C4F43414C3444 accepted as short form by command: \46F9002101g
    #e# 20200412-121904 755 //VOICE/254 - InterfaceState=running, TargetState=running
    #e# 20200412-121904 757 //VOICE/254 - State=new Previous=(unchanged) Reason=Interface Opened
     
    skarotech, Apr 12, 2020
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.