Closed nelsontalag closed 3 years ago
It not only fails on scale up. It seems to be failing on initial deploy also.
@UmakanthOS are you seeing the same at your end?
We were getting this error when using:
"fileServerType": {
"value": "nfs"
},
Thanks @nelsontalag and @ChrisLopezUK. For 18.04, there was a jq bug that needed the addition of a repository (fixed in latest iteration of template).
Looks like we have two issues here:
Flagging with @ummadisudhakar. Will investigate.
Latest changes seemed to resolve this for me. @nelsontalag are you still seeing issues?
Yes its working fine now the latest update fixed the issue
this was the line that helped
curl https://stedolan.github.io/jq/download/linux64/jq > /usr/bin/jq && chmod +x /usr/bin/jq
The latest Template has worked well and we were able to handle abouta total of 29k users(not concurrent) with around 2600 users concurrently online.
it had scaled as expected for about 2 weeks until we had encountered this error
_/helper_functions.sh: line 65: jq: command not found + export phpVersion= + phpVersion= + echo + echo + echo + echo + echo + echo + echo + echo + echo + echo + echo + echo + echo + echo + sudo add-apt-repository ppa:ondrej/php -y + sudo apt-get update + check_fileServerTypeparam + local fileServerType= + '[' '' '!=' gluster -a '' '!=' azurefiles -a '' '!=' nfs -a '' '!=' nfs-ha -a '' '!=' nfs-byo ']' + echo 'Invalid fileServerType () given. Only '\''gluster'\'', '\''azurefiles'\'', '\''nfs'\'', '\''nfs-ha'\'' or '\''nfs-byo'\'' are allowed. Exiting' + exit 1
its interesting to note that as a fix, we added a sudo apt install jq before the breakpoint line error but stilll get the same error.
we have rewritten the the script and it now works see scrip here
then we replaced the vmss extension to get from a storage blob
We are just perplexed on how a previously working script suddenly fails on scale up
how somebody can help give light on this scaling problem
thanks