How to troubleshoot "Failed to get local socket name :"???

Gentlemen;

I have a small server running ubuntu 6.06.1 server disto which has no gui.
Therefor, for sysadmin I normally install and use webmin. However, on this
one machine when I try to access webmin from a browser on another machine
it fails. The subject server's webmin miniserv.error log show the error:
"Failed to et local socket name :"

I can't find any references to this anywhere (usenet, google, forums, etc).

nmap, lsof and other utils show the onlything using the specified port
(10000) is miniserv.pl itself.

Can anyone shed some light on how one can go about troubleshooting this
error?

I am quite lost!!!!

TIA

On Jan 26, 5:42 pm, bobmct <b...@worthless.info> wrote:

> I have a small server running ubuntu 6.06.1 server disto which has no gui.
> Therefor, for sysadmin I normally install and use webmin. However, on this
> one machine when I try to access webmin from a browser on another machine
> it fails. The subject server's webmin miniserv.error log show the error:
> "Failed to et local socket name :"

Can you describe the problem with a bit more detail than "it fails"?

DS

David Schwartz wrote:

>
>
> On Jan 26, 5:42 pm, bobmct <b...@worthless.info> wrote:
>
>> I have a small server running ubuntu 6.06.1 server disto which has no
>> gui.
>> Therefor, for sysadmin I normally install and use webmin. However, on
>> this one machine when I try to access webmin from a browser on another
>> machine
>> it fails. The subject server's webmin miniserv.error log show the error:
>> "Failed to et local socket name :"
>
> Can you describe the problem with a bit more detail than "it fails"?
>
> DS

Well, I would love to. But it fails and the ONLY message I receive anywhere
is the one I posted.

However, I was able to resolve this issue with a response from a local Linux
Group member. His suggestion was to be sure the the server's domain name
was being resolved properly. It wasn't! I added a FQDN (Fully Qualified
Domain Name) to the /etc/hosts file, the tried to access webmin from
another systems browser and it worked like a charm.

It's too bad that there wan't more "MEAT" to the error being reported. It
was a simple fix. If only the error was reported for the right reason.

Thanks...