Welcome to the new home of the Cumulus Support forum.

Latest Cumulus release v1.9.4 (build 1099) - Nov 28 2014
Latest Cumulus MX release - v3.0.0 build 3043 Jan 20 2017. See the Wiki for download

An error has occurred - please zip up the MXdiags folder and post it in the forum

Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.
agsteele
Posts: 39
Joined: Tue 21 Jun 2011 7:50 am
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Keighley, UK

An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by agsteele » Sun 09 Jul 2017 3:04 pm

Well, I made the switch to Cumulus MX about a month back. All worked well and seems to be running happily on a standalone machine under Windows 10. I have MX build 3043.

This week I decided to set up some FTP space on my personal website and get CumulusMX to drive that. All seemed to go OK apart from the gauges page. A bit of investigation revealed that realtimesettings.txt was not being copied over. I did this manually and suddenly that seems to be working permanently.

So my last tweak was to set up a feed to Twitter. This has been unsuccessful.

I took another look at the command console and discovered several pages of error message ending in the line:

An error has occurred - please zip up the MXdiags folder and post it in the forum

Reading the messages I suspect that there is a problem with the Twitter stuff although I cannot be certain. I did remove all the Twitter settings, stopped CumulusMX, edited the Cumulus.ini file to remove the OAuth and OAuthSecret tokens. Reset my Twitter password. Re-entered the Twitter settings in MX and restarted. In due course the errors reappeared.

So I've done what the program requested and zipped up the MXdiags folder and it is attached along with a capture of the error text from the console.

Being only slightly competent to read these files it seems to suggest that Twitter is refusing a connection from CumulusMX with an error 87 - 'Client is not permitted to perform this action'.

I've disabled Twitter posting for now and the errors have not been seen so far.

Anyone with insight able to help me diagnose this?

Andrew
You do not have the required permissions to view the files attached to this post.

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Sun 09 Jul 2017 5:13 pm

It could be that Twitter have changed their API (again) and Cumulus breaks the new rules. I'll see if I can find anything about this. It would be useful if someone using MX and Twitter could reply to say whether it still works for them.

Has MX managed to get the tokens again?
Steve

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Sun 09 Jul 2017 5:23 pm

Found it. As of June 30th they have withdrawn support for xAuth, which is the mechanism Cumulus uses for authentication. The problem is that they really don't cater properly for applications which do Twitter updates automatically like Cumulus. They do have an alternative mechanism called 'PIN based authorization' which would require Cumulus to display a URL to the user which they would then put in a browser, receive a PIN, and then enter that PIN into Cumulus.
Steve

freddie
Posts: 320
Joined: Wed 08 Jun 2011 11:19 am
Weather Station: Davis Vantage Pro 2
Operating System: GNU/Linux (Ubuntu 18.04)
Location: Ystrad, Rhondda, Wales
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by freddie » Sun 09 Jul 2017 7:00 pm

steve wrote:It could be that Twitter have changed their API (again) and Cumulus breaks the new rules. I'll see if I can find anything about this. It would be useful if someone using MX and Twitter could reply to say whether it still works for them.
It works for me - hourly updates. https://twitter.com/FishpoolFarmWx
Last edited by freddie on Sun 09 Jul 2017 9:04 pm, edited 1 time in total.
Freddie
Image

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Sun 09 Jul 2017 8:20 pm

Thanks - I think it's the initial setup that's affected, obtaining the tokens. But I can't remember the full details of how it works, it was stupidly complicated even before this latest change.
Steve

User avatar
PaulMy
Posts: 1714
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis Vantage Pro 2+ w/Envoy USB
Operating System: Windows-8
Location: Komoka, ON Canada
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by PaulMy » Sun 09 Jul 2017 9:33 pm

My https://twitter.com/KomokaWeather seems to be working

I am using Cumulus1

Enjoy,
Paul

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Sun 09 Jul 2017 9:59 pm

Cumulus 1 should have the same problem. I'll do some experimenting tomorrow to see what happens if I delete my tokens. I strongly advise that no-one else tries this! If it's working for you, leave it well alone.
Steve

agsteele
Posts: 39
Joined: Tue 21 Jun 2011 7:50 am
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Keighley, UK

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by agsteele » Mon 10 Jul 2017 6:23 am

Thanks Steve. I'm pleased that I was reading the errors correctly but sorry that you have more work again :groan:

OAuthToken/OAuthSecretToken=unknown

Andrew

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Mon 10 Jul 2017 9:46 am

I can confirm that it's the initial obtaining of the tokens which no longer works. If you already have tokens, updates still work OK.
Steve

ExperiMentor
Posts: 46
Joined: Tue 24 Nov 2015 11:30 pm
Weather Station: Fine Offset
Operating System: Windows 7; Linux
Location: Switzerland

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by ExperiMentor » Sun 06 May 2018 4:06 pm

My tweets were working fine until I broke the SD card and had to reinstall. Now, even though I have a note of the previously-working tokens, I can't get it to restart. Any suggestions?

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Sun 06 May 2018 4:47 pm

Perhaps the tokens encode some information about the installation, I don’t really know.
Steve

ExperiMentor
Posts: 46
Joined: Tue 24 Nov 2015 11:30 pm
Weather Station: Fine Offset
Operating System: Windows 7; Linux
Location: Switzerland

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by ExperiMentor » Sun 06 May 2018 9:59 pm

