These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Webmin 1.401 breaks and deletes VM Pro on the new forum.
Web Hosting and Cloud Computing Control Panels
What OS/version have you seen this behavior on? Were there any errors when updating Webmin?
--
Check out the forum guidelines!
It happened on...
debian 4.0
Ubuntu Linux 6.10
Mandriva 2007 and 2007.1
And the updates took place automatic so I have no clue if there were any errors but I have disabled all automatic updates from now on because of this.
<div class='quote'>And the updates took place automatic so I have no clue if there were any errors but I have disabled all automatic updates from now on because of this.</div>
Oh! So it might not be the Webmin update...it could be virtualmin-base? jezdez has reported the postinst running on upgrades (which shouldn't happen, but if it does might cause the theme to be switched back to default, among other things). I'm trying to reproduce this behavior now.
If you'd like me to drop in on your box, I'd be happy to. I'd actually like to see what happened. This is clearly dramatic behavior...but I don't see it on my boxes, and so I'm at a loss for how to fix it.
--
Check out the forum guidelines!
There was no changing of types of installs either -- tar to rpm or tar to deb
These updates have been the same from day one -- automatic and with no issues before until now.
What are you wanting to look at? I can't give you access right now but I can paste what ever you need.
Doing a upgrade for webmin......
debian package
Setting up webmin (4.0.1) ...
Error: Script was not run with full path (failed to find /usr/share/webmin/run-postinstalls.pl under /usr/share/webmin)
This was intentional to break the postinstall and to show you that it DOES run the postinstall even for a upgrade.
<div class='quote'>Setting up webmin (4.0.1) ...
Error: Script was not run with full path (failed to find /usr/share/webmin/run-postinstalls.pl under /usr/share/webmin)</div>
That's supposed to happen, and should be harmless (actually it's a positive thing, as it update stuff that has changed between versions). If it's not harmless, we'd want to fix it. I'm testing on an already installed Debian system now to see if there are any issues with the new Webmin or virtualmin-base (I only tested fresh installs over the weekend, though Jamie upgraded all of his Debian and Ubuntu installs without any errors, as far as I know).
The post install script running problem I'm talking about would be with the postinst in the virtualmin-base Debian package. Wholly orthogonal to Webmin's postinstalls scripts. The script I'm talking about is one triggered by Debian's packaging systemm and included in the virtualmin-base deb. This postinstalls.pl is a standard Webmin thing that always gets run on updates--and has been so for many years.
--
Check out the forum guidelines!
All I know is that upgrading webmin to 4.0.1 is broken. It removes all VM Pro plus plugins and even the VM Pro theme.
I prevented one of my biggest customer from upgrading webmin for fear it will completely kill his users and accounts.
But I know for a fact when webmin upgrades no existing modules from the previous version was transfered.
In fact it deleted the old version on a tarball upgrade before it copied the existing modules.
This is a webmin bug clearly.
I know I'm going to sound stupid saying the same thing again...but I just don't understand what's happening on your sytsems. I just can't reproduce this behavior, and nothing has changed in the Webmin upgrade process in several revisions.
1.400 had the referer lockdown that affected the install.sh installation process...and it also had a bug that made some BIND installations look like they weren't running, when they actually were. The former was fixed by an update to virtualmin-base, while the latter was fixed by the release of 1.401. But nothing changed in the way Webmin is upgraded.
If, as jezdez indicated, the virtualmin-base postinst script is running under some circumstances on updates, then Debian and Ubuntu systems would possibly see some configuration breakage on installation of that package (which could make the theme switch back to the blue framed theme, but wouldn't delete any modules or themes...just some configuration files might change). This wouldn't effect tarball or RPM installed systems, at all (and couldn't--tarball systems don't have a virtualmin-base, and RPM uses a completely different test to determine if the package is being upgraded or installed fresh).
Of course, if the Webmin upgrade process is the culprit, then virtualmin-base is irrelevant, and I should stop worrying over it in this thread--that's something I'll have to work with jezdez to figure out. I just can't think of how the Webmin upgrade would suddenly behave so differently on some subset of systems (the subset that is wholly contained by the subset that you manage). ;-)
--
Check out the forum guidelines!
It's not just mine system -- it was all my clients that updated that were affected. The big client of mine I have prevented the upgrade of webmin until I see fit.
Upgrading webmin did NOT -- I repeat DID NOT transfer any previous installed modules to the new version. I can't make this any clearer.
1) purchased your license today
2) upgraded modules
3) entered the license
4) installed phpmyadmin
5) installed the powerdns and mail relay module and upgraded webmin
6) logged out
7) logged back in and saw a very new look/feel which is the "old" gui so that got changed automatically, then i changed it back to the framed version.
Here are some screen shots: <a href='http://picasaweb.google.com/billyclark/WorkStuff' target='_blank'>http://picasaweb.google.com/billyclark/WorkStuff</a>
Even I fail to see what is broken.
You are using a theme that is NOT virtualmin aware. That has nothing to do with VM Pro missing.
If you click on System Information does your license show up?
No it does not. I am new to VM Pro so not sure how I would do anything outside of the default settings. I liked the framed version and would not change it so the theme was not by my choice. This accelerator is brand new and I've only logged into it about 10-15 times total. The upgrade to the 1.401, PowerDNS, Mail Relay. I think these all were tried at the same time. The only install before those is phpmyadmin. That is the extent of what I've done inside Virtualmin.
Here are some logs if they help any:
from etc/webmin/config
passwd_cindex=2
real_os_type=Sun Solaris
gotoone=1
realname=
os_version=11
passwd_file=/etc/shadow
tempdelete_days=7
os_type=solaris
hostnamemode=0
ld_path=/lib:/usr/lib:/opt/csw/lib:/opt/csw/apache2/lib:/opt/csw/bdb4/lib:/opt/csw/bdb43/lib:/opt/csw/flex-2.5.31/lib:/opt/csw/gcc3/lib:/opt/csw/lighttpd/lib:/opt/csw/mysql4/lib:/opt/csw/mysql5/lib:/opt/csw/postgresql/lib:/opt/csw/sparc-sun-solaris2.8/lib
ownmods_lbt=mysql apache virtual-server passwd proc cron change-user htaccess-htpasswd mailboxes virtualmin-dav virtualmin-svn
help_width=
gotomodule=
logusers=
passwd_pindex=1
passwd_mindex=4
nofeedbackcc=2
hostnamedisplay=
referers_none=1
feedback_to=
passwd_uindex=0
noremember=
deftab=system
readonly_lbt=virtual-server
real_os_version=11
logfiles=1
sysinfo=0
logfullfiles=
by_view=0
logtime=168
log=1
logperms=
texttitles=1
md5pass=1
theme=blue-theme
nohostname=
notabs=0
ld_env=LD_LIBRARY_PATH
showlogin=0
notabs_lbt=1
find_pid_command=ps -ef | grep NAME | grep -v grep | awk '{ print $2 }'
logmodules=
path=/sbin:/bin:/opt/csw/apache2/sbin:/opt/csw/sbin/:/opt/csw/bin/:/usr/sbin:/usr/bin:/usr/local/bin:/opt/csw/apache2/sbin:/opt/csw/sbin/:/opt/csw/bin/:/opt/csw/gcc3/bin:/opt/csw/gnu:/opt/csw/mysql5/bin:/opt/csw/mysql4/bin:/opt/csw/postgresql/bin:/opt/SUNWspro/bin
logclear=
product=webmin
help_height=
lang_admin=en
theme_admin=blue-theme
i saw this in the system logs that happened about the same time i performed the upgrade as virtualmin suggested:
Changed file /etc/webmin/security-updates/config
1a2,3
> sched_action=0
> sched_email=billy.clark@rassai.com
Changed file /var/spool/cron/crontabs/root
42a43
> 0 0 * * * /etc/webmin/security-updates/update.pl
Created file /etc/webmin/security-updates/update.pl
0a1,10
> #!/opt/csw/bin/perl
> open(CONF, "/etc/webmin/miniserv.conf");
> while(<CONF>) {
> $root = $1 if (/^root=(.*)/);
> }
> close(CONF);
> $ENV{'WEBMIN_CONFIG'} = "/etc/webmin";
> $ENV{'WEBMIN_VAR'} = "/var/webmin";
> chdir("$root/security-updates");
> exec("$root/security-updates/update.pl", @ARGV) || die "Failed to run $root/security-updates/update.pl : $!";
here is a link to the joyent forum post that i put out there:
<a href='http://discuss.joyent.com/viewtopic.php?pid=175775#p175775' target='_blank'>http://discuss.joyent.com/viewtopic.php?pid=175775#p175775</a>
No it does not. I am new to VM Pro so not sure how I would do anything outside of the default settings. I liked the framed version and would not change it so the theme was not by my choice. This accelerator is brand new and I've only logged into it about 10-15 times total. The upgrade to the 1.401, PowerDNS, Mail Relay. I think these all were tried at the same time. The only install before those is phpmyadmin. That is the extent of what I've done inside Virtualmin.
Here are some logs if they help any:
from etc/webmin/config
passwd_cindex=2
real_os_type=Sun Solaris
gotoone=1
realname=
os_version=11
passwd_file=/etc/shadow
tempdelete_days=7
os_type=solaris
hostnamemode=0
ld_path=/lib:/usr/lib:/opt/csw/lib:/opt/csw/apache2/lib:/opt/csw/bdb4/lib:/opt/csw/bdb43/lib:/opt/csw/flex-2.5.31/lib:/opt/csw/gcc3/lib:/opt/csw/lighttpd/lib:/opt/csw/mysql4/lib:/opt/csw/mysql5/lib:/opt/csw/postgresql/lib:/opt/csw/sparc-sun-solaris2.8/lib
ownmods_lbt=mysql apache virtual-server passwd proc cron change-user htaccess-htpasswd mailboxes virtualmin-dav virtualmin-svn
help_width=
gotomodule=
logusers=
passwd_pindex=1
passwd_mindex=4
nofeedbackcc=2
hostnamedisplay=
referers_none=1
feedback_to=
passwd_uindex=0
noremember=
deftab=system
readonly_lbt=virtual-server
real_os_version=11
logfiles=1
sysinfo=0
logfullfiles=
by_view=0
logtime=168
log=1
logperms=
texttitles=1
md5pass=1
theme=blue-theme
nohostname=
notabs=0
ld_env=LD_LIBRARY_PATH
showlogin=0
notabs_lbt=1
find_pid_command=ps -ef | grep NAME | grep -v grep | awk '{ print $2 }'
logmodules=
path=/sbin:/bin:/opt/csw/apache2/sbin:/opt/csw/sbin/:/opt/csw/bin/:/usr/sbin:/usr/bin:/usr/local/bin:/opt/csw/apache2/sbin:/opt/csw/sbin/:/opt/csw/bin/:/opt/csw/gcc3/bin:/opt/csw/gnu:/opt/csw/mysql5/bin:/opt/csw/mysql4/bin:/opt/csw/postgresql/bin:/opt/SUNWspro/bin
logclear=
product=webmin
help_height=
lang_admin=en
theme_admin=blue-theme
i saw this in the system logs that happened about the same time i performed the upgrade as virtualmin suggested:
Changed file /etc/webmin/security-updates/config
1a2,3
> sched_action=0
> sched_email=billy.clark@rassai.com
Changed file /var/spool/cron/crontabs/root
42a43
> 0 0 * * * /etc/webmin/security-updates/update.pl
Created file /etc/webmin/security-updates/update.pl
0a1,10
> #!/opt/csw/bin/perl
> open(CONF, "/etc/webmin/miniserv.conf");
> while(<CONF>) {
> $root = $1 if (/^root=(.*)/);
> }
> close(CONF);
> $ENV{'WEBMIN_CONFIG'} = "/etc/webmin";
> $ENV{'WEBMIN_VAR'} = "/var/webmin";
> chdir("$root/security-updates");
> exec("$root/security-updates/update.pl", @ARGV) || die "Failed to run $root/security-updates/update.pl : $!";
here is a link to the joyent forum post that i put out there:
<a href='http://discuss.joyent.com/viewtopic.php?pid=175775#p175775' target='_blank'>http://discuss.joyent.com/viewtopic.php?pid=175775#p175775</a>
Please call me and we can get this done. -Billy 1.817.312.8211
Please join my meeting at
https://www1.gotomeeting.com/join/836661741
I'll leave this open until we talk. My skype IM is billy.dean.clark and yahoo is froggydetail
To fix this you have to manually re-install webmin-virtual-server -- DO NOT RE-RUN THE INSTALL SCRIPT.
And it looks like Joe/Jamie are busy so if you need this ASAP you can always hire a person here like me.
You can also see that my work is impeccable -- Just read what others have said about my work for them at http://www.virtualmin.com/forums/jobs/looking-for-jobs.html
can you jump in right now? do you accept paypal?
Yes I can on both.
I'll skype you
i just added you to my skype, please go ahead accept me and start this go2m
Please join my meeting at https://www1.gotomeeting.com/join/836661741
thanks!
gotomeeting is a windows/mac only thing -- I use linux only.
Joe this is a solaris install done by Joynet who say that webmin/virtualmin are fully supported but by all accounts the docs I read and the comments from you in the past solaris isn't supported.
In fact this Joynet has completely screwed up the linux/unix hierarchy. Wget doesn't even work correctly -- You cant get VM Pro installed because this install has the wrong env path's set.
They claim that Joyent is your largest deployment. I can not believe this after looking at this server install.
<div class='quote'>Joe this is a solaris install done by Joynet who say that webmin/virtualmin are fully supported but by all accounts the docs I read and the comments from you in the past solaris isn't supported.</div>
Solaris is definitely supported, and Joyent have been using Virtualmin since the very earliest days. They know what they're doing.
<div class='quote'>In fact this Joynet has completely screwed up the linux/unix hierarchy. Wget doesn't even work correctly -- You cant get VM Pro installed because this install has the wrong env path's set.</div>
They have a custom Webmin/Virtualmin install. We thought the Upgrade to Professional button worked well on Joyent systems, but it doesn't seem to. We work with them regularly, however, and the problem will be fixed (whether its on our end or theirs...probably ours).
<div class='quote'>They claim that Joyent is your largest deployment. I can not believe this after looking at this server install.</div>
They are. They've been a great friend to Virtualmin over the years, and they know their business. It doesn't look like a usual Virtualmin deployment--but it's still a good deployment. (In fact, they came up with a lot of the techniques we use for PHP and Ruby on Rails. We modified them a bit to make them more sane on Linux, but they definitely provided a lot of guidance.)
--
Check out the forum guidelines!
Well this upgrade from GPL to Pro is completely broke -- right now only webmin is installed and trying to get the Pro to install again has not worked.
<div class='quote'>Well this upgrade from GPL to Pro is completely broke -- right now only webmin is installed and trying to get the Pro to install again has not worked.</div>
That would be our fault, not Joyent's. The Upgrade to Professional feature is our code, and should work without pain...if it doesn't, we've failed. ;-)
Billy, if you'd like to contact me via email with the details of this system, I'll drop in and fix it, and get Jamie on the task of making sure future upgraders are not hit with this bug.
--
Check out the forum guidelines!
Oh, yeah, my email is joe@virtualmin.com.
--
Check out the forum guidelines!
I can't get over there env stuff either -- it follows no lunix/unix setup -- instead of using /usr/local/bin they use /opt/csw/bin/ which I completely fail to understand why any unix OS would do such a silly thing.
<div class='quote'>I can't get over there env stuff either -- it follows no lunix/unix setup -- instead of using /usr/local/bin they use /opt/csw/bin/ which I completely fail to understand why any unix OS would do such a silly thing.</div>
This is a standard location on Solaris. Weird, I know, but non-system stuff goes in /opt on Solaris. Interestingly, if you read the Red Hat packaging guidelines, they also require third party software to install into /opt. So, some big name third party apps for RHEL install into /opt. We've opted not to go that route (pun not intended), since experienced Linux admins, like you, would be utterly confused by packages installing into /opt. ;-)
--
Check out the forum guidelines!
RH sings to a entirely different tune then the average linux OS.
Just look how many times they have broken libraries without telling of the changes.
And solaris? WOW what a messed up OS -- it will be one I never use for any reason.
<div class='quote'>And solaris? WOW what a messed up OS -- it will be one I never use for any reason.</div>
Don't teach your granny how to suck eggs. Sun was doing UNIX before most of us were born, and certainly before I ever used a shell. I was using a Commodore 64 when those guys were building the original Sun workstations and popularizing UNIX. ;-)
I actually agree, and think Solaris needs a MAJOR overhaul in several areas--the standard system tools feel ancient, their package management is a joke, they don't support group quotas, and the have some odd limits in uncomfortable places. But, they get some things right. Solaris Zones are, by far, the best option for virtualized hosting right now. From a stability and performance standpoint, they rock the socks off anything for Linux. Xen is stable enough but a resource hog in contrast. vservers/OpenVZ is roughly as efficient but has some weird stability issues if not configured very carefully. And, of course, Joyent are selling virtualized system hosting...so Solaris is a smart choice. It takes getting used to, and I certainly prefer working in Linux, but it's a really solid OS. Reliability of Solaris is definitely among the best in the world.
Different strokes for different folks, and all. (Jamie's also a big fan of Solaris, and the first version of Webmin worked only on Solaris. Sun's been a supporter of Webmin over the years, too. We like Sun, even if they are imperfect. We've all got room for improvement, I reckon.)
--
Check out the forum guidelines!
Point taken. But seriously linux/unix admin follow basic hierarchy. /usr/bin /bin /usr/local -- heck even BSD uses that now. So why can't solaris ?
Guess I need to brush up on my solaris -- first on list is asprin and beer the solaris LOL
this happened to me too! please HELP!!!
<div class='quote'>this happened to me too! please HELP!!!</div>
What happened to you, too? You need to tell us something about your system--this is not an issue I have ever seen with my own eyes, and I've never been able to reproduce it.
If I'm ever going to be able to do anything about this issue, I need to know:
What OS/version you are running
What version of Webmin you started with and what version you upgraded to
What kind of package you're using (and whether you used the same package type for the original install and the upgrade)
Where the package came from (Webmin.com, Virtualmin.com, some OS repo)
Any errors you saw during the upgrade
Without all of that, I have no clue what happened, because I've never seen it myself.
--
Check out the forum guidelines!
Linda & Filip from Joyent will be in touch with you shortly. I have this web meeting open right now where I can share my desktop:
Please join my meeting at https://www1.gotomeeting.com/join/141901137
Call me if you need to at 1.817.312.8211 (please delete this # after you write it down"
Looks like there's a bug in the upgrade from GPL to Pro process on Solaris. The theme should be "virtual-server-theme", but it's set to "blue-theme" here, which, if it isn't actually available (I know Joyent use a custom minimized Webmin with all extraneous stuff removed) would lead to you seeing the ancient unthemed Webmin appearance, which I believe is what you're seeing.
So, if you switch to the Virtualmin theme in Webmin:Webmin Configuration:Webmin Themes do things look normal again? If you don't have that option in the themes page, maybe the new directory doesn't contain all of the additional modules--this would be congruent with what Scott has reported, and I seem to recall he has at least some systems installed from tarball (I've never been able to replicate it with RPM or deb installed systems, but maybe the copy step is broken in tarb upgrades).
You can see whether you have the Virtualmin module and theme by looking in the currently running Webmin versions directory to see if a "virtual-server" and "virtual-server-theme" directory exist.
I'd be happy to drop in on your box and have a look to see what is actually going on. I'm having a hard time really grasping what's going on.
--
Check out the forum guidelines!