Yeah, might be that time, hopefully I don’t get in trouble:)
so modpolling from the server doesn’t work, but telnet does, any thoughts on that
modpoll 3.7 - FieldTalk™ Modbus® Master Simulator
Copyright © 2002-2019 proconX Pty Ltd
Visit https://www.modbusdriver.com for Modbus libraries and tools.
Protocol configuration: MODBUS/TCP
Slave configuration…: address = 1, start reference = 101, count = 1
Communication…: plc, port 502, t/o 1.00 s, poll rate 10000 ms
Data type…: 16-bit register, output (holding) register table
Can’t reach server/slave! Check TCP/IP and firewall settings.
plc is of course the device
This sounds like an anti-virus layer. Letting the connection open then buffering the initial real traffic in order to inspect it, and not knowing that it’s holding a complete initial read command packet. Stalling the pipe. Telnet is probably whitelisted by such a layer.
I don’t see anything running, I see there are ubuntu virus scanners, but none of the processes were it, what else could filter processes like that
See if you have anything defined in LD_PRELOAD.
empty envar
Sorry, I’m out of ideas. Spin up a new server and test another copy of Ignition in trial mode. Then move the Ignition license if that server works.
Something I noticed, netstat shows a crap ton of established tcp connections, not sure why these open connections aren’t utilized.
Okay, so I’m a little further, modpoll does work, for some reason on the ignition server it didn’t like have the url, the ip though worked just fine. So now back to only ignition not requesting data. It seems to keep the tcp connections, they go down from lack of activity, but seem to get reestablished. So what could cause this on an ignition server? thx
Here’s what I’m getting a lot of:
wireshark:
34 962.392550728 svr → plc TCP 54 [TCP Dup ACK 2#16] [TCP ACKed unseen segment] 48382 → 502 [ACK] Seq=1 Ack=2 Win=28400 Len=0
35 1022.502767010 plc → svr TCP 54 [TCP Dup ACK 1#17] 502 → 48382 [ACK] Seq=1 Ack=1 Win=2048 Len=0
36 1022.502806604 svr → plc TCP 54 [TCP Dup ACK 2#17] [TCP ACKed unseen segment] 48382 → 502 [ACK] Seq=1 Ack=2 Win=28400 Len=0
37 1082.699727026 plc → svr TCP 54 [TCP Dup ACK 1#18] 502 → 48382 [ACK] Seq=1 Ack=1 Win=2048 Len=0
38 1082.699768172 svr → plc TCP 54 [TCP Dup ACK 2#18] [TCP ACKed unseen segment] 48382 → 502 [ACK] Seq=1 Ack=2 Win=28400 Len=0
39 1142.898447921 plc → svr TCP 54 [TCP Dup ACK 1#19] 502 → 48382 [ACK] Seq=1 Ack=1 Win=2048 Len=0
40 1142.898490082 svr → plc TCP 54 [TCP Dup ACK 2#19] [TCP ACKed unseen segment] 48382 → 502 [ACK] Seq=1 Ack=2 Win=28400 Len=0
41 1203.100141057 plc → svr TCP 54 [TCP Dup ACK 1#20] 502 → 48382 [ACK] Seq=1 Ack=1 Win=2048 Len=0
42 1203.100168535 svr → plc TCP 54 [TCP Dup ACK 2#20] [TCP ACKed unseen segment] 48382 → 502 [ACK] Seq=1 Ack=2 Win=28400 Len=0
Here’s the only thing in the ignition server logs:
INFO | jvm 1 | 2020/04/27 13:57:55 | ERROR [SocketIODelegate ] [13:57:55,875]: [hostname=plc,port=503] Socket connection closed, DriverState was Connected.
INFO | jvm 1 | 2020/04/27 13:57:56 | ERROR [SocketIODelegate ] [13:57:55,868]: [hostname=plc,port=504] Socket connection closed, DriverState was Connected.
The wireshark logs are not aligned in anyway.
Thanks,
Now we’re getting somewhere the server seems to be stuck in a connecting status for the opc-ua server. So that’s what’s not starting up. What do you guys think?
Thanks
Alright, for all watching this thread finally figured it out. The opc-ua connection was never happening. I had to recreate the connection with the same settings to get it working. So if anyone else sees this check the opc-ua server connection status and deal with that first.
1 Like
Oh, and thx for everybody’s help, extra eyes never hurt.
Just a quick thought. Did you check to see if the name of the OPC connection is Ignition OPC-UA Server vs Ignition OPC UA Server ?
Notice the hyphen between OPC and UA
That’s a good troubleshooting tip for an Ignition 8 gateway but this one is 7.8.5 according to OP, so there’s not much reason for that to have happened.
FWIW, we’ve added a warning dialog that pops up when you import tags that reference a non-existent OPC server. Should help this kind of thing.
Yeah, that would have saved some headache. The other comment about the server name, I did have to match the old one before it started working.
Thanks all