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

Problems with CUtags.txt and realtimegauges.txt

Discussion of Ken True's web site templates

Moderator: saratogaWX

Post Reply
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Hi,

I tried to solve this without bugging anybody, to no avail. :(

In late October, for no reason I can figure out Cumulus began uploading CUtags.txt and realtimegauges.txt as "CUtags.phptmp" and "realtimegauges.txttmp", both of them zero bytes. My internet connection seems pretty solid, and the realtime data is okay, Status shows "Cumulus FTP - Age Unknown - File not found " and "Cumulus Weather data - age 148547:5:20 - > 0:29:15 Tue, 30-Nov-1999 12:00am MST. Both of them say "not current"

I didn't change anything in Cumulus before this happened, and my site has been up for about 4 years nonstop with no similar problems.
Site is here: http://weather.pmhahn.com

Any help would be greatly appreciated!

Paul
User avatar
saratogaWX
Posts: 1170
Joined: Wed 06 May 2009 5:02 am
Weather Station: Davis Vantage Pro Plus
Operating System: Windows 10 Professional
Location: Saratoga, CA, USA
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by saratogaWX »

Your wxstatus.php page shows
Cumulus FTP NOT Current unknown > 0:29:15 file not found
so CUtags.php is not on your website.

I'd suggest using your FTP client and check for and remove any .phptmp files you find. It may be that Cumulus is having trouble uploading and renaming a new CUtags.php file due to a past upload/rename failing.
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Re: Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Every time I delete the CUtags.phptmp on the website Cumulus just uploads another with that same name. For some reason it's adding the "tmp" to the name and uploading a blank file.

The files that remain on my home machine in the webfiles directory are CUtags.txt and CUtags.txttmp. The txttmp file seems normal and has all the weather data in it, and is about 19k in size.

Paul
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: Problems with CUtags.txt and realtimegauges.txt

Post by freddie »

saratogaWX wrote:I'd suggest using your FTP client and check for and remove any .phptmp files you find. It may be that Cumulus is having trouble uploading and renaming a new CUtags.php file due to a past upload/rename failing.
You get .phptmp files when you have selected the "rename on upload" option in Cumulus. Cumulus (or rather the FTP component that it uses) will not upload new files if the .phptmp files are present.
Freddie
Image
User avatar
steve
Cumulus Author
Posts: 26702
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by steve »

Just to add that one cause of zero-length files on the server is selecting 'active' ftp mode when 'passive' is required, or vice versa. On some setups, either way works, but some firewall configurations require one or the other. If that doesn't help, turn on ftp logging and look at ftplog.txt, there may be some clues in there.

Note that the reason for 'tmp' files locally is not the same as the reason for 'tmp' files on the server (the latter is as described by freddie above). There is page in the wiki which explains this all in detail.
Steve
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Re: Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Freddie, Thank you, that cleared up the file extension problem!

Steve, unfortunately, active or passive makes no difference, still getting zero byte files after manually deleting the previous one on the server.
jlmr731
Posts: 225
Joined: Sat 27 Aug 2016 12:11 am
Weather Station: Davis vantage pro 2
Operating System: Debian
Location: Wickliffe, Ohio
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by jlmr731 »

turn on ftp logging and lets look at the logs.
also check your web server that you have the permissions set right in case the server had some upgrades or changes that messed up or whatever.

Can you manually upload files to the server with an ftp client?
you can also try turning off rename option in cumulus and see what happens.
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Re: Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Hi,

File permissions are on CUtags and reatlmegauges is set to 644. I just transferred a small text file via filezilla no problem. Also the realtime.txt file is uploading normally and my main page shows the current weather (85 degrees right now - beautiful day!), so it's just those two files I'm having trouble with. Here is my log:

Code: Select all

14:55:08:566 ! HighLevelAsync 0
14:55:09:307 02F97750 Socket handle created 1260
14:55:09:307 TWSocket will connect to 173.254.28.60:21
14:55:09:307 02F97750 TriggerDataSent 1260
14:55:09:477 FTP Response: 220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
14:55:09:477 >|220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------|

14:55:09:477 FTP Response: 220-You are user number 4 of 1000 allowed.
14:55:09:477 >|220-You are user number 4 of 1000 allowed.|

14:55:09:477 FTP Response: 220-Local time is now 15:55. Server port: 21.
14:55:09:477 >|220-Local time is now 15:55. Server port: 21.|

14:55:09:477 FTP Response: 220-This is a private system - No anonymous login
14:55:09:477 >|220-This is a private system - No anonymous login|

14:55:09:477 FTP Response: 220-IPv6 connections are also welcome on this server.
14:55:09:477 >|220-IPv6 connections are also welcome on this server.|

14:55:09:477 FTP Response: 220 You will be disconnected after 15 minutes of inactivity.
14:55:09:477 >|220 You will be disconnected after 15 minutes of inactivity.|

14:55:09:477 FTP Session Connected, code = 0
14:55:09:477 ! HighLevelAsync 0
14:55:09:477 FTP Command: USER ----------------
14:55:09:477 02F97750 TriggerDataSent 1260
14:55:09:547 FTP Response: 331 User ------------ OK. Password required
14:55:09:547 >|331 User -------------- OK. Password required|

14:55:09:547 ! HighLevelAsync 0
14:55:09:547 FTP Command: PASS
14:55:09:547 02F97750 TriggerDataSent 1260
14:55:09:758 FTP Response: 230 OK. Current restricted directory is /
14:55:09:758 >|230 OK. Current restricted directory is /|

14:55:09:758 ! HighLevelAsync 0
14:55:09:758 ! HighLevelAsync done
14:55:09:768 Getting directory listing
14:55:09:768 FTP Command: PWD
14:55:09:768 02F97750 TriggerDataSent 1260
14:55:09:828 FTP Response: 257 "/" is your current location
14:55:09:828 >|257 "/" is your current location|

14:55:10:769 ! HighLevelAsync 0
14:55:10:769 FTP Command: PORT 192,168,1,103,12,187
14:55:10:769 02F97750 TriggerDataSent 1260
14:55:10:849 FTP Response: 200 PORT command successful
14:55:10:849 >|200 PORT command successful|

14:55:10:849 ! HighLevelAsync 0
14:55:10:849 FTP Command: NLST
14:55:10:849 02F97750 TriggerDataSent 1260
14:55:10:979 ! Data Session requested
14:55:10:989 02F97F10 Socket accepted 1236
14:55:10:989 02F97F10 TCustomWSocket.Shutdown 1 968
14:55:10:989 ! Data Session opened
14:55:10:989 02F97F10 TriggerDataSent 1236
14:55:10:989 FTP Response: 150 Connecting to port 5008
14:55:10:989 >|150 Connecting to port 5008|

14:55:11:029 ! Data Session closed
14:55:11:049 ! Next3GetAsync
14:55:11:049 02F97F10 TCustomWSocket.Shutdown 1 1236
14:55:11:049 FTP Response: 226-Options: -a 
14:55:11:049 >|226-Options: -a |

14:55:11:049 FTP Response: 226 50 matches total
14:55:11:049 >|226 50 matches total|

14:55:11:049 ! Next3GetAsync
14:55:11:049 ! HighLevelAsync 0
14:55:11:049 ! HighLevelAsync done
14:55:11:770 Local file: E:\Program Files\Cumulus\webfiles\CUtags.txt Remote file: public_html/weather/CUtags.php
14:55:11:770 FTP Command: TYPE A
14:55:11:770 02F97750 TriggerDataSent 1260
14:55:11:841 FTP Response: 200 TYPE is now ASCII
14:55:11:841 >|200 TYPE is now ASCII|

14:55:12:772 Uploading E:\Program Files\Cumulus\webfiles\CUtags.txttmp to public_html/weather/CUtags.php
14:55:12:772 ! HighLevelAsync 0
14:55:12:772 FTP Command: PORT 192,168,1,103,12,191
14:55:12:782 02F97750 TriggerDataSent 1260
14:55:12:852 FTP Response: 200 PORT command successful
14:55:12:852 >|200 PORT command successful|

14:55:12:852 ! HighLevelAsync 0
14:55:12:852 FTP Command: STOR public_html/weather/CUtags.php
14:55:12:852 02F97750 TriggerDataSent 1260
14:55:12:992 ! Data Session requested
14:55:12:992 02F97F10 Socket accepted 1212
14:55:12:992 02F97F10 TCustomWSocket.Shutdown 1 968
14:55:12:992 ! Data Session opened
14:55:12:992 FTP Response: 150 Connecting to port 5023
14:55:12:992 >|150 Connecting to port 5023|

14:55:12:992 02F97F10 TriggerDataSent 1212
14:55:12:992 DataSocketPutDataSent 19589
14:55:43:776 ! Aborting
14:55:43:786 FTP Session Closed
14:55:43:786 ! HighLevelAsync 0
14:55:43:786 ! Abort detected
14:55:43:786 ! HighLevelAsync done
14:55:43:786 02F97F10 TCustomWSocket.Shutdown 1 1212
14:55:43:786 ! Data Session closed
14:55:43:786 ! Next3PutAsync
14:55:43:786 FTPRequestDone ftpPutAsync Errcode = 426
The dashed lines after the user name are my doing for this public display.

I did unclick the ftp rename box and that corrected the extension issue. Also, this began happening around the time we had that huge DoS attack throughout the U.S., so they could have changed some server settings on me...
User avatar
PaulMy
Posts: 3777
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2 Plus 24-Hour FARS
Operating System: Windows8 and Windows10
Location: Komoka, ON Canada
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by PaulMy »

14:55:11:770 Local file: E:\Program Files\Cumulus\webfiles\CUtags.txt Remote file: public_html/weather/CUtags.php
Probably nothing to with your problem but from my recollection of posts here it is highly recommended not to install Cumulus in the C:\Program Files\ folder http://wiki.sandaysoft.com/a/Setup

Paul
Davis Vantage Pro2+
C1 www.komokaweather.com/komokaweather-ca
MX www.komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX www.komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX www. komokaweather.com/cumulusmx4/index.htm

Image
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Re: Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Hi Paul,

Although Cumulus has lived there for probably 5 or 6 years, that's a good suggestion and I'm thinking of redoing the whole shebang. The PC is an old Pentium running Windows XP, probably around 15 years old now. I'm starting to wonder if the LAN card has gone south. In any case I'll probably get a newer PC and set up Cumulus on the C: root. Might even redo the server-side stuff, although just thinking about that gives me a big headache.

Paul
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: Problems with CUtags.txt and realtimegauges.txt

Post by freddie »

drat wrote:I just transferred a small text file via filezilla no problem
Was Filezilla using active or passive?
drat wrote:the realtime.txt file is uploading normally
Interesting. So you can make transfers with Cumulus. Are the perms for realtime.txt the same as they are for the other two files?

Code: Select all

FTP Response: 230 OK. Current restricted directory is /
You are logged in okay. Are the remote file paths correct?

Code: Select all

14:55:11:770 Local file: E:\Program Files\Cumulus\webfiles\CUtags.txt
Does any local process have this file open? I'm thinking any back-up processes or maybe antivirus or even Cumulus itself. Hopefully you don't have it open in a text editor.

Code: Select all

14:55:12:992 ! Data Session opened
14:55:12:992 FTP Response: 150 Connecting to port 5023
14:55:12:992 >|150 Connecting to port 5023|
14:55:12:992 02F97F10 TriggerDataSent 1212
14:55:12:992 DataSocketPutDataSent 19589
Your data session appears to open okay...

Code: Select all

14:55:43:776 ! Aborting
14:55:43:786 FTP Session Closed
14:55:43:786 ! HighLevelAsync 0
14:55:43:786 ! Abort detected
14:55:43:786 ! HighLevelAsync done
14:55:43:786 02F97F10 TCustomWSocket.Shutdown 1 1212
14:55:43:786 ! Data Session closed
14:55:43:786 ! Next3PutAsync
14:55:43:786 FTPRequestDone ftpPutAsync Errcode = 426
...and then it is aborted 30 seconds later. It is interesting that it is an abort, and the FTP session is logged as closed (i.e. you lost your connection with the FTP server) before the data session is logged as closed.

Have you tried toggling active/passive mode?
Freddie
Image
drat
Posts: 12
Joined: Mon 29 Jun 2009 1:45 am
Weather Station: VP2

Re: Problems with CUtags.txt and realtimegauges.txt

Post by drat »

Problem solved.

It was my modem. I did have to get a new modem a while back because my old one was disconnecting frequently. Put the old one back in an it uploaded the two files correctly.

Thank you Steve, Ken, Paul and Freddie for your help. I learned a lot!

Paul
User avatar
PaulMy
Posts: 3777
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2 Plus 24-Hour FARS
Operating System: Windows8 and Windows10
Location: Komoka, ON Canada
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by PaulMy »

Glad you have it back working properly, and a lesson learned is a bit of reward for the trials and tribulations...

Enjoy,
Paul
Davis Vantage Pro2+
C1 www.komokaweather.com/komokaweather-ca
MX www.komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX www.komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX www. komokaweather.com/cumulusmx4/index.htm

Image
jlmr731
Posts: 225
Joined: Sat 27 Aug 2016 12:11 am
Weather Station: Davis vantage pro 2
Operating System: Debian
Location: Wickliffe, Ohio
Contact:

Re: Problems with CUtags.txt and realtimegauges.txt

Post by jlmr731 »

glad you got it working. but now you need a new modem it seems like i go through modem and router every few years so i know the pain.
Post Reply