REXYGEN Community Forum / Connection refused (code -413)

Re: Connection refused (code -413)

2018-06-11T10:16:57Z

Hi Joroslav,
I"m using Modbus TCP Master.
And it all is still working fine so far

Best regards,
Peter

Re: Connection refused (code -413)

2018-06-08T12:11:29Z

Hi Peter,
are you running as Modbus TCP master or slave? I suppose slave from what you write. It's a pity you did not make a copy of your project but at least we have some trace. Thanks for reporting all this.

Best regards,
Jaroslav

Re: Connection refused (code -413)

2018-06-08T12:00:21Z

Hi Jaroslav,

I found out what was going on!
The ModBus driver all of a sudden had an incorrect IP address listed (something like 127.0.0.1 or something like that.
I changed ONLY that to the correct IP address and I could load it without a problem.
After I tried changing it back what I thought was listed above, so 127.0.0.1, it also worked again without a problem.
Too bad that I did not have made a copy before changing this.... :-(
But anyway that was the only thing apparently.

Sorry for not being able to forward it now to you in a NON working order...

Best regards,
Peter

Re: Connection refused (code -413)

2018-06-08T10:29:02Z

Hi Peter,
thanks for your message. I understand you prefer not to put your project online. Please send the project files as soon as possible so we can hunt the bug down.

Kind regards,
Jaroslav

Re: Connection refused (code -413)

2018-06-07T19:42:32Z

Sorry for the delay.
It really seems that my project is generating the error that the core module stopped.
After recycling the power, I can connect and I can load any other example file without problems.
But when loading my project it is crashing and recycling power is mandatory to get it back up and running.
I will send my project files by email to you for evaluation / debugging. I do not like to publish them here online.

Best regards,
Peter

Re: Connection refused (code -413)

2018-06-04T06:29:43Z

Hi Peter,
the error "Connection refused (code -413)" means that the target device was reached, but it has actively refused the connection. See e.g. this explanation.

I still believe the problem is in RexCore, which crashes for some reason. At least I do not see RexCore among your processes listed by "ps ax".

Please try to remove all *.rex files from your Raspberry Pi as advised in the Knowledge base, restart RexCore and try to connect from your PC in the office.

If this solves the problem, you have found a serious bug and I'd love to have your project files which are causing RexCore to crash so we can debug it and trace the root cause. Please let me know.

Kind regards,
Jaroslav

Re: Connection refused (code -413)

2018-06-01T20:23:23Z

Hi Jaroslav,

Thanks for the feedback on this.
Just to inform you, I hooked up one of the 2 Raspberry's at home to my network and connected with another PC and it is directly working like a charm without having done anything.
Also in my office i power-cycled the RPi a few times, but I never could connect with that PC over there. So I still fear that there is something else with my PC in the office that failed to connect to both RPi's today.
I will try this PC in my office as well and will report my findings.
For now it is at least working fine and that means I can continue with my "project" ;-)
Thanks and have a great weekend!.

Kind regards,
Peter

Re: Connection refused (code -413)

2018-06-01T15:38:01Z

Hi Peter,
"Connection refused (code -413)" means that RexCore is not running on the target device, i.e. nobody is listening on the other end of the communication line and that's why the connection is refused.

Please follow the instructions on restarting RexCore.

Let me know if this helped.

Kind regards,
Jaroslav

Connection refused (code -413)

2018-06-01T14:12:15Z

Hi all,

I was succesfully working with Rexygen for some while on a Raspberry Pi with MonarcoHAT. But now all of a sudden, I'm getting this above listed error message "Connection refused (code -413)".

I tried with a second RPi with MonaroHAT, but am facing the same problem.
Everything was working before, but now I'm facing this problem.
I can "ping" both RPi's without problem.
Would it be possibible that an automatic update of Windows or an update of a virusscanner would have caused this problem to appear?

pi@MonarcoHAT01:~ $ uname -a
Linux MonarcoHAT01 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux
pi@MonarcoHAT01:~ $ cat /etc/*-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@MonarcoHAT01:~ $ ps ax
  PID TTY      STAT   TIME COMMAND
    1 ?        Ss     0:04 /sbin/init
    2 ?        S      0:00 [kthreadd]
    3 ?        S      0:00 [ksoftirqd/0]
    4 ?        S      0:00 [kworker/0:0]
    5 ?        S<     0:00 [kworker/0:0H]
    7 ?        S      0:00 [rcu_sched]
    8 ?        S      0:00 [rcu_bh]
    9 ?        S      0:00 [migration/0]
   10 ?        S      0:00 [migration/1]
   11 ?        S      0:00 [ksoftirqd/1]
   13 ?        S<     0:00 [kworker/1:0H]
   14 ?        S      0:00 [migration/2]
   15 ?        S      0:00 [ksoftirqd/2]
   17 ?        S<     0:00 [kworker/2:0H]
   18 ?        S      0:00 [migration/3]
   19 ?        S      0:00 [ksoftirqd/3]
   21 ?        S<     0:00 [kworker/3:0H]
   22 ?        S      0:00 [kdevtmpfs]
   23 ?        S<     0:00 [netns]
   24 ?        S<     0:00 [perf]
   25 ?        S      0:00 [khungtaskd]
   26 ?        S<     0:00 [writeback]
   27 ?        S<     0:00 [crypto]
   28 ?        S<     0:00 [bioset]
   29 ?        S<     0:00 [kblockd]
   31 ?        S<     0:00 [rpciod]
   32 ?        S      0:00 [kswapd0]
   33 ?        S<     0:00 [vmstat]
   34 ?        S      0:00 [fsnotify_mark]
   35 ?        S<     0:00 [nfsiod]
   44 ?        S<     0:00 [kthrotld]
   46 ?        S      0:00 [kworker/2:1]
   47 ?        S<     0:00 [bioset]
   48 ?        S<     0:00 [bioset]
   49 ?        S<     0:00 [bioset]
   50 ?        S<     0:00 [bioset]
   51 ?        S<     0:00 [bioset]
   52 ?        S<     0:00 [bioset]
   53 ?        S<     0:00 [bioset]
   54 ?        S<     0:00 [bioset]
   55 ?        S<     0:00 [bioset]
   56 ?        S<     0:00 [bioset]
   57 ?        S<     0:00 [bioset]
   58 ?        S<     0:00 [bioset]
   59 ?        S<     0:00 [bioset]
   60 ?        S<     0:00 [bioset]
   61 ?        S<     0:00 [bioset]
   62 ?        S<     0:00 [bioset]
   63 ?        S<     0:00 [bioset]
   64 ?        S<     0:00 [bioset]
   65 ?        S<     0:00 [bioset]
   66 ?        S<     0:00 [bioset]
   67 ?        S<     0:00 [bioset]
   68 ?        S<     0:00 [bioset]
   69 ?        S<     0:00 [bioset]
   70 ?        S<     0:00 [bioset]
   71 ?        S<     0:00 [VCHIQ-0]
   72 ?        S<     0:00 [VCHIQr-0]
   73 ?        S<     0:00 [VCHIQs-0]
   74 ?        S<     0:00 [iscsi_eh]
   75 ?        S<     0:00 [dwc_otg]
   76 ?        S<     0:00 [DWC Notificatio]
   78 ?        S      0:00 [irq/92-mmc1]
   79 ?        S      0:00 [VCHIQka-0]
   80 ?        S<     0:00 [SMIO]
   81 ?        S<     0:00 [deferwq]
   84 ?        S<     0:00 [bioset]
   85 ?        S      0:00 [mmcqd/0]
   87 ?        S      0:00 [jbd2/mmcblk0p2-]
   88 ?        S<     0:00 [ext4-rsv-conver]
   89 ?        S<     0:00 [ipv6_addrconf]
  103 ?        S<     0:00 [kworker/2:1H]
  128 ?        Ss     0:00 /lib/systemd/systemd-journald
  130 ?        Ss     0:00 /lib/systemd/systemd-udevd
  169 ?        S      0:00 [spi0]
  170 ?        S      3:42 [w1_bus_master1]
  209 ?        S<     0:00 [cfg80211]
  211 ?        S<     0:00 [brcmf_wq/mmc1:0]
  213 ?        S      0:00 [brcmf_wdog/mmc1]
  216 ?        S      0:00 [kworker/3:2]
  399 ?        Ss     0:00 /usr/sbin/cron -f
  401 ?        Ss     0:00 /lib/systemd/systemd-logind
  404 ?        Ss     0:00 avahi-daemon: running [MonarcoHAT01.local]
  406 ?        Ss     0:00 /usr/bin/dbus-daemon --system --address=systemd: --no
  421 ?        Ss     0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy/t
  439 ?        S      0:00 avahi-daemon: chroot helper
  460 ?        S<     0:00 [kworker/1:1H]
  476 ?        Ssl    0:00 /usr/sbin/rsyslogd -n
  489 ?        Ss     0:00 /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wla
  577 ?        S<     0:00 [kworker/u9:0]
  578 ?        S<     0:00 [hci0]
  579 ?        S<     0:00 [hci0]
  581 ?        S      0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow
  583 ?        S<     0:00 [kworker/u9:2]
  585 ?        Ss     0:00 /usr/lib/bluetooth/bluetoothd
  679 ?        Ss     0:00 /sbin/dhcpcd -q -w
  682 ?        Ss     0:00 /usr/sbin/sshd -D
  713 ?        Ss     0:00 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/r
  715 tty1     Ss+    0:00 /sbin/agetty --noclear tty1 linux
  741 ?        Ss     0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:111
  785 ?        S      0:00 [kworker/u8:1]
  814 ?        S      0:00 [kworker/1:2]
  847 ?        S      0:00 [kworker/u8:2]
  860 ?        S      0:00 [kworker/1:0]
  878 ?        S      0:00 [kworker/2:2]
  879 ?        S      0:00 [kworker/3:0]
  884 ?        S      0:00 [kworker/0:1]
  893 ?        S      0:00 [kworker/2:0]
  896 ?        S      0:00 [kworker/3:1]
  899 ?        Ss     0:00 sshd: pi [priv]
  916 ?        S      0:00 sshd: pi@pts/0
  918 pts/0    Ss     0:00 -bash
  921 ?        S      0:00 [kworker/1:1]
  954 ?        S      0:00 [kworker/0:2]
  967 ?        S      0:00 [kworker/u8:0]
  972 pts/0    R+     0:00 ps ax
pi@MonarcoHAT01:~ $

Any help would be welcome.

Regards,
Peter