Menu

#5593 problems with 2.010 upgrade on x86_64 - file manager and terminal

2.010
open
nobody
5
2022-12-02
2022-11-30
No

3 problems with 2.010 upgrade on x86_64

1) On both opensuse 15.4 and Centos 7.9.2009, File manager no longer runs:

HTTP/1.0 500 Perl execution failed
Server: MiniServ/2.010
Date: Tue, 29 Nov 2022 21:54:01 GMT
Content-type: text/html; Charset=utf-8
Connection: close
Error — Perl execution failed
Undefined subroutine &filemin::mimetype called at ./filemin-lib.pl line 466.

This still works on Debian 11 / Raspberry pi however

2) On Opensuse 15.4, the new terminal package reports "The Perl package perl-IO-Tty is missing..." Yet it is installed and up to date.

3) On Centos 7.9.2009 the new terminal package reports "The Perl module Net::WebSocket::Server is missing", Yet it is installed and up to date

Discussion

  • Ilia

    Ilia - 2022-11-30

    On both opensuse 15.4 and Centos 7.9.2009, File manager no longer runs:

    Tried restarting Webmin manually?

    On Opensuse 15.4, the new terminal package reports "The Perl package perl-IO-Tty is missing..." Yet it is installed and up to date.

    How did you install perl-IO-Tty package? If you run on the command line perl -e "use IO::Tty;" -- what do you get?

    On Centos 7.9.2009 the new terminal package reports "The Perl module Net::WebSocket::Server is missing", Yet it is installed and up to date

    Also, what do you get if you run perl -e "use IO::Tty;"? Also, what is getting logged to /tmp/.webmin/ws-nn.out file when trying to connect?

     
  • Richard Farthing

    Yes- both instances of webmin restarted from Systemd

    On Suse, perl-IO-Tty was installed already. I updated via YAST from Suse repo as there was a later version (link was provided in webmin to devel:languages:perl repository, but made no difference.

    perl -e "use IO::Tty;" runs with no errors, same on Centos

    However on Centos perl -e "use Net::WebSocket::Server;" works OK on command line, but has a reported missing module when trying to update in Webmin.
    "Test::More Protocol::WebSocket (Missing 1 modules)"

    On Centos manual update via cpan however reports all OK, as follows:
    cpan[2]> install Test::More
    Test::More is up to date (1.302191).
    cpan[3]> install Protocol::WebSocket
    Protocol::WebSocket is up to date (0.26).
    cpan[8]> upgrade Protocol::WebSocket
    All modules are up to date for Protocol::WebSocket

    On OpenSuse I removed and updated CPAN and Net::WebSocket::Server
    Now I get a connection, but get connection error
    "Error: Connection to the socket wss://ha-server.lan:7991/xterm/ws-555 lost

    /tmp/.webmin files...
    ws-555.out:
    Running shell '/bin/bash -bash' with pid 4374
    listening on port 555
    timeout waiting for connection at /usr/libexec/webmin-2.010/xterm/shellserver.pl line 88.
    ws-556.out:
    Running shell '/bin/bash -bash' with pid 6536
    listening on port 556
    timeout waiting for connection at /usr/libexec/webmin-2.010/xterm/shellserver.pl line 88.

    I have an internal firewall, but if I disable the firewall, terminal still doesn't work.

    I don't understand what's going on with Centos and the different version reporting. Seems there are 2 different perl module installs, and/or a path missing somewhere. OpenSuse similar.

    In the end, as the command line perl install (such as cpan -i Net::WebSocket::Server or perl -MCPAN -e shell) is installing somewhere webmin can't see, and the webmin perl module installer was failing on dependency installs, I manually worked through each dependency until webmin would install Net::WebSocket::Server on Centos.

    Now Centos has the same error reports "Error: Connection to the socket... " as OpenSuse.
    File manager is still broken.

     
    • Ilia

      Ilia - 2022-12-01

      File manager is still broken.

      Also, what do you mean File Manager is still broken? Broken how?

       
      • Richard Farthing

        Please check my original bug report - it gives the file / line number of the error

         
  • Jamie Cameron

    Jamie Cameron - 2022-12-01

    "timeout waiting for connection" suggests that the browser isn't able to make a websockets connection to the shell server. Do you see any errors in your browser console?

     
    • Ilia

      Ilia - 2022-12-01

      Odd. I have never received response to that ticket until latest reply.

      CentOS 7 would work fine only if you enable EPEL repos the way it's described on their website.

      openSUSE work for me by enabling devel:languages:perl and installing perl-IO-Tty from there. Do not install it using CPAN.

       
    • Ilia

      Ilia - 2022-12-01

      Do you see any errors in your browser console?

      This is most likely the problem of Perl dependencies.

       
    • Richard Farthing

      No, sorry. Can you answer the query about the ports used in my earlier post? I'm using Squid and non standard ports may need ports opening.

       
  • Ilia

    Ilia - 2022-12-01

    Is perl-lib module installed on your openSUSE system?

    Is the new Webmin 2.010 installation dir has vendor_perl dir in it? Have you tried restarting Webmin from command line?

    If nothing of this helps, is there a way i could login to the sytem and see what's going on?

     
  • Richard Farthing

    I'm now seeing this (below) when I log in remotely. Both Centos or Opensuse systems. I'm afraid this version is broken. I've been using Webmin for 15 years and never had problems like this - going to revert to older version for now

    HTTP/1.0 500 Perl execution failed Server: MiniServ/2.010 Date: Thu, 1 Dec 2022 10:00:09 GMT Content-type: text/html; Charset=utf-8 Connection: close
    ERROR — PERL EXECUTION FAILED
    Undefined subroutine &main::miniserv_using_default_cert called at /usr/libexec/webmin-2.010/session_login.cgi line 50.

     
  • Ilia

    Ilia - 2022-12-01

    ERROR — PERL EXECUTION FAILED
    Undefined subroutine &main::miniserv_using_default_cert called at /usr/libexec/webmin-2.010/session_login.cgi line 50.

    This problem can indicate:

    1. Webmin wasn't properly restarted
    2. Webmin 2.010 upgrade failed leaving various files missing in the package.

    I would rather used RPM package for openSUSE. Your system may miss some dependencies. Besides, openSUSE is fully supported with Webmin 2.010. Just keep your existing config files. No reason to downgrade. You need to figure out what's wrong!

     
  • Jean-Marc Annonier

    Hello all,

    I have upgraded Webmin from 2.000 to 2.010 on my Raspberry Pi 4b on Raspbian 11. It works however the new Terminal does not. See error message attached. It appears only once after I restart Webmin. The other times, the Terminal screen remains black. Similarly if I press Alt-K to open the old Terminal window it remains black with Connecting... in the left top corner.

    Thanks!

     

    Last edit: Jean-Marc Annonier 2022-12-02
    • Ilia

      Ilia - 2022-12-02

      Please double check if you have libdigest-sha-perl and libdigest-md5-perl packages installed.

      If that still doesn't work, check /tmp/.webmin/wp-nn.out to get more details.

       
  • Jean-Marc Annonier

    Thanks but I think I've found the culprit without installing the missing Perl modules. I had disabled SSL in Webmin as I only use it on the LAN. Once I turn it back on, Terminal works!

    I guess I need to install let's Encrypt certificates to fully enable https without Chrome complaining each time.

    Cheers,

     
    • Ilia

      Ilia - 2022-12-02

      Oh, I see. That issue (not working in non-SSL mode) was fixed too.

      We will do our best to wrap a new Webmin 2.011 as soon as possible.

       
      👍
      1

Log in to post a comment.

MongoDB Logo MongoDB