Folding Forum

uncle_fungus wrote:As far as I know you should be able to fix it with

Code: Select all

update-alternatives --config wx-config

And choose wxgtk instead of wxbase.

That did the trick, thanks!

I added my dedicated server to Fahmon ... the HTTP monitoring is working fine

I get errors, using Experimental mode. Some GPU clients go read with text "Hung". After F6 key everything OK again, until next "Hung" texts.

Sorry, if the issue is covered already.

Jaak

Occasionally, and for reasons I don't fully understand the log files for certain windows clients don't reliably update their mtime (modification time) which confuses experimental mode as it uses this to check whether or not the file needs reloading.

It's more work but you can make a hash of the filezise or just keep the filesize property between updates and use both that and last acces time, if either changed they need to be updated.

Btw, question you probably know, I can't seem to get failed uploads for the gpu clients from the queue file, the counter always stays zero for the indicated field ( in the wiki documentation ) but the client is able to read it as it does increase the 'x failed uploads of this unit'. Think the bitposition is diffrent with the gpu clients

FahMon 2.3.99.1 Released

FahMon 2.3.99.1 is now available for download here: http://fahmon.net/download.html

What's new in this release

* Fixed a nasty crash-bug which affected Windows users monitoring linux clients. This also cleans up some behaviour that affects all platforms

As always if you find any bugs in FahMon please report them using trac

Complete changelog:

Just downloaded 2.3.99.1 and I am getting this error:
I looked in Synaptic and it appears I have the latest version of libCurl installed.

You need libcurl-dev(el) too

That did the trick, thanks!

Fixed a nasty crash-bug which affected Windows users monitoring linux clients.

Hurray,, it works! Many Thanks!

Since installing 2.3.99.1 I have been getting the following errors:

can't open file \\Felix1-desktop\FAH\work\logfile_04.txt (error5: access is denied.)

on three machines each running Ubuntu under VMware.
I've set up the work folder as a shared folder and set permissions to allow anyone read and write access. Each time I do this FahMon is able to read the file fine until the next wu is loaded. At that point I get the error again, in this case it would be logfile_05.txt.
I don't recall ever seeing this on previous versions of FahMon. I'm barely conversant with Ubuntu, just enough to fold and follow simple directions.
I hoped by setting up the work folder to share and setting permissions would allow any file created in that folder to be shared but apparently not. I did this by using places to find the folder and right click, share and permissions to set it up.

Any ideas on how I can fix this so it doesn't need constant tending?

Many thanks.

2.3.99.1 should fix precisely the problem you describe.

Ok.
I double checked the about page and it says 2.3.99.1. I uninstalled it and re-installed keeping preferences. Each time I refresh that client it gets the error. I also set the create and directory mask to 0777 in the smb.conf file and did a samba restart.
Is there any info I can collect for you?

Update:
In order to get around this problem I fired up my nifty sync program and every few minutes copy just FAHlog.txt and queue.dat from the VM Ubuntu client to a shared folder on the host XP machines, and then point FahMon to that folder. It doesn't complain about not having access to log file and seems to work fine.

My remote monitoring setup consists of copying files via scp (soon to be rsync) to a central server through a cron job, and FahMon reads the data from there.

I noticed that 2.3.99.1 is now asking for work/logfile_xx.txt, which I'm now going to include in my file copying. Which files should I be copying over for this new version of FahMon to work properly?

FAHlog.txt, unitinfo.txt, queue.dat, work/logfile_xx.dat