New error I’ve never seen.
[code]=======================================================
Error
Error in RenderTasks: RenderFrame: Exception caught in 3ds max: simple_socket::receive: Invalid packet size (given 1131770482)
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage, AbortLevel& abortLevel)
=======================================================
Type
RenderPluginException
=======================================================
Stack Trace
at Deadline.Plugins.Plugin.RenderTask(String taskId, Int32 startFrame, Int32 endFrame)
at Deadline.Slaves.SlaveRenderThread.RenderCurrentTask(TaskLogWriter tlw)
=======================================================
Full Log
0: Task timeout is disabled.
0: Plugin rendering frame(s): 55
0: INFO: Render Tasks called
0: INFO: ERROR: Exception caught in 3ds max: simple_socket::receive: Invalid packet size (given 1131770482)[/code]
Not sure if its related, but we get a similar error on the pulse machine’s system log:
Nov 11 13:00:30 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:08:19 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:08:20 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:08:23 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:09:55 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:09:59 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:10:08 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:11:24 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:11:28 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:11:41 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:12:04 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:12:05 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:12:08 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:12:17 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:13:46 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:13:47 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:13:50 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:13:59 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:22:57 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:22:58 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:28:46 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:28:50 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:28:59 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:31:05 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:31:08 deadline avahi-daemon[1864]: Invalid query packet.
Nov 11 13:31:17 deadline avahi-daemon[1864]: Invalid query packet.
This max error has been around for a while, and can happen if the socket connection to max becomes corrupted. How often are you seeing this error come up?
It’s completely unrelated to the Pulse messages Laszlo is seeing. I’m not sure those are even related to Deadline…
bugs.launchpad.net/ubuntu/+sour … bug/426909
Is “deadline” in those system logs the name of the user that avahi-daemon is running as?
Just a thought…but reading up on the “avahi-daemon” (OSX ‘bonjour’ like networking type service, which I assume is very chatty over the network) and I’m getting quite a few hits describing how this daemon causes excessive CPU usage. If it’s running on your Pulse machine which potentially has lots of machines connecting to it, perhaps this might help explain the high CPU usage Laszlo has been seeing? Perhaps this daemon is running on your DB machine as well?
Ok, we turned off avahi. It was running as its own ‘avahi’ user, not sure how deadline ended up in that log line to be honest. Probably part of some domain name or something