Did a upgrade and a funky issue is now going on...
Setting up webmin (1.650) ...
Webmin install complete. You can now login to https://borgnet.us:10100/
as root with your root password, or as any user who can use sudo
to run commands as root.
Setting up webmin-virtual-server (4.02) ...
sh: -M: invalid option
Usage: sh [GNU long option] [option] ...
sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--protected
--rcfile
--restricted
--verbose
--version
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
sh: -M: invalid option
Usage: sh [GNU long option] [option] ...
sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--protected
--rcfile
--restricted
--verbose
--version
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
Comments
Submitted by sgrayban on Thu, 08/22/2013 - 04:22 Comment #1
Now I am getting errors with a cronjob...
Subject: Cron <root@borgnet> /etc/webmin/status/monitor.pl
Content-Type: text/plain; charset=UTF-8
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
sh: -M: invalid option
Usage: sh [GNU long option] [option] ...
sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--protected
--rcfile
--restricted
--verbose
--version
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
sh: -M: invalid option
Usage: sh [GNU long option] [option] ...
sh [GNU long option] [option] script-file ...
GNU long options:
--debug
--debugger
--dump-po-strings
--dump-strings
--help
--init-file
--login
--noediting
--noprofile
--norc
--posix
--protected
--rcfile
--restricted
--verbose
--version
Shell options:
-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
Submitted by andreychek on Thu, 08/22/2013 - 09:12 Comment #2
Hi Scott -- thanks for the bug report! Jamie will be able to comment with more details shortly, but I wanted to ask a few questions in the meantime --
I've been working to reproduce the issue you're seeing, but so far I haven't been able to reproduce it on any of my systems. I attempted the upgrade on a Debian 6, Debian 7, CentOS 6, and Ubuntu 12.04 system.
Is it just this one system that you're seeing this problem on? Or have you seen that on multiple systems?
If it's multiple systems, were they all Debian 6?
Also, what's the output of this command on one of the systems having that problem:
ls -l /bin/shThanks!
Submitted by JamieCameron on Thu, 08/22/2013 - 11:05 Comment #3
Someone else reported this on the mailing list as well, but I haven't figured out the cause yet. What's odd is that nowhere in Webmin or Virtualmin is the -M flag passed to the shell for anything!
If you SSH in as root and manually run
/etc/webmin/status/monitor.pl, does it output that same error?If so, what is the output from :
grep -- -M /etc/webmin/status/services/*Submitted by sgrayban on Thu, 08/22/2013 - 15:58 Comment #4
This is very odd.
Nothing happens when running from the command line but when run via cron I get the error.
Submitted by JamieCameron on Thu, 08/22/2013 - 23:07 Comment #5
Is the error coming from cron on every run?
Submitted by sgrayban on Fri, 08/23/2013 - 02:14 Comment #6
Every cron run and its only happening on debian 6 (squeeze)
Submitted by JamieCameron on Fri, 08/23/2013 - 18:28 Comment #7
Do you have a monitor setup that checks an SSL certificate for validity? That's the only change that has been made recently in the System and Server Status module.