Installing webmin on Knoppix

**lasar** · 09-10-2003, 01:57 PM

Hello all.

I am trying to install Webmin on my remastered Knoppix CD. The CD is supposed to be a rescue bootup CD for faceless servers. The CD contains network configs and such.
If you mean to tell me that Webmin isn't the best way to do things, don't. I know that, my boss doesn't.

So far I have tried three ways:

a) apt-get install webmin
b) Get webmin-1.100 from webmin.com and install with ./setup.sh
c) Copy all webmin-related files from my host Debian system onto the CD image.

Always, no matter what installation method I tried, I get this:

Code:

[root@debian:~] /etc/webmin/start
Starting Webmin server in /usr/share/webmin
unix dgram connect: No such file or directory at /usr/share/webmin/miniserv.pl line 191
Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/perl/5.8.0/Socket.pm line 201.

Any ideas on this one? I have searched the interweb by google and found no relevant pages.
Perl version on the CD (and on the host system, where webmin works just fine) is 5.8.0.
By the way, I have updated the CD's system by running apt-get update;apt-get dist-upgrade. Might this be the problem?

Thanks all,

_Lasar

**hugo** · 09-11-2003, 01:34 AM

What's here?

unix dgram connect: No such file or directory at /usr/share/webmin/miniserv.pl line 191

What does that line refer to?
Why would doing a dist-upgrade cause the problem?

Regards,

Hugo.

**garyng** · 09-11-2003, 01:39 AM

Have you tried running webmin before the remastering ? Sounds like some configuration issue to me.

**cesman** · 09-11-2003, 08:53 AM

Originally Posted by lasar

By the way, I have updated the CD's system by running apt-get update;apt-get dist-upgrade. Might this be the problem?

I'm not certain, but I've been told apt-get dist-upgrade brakes too many things and not to use it. I myself have installed webmin(apt-get), the only issue I have is having to change the password after an hdinstall...

cesman

**lasar** · 09-11-2003, 09:00 AM

Good insert-your-time-of-day-here.

The line that throws the error is this one:

Code:

eval { syslog("info", ucfirst($config{'pam'})." starting"); };

and it comes from this code block:

Code:

if ($use_syslog) {     
        eval 'openlog($config{"pam"}, "cons,pid,ndelay", "authpriv"); setlogsock("unix")';
        if ($@) {
                $use_syslog = 0;
                }
        else {                  
                eval { syslog("info", ucfirst($config{'pam'})." starting"); };
                if ($@) {
                        setlogsock("inet");
                        syslog("info", ucfirst($config{'pam'})." starting");
                        }
                }
        }

Have you tried running webmin before the remastering ? Sounds like some configuration issue to me.

It did not matter whether I ran webmin while chrooted into it on the disk or while booted from CD.

Why would doing a dist-upgrade cause the problem?

I don't know if it matters at all. I just wanted to mention it in case it did (or does) matter.

I'm not certain, but I've been told apt-get dist-upgrade brakes too many things and not to use it. I myself have installed webmin(apt-get), the only issue I have is having to change the password after an hdinstall...

Well, it might be the reason. Next time I start from scratch I'm not going to do the dist-upgrade. Thanks for letting me know that webmin can indeed run on Knoppix :)

Anyway, I solved the problem by disabling the whole code block above. As far as I can tell it is just used for Webmin's own logging purposes, which do not interest me in this case.
I simply replaced "if ($use_syslog) {" with "if(0){" and it worked.
Surely a dirty solution, but it works for me, so I'm happy.

Thanks for your help everybody,

_Lasar

**mikeypants** · 09-11-2003, 02:51 PM

I've never used Webmin before, but my first thought was that maybe the log file it's trying to write to is read only, or you don't have permission to access it.

It's just a guess, though I don't see why there would be a problem with writing to a log if it's on your hdd - that should only be a problem if it's on a read-only CD (or more specifically, a read-only dir on the CD).

Again, just a guess.

Good luck.