I've tried four or five fresh installs of Scripta now, but it's the same every time: after the very first initial setup, the miners show up fine in the web ui and report that they are hashing. After I change the mining pools and other settings, I reboot the pi. Then, the next time that Scripta starts up, the miners no longer show in the web ui and there is no hash rate reported to the pool. Any idea what is going on here? I thought my set up was pretty standard, just gridseeds, a power supply that came with them and a pi model b.
Same here, I hope this is being acknowledge by the designer.
There seems to a problem when it updates the settings. It does not happen every time. I can usually change pools several times before the miner disappears and never comes back. Tried reboot and powerdown, restore, other browsers.
My jackhammer solution is rewrite the SDcard with the image that is strangely over 14GB (takes ages )
although the system shows up only 4GB when running on the Pi, so there is very little space on the 16GB SDcard that could be used for other applications.
I may (or may not have) found the problem.
I noticed that the system's SDcard is full when the error occurs which might explain why it fails after I try to update the settings.
I searched if there are some logs that are filling it up and sure enough I found some files with several hundred MEGAbyte under /var/log.
Deleting them didn't help as Scripta was already kaputt from running on a 0byte filesystem but after I created the new image these files are only a few hundred kilobytes.
Then they start to grow again.
Is there a way to stop it from trying to send these useless log mails?
Scripta running on Midori is the only application I have running.