[SOLVED]Artisan commands possibly being cached or running wrong command

I'm having a strange issue since I've moved my website to a new server. The old server was running PHP 5.4, the new server PHP 5.6. I have over a dozen Artisan commands in Laravel 4.2 that run via cron at different intervals. Occasionally, it will run the wrong command. I don't know how often it happens since most don't give any output, but occasionally I'll get an error notification from Command Y, but the command that was run was Command M. apc.enable_cli and opcache.enable_cli are set to off. Are there any other caching settings I should be looking at, or a different setting?



via aynber