After upgrading to 14.2 ssh dont works

check if this port is not currently used using
sockstat -4

If the previous sshd process is not closed you can kill it to free the port and then start it again.
 
I'll take a look tomorrow. I had the same thing when upgrading from 13 to 14. Then it seems they reinstalled the ssh packages
 
Between 13 and 14, the /etc/ssh/sshd_config changed. Small change between 14.1 and 14.2 on the row VersionAddendum there the installer inserted >> ===, witch will fail on sshd load. Remove these “update inserts” and it will probably work. Under the update/install, you should get a message to manually edit the file under the update. Maybe you didn’t save?
 
amilis said:
Between 13 and 14, the /etc/ssh/sshd_config changed. Small change between 14.1 and 14.2 on the row VersionAddendum there the installer inserted >> ===, witch will fail on sshd load. Remove these “update inserts” and it will probably work. Under the update/install, you should get a message to manually edit the file under the update. Maybe you didn’t save?
Click to expand...
You were right. I deleted ">>>>>=====current version" in sshd_config and everything worked on server supermicro .
 
But on the Tayan server the situation is different. Everything is fine with the sshd configuration file. But sockstat -4 doesn't show anything.

There are no sockets at all and sshd don't start
 
A lot of things didn't load, for example

ifconfig
ifconfig : netlink is not loaded and load attempt failed:No such file or directory
 
I looked at the errors when loading the system.

module_register_init:MOD_LOAD (vesa 0xffffffff115e10) error19
and apei0 < ACPI Platform error Interface>
and rinetd errors
and sshd errors
 
So I’m wondering whether it makes sense to restore the system or is it better to copy the hard disk of a supermicro server using DD?It’s just inconvenient because the supermicro is in a rack and it’s difficult to get it out of there
 
When it boots can you login on the console? I'm wondering what freebsd-version -urk outputs. Those "Function not implemented" errors might be an indication of an old kernel running on new userland. Does this machine perhaps have a custom kernel?
 
SirDice said:
When it boots can you login on the console? I'm wondering what freebsd-version -urk outputs. Those "Function not implemented" errors might be an indication of an old kernel running on new userland. Does this machine perhaps have a custom kernel?
Click to expand...
 
this machine have not a custom kernel.I copied to this machine using dd a hard drive from another machine. 14.1 worked in this machine well
 
You didn't completed the upgrade.

After installing new kernel you need to do another

freebsd-upgrade install

To install the new userland then you need to reboot and reinstall/upgrade ALL pkgs/ports and reboot 3-th time.
 
You canceled the automatic conflict merge that's why you didn't install the new userland.

Here's the summary steps:

Fetch the 14.2 upgrade

freebsd-update upgrade -r 14.2-RELEASE


Install new 14.2 kernel and reboot using the new kernel.

freebsd-update install
shutdown -r now


Install new 14.2 userland

freebsd-update install
shutdown -r now


Reinstall all pkg/ports so they use new 14.2 libs then restart again

pkg bootstrap -f
pkg update
pkg upgrade


or if you use ports use your portupgrade/portmaster to force rebuild and install of all ports
then reboot. Also you will need to upgrade some old obsolete pkgs which doesn't exist anymore between 12.2 -> 14.2

pkg ver | grep "?"



freebsd-update install
shutdown -r now
 
VladiBG said:
You didn't completed the upgrade.

After installing new kernel you need to do another

freebsd-upgrade install

To install the new userland then you need to reboot and reinstall/upgrade ALL pkgs/ports and reboot 3-th time.
Click to expand...
ц
VladiBG said:
You canceled the automatic conflict merge that's why you didn't install the new userland.

Here's the summary steps:

Fetch the 14.2 upgrade

freebsd-update upgrade -r 14.2-RELEASE


Install new 14.2 kernel and reboot using the new kernel.

freebsd-update install
shutdown -r now


Install new 14.2 userland

freebsd-update install
shutdown -r now


Reinstall all pkg/ports so they use new 14.2 libs then restart again

pkg bootstrap -f
pkg update
pkg upgrade


or if you use ports use your portupgrade/portmaster to force rebuild and install of all ports
then reboot. Also you will need to upgrade some old obsolete pkgs which doesn't exist anymore between 12.2 -> 14.2

pkg ver | grep "?"



freebsd-update install
shutdown -r now
Click to expand...
How can I reinstall if the network stops working?
ifconfig
ifconfig : netlink is not loaded and load attempt failed:No such file or directory
I think I understand what happened. Probably the network files were broken during the upgrade
 
When the server is booting (the menu), can you start the server on the old kernel and everything working? Option 6 (if you have more kernels).
 
amilis said:
When the server is booting (the menu), can you start the server on the old kernel and everything working? Option 6 (if you have more kernels).
Click to expand...
Thanks, using point 6, I booted from the second kernel. Ifconfig works there
I was thrown to root, but I can’t edit rc.conf - is unwritable. And in general the entire system with this kernel is unwritable
:D
 
Is that server a 12.2-Release? Or that is the old kernel.
That’s old!

About this “unwritable”, can’t give you any hint there. :(
Maybe time to make a clean fresh install?
 
amilis said:
Is that server a 12.2-Release? Or that is the old kernel.
That’s old!

About this “unwritable”, can’t give you any hint there. :(
Maybe time to make a clean fresh install?
Click to expand...
Second kernel 14.1-Release-p6.And the first kernel is also 14.1-p6, but broken by the upgrade knee :D
 
You must log in or register to reply here.
Back
Top