Submitted by yngens on Wed, 10/24/2018 - 04:34
I am absolutely sure I had updated Authentic Theme to 19.20-beta6 several hours ago, but logging back to the same system just now I've noticed it's back to 19.19. Can you please elaborate on why it could do so? Is Authentic Theme version is bound to Webmin theme? How can we make theme updates persistent?
Another question is I know you, guys, are going to push 19.20 to production soon, however we have bunch of Virtual servers the end-users of which are complaining they do not see Webmin tab, so we need to be able to push 19.20 programmatically on multiple systems. Updating Authentic Theme through UI is easy, but how could we do it on command line?
Status:
Closed (works as designed)
Comments
Hi,
It couldn't happen automatically. Your package manager apparently was run in the background and upgraded to the Webmin package containing older theme.
To upgrade using command line you can run
theme-update.shfrom theme directory. Use--helpswitch to get more details on it.Regards, Ilia
Submitted by yngens on Wed, 10/24/2018 - 05:24 Comment #2
Worked like a charm. Thanks Ilia!
You are also welcome to try latest mail in Usermin.
You would need to run
./update-from-repo.shfrom Usermin dir, after running theme update script. (which pulls latest and working update script for Usermin).It's going to production soon. It's been gigantic amount of work done, and countless days put into it (only listing so far).
In case you pull all changes for Usermin - all should work.
Submitted by yngens on Sat, 10/27/2018 - 06:45 Comment #4
I have to re-open this issue as logging in today I found Authentic Theme reverted back to 19.19 on the same CentOS 7.x system with Webmin 1.894.1017.0250, Usermin 1.741 and Virtualmin 6.04. I am afraid regular updates from Webmin repository override upgraded Authentic Theme's dev version to regular one.
Ilia, thanks for your suggestion to also update Usermin, however we use RoundCude becuase of its feature-richness. We completely disable Usermin on our servers. Do you think we should start using Usermin instead of RoundCube and if so then why do you believe so? Is Usermin now good enough to ditch RoundCube over it?
How do you run update script for Webmin exactly? Do you use any switches when running it?
Speaking about Usermin in comparison to RoundeCube - I'm working on making it more and more feature-rich. Latest theme updates take Usermin closer to this goal.
Please share which features exactly you find most useful in RoundCube that currently missing in Usermin? By the way, why not use Desktop Mail Client for managing mail?
Submitted by yngens on Sat, 10/27/2018 - 07:41 Comment #6
Usually, we dont take any additional action letting *min software to get automatic updates through
/etc/yum.repos.d/virtualmin.repo, however in case of this server we had to pull the latest dev Webmin version because of https://www.virtualmin.com/node/59124 using the/usr/libexec/webmin/update-from-repo.shscript. Also we upgraded to the latest Authentic Theme version using/usr/libexec/webmin/authentic-theme/theme-update.sh, however what is strange it that the theme keeps reverting back to 19.19.I will give another try to Usermin today to see if it meets our expectations. Probably Jamie is the best person to know, but maybe you, Ilia, could also elaborate on whether using Usermin increases the server resources consumption? You see, when we install RoundCude, then its scripts are invoked only when a user tries to login and use it whereas when Usermin is activated its deamon is always running in background eating resources. So for small servers with limited resources turning it off is better. But I'd love to learn I am wrong about this.
I'll do if we decided to start using Usermin.
Well, we do recommend our customers to use phone and desktop mail client programs to pull their e-mails via pop or imap, however there are cases when they use webmail.
Submitted by yngens on Sun, 10/28/2018 - 09:04 Comment #7
Logged in today to the same server and see now:
Webmin version 1.894.1017.0250Usermin version 1.741
Virtualmin version 6.04
Theme version Authentic Theme 19.19
Have to run the
/usr/libexec/webmin/authentic-theme/theme-update.shcommand again, but it would be really nice to have sustainable version upgrades.:) you possible have it run in cron jobs. Check your logs! Theme doesn't do anything by itself! It would be unethical!
Submitted by yngens on Sun, 10/28/2018 - 09:08 Comment #9
Uups, running the
/usr/libexec/webmin/authentic-theme/theme-update.shtoday has given:HTTP/1.0 500 Perl execution failed Server: MiniServ/1.89410170250 Date: Sun, 28 Oct 2018 14:04:42 GMT Content-type: text/html; Charset=iso-8859-1 Connection: close
Error - Perl execution failed
Can't use an undefined value as a HASH reference at /usr/libexec/webmin/authentic-theme/authentic-lib.pm line 1132.
Submitted by yngens on Sun, 10/28/2018 - 09:29 Comment #10
Hi Ilia,
Crontab is empty and only has the following line:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /etc/webmin/status/monitor.plI have an impression it is not a theme, but a Webmin problem. I suppose regular Webmin updates from
/etc/yum.repos.d/virtualmin.repokeep overriding theme upgrade to git version. So maybe James can do something about this inconsistency?For the error - update Webmin with update script as well!
Submitted by yngens on Sun, 10/28/2018 - 09:40 Comment #12
I did, Ilia, unfortunately the error persists even with the latest Webmin pulled from git.
Submitted by yngens on Sun, 10/28/2018 - 10:50 Comment #13
Ok, since it was taking some time for you, guys, to troubleshoot this I had to try to get through this with the solution reported on https://www.virtualmin.com/comment/804282#comment-804282 - I had to manually delete the
/usr/libexec/webmin/.~files.Submitted by yngens on Mon, 10/29/2018 - 05:12 Comment #14
It is funny, but I find it really amusing logging back to the same system every time and find the theme reverted back to 19.19. Todays stats:
Operating system CentOS Linux 7.5.1804Webmin version 1.894.1028.1330
Usermin version 1.741
Virtualmin version 6.04
Theme version Authentic Theme 19.19
Time on system Monday, October 29, 2018 1:03 PM
Kernel and CPU Linux 3.10.0-862.14.4.el7.x86_64 on x86_64
I have an impression this issue is tracked only by me and you, Ilia, so let's attribute it to Webmin core project in hope Jamie or Joe will finally start paying attention to the subject matter of the problem. I understand that the production version for Authentic Theme is 19.19 at the moment, however for those who want to be on a bleeding edge and use git version of Webmin and Authentic Theme it should been made possible. Otherwise, the existence of such scripts like
/usr/libexec/webmin/authentic-theme/theme-update.shis meaningless, because after a while the theme reverts back to its production version.That is odd.
Try checking output
yum historyon your machine; try modifying theme update script and make it write the log, including the caller.Do you run script manually and it updates wrong or it happens automatically?
Submitted by yngens on Mon, 10/29/2018 - 06:16 Comment #16
Ilia, nothing is wrong with the theme update script - it does its job. What I am trying to conduct here is that in my guess its Webmin that pulls the production version of Authentic Theme and overrides it.
Submitted by yngens on Mon, 10/29/2018 - 10:14 Comment #17
I've sorted this out thanks to Ilias hint to check everything. The server reported had the following custom cron-job which was not in the main crontab and therefor was not easy to spot:
yes | sh /usr/libexec/webmin/authentic-theme/theme-update.sh -release >/dev/null 2>&1So I am marking this as closed and sorry for false alarm.