LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   ssh periodically disconnects after swaret upgrade -a (https://www.linuxquestions.org/questions/slackware-14/ssh-periodically-disconnects-after-swaret-upgrade-a-358552/)

tallship 08-30-2005 01:21 PM

ssh periodically disconnects after swaret upgrade -a
 
Hi,

I installed slackware 10.0, and then swaret as a package, ran the upgrade a few times, and noticed a few quirks in my system following the process for "current' settings.

1.) The system reports a lack of space available (when there is plenty).

2.) The system reboots somewhere during the upgrade -a process

3.) and the most annoying of all, ssh clients get disconnected periodically w/o warning, for no apparent reason.

Here's the packages for the versions past, and currently running:
/var/swaret/rollback/openssh-3.8.1p1-i486-1.tgz
/var/swaret/openssh-4.1p1-i486-1.tgz

The /etc/ssh/ssh_config file is way different than the ssh_config file from a stock 10.1 install too. I find that really interesting.

If anyone has any input, insight, or otherwise as to why these peculiar behaviours are occuring it would be greatly appreciated.

gbonvehi 08-30-2005 01:23 PM

1) It's a bug of a version of Swaret (at least that's what I've read here), try upgrading to the latest one.

tallship 09-06-2005 03:51 PM

Yes I see now that this space issue is a bug of, I guess, the latest release, which is what I d/l'd as a package and installed.

does anyone know why my ssh would be disconnecting periodically afterwards?

gbonvehi 09-06-2005 04:58 PM

Are you doing something when it disconnects you? Probably it has a timeout that disconnects if there's no activity during a period of time.

shilo 09-07-2005 12:31 AM

After doing a BIG upgrade (like "swaret --upgrade -a"), did you do anything else?

You may want to:
Code:

find /etc -name "*.new"
This will give you an idea about configuration files that MAY have changed.

If you find a file with the ".new" extension, you need to ask yourself, "Have I manually updated that file?" If the answer is NO, then you should use a command like:
Code:

mv config_file.new config_file
If the answer is YES, you should use a command like:
Code:

diff config_file config_file.new
and use the results to help you edit your current config file.

This is a step that many people who use "automagic" upgrade tools like SWareT seem to forget. THis may be the cause of your problem. Also, try the old "Windows trick" of rebooting.


All times are GMT -5. The time now is 04:04 AM.