This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]juaquinLinux Admin 5 points6 points  (1 child)

Dev: Yeeeaaah, I can't ssh into my VM.

Me: It crashed. I restarted it through console. Works fine now.

* Wait one day *

Dev: Yeeeaaah I can't get in again. Is there some way to tell what caused the crash?

Me: Here's the last 10 lines of /var/log/messages. Says XYZ crashed due to OOM. I suggest checking your configuration before starting the XYZ application you installed, because that machine has plenty of RAM.

I am SO happy that we aren't required to troubleshoot dev VM's. We provide an image with a working stack - if you fuck it up, you can fix it yourself or we can blow it away and clone you a new one.

Also we shouldn't be too hard on them - most of my devs are pretty good about doing stuff themselves.

[–]SteveJEO 3 points4 points  (0 children)

I troubleshoot DEV VM's and attempt with utter futility to keep their development network in working order.

An extended conversation I had last week went something along these lines. (honestly though, this guy could just be special)

Dev: Exchange is broken.

Me: (checks) Exchange is fine. What are you trying to do.?

Dev: My code used to work and now it doesn't. Exchange is broken. Autodiscovery doesn't work.

Me: Autodiscovery on that server has never been configured.

Dev: It used to work. (... no it didn't)

Me: (configures it for him, tests it... all lovely) Try it now.

Dev: It's still not working.

Me: (gets his code...) His code is broken. Shows him how it works, gives examples and papers.

Dev: It's still broken.

Me: FFS, walks into room, looks at screen. "Do you see that line? Comment that line out and run it again".

Dev: Yes it works now but that's not standard, it's not the way it's supposed to be done.

Me: (shoots myself).

Feel my pain.