I suspect this is probably down to memory availability i.e. processes consuming too much RAM at once, particularly as this command had worked previously and the error doesn’t seem to be coming from the command.
You can check the amount of free memory (in Megabytes) at any time using:
free -m
or open another SSH connection to your instance and use htop to monitor processes in real-time: