fat fingering cif --otype -f resulted in odd behaviors twice.
after troubleshooting cif being unresponsive, it appears that the user root@localhost was not in the cif-tokens table. -> restarted server.. it was back
when trying to reproduce the problem (by analyzing apache logs) cif --otype -f was a hung command which required ctrl-c to interrupt the process. immediately after running cif -p, it failed.
waiting 1m, cif -p and cif started working again.
end result, cannot reliably reproduce but I saw some wonky behavior.
fat fingering
cif --otype -f
resulted in odd behaviors twice.cif --otype -f
was a hung command which required ctrl-c to interrupt the process. immediately after running cif -p, it failed.waiting 1m, cif -p and cif started working again.
end result, cannot reliably reproduce but I saw some wonky behavior.