Skip to main content
Question

Jamf log flooded with this error today

  • March 16, 2017
  • 13 replies
  • 36 views

Forum|alt.badge.img+11

[MDMController ] - Error processing mdm request, returning 400

Just started today when I got in. The log is almost completely this error on dozens of devices. At one point I thought i saw that this was related to comms with Apple's Cloud but not sure.

Any ideas??

13 replies

Forum|alt.badge.img+5
  • New Contributor
  • April 6, 2017

We have seen the same thing for 8 months now, it eventually brings our JSS interface to such a crawl that the web page times out. Tech support has not found or resolved this issue for us either.

Hope they do soon. We are having to restart tomcat 2 - 3 times a day to get it stable.


Forum|alt.badge.img+26
  • Esteemed Contributor
  • April 6, 2017

What version(s) JSS are you at?


Forum|alt.badge.img+26
  • Esteemed Contributor
  • April 6, 2017

I am at 9.98, have 4300+ iOS devices, and yesterday I had more than normal #s of this error, not seeing them today.


Forum|alt.badge.img+5
  • Contributor
  • June 28, 2017

I am seeing this error as well, we have ~2000 devices and noticed it when it was redlining our mysql db cpu utilization. All the queries were MDM related and it seemed to be stuck looping aggressively. Restarting jss tomcat stopped the behavior, but would only remain normal for 1-6 hours before spamming 400 errors again spontaneously and redlining the database server again.

Not great, and looks like this issue is ongoing since 2014.


Forum|alt.badge.img+21
  • Valued Contributor
  • June 28, 2017

Maybe VPP is just screwed up right now. That would explain why my device-based installs aren't working.

IIRC they were going to integrate VPP into ASM this summer, which will likely cause a bump or two along the way.


Forum|alt.badge.img+8
  • Contributor
  • September 20, 2017

I have this issue just now.. (upgraded from 9.100 tot 9.101) and it is only on our slave server.... (in the DMZ)

Anyone have a fix for this ?


Forum|alt.badge.img
  • New Contributor
  • September 20, 2017

Apple has new terms & conditions that I had to accept when logging in to their site today, perhaps that has something to do with it? I saw this had caused problems in the past for people.


Forum|alt.badge.img
  • Employee
  • September 22, 2017

Same issue here... What I see from my side is that "Update Inventory" command always get pending, all commands following "Update Inventory" will get pending as well unless I cancel the "Update Inventory" command.


Forum|alt.badge.img+11
  • Contributor
  • September 22, 2017

Guys, we're on 9.100.0 and have seen the issue since August-ish (when we really started looking due to perf issues). We rolled out laptops to students the 2nd week and were having DB performance issues, etc. as a result of the error and some network changes. After ironing out several network bugs (new public IPs, etc.), we still noticed a sizable lag, especially if we deployed software packages.

Long story, kind of short, we've cleaned out logs and our DB is back down to a reasonable size, but we've had to work at it. The log file ballooned from ~650 MB to 7.92 GB in about a month....

Good news is the iOS side seems OK, but the commands will be slow to respond--app rollouts/installs are OK, inventory update, passcode clear, etc. take some time. After working to clean out logs/DB, it's much better, but still a delay larger than what we'd previously seen. We have an active open ticket at the moment to see how we can resolve.


Forum|alt.badge.img+1
  • New Contributor
  • October 11, 2017

We are having a similar issue. However, I'm not sure when it began, as our infosec team recently brought it to our attention. We recently upgraded to JSS to 9.101.0xxxx.
The LTM shows the error as: <142>Sep 29 07:49:58 lv-nap-ltm-1 httpd: <FOO SRC IP ADDRESS 1> <BAR DST IP ADDRESS> [29/Sep/2017:07:49:58 -0700] "PUT /mdm/ServerURL HTTP/1.1" 400 8443 -
<142>Sep 29 07:49:57 lv-nap-ltm-1 httpd: <FOO SRC IP ADDRESS 1> <BAR DST IP ADDRESS> [29/Sep/2017:07:49:57 -0700] "PUT /teesnap/mdm/ServerURL HTTP/1.1" 400 8443

Tomcat Logs as:
[ERROR] [43-exec-218] [MDMController ] - Error processing mdm request, returning 400. Device: 691, CommandUUID: e0b3cf38-xxxxxx
[ERROR] [43-exec-170] [MDMController ] - Error processing mdm request, returning 400. Device: 1140, CommandUUID: f0b322d1


Forum|alt.badge.img+10
  • Valued Contributor
  • October 12, 2017

you guys are lucky if you get a device ID or any details at all - my logs flood with this crap:

[MDMController ] - Error processing mdm request, returning 400. Device: Null, CommandUUID: mraNull

it's only when students are on prem, though...have a case open with jamf but not getting anywhere...


Forum|alt.badge.img+8
  • Contributor
  • December 7, 2017

For posterity - we had this happen today. We were getting APNS rejections, and the 400 errors in our logs. And, like @WSDIT said, there was a new T&C on School Manager. I accepted it, and we were able to start sending APNs again.


Forum|alt.badge.img+9
  • Contributor
  • December 22, 2017

Hello,

See this post here, but this might be issue PI-004915
https://www.jamf.com/jamf-nation/discussions/26331/jamf-pro-10-0-virtually-killed-my-jss#responseChild156827

Thanks,
Jason