Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to ssh to server after upgrade #413

Open
vjoomens opened this issue Jan 18, 2025 · 0 comments
Open

Unable to ssh to server after upgrade #413

vjoomens opened this issue Jan 18, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@vjoomens
Copy link

vjoomens commented Jan 18, 2025

Hi,

After many failures with previous versions of the tool I finally managed to perform a pretty flawless upgrade with 1.4.5 of centos2alma. There are 2 major issues and 1 minor:

Major:

  1. I'm unable to login, either via console or via ssh (client_loop: send disconnect: Broken pipe), looks like the user manager is stopped:
    ip-172-30-2-95 login: root
    Password:
    Last login: Sat Jan 18 2 Stopping User runtime directory /run/user/0...
    [ OK ] Stopped User runtime directory /run/user/0.
    [ OK ] Removed slice User Slice of UID 0.
    [ OK ] Stopped Serial Getty on ttyS0.
    [ OK ] Started Serial Getty on ttyS0.
    [FAILED] Failed to start Seafile hub.
    See 'systemctl status [email protected]' for details.
    [FAILED] Failed to start Seafile hub.
    See 'systemctl status [email protected]' for details.

AlmaLinux 8.10 (Cerulean Leopard)
Kernel 4.18.0-553.34.1.el8_10.x86_64 on an x86_64

ip-172-30-2-95 login:

  1. There's a problem with the apache config:
    httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 13 of /etc/httpd/conf.d/00_mod_security.conf: No matches for the wildcard '00*exclude.conf' in '/etc/httpd/modsecurity.d', failing (use IncludeOptional if required)

Minor:

  1. The Plesk Premium Email installation got corrupted, but that was easily fixed via plesk admin.

Please help me with the 2 major issues, that would bring this upgrade to a positive end.

NOTE on issue 1, I could still ssh the server after the completion of stage 1 (the reboot).

Kind regards,

Victor Oomens

@vjoomens vjoomens added the bug Something isn't working label Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant