Back

#Laravel friends, I need your help! I'm on a tight deadline and running into a weird issue where queued jobs are running even when the workers are stopped AND it's logging OLD exception verbiage instead of new. Details:

gist.github.com/chrispian/ea62ba268fbc790ef357a4f463d4f1cd



I'm stuck and if you have a minute to read that gist and have any ideas I could really use some help.

5

267

0 / 1000

Forgot to make the gist public, fixed.

42

Seen this a couple of times before. Happy to help. How to get in touch?

1

91

@martin_ro I have some ideas what's going on but would love to have another person who's familiar to bounce some ideas off of. Hit me up chrispian @ gmail.com and we can take it from there. I'd be happy to jump on a call if you want and share my screen. I can't post the code public, unfortunately.

1

102

I've emailed you

76

Had a very similar thing, but the full restart solved the issue (but it was hard to understand that the exception thrown in the logs is the old one). Might be a dumb one, but have you tried to change the queue connection in .env?

24

You not gonna believe this, but right now I'm experiencing the same issue (except I don't have jobs on my project yet) and Laravel keeps throwing an exception with the old code :/

17

@martin_ro @HungryBus I ended up finding out that the network team cloned the box to create us a new dev env - so the queue worker was running over there causing the odd behavior we've been seeing. So glad to finally have found this!

Thank you guys both for trying to help. This was a tough one to prove out. Ended up watching DB connections because our network team didn't have a record of any clone being done - the ticket is still in progress! Such a weird one.

1

59

Glad you figured it out!

1

98

@martin_ro Thanks! Bad timing but I'm glad it happened, really learned a lot about the queue and debugging them even more and now I understand the serialization / deserialization even better. This was a good thing with horrible timing lol.

70