Error close proppfrexx

You found a bug or have any issues? Please post them here!
Bob Van Dongen
Posts: 51
Joined: 10 Nov 2020 17:36
Re: Error close proppfrexx

Post by Bob Van Dongen »

Hello everyone, maybe this is a different question, but when I close Proppfrexx I get this message. Cannot connect because the target computer has actively denied the connection 127.0.0.1:9042
Attachments
Proppfrexx Gpio.JPG
User avatar
radio42
Site Admin
Posts: 8658
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Error close proppfrexx

Post by radio42 »

Sure, that is normal. The GPIO client tries to connect to ProppFrexx ONAIR. So when you close PFOA, the GPIO client can not connect anymore.
Close the GPIO client first and then close PFOA.
Bob Van Dongen
Posts: 51
Joined: 10 Nov 2020 17:36
Re: Error close proppfrexx

Post by Bob Van Dongen »

Hi, good evening, I had never seen it before in all the years that I have been a user of Proppfrexx. Thank you for your message and what you say makes sense. Greetings Bob Van Dongen
User avatar
Pieter
Posts: 19
Joined: 03 Jun 2020 16:15
Location: Netherlands
Contact:
Re: Error close proppfrexx

Post by Pieter »

radio42 wrote: 12 Jan 2025 00:16 But I can not do much against an OutOfMemory error.
Please also try to delete the in the error mentioned config file. Maybe it is corrupt and causing the issue.
I deleted the config file, which was almost 180MB.
Proppfrexx closed smoothly and start Proppfrexx again. The config file was now several KB.

Upddate: the faders did not working anymore. In my case the Velleman Control goes offline. So I set it online. Then I closes PFOA and after a while restarted it, Velleman Control is still offline and faders do not work
I replaced the large config file back, the faders works properly. Stop PFOA, the GPIO hangs and have to close this in WIndows Task Manager.
User avatar
radio42
Site Admin
Posts: 8658
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Error close proppfrexx

Post by radio42 »

When you delete the config file your GPI configuration (not the mapping) is gone. Ie. the settings regarding the ports, enabled at startup etc.
So when your Velleman device goes offline the connection can not be established. Also check if the correct mapping is selected and the connection to ProppFrexx is available.
Maybe your correct Password simply got lost?
User avatar
Pieter
Posts: 19
Joined: 03 Jun 2020 16:15
Location: Netherlands
Contact:
Re: Error close proppfrexx

Post by Pieter »

Found it!
- The port number in General setting under GPIO section was different than GPIO
- In de GPIO the mapping was alright, but I saw that "Enable at startup" was not switched to ON

That was the trick. All works fine by now

Thanks Bernd
warmeman
Posts: 31
Joined: 05 Feb 2023 12:15
Re: Error close proppfrexx

Post by warmeman »

It's a bug indeed. Two of my (radio)friends had the same issue this week. I fixed it for them by delete the config file. The same error by closing propffrexx that the gpioclient.config file could not be loaded with an exeption system.outofmemomory.
atlantic
Posts: 95
Joined: 09 Apr 2012 18:35
Location: Belgium
Contact:
Re: Error close proppfrexx

Post by atlantic »

I have the same error. File deleted and error message done.
I think something is wrong with <add key="RESTPassword" value

Here is the download link of the file it is 183mb

https://www.dropbox.com/scl/fi/ent1ysbv ... 61zgn&dl=0
User avatar
radio42
Site Admin
Posts: 8658
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Error close proppfrexx

Post by radio42 »

The question where does these long passwords come from, as I can not reproduce that on my systems.
But as many experience the same, it must be something common. Even if recently no change or update was made to the GPIO client.
So I wonder, what can trigger that.
I will add some extra checks to the next version!
User avatar
radio42
Site Admin
Posts: 8658
Joined: 05 Apr 2012 16:26
Location: Hamburg, Germany
Contact:
Re: Error close proppfrexx

Post by radio42 »

I guess I found the error and fixed it in v4.5.0.3.

But this fix requires, that all passwords must be entered again in the GPIO Client application.

ATTENTION!!!
You MUST re-enter ALL passwords in the GPIO Client app due to a bug, which might lead to an out-of-memory error.

Post Reply