I have successfully install Virtualmin on Debian Etch 4.0 - all works good. After that I try to do an upgrade from Debian Etch to Lenny and see unmet dependencies: [code:1] The following packages are BROKEN: virtualmin-base The following packages have unmet dependencies: virtualmin-base: Depends: proftpd-common which is a virtual package. Depends: libsasl2 which is a virtual package. [/code:1] On Debian Lenny this packages named as proftpd and libsasl2-2. When I change dependencies in deb package manually, all installs good.
Will this be fixed in future versions of Virtualmin or this is a problem in Debian Lenny?
The problem is stay here on fresh Debian Lenny install:
[code:1]# dpkg -i ./virtualmin-base_1.0-19_all.deb
Selecting previously deselected package virtualmin-base.
(Reading database ... 122387 files and directories currently installed.)
Unpacking virtualmin-base (from .../virtualmin-base_1.0-19_all.deb) ...
dpkg: dependency problems prevent configuration of virtualmin-base:
virtualmin-base depends on proftpd-common; however:
Package proftpd-common is not installed.
virtualmin-base depends on libsasl2; however:
Package libsasl2 is not installed.
dpkg: error processing virtualmin-base (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
virtualmin-base
[/code:1]
In Debian Lenny repos packages have another names:
[code:1]proftpd-common -> proftpd
libsasl2 -> libsasl2-2[/code:1]<br><br>Post edited by: Murz, at: 2008/09/26 04:35
I hope your dog gets through this.
I found this discussion about Debian 5.0 (Lenny) and have the same curiosities as the others. I need to install Virtualmin on a new server running Debian 5.0 and obviously I'm in a hurry. (you know, bigger, better, faster!)
I hope that the pooch is OK...
Not trying to be rude, but is there an ETA for this? I'm getting pretty close to having to get this Lenny server live and would rather get virtualmin than ispconfig to run it.
Thanks, and good luck to your pupster!
I don't like to put a firm date on things, because I'm always wrong when I do. But, ETA might be tonight. I've been poking and prodding and tweaking all day, and I'm in the middle of a test install right now that I kinda expect to complete without error (and then the actual testing of the completed install begins, which could take another several hours, but if we're lucky and Debian 5.0 isn't majorly different from Debian 4.0 or Ubuntu 8.04, then it should go fast).
I've taken a break from that to answer this question. So, now it's gonna be 1.5 minutes later. ;-)
--
Check out the forum guidelines!
OK, so a couple of test installs and tweaks later, we are pretty much "go" on Debian Lenny. There are a couple of cosmetic issues with mail server detection, but those straighten out pretty much on their own when you click "start" on the Mail Server item in the Status section of the System Information page (after the configuration check).
I'm not going to announce it as officially supported until the couple of issues I noted have been fixed...but I don't think there's any harm in folks installing right now--we can fix whatever problems pop up. Just know that it hasn't been heavily tested. Very superficial testing (configuration check passes, basic poking around looks reasonable...but no functional testing of actual hosting features has been done).
I just noticed one other bug. The suexec configuration failed for some reason, so you'll need to edit /etc/apache2/suexec/www-data and change the first line from "/var/www" to "/home". I could have sworn I'd gotten that one right, but obviously not. I'll tackle it first thing in the morning.
So all you folks offering to test...have at it! Expect issues. Try not to be too repetitive in reporting them (this is why I rarely roll out "testing" releases...I get fifty reports of the same bug...often a problem that is already noted in the release notes). ;-)
And for folks not feeling even a little adventurous, it'll certainly be more solid by tomorrow night.
--
Check out the forum guidelines!
One last caveat, I don't build the 64 bit version until the 32 bit version is solid. So there is <i>no</i> 64 bit support for Lenny. It will come tomorrow after the 32 bit version is solid.
--
Check out the forum guidelines!
ok i successfully managed to upgrade a debian 4.0 + virtualmin pro to debian 5.0 + virtualmin pro in a vmware machine, 32 bit.
there are no gpl packages yet i believe so couldnt test that one.
i guess in 2 days i will upgrade my production 64 bit debian to lenny + vm pro, wish me luck :P
I should have been more clear: Virtualmin GPL gets rolled out at the same time as the 64 bit builds. There will be no GPL support for Lenny until tonight some time when the last couple of bugs I mentioned are ironed out.
That's what I get for talking after my bed time.
--
Check out the forum guidelines!
Oh, I'm sorry, didn't understand this. Time zones allow for answers even when you're sleeping!
<div class='quote'>Oh, I'm sorry, didn't understand this.</div>
No reason for you to have known about my build and deploy process. ;-)
It goes like this:
Build, test, and iterate on 32 bit Virtualmin Professional repository. This takes a week or so, usually, though this stage took two weeks this time due to personal issues I mentioned earlier (and my dog is gonna be fine--she's one of the very lucky 25-50% for whom the splenic tumor is not malignant, as far as the pathologist can tell).
Once everything looks as good as I can make it, build 64 bit packages, test that.
Once tests are passing, add the new OS to the GPL link script (which links the packages into the non-password protected /gpl/ directory tree).
Update the GPL download script to the new version that supports the OS.
Finally, update the OS Support page to reflect the new OS.
Oh, and I guess there's the "let people bang on it for a while" stage, which usually reveals another half dozen subtle issues that need to be fixed.
--
Check out the forum guidelines!
Hello, I'm really new to virtualmin (saw it the first time 2 days ago :) ), so no idea if I'm doing anything wrong...
Tried to install it on a clean freshly installed Debian 5.0 - virtual machine in VirtualBox.
I ran the script as root, here the problem:
<div class='quote'>INFO - Download of http://software.virtualmin.com/lib/RPM-GPG-KEY-webmin Succeeded.
INFO - OK
INFO - OK
E: Malformed line 14 in source list /etc/apt/sources.list (dist parse)
INFO -
INFO - Removing Debian standard Webmin package, if they exist (because they're broken)...
INFO - Removing Debian apache packages...
E: Malformed line 14 in source list /etc/apt/sources.list (dist parse)
E: The list of sources could not be read.
INFO - Installing dependencies using command: /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install postfix postfix-pcre webmin usermin ruby libapache2-mod-ruby libxml-simple-perl libcrypt-ssleay-perl unzip zip
...in progress, please wait...
E: Malformed line 14 in source list /etc/apt/sources.list (dist parse)
E:-The list of sources could not be read. /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install postfix postfix-pcre webmin usermin ruby libapache2-mod-ruby libxml-simple-perl libcrypt-ssleay-perl unzip zip failed. Error (if any): 0
Displaying the last 15 lines of /root/virtualmin-install.log to help troubleshoot this problem:</div>
Now this seems strange:
<div class='quote'>machine:~# cat /etc/apt/sources.list
01: #
02: # deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official i386 NETINST Binary-1 20090214-16:03]/ lenny main
03:
04: #deb cdrom:[Debian GNU/Linux 5.0.0 _Lenny_ - Official i386 NETINST Binary-1 20090214-16:03]/ lenny main
05:
06: deb http://mirror.switch.ch/ftp/mirror/debian/ lenny main
07: deb-src http://mirror.switch.ch/ftp/mirror/debian/ lenny main
08:
09: deb http://security.debian.org/ lenny/updates main
10: deb-src http://security.debian.org/ lenny/updates main
11:
12: deb http://volatile.debian.org/debian-volatile lenny/volatile main
13: deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
</div>
sources.list is only 13 lines long... why is there a problem in the 14th line??
Thanks in advance
nice, i scheduled the dist-upgrade of my production server for this friday :)
Yep, we'll definitely be shiny on lenny by Friday.
I rolled out all of the packages for 64 bit and GPL (except for the actual virtual-server module, which I'm rolling right now) last night, and I'm doing test installs today. I usually find a few mistakes when first setting up repos, so I wouldn't expect it to actually work until this afternoon some time. I'll add lenny to the OS Support page as soon as I have successful test installs across all of the various arches and versions. Each test install takes about 30 minutes to an hour, including some basic QC testing.
--
Check out the forum guidelines!
Iâ
Iâ
Iâ
Nothing like being at the forefront of technology. :)
Cheers!
Yep. Until it's listed on the OS Support page, you're gonna have to expect problems. (I'm not holding out on anybody--if it works, I like to brag about it.) ;-)
Anyway, I think 32 bit GPL is now mostly working. My quick test ran fine (a quick test involves not actually starting from a fresh OS install, so it can miss several classes of issue--saves me 15 minutes, and reveals obvious stupid stuff like broken repositories faster). I'm starting the 64 bit testing now, which will probably shake out any remaining issues, as it'll be starting from a fresh OS install.
--
Check out the forum guidelines!
i am getting the same error except a different line number.
<div class='quote'>E: Malformed line 7 in source list /etc/apt/sources.list (dist parse)</div>
Now /etc/apt/sources.list is only 6 lines so guess it is something the install script is adding.
x86 GPL version
Howdy,
So, I have an idea of how we can figure out what the problem is. The question is, are you into doing some Bash script hacking, or would you like a hand with it? :-) I'm also assuming that Virtualmin didn't install on your system.
If you look in the install.sh script, on line 736, it says "# Install our keys".
Immediately before that line, add in this line:
[code:1]
cp /etc/apt/sources.list /root/sources.list.broken
[/code:1]
And next time you run the installer (which, again, you shouldn't do if Virtualmin is working on your system), you have the problem version of sources.list stored in /root/sources.list.broken.
Could you then attach (or carefully paste) that sources.list.broken file into a forum posting?
If you'd like a hand doing the above, feel free to yell ;-)
Thanks!
-Eric
using the above tip, line 7 looks like this
<div class='quote'>deb http://software.virtualmin.com/gpl/debian/ main</div>
Indeed, that is malformed!
It's missing the distribution/version between the URL there and "main".
I'll make sure Joe sees that so he can tweak the install script.
Thanks!
-Eric
I don't see that happening on my test systems. What is in /etc/issue?
--
Check out the forum guidelines!
Argh. Somehow I managed to copy an old version of install.sh into the GPL download location--which didn't know about lenny. It's fixed now, I think. At least, the install.sh that you get when you download it is the one I've actually been testing with, so when there are problems they should be problems I can reproduce. ;-)
--
Check out the forum guidelines!
just installed your latest on a 64 bit system, installed and set up without any errors of any kind, after my reboot had a couple of minor errors mailman and saslauthd, good work! :)
<div class='quote'>just installed your latest on a 64 bit system, installed and set up without any errors of any kind, after my reboot had a couple of minor errors mailman and saslauthd, good work!</div>
Yep, still needs some tweaking. The GPL version seems to be ending with an error, despite no clues about why (the install completes, but it still ends with an error rather than success). apt-get/dpkg is very persnickety when running non-interactively, unfortunately.
But, anyway, it <i>does</i> look like it's working close enough to get folks a working system, though the system might need a couple of tweaks afterward.
--
Check out the forum guidelines!
I am using the GPL version by the way.
Ugh, since I can't edit my post I'll have to triple post.
I looked a bit closer and it didn't give me the exact same error. First it told me the package was not installed and then it gave me the same error.
Try apt-get clean. This might just be a bad download (maybe downloaded when I was still having issues with the repo maintenance scripts). I haven't seen this error in any of my test installs, so I don't think there's anything wrong with the package or the repo in this case.
--
Check out the forum guidelines!
Wow! Install went as smooth as can be! Even on a server that has been pretty beaten up with installing/removing other management products and mail/database/ftp servers.
This is really a FANTASTIC product. My first time using it and I have already added a server, configured it to use my external DNS servers, created and tested email and FTP users and all within 20 minutes!
Amazing work, Joe. Thanks! Now I am going to sit down and read the documentation!
Again, great job and well worth the wait.
<div class='quote'>Wow! Install went as smooth as can be!</div>
Sweet! I'm definitely getting closer, anyway. I think there are still some quirks on lenny, but it's close enough for hand grenades.
--
Check out the forum guidelines!
12 hours to go, then i'll do the dist-upgrade on my production virtualmin pro x64 debian server :P
hopefully no bad surprises =)
I did a clean and fresh brabones install of Lenny and then installed virtualmin. Everything looked pretty good, and I set up an outlook client for email and tested account settings (SMTP requires auth and tried both log into incoming first and use same settings but outgoing fails with a timeout after a generous 2 minutes)
Sending from usermin is successful.
Any thoughts? Is this the wrong forum or thread for this?
Thanks! I'm still thoroughly impressed and somewhat amazed at the quality of work you've put into this.
I've now (successfully) upgraded to Debian lenny 5.0.
I had some problems, especially with Apache (the new ports.conf and default site config break things, and had to config the custom suexec path by hand, then php5 segfaulting... though that "seems" to have gone away since i rebooted.
However I broke PostgreSQL. Not really tragic, since no one uses it. Basically I had 7.4 which is deprecated, so I uninstalled it and adapted the config in Webmin to use the 8.3 stuff. However, I get this error: DBI connect failed : could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
Any ideas how to fix this?
damn, now this is more urgent... sending mail with smtp is broken, something with sasl is wrong :( if anyone has had problems pleas tell me how you solved them! i'm trying on my own in the meanwhile...
add this to your /etc/default/saslauthd file
OPTIONS="-c -r -m /var/run/saslauthd"
restart the server and it should not post an error and mail should work
doesn't work :'(
actually i looked at my backup of that file and i got this:
OPTIONS="-m /var/spool/postfix/var/run/saslauthd -r"
but this doesn't work either... something else must have screwed up. damn!!!
ok actually Tdah i think your line does solve the problem :P
i hope i can go to sleep now without things going bad... :)
one more issue I had was the php mysql connector, my sites were saying it was missing so I just used the apt search for php5-mysql installed it, restarted both mysql and apache2 and it worked
You might run into a sending mail issue that involves the saslauthd, I read on another forum post from andreychek
http://www.virtualmin.com/forums/virtualmin/can-receive-but-not-send-ema...
Run these commands and youâ
There's also the problem that shows up Ubuntu and maybe is also present on Debian now. Worth checking:
http://www.virtualmin.com/index.php?option=com_fireboard&Itemid=77&a...
--
Check out the forum guidelines!
Still same issue. Cant send emails. I've done the steps above, mentioned by tdah and in the theads posted by Joe and tdah respectively...
When I try to send mail I get this in mail.log
[code:1]
Mar 7 09:23:59 evil dovecot: pop3-login: Login: user=<scott.mydomain>, method=PLAIN, rip=64.156.25.3, lip=64.157.15.75, TLS
Mar 7 09:23:59 evil dovecot: POP3(scott.mydomain): Disconnected: Logged out top=0/0, retr=0/0, del=0/3, size=7680
Mar 7 09:24:20 evil postfix/smtpd[10349]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit
Mar 7 09:24:21 evil postfix/master[10335]: warning: process /usr/lib/postfix/smtpd pid 10349 exit status 1
Mar 7 09:24:21 evil postfix/master[10335]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Mar 7 09:25:21 evil postfix/smtpd[10381]: fatal: parameter "smtpd_recipient_restrictions": specify at least one working instance of: check_relay_domains, reject_unauth_destination, reject, defer or defer_if_permit
Mar 7 09:25:22 evil postfix/master[10335]: warning: process /usr/lib/postfix/smtpd pid 10381 exit status 1
Mar 7 09:25:22 evil postfix/master[10335]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
[/code:1]
and I'm not sure what the "specify at least one working instance of: ... lines refer to.
I have patched the virtualmin-base_1.0-19-lenny1_all.deb package file for succesfully install on Debian Lenny. Patched deb is attached to message.
Patched deb is here: [file name=virtualmin_base_1.zip size=11101]http://www.virtualmin.com/components/com_fireboard/uploaded/files/virtua...
P.S. Again I can't edit my previos post in forum because URL for editing post is exactly like for earlier messages.
in the meanwhile a newer virtualmin version has been released.
are the dependencis fixed in that version? or do i still need to patch...
s.
Howdy,
I wouldn't expect Virtualmin to support Lenny out of the box until sometime after Lenny has been released :-)
Etch and Sarge are currently the only Debian releases Virtualmin provides packages for:
http://www.virtualmin.com/os-support.html
It of course *can* work on those other ones, but there's some effort involved ;-)
-Eric
As Eric mentioned, we do not support unreleased operating systems. We just can't. There are too many variables, too few people to maintain all of the packages and repositories (we already have more than a dozen repositories), and too many ways for beta software to go wrong. So, no need to ask...if the OS isn't released yet, we definitely do not support it and have no plans to do so.
--
Check out the forum guidelines!
allright! i fully understand and will patiently wait :)
Newer version of virtualmin deb has all dependencies solved on Debian Lenny 5.0, thanks!
I have a fresh install of Lenny. And since it is officially stable, I was wondering about the Virtualmin. Does it support Debian 5 now?
Pages