Thanks for trying. The tokens - as I understand it - give your twitter app "Sandaysoft Cumulus" permission to access (ie write to) my twitter account, but without me telling you my username and password. I'm guessing that Cumulus uses the username and password when trying to get tokens (the feature known to not work), but then does not need them any more (which is why if we change either username or password we were told to delete the tokens and let them be regenerated).

Further information. When I run with no OAuth tokens, I get as follows (red added by me):

pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:02:09
Type Ctrl-C to terminate
System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Error: SendFailure (Error writing headers) ---> System.Net.WebException: Error writing headers ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: Invalid certificate received from server. Error code: 0xffffffff800b010a
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.RemoteValidation (Mono.Security.Protocol.Tls.ClientContext context, AlertDescription description) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.validateCertificates (Mono.Security.X509.X509CertificateCollection certificates) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.Client.TlsServerCertificate.ProcessAsTls1 () [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.Handshake.HandshakeMessage.Process () [0x00000] in <filename unknown>:0
at (wrapper remoting-invoke-with-check) Mono.Security.Protocol.Tls.Handshake.HandshakeMessage:Process ()
at Mono.Security.Protocol.Tls.ClientRecordProtocol.ProcessHandshakeMessage (Mono.Security.Protocol.Tls.TlsStream handMsg) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.RecordProtocol.InternalReceiveRecordCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHandshake (IAsyncResult result) [0x00000] in <filename unknown>:0
at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallback (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpWebRequest.EndGetRequestStream (IAsyncResult asyncResult, System.Net.TransportContext& context) [0x00000] in <filename unknown>:0
at System.Net.Http.HttpClientHandler.GetRequestStreamCallback (IAsyncResult ar) [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.Net.Http.HttpResponseMessage].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<HttpPostAsync>d__39.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[System.String].GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.AuthorizerBase+<PostAccessTokenAsync>d__15.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at LinqToTwitter.XAuthAuthorizer+<AuthorizeAsync>d__1.MoveNext () [0x00000] in <filename unknown>:0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0
at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0
at CumulusMX.Cumulus+<UpdateTwitter>d__479.MoveNext () [0x00000] in <filename unknown>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

The file in MXdiags has exactly the same information, no more or less.

But if I run with my previously working OAuth tokens, I get no error messages here; but there are errors noted in MXdiags

pi@Pi-Hole:~/Cumulus $ sudo mono CumulusMX.exe
Current culture: English (United Kingdom)
Serial: BCE5D89FE8883D398946275B4BDE2E5A
Cumulus MX v.3.0.0 build 3043
Today.ini = data/today.ini
Last update=2018-05-06T23:00:00
Looking for Fine Offset station, VendorID=0x1941 ProductID=0x8021
sysname=Linux release=4.14.34 machine=armv6l
Fine Offset station found
Connected to station
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
06/05/2018 23:04:49
Type Ctrl-C to terminate

From MXdiags:
2018-05-06 23:04:51.649 End of PWS archive upload
2018-05-06 23:05:02.263 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:06:00.346 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:07:00.486 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:08:00.345 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:09:00.316 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:10:00.110 Writing log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.114 Written log entry for 06/05/2018 23:10:00
2018-05-06 23:10:00.128 Writing today.ini, LastUpdateTime = 06/05/2018 23:10:00 raindaystart = 3126 rain counter = 3126
2018-05-06 23:10:00.138 Latest reading: 7960: 04 27 EB 00 55 B2 00 A0 24 00 0A 00 00 B4 28 00
2018-05-06 23:10:00.408 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:11:00.334 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:12:00.376 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:13:00.385 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:14:00.394 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:15:00.370 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:16:00.534 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:17:00.424 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:18:00.529 UpdateTwitter: An error occurred while sending the request.
2018-05-06 23:19:00.452 UpdateTwitter: An error occurred while sending the request.

Maybe the problem is that (following earlier suggestions) I revoked access to my Twitter account by your app "Sandaysoft Cumulus"; it now no longer appears on my list of apps. Any ideas how reinstate access? I don't remember ever giving access permission

User avatar
steve
Cumulus Author
Posts: 26714
Joined: Mon 02 Jun 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by steve » Mon 07 May 2018 7:17 am

That may be the problem, but I don’t know how you would reinstate it, sorry.
Steve

User avatar
mcrossley
Posts: 5209
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2
Operating System: Stretch Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by mcrossley » Mon 07 May 2018 9:05 am

Qualifier: I have no idea what I am talking about! But...

There is a twitter apps page https://apps.twitter.com/ where you can register your own apps - is that of any use?

ExperiMentor
Posts: 46
Joined: Tue 24 Nov 2015 11:30 pm
Weather Station: Fine Offset
Operating System: Windows 7; Linux
Location: Switzerland

Re: An error has occurred - please zip up the MXdiags folder and post it in the forum

Post by ExperiMentor » Mon 07 May 2018 7:45 pm

mcrossley wrote:There is a twitter apps page https://apps.twitter.com/ where you can register your own apps - is that of any use?
I accidentally thought that too and made one. But no, that's not what's wanted. Cumulus needs to access the "Sandaysoft Cumulus" app not one I made myself. Tough luck :(.

Nice web page you have btw - I plan copying bits of it when I get time.

How's Macc? I used to work at AstraZeneca !

Post Reply