[ARGUS] radium remote file error

[Patrick Forsberg]

I found the error causing this, and it was inline commenting that 
doesn't work for RADIUM_ARGUS_SERVER, ie
RADIUM_ARGUS_SERVER=argus://192.168.0.1:561 // sensor1

Is not a valid entry in radium.conf, it has to be
# sensor1
RADIUM_ARGUS_SERVER=argus://192.168.0.1:561

/Patrick

On 2025-10-23 21:33, Patrick Forsberg wrote:
> I run radium connecting to two remote argi
>
> Running 'ra -S localhost' produces what looks like good output, but 
> the radium instance outputs this
>
> radium[1758130]: 21:19:09.720990 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:10.771015 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:12.757519 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:13.762791 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:19.795728 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:20.821817 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:22.773869 remote file error recv 0 bytes, 
> Operation now in progress
> radium[1758130]: 21:19:23.775306 remote file error recv 0 bytes, 
> Operation now in progress
>
> Is this a "real" error or is it just that one of the remote argi isn't 
> outputing data at the time?
>
> argus is running 3.0.8.3 and radium is 3.0.8.4
>
> Regards,
>
> Patrick Forsberg
> Chalmers University of Technology
>