Closed aqueos closed 1 year ago
hard to read in the ticket here is the trace in txt file ! usermintrace.txt
Webmin and Usermin usually never crash really. Although, it can be killed by kernel (OOM). Try checking this out, e.g.:
dmesg -T | grep -i 'kill'
oh yes good idea i had not look there but i just reviewed all the kernel and syslog of the server and there is not any ooem or other messages.
the usermin log show only this when i click on it: ==> /var/usermin/miniserv.error <== [30/Jan/2023:17:45:34 +0100] Shutting down
best regards, Ghislain.
That indicates it was told to shut down. Quite different from a "crash".
yes the strace show the same but the very same thing work on the previous version and here each click makes it shutdown for no reason.
i dont know what i can do more to debug this :(
What is the output of systemctl restart usermin
and then systemctl status usermin
?
Also, check what is getting printed to /var/usermin/miniserv.error
after running those commands.
its a sysv system here it is:
VSGUEST:root@:[~]: /etc/init.d/usermin restart
Stopping Usermin server in /usr/share/usermin
/etc/usermin/.stop-init: 10: kill: No such process
Starting Usermin server in /usr/share/usermin
VSGUEST:root@:[~]: /etc/init.d/usermin restart
Stopping Usermin server in /usr/share/usermin
Starting Usermin server in /usr/share/usermin
VSGUEST:root@:[~]:
resulting logs:
[30/Jan/2023:18:33:10 +0100] miniserv.pl started
[30/Jan/2023:18:33:10 +0100] Using MD5 module Digest::MD5
[30/Jan/2023:18:33:10 +0100] Using SHA512 module Crypt::SHA
[30/Jan/2023:18:33:10 +0100] PAM authentication enabled
[30/Jan/2023:18:33:13 +0100] Shutting down
[30/Jan/2023:18:33:16 +0100] miniserv.pl started
[30/Jan/2023:18:33:16 +0100] Using MD5 module Digest::MD5
[30/Jan/2023:18:33:16 +0100] Using SHA512 module Crypt::SHA
[30/Jan/2023:18:33:16 +0100] PAM authentication enabled
VSGUEST:root@:[~]: facter os
{
architecture => "amd64",
distro => {
codename => "buster",
description => "Debian GNU/Linux 10 (buster)",
id => "Debian",
release => {
full => "10.13",
major => "10",
minor => "13"
}
},
family => "Debian",
hardware => "x86_64",
name => "Debian",
release => {
full => "10.13",
major => "10",
minor => "13"
},
selinux => {
enabled => false
}
}
VSGUEST:root@:[~]: dpkg -l usermin-webmail
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============-============-============-================================================================
ii usermin-webmail 1.861 all web-based user account administration interface for Unix systems
I thought that Debian 10 is always a systemd
system .. why not sticking with systemd
anyway?
It is not clear what is happening with Usermin but you will have to debug it. Start from looking into available resources (memory and disk space/quota).
By the way, what about Webmin? Does it get killed too?
no webmin/virtualmin are fine.
connecting directly from usermin with the user login/pass works. This is when i come from virtualmin that usermin is shutdown.
I can reproduce that issue (Jan 7 Virtualmin install / Usermin 1.861). Actually I had been experiencing its side effects without realizing the cause. Steps to reproduce:
Usermin log: [03/Apr/2023:12:28:52 +0000] PAM authentication enabled [03/Apr/2023:12:28:52 +0000] Using SHA512 module Crypt::SHA [03/Apr/2023:12:28:52 +0000] Using MD5 module Digest::MD5 [03/Apr/2023:12:28:52 +0000] miniserv.pl started [03/Apr/2023:12:28:48 +0000] Shutting down
Syslog: Apr 3 12:28:52 mars systemd[1]: Started Usermin server daemon. Apr 3 12:28:52 mars systemd[1]: usermin.service: Can't open PID file /var/usermin/miniserv.pid (yet?) after start: Operation not permitted Apr 3 12:28:50 mars systemd[1]: Starting Usermin server daemon... Apr 3 12:28:50 mars systemd[1]: usermin.service: Consumed 2.312s CPU time. Apr 3 12:28:50 mars systemd[1]: Stopped Usermin server daemon. Apr 3 12:28:50 mars systemd[1]: usermin.service: Scheduled restart job, restart counter is at 4. Apr 3 12:28:48 mars systemd[1]: usermin.service: Consumed 2.312s CPU time. Apr 3 12:28:48 mars systemd[1]: usermin.service: Failed with result 'signal'. Apr 3 12:28:48 mars systemd[1]: usermin.service: Main process exited, code=killed, status=10/USR1
Confirmed.
The reason why this happens is because when setting a new session for the user, Usermin is getting killed and automatically restarted only in 3 seconds (by systemd
). I will look into this problem deeper.
Thanks for reporting this.
This issue will be fixed in the next Webmin release.
https://github.com/webmin/webmin/commit/eaaa47081892099bfdbe5b173dd712f870ce7243
hi,
Since the upgrade to 1.861 connecting to a user from virtualmin lead to usermin crash.
Commandline: apt-get install --reinstall usermin-webmail=1.823 Downgrade: usermin-webmail:amd64 (1.861, 1.823) Upgrade: usermin-webmail:amd64 (1.823, 1.861)
i am on debian 10.
usermin 1.823 works fine.
When you edit user in virtualmin you have an option to "connecto to usermin as this user". After the upgrade the usermin stack crash without messages in the log.
Here is a trace of the crash when i click in virtualmin on this button to connect to usermin:
tell me if you need anything more ?
best regards, Adnet ghislain Aqueos.