Support Questions

Find answers, ask questions, and share your expertise

QuickStart on Windows VM - Impala Daemon fails to start

avatar
New Contributor

Hi

 

I am unable to progress through the tutorial as I cant start Impala due to below error.

 

Thanks

Mark

 

Dec 28, 9:57:46.827 PM INFO impala-server.cc:1760

ImpalaInternalService listening on 22000

Dec 28, 9:57:46.831 PM INFO thrift-util.cc:109

TServerSocket::listen() socket() Address family not supported by protocol

Dec 28, 9:57:46.831 PM ERROR thrift-server.cc:175

ThriftServer 'backend' (on port: 22000) exited due to TException: Could not create server socket.: Address family not supported by protocol

Dec 28, 9:57:46.831 PM ERROR thrift-server.cc:164

ThriftServer 'backend' (on port: 22000) did not start correctly

Dec 28, 9:57:46.831 PM INFO status.cc:112

ThriftServer 'backend' (on port: 22000) did not start correctly
@ 0x79eff3 (unknown)
@ 0x952489 (unknown)
@ 0x952d28 (unknown)
@ 0x77b02a (unknown)
@ 0x305be1ecdd (unknown)
@ 0x77ac89 (unknown)

Dec 28, 9:57:46.831 PM ERROR impalad-main.cc:76

ThriftServer 'backend' (on port: 22000) did not start correctly

1 ACCEPTED SOLUTION

avatar
New Contributor

Problem fixed. Changed the VM settings back to 1 virtual CPU and installed VMWare update for Linux. 

View solution in original post

5 REPLIES 5

avatar
New Contributor

Problem fixed. Changed the VM settings back to 1 virtual CPU and installed VMWare update for Linux. 

avatar
New Contributor

Can you please elaborate on the fix?

avatar
New Contributor

Not much to add. When I started the Linux VM. The VM promoted me to download an update for Linux. Once I did this the Impala Deamon issues disappeared.

avatar
New Contributor
Can you please provide details regarding which VM platform you use and the Linux version you updated to.

I'm having the exact issue using VMWare Workstation, I have reduced the number of CPUs to 1 and updated VMWare-Tools, no Linux update was shown though.

avatar
Explorer

Hi!

 

Could you please be more specific as to which update was needed? I've upgraded my VMWare Tools to the latest ones but I assume we're talking about more Linux-kernel based upgrades which are not part of the VMWare Tools. I'm still experiencing exactly the same error as initially mentioned in this topic although I've upgraded my VMWare related stuff.