Due to a change in an external price ticker API, a patch to your admin server is likely required for many machines to continue service.
This affects those using a fiat currency not natively supported by their selected ticker source, which are most currencies other than USD and EUR, or those using BitPay as a ticker.
Until you do so, your machines will not be able to transact on cryptocurrencies for which it cannot retrieve a price.
Patching your server
To do so, log into your server's terminal and run the following command:
curl -sS https://raw.githubusercontent.com/LamassuSupport/lamascripts/master/patch/ticker-bignumber/patch.sh | bash
Following that, you'll see 'Patch applied' and your server will continue retrieving price rates as expected.
You may then check your admin's Funding panel for the fiat balance equivalent of your wallets, which indicates ticker rates are being correctly retrieved.
No further action is needed, though if you have any questions, please reach out to our support team.
This afternoon (04 June 2019) it was discovered that BitPay greatly increased the precision to which they're producing BTC price rates. This caused newly retrieved rates from them to not be parsed, and servers as a result were no longer able to produce local prices for cryptocurrencies.
In addition to a ticker option itself, BitPay is used to obtain FOREX rates when native pairs don't exist for an admin's selected fiat currency and cryptocurrency.
Because supported ticker sources have trading pairs mostly for USD and EUR, this means that tickers for other currencies rely on the BitPay API to produce local fiat exchange rates, converting the Kraken BTC / USD rate, for example, into the BTC / CHF Kraken-equivalent.
When the server is unable to retrieve a current price, rather than risk transacting using a stale price, it will take the coin offline until it obtains a new rate. Thus, coins are not at risk of being sold at incorrect rates.
The above patch will be incorporated in any newly created servers and in our upcoming v7.3 update, though existing servers will need to apply it before then.
We will closely monitor the server's various price APIs and make any further notices on our Twitter and Telegram channels. The update to servers mitigates the effect of future such changes to API responses, and we'll also be exploring options for additional native price sources.