socket.error: [Errno 92] Protocol not available

[Andres Rodriguez]

MAAS 1.8.0b1
Running on Trusty LXC Container on Precise Host

maas-regiond and maas-clusterd failed to start with the following error:

Traceback (most recent call last):
  File "/usr/bin/twistd", line 14, in <module>
    run()
  File "/usr/lib/python2.7/dist-packages/twisted/scripts/twistd.py", line 27, in run
    app.run(runApp, ServerOptions)
  File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 642, in run
    runApp(config)
  File "/usr/lib/python2.7/dist-packages/twisted/scripts/twistd.py", line 23, in runApp
    _SomeApplicationRunner(config).run()
  File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 376, in run
    self.application = self.createOrGetApplication()
  File "/usr/lib/python2.7/dist-packages/twisted/application/app.py", line 436, in createOrGetApplication
    ser = plg.makeService(self.config.subOptions)
  File "/usr/lib/python2.7/dist-packages/provisioningserver/plugin.py", line 196, in makeService
    image_service = self._makeImageService()
  File "/usr/lib/python2.7/dist-packages/provisioningserver/plugin.py", line 122, in _makeImageService
    s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEPORT, 1)
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
socket.error: [Errno 92] Protocol not available

[Andres Rodriguez (andreserl)]

Researching on the internet I came across this:

https://hg.python.org/cpython/rev/00766fa3366b

I tested this manually and this patch seemed to fix things

[Gavin Panella (allenap)]

We can also fix this in our code, by catching the socket.error around
that particular call.

However, we're targeting Trusty and later with 1.8, so maybe this should
be Won't Fix? Trusty-on-Precise-via-LXC is not "real" Trusty because it
is using the older Precise kernel.

[Andres Rodriguez (andreserl)]

Precise is a LTS release and running a Trusty LXC is a perfect valid
scenario. This has to be fixed as this is affecting a production service.
On Apr 8, 2015 4:45 AM, "Gavin Panella" <email address hidden> wrote:

> We can also fix this in our code, by catching the socket.error around
> that particular call.
>
> However, we're targeting Trusty and later with 1.8, so maybe this should
> be Won't Fix? Trusty-on-Precise-via-LXC is not "real" Trusty because it
> is using the older Precise kernel.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1441399
>
> Title:
> socket.error: [Errno 92] Protocol not available
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1441399/+subscriptions
>

[Gavin Panella (allenap)]

Is the Precise host using linux-image-generic-lts-trusty? That would /probably/ be another way to work around this problem.