Welcome to the Cumulus Support forum.

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Cumulus MX V4 beta test release 4.0.0 (build 4018) - 28 March 2024

Legacy Cumulus 1 release v1.9.4 (build 1099) - 28 November 2014 (a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

TCP Port in Station Settings already in use

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

TCP Port in Station Settings already in use

Post by aznetcowboy »

After setting up a new router, the TCP Port in the Station Setting is not working. It has been 22222 ever since I can remember. Was getting a message stating "Cannot establish connect since port is already in use". By what, who knows. How can I either find out who/what is using port 22222 or possibly use a different port in the VP TCP/IP setting?

Would this have something to do with the "Error -32701 while trying to initialize the station" error I am also getting? :?
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
jank
Posts: 239
Joined: Sat 13 Jun 2015 5:57 pm
Weather Station: FineOffset WS3080
Operating System: Debian Buster - Raspbian - Raspb
Location: Germany - nearby Kassel

Re: TCP Port in Station Settings already in use

Post by jank »

Hi

under linux this command should work for you: netstat -aon |grep :22222
under windows this command might help: netstat -aon | findstr :22222

It will show you all Programs using this TCP Port :22222

Jan
Do want a Managing Dashboard for CumulusMX on RaspberryPi? cumulusmx.sh
viewtopic.php?f=40&t=17907
Image
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

aznetcowboy wrote: Tue 19 May 2020 12:38 am under windows this command might help: netstat -aon | findstr :2222
The response I get is "findstr: Cannot open 22222". That sure doesn't help at all, does it? :bash:
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
freddie
Posts: 2434
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: TCP Port in Station Settings already in use

Post by freddie »

Looks like a syntax error with the command you used - instead of looking for "22222" in the output from netstat it is looking for the file named "22222" which isn't what you wanted.
Freddie
Image
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

jank wrote: Tue 19 May 2020 8:22 am Looks like a syntax error with the command you used - instead of looking for "22222" in the output from netstat it is looking for the file named "22222" which isn't what you wanted.
How can I determine then what the problem is with this 22222 port? Until then, my weather station is offline. It needs to communicate apparently with the 22222 port via IP address 192.168.0.102. This weather station has been operating since 2013, the last year in a new location. It has just been in the recent week this problem has cropped up. I am totally baffled as to the issue and will appreciate any help I can get.
:shock:
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
freddie
Posts: 2434
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: TCP Port in Station Settings already in use

Post by freddie »

You need to type in the command Jank supplied correctly. You must've made a mistake with your typing otherwise it would have worked correctly.
Freddie
Image
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

I thought I was typing it in correctly, but tried it once more and got the following this time:
TCP 192.168.0.3:59027 192.168.0.102 ESTABLISHED 10092

Now, just what does this tell me?bbb :?:
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
freddie
Posts: 2434
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2 + Ecowitt
Operating System: GNU/Linux Ubuntu 22.04 LXC
Location: Alcaston, Shropshire, UK
Contact:

Re: TCP Port in Station Settings already in use

Post by freddie »

It means that something is indeed listening on port 22222 and that a connection is established between 192.168.0.3 and 192.168.0.102. So you will either need to change the port that Cumulus uses or shut down whatever is listening on 22222. I think there is a setting in the Cumulus.ini file that you can change to make it use another port (hint: search that file for 22222). There is a section in the Wiki that covers this.
Freddie
Image
sfws
Posts: 1183
Joined: Fri 27 Jul 2012 11:29 am
Weather Station: Chas O, Maplin N96FY, N25FR
Operating System: rPi 3B+ with Buster (full)

Re: TCP Port in Station Settings already in use

Post by sfws »

freddie wrote: Tue 19 May 2020 5:49 pm I think there is a setting in the Cumulus.ini file that you can change to make it use another port (hint: search that file for 22222). There is a section in the Wiki that covers this
Yes, Freddie, the Wiki reference is https://cumuluswiki.org/a/Cumulus.ini#D ... _specific: Essentially there is the following line in the [Station] section of the settings file to edit.
VP2TCPPort=22222
User avatar
mcrossley
Posts: 12695
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: TCP Port in Station Settings already in use

Post by mcrossley »

aznetcowboy wrote: Tue 19 May 2020 5:38 pm I thought I was typing it in correctly, but tried it once more and got the following this time:
TCP 192.168.0.3:59027 192.168.0.102 ESTABLISHED 10092

Now, just what does this tell me?bbb :?:
The last field - 10092 here - is the Process ID (PID) of whatever is using the port. To lookup the process name you could use this command...

Code: Select all

tasklist /fi "pid eq 10092"
User avatar
mcrossley
Posts: 12695
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: TCP Port in Station Settings already in use

Post by mcrossley »

Though that line you posted does not contain the port 22222 !

TCP 192.168.0.3:59027

Shows something listening on port 59027 ?

Are you sure you're sure you are typing the command correctly? :)
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

I find nothing under either 10092 or 59027. The result of the tasklist is it finds "No tasks are running which match the specified criteria". This gets more confusing as time goes on. :cry:
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

Ah- ha! I think I found it. It was that the router was working with 1 192.168.1.x and I had my settings, so I thought, set to 192.168.0.x. While I was working with 192.168.0.102 for the Davis Weatherlink, the router was using 192.168.1.2. Once I caught that through pinging my settings, the light went on. So I went into the Station setup and changed the 0.102 to 1.2 and made sure the router was indeed seeing the Davis weatherlink now and it was! Ever since I starting using my system, it was a 0.x settings. The old router needed to be replaced and the new one wanted to be 1.x. I thought I had changed it to 0.x, but it stayed at 1.x. All is find on that front now. :D
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
User avatar
aznetcowboy
Posts: 357
Joined: Fri 04 Jan 2013 6:03 pm
Weather Station: Davis 6153 Vantage Pro2
Operating System: Windows 10 Home 64-bit
Location: West Bend, WI USA
Contact:

Re: TCP Port in Station Settings already in use

Post by aznetcowboy »

I was jumping for joy too soon. The only problem I have now is that my weather PC can ping everything except 192.168.1.2 which is what is required for Cumulus to get the reading for transmission to my website. My Davis Vantage Pro2 console is showing all the data from the ISS. The main computer will ping the 192.168.1.2 with no problem. For some reason my weather PC cannot ping or find the Davis Weatherlink. I have double-checked the connections and according to the Davis manual everything is good. It has worked int he past. Before I call the Davis Tech Support, any suggestions on this error.
Tom Wills
Ridge Run Weather Station: http://www.ridgerun.us
Image
water01
Posts: 3215
Joined: Sat 13 Aug 2011 9:33 am
Weather Station: Ecowitt HP2551
Operating System: Windows 10 64bit
Location: Burnham-on-Sea
Contact:

Re: TCP Port in Station Settings already in use

Post by water01 »

Does your weather have a fixed IP on your old network (i.e. 192.168.0.xx), if so that will be the problem? You need to look at the TCP/IPv4 parameters for your Ethernet / Wifi connection and either let the router allocate an IP via DHCP or alter it to a 192.168.1.xxx IP address.
David
Image
Post Reply