Communications Problem Service Required VDS Message

[marco2228]

Thanks, thats great. Will try that

 

[hanknum]

IT'S ALIVE!!!

Many thanks to Mark and this forum. Don't know where I'd be without them.

Mark tried to reset the VMS remotely, but that didn't work. I unplugged the VMS with help from Mark and other threads with photos and instructions, and Viola. I will pull the logs and see what there is to see.

Again, thanks everyone. I don't think these Roadsters would be viable w/o this forum.

Henry

 

[hcsharp]

Nominating @markwj for Roadster MVP...

 

[markwj]

IT'S ALIVE!!!

Many thanks to Mark and this forum. Don't know where I'd be without them.

Mark tried to reset the VMS remotely, but that didn't work. I unplugged the VMS with help from Mark and other threads with photos and instructions, and Viola. I will pull the logs and see what there is to see.

Again, thanks everyone. I don't think these Roadsters would be viable w/o this forum.

Henry

FYI (for others in the same boat):

From the logs, the issue started a week or so before vds comms fault was shown. Linux out-of-memory called, and killed obd, inetd, and watchdog (so no remote diagnostics, or magic restart).

Then a week later another out-of-memory killed vms processes (hence car dead and vds comms error).

A hard unplug and replug of the VMS solved the problem.

 

[markwj]

Nominating @markwj for Roadster MVP...

From you, Henry, that means a lot

 

[spaceballs]

... Linux out-of-memory called, and killed obd, inetd, and watchdog (so no remote diagnostics, or magic restart)....

Any idea what process has the memory leak?

 

[markwj]

Any idea what process has the memory leak?

None. Logs don’t say much, and VMS was rebooted. Wouldn’t have been able to get in remotely anyway with obd process killed.

 

[hanknum]

I'm just going to proceed normally, unless someone has a better idea.

Thanks.