Dear All,
unable to start the ssh service in fedora 16
Please help me any ine knows the issue resolution.
Thanks Prashanth
Am 28.03.2013 14:56, schrieb Prashanth Kasula:
unable to start the ssh service in fedora 16
Please help me any ine knows the issue resolution
STOP asking the same question 20 times as said F16 is no longer supported
and if you need help provide infos from command outputs and at least /var/log/messages and /var/log/secure
On Thu, 28 Mar 2013 19:26:30 +0530 Prashanth Kasula prashanthkasula@gmail.com wrote:
Dear All,
unable to start the ssh service in fedora 16
Please help me any ine knows the issue resolution.
Upgrade to Fedora 17 or 18. Is the solution
On Thu, Mar 28, 2013 at 02:01:59PM +0000, Frank Murphy wrote:
On Thu, 28 Mar 2013 19:26:30 +0530 Prashanth Kasula prashanthkasula@gmail.com wrote:
Dear All,
unable to start the ssh service in fedora 16
Please help me any ine knows the issue resolution.
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
That said, the OP should provide more information; just saying "unable to start ssh service" is not enough. What does it say when you do the following:
# systemctl start sshd.service # systemctl status sshd.service
What does /var/log/secure say?
# grep sshd /var/log/secure
If you do not provide the appropriate information, how can list members help?
On Thu, 28 Mar 2013 15:41:15 +0100 Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
Hepling OP stay on a possible _no_longer_secure_ box, is no help either.
On Thu, Mar 28, 2013 at 02:51:22PM +0000, Frank Murphy wrote:
On Thu, 28 Mar 2013 15:41:15 +0100 Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
Hepling OP stay on a possible _no_longer_secure_ box, is no help either.
There are often other reasons like unavailability of time or resources, etc that prevents one from upgrading. As a long time Fedora user you must know a distribution upgrade is not something you take on without planning. In light of that, a friendly reminder that the release is EOL followed by the specific help the OP is looking for might be a more useful response.
Just a thought.
Am 28.03.2013 16:08, schrieb Suvayu Ali:
On Thu, Mar 28, 2013 at 02:51:22PM +0000, Frank Murphy wrote:
On Thu, 28 Mar 2013 15:41:15 +0100 Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
Hepling OP stay on a possible _no_longer_secure_ box, is no help either.
There are often other reasons like unavailability of time or resources, etc that prevents one from upgrading.
not really, a dist-upgrade doe snot take that long
As a long time Fedora user you must know a distribution upgrade is not something you take on without planning.
and the lifetime-cycles are unknown? F17 is out since a very very long time
In light of that, a friendly reminder that the release is EOL followed by the specific help the OP is looking for might be a more useful response
the OP does not provide any information to help him and 5 identical posts does not add any information
Am 28.03.2013 16:08, schrieb Suvayu Ali:
On Thu, Mar 28, 2013 at 02:51:22PM +0000, Frank Murphy wrote:
On Thu, 28 Mar 2013 15:41:15 +0100 Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
Sometimes its good to try to be helpful even if the person can't take advantage of the kneejerk obvious response. There can be lots of reasons that a person can't upgrade an OS.
For instance, I am closely affiliated with a very large multi-hospital group that is still running Windows XP. Why? The reason is that the healthcare software (case management, automated medical records, etc.) has to be approved by the Food and Drug Administration before it can be substantially changed, and running it on a new operating system counts as a substantial change. Unfortunately, the bureaucratic and regulatory mess involved with validating this kind of software can take years, and the switch will likely cost this organization over a million dollars. And of course, as soon as it's done, it will already be "obsolete."
A few years ago, I directed a scientific laboratory that was very heterogeneous for similar reasons. Many machines were dedicated to specific pieces of laboratory equipment, and the OS was determined by the needs of the software that ran the equipment, not my convenience. I had one piece of equipment that required AmigaOS that we didn't decommission until 2008.
While upgrading is, indeed, the best solution, it may also be appropriate to help people who do not have that option.
That being said, it's hard to help without more information. The most common things that have made ssh not work for me have been:
1) Some ssh packages come initially configured to only allow ssh to localhost (127.0.0.1). Make sure that's changed in the config file if your package is like that.
2) Some initial configurations of selinux are not ssh friendly, either make sure that your selinix configuration allows ssh.
3) Is this a server or client problem? I wasn't sure from what you wrote whether your problem is that people can't get to your machine to ssh, or if you can't get to other machines from yours.
4) Have you made sure this isn't a firewall/connection problem if it's a client issue -- perhaps the packets are getting munched by a firewall. Can you get to and from other machines behind your firewall? Can other machines get out through your firewall?
5) You don't say whether your problem is global -- you can't ssh at all -- or to a specific host. Many servers don't use the standard ports, and you need to make sure you are pointing to the right place. Similarly, you need to make sure the server is actually serving. Can you connect with netcat?
6) If you are testing your client on your localhost as server, are you sure the daemon is really running?
7) You need to show us what your log files say. Are you having authorization problems?
8) Is this a problem all the time or is it intermittent?
9) Is your problem with standard sitting-at-the-console ssh, or is it with automatic-with-a-cron-job, or both?
billo
On 28.03.2013 16:56, Bill Oliver wrote:
Am 28.03.2013 16:08, schrieb Suvayu Ali:
On Thu, Mar 28, 2013 at 02:51:22PM +0000, Frank Murphy wrote:
On Thu, 28 Mar 2013 15:41:15 +0100 Suvayu Ali fatkasuvayu+linux@gmail.com wrote:
Upgrade to Fedora 17 or 18. Is the solution
Although that is good advice, it is definitely not a solution to the OP's problem.
Sometimes its good to try to be helpful even if the person can't take advantage of the kneejerk obvious response. There can be lots of reasons that a person can't upgrade an OS.
For instance, I am closely affiliated with a very large multi-hospital group that is still running Windows XP. Why? The reason is that the healthcare software (case management, automated medical records, etc.) has to be approved by the Food and Drug Administration before it can be substantially changed, and running it on a new operating system counts as a substantial change. Unfortunately, the bureaucratic and regulatory mess involved with validating this kind of software can take years, and the switch will likely cost this organization over a million dollars. And of course, as soon as it's done, it will already be "obsolete."
A few years ago, I directed a scientific laboratory that was very heterogeneous for similar reasons. Many machines were dedicated to specific pieces of laboratory equipment, and the OS was determined by the needs of the software that ran the equipment, not my convenience. I had one piece of equipment that required AmigaOS that we didn't decommission until 2008.
While upgrading is, indeed, the best solution, it may also be appropriate to help people who do not have that option.
That being said, it's hard to help without more information. The most common things that have made ssh not work for me have been:
- Some ssh packages come initially configured to only allow ssh to
localhost (127.0.0.1). Make sure that's changed in the config file if your package is like that.
- Some initial configurations of selinux are not ssh friendly, either
make sure that your selinix configuration allows ssh.
- Is this a server or client problem? I wasn't sure from what you
wrote whether your problem is that people can't get to your machine to ssh, or if you can't get to other machines from yours.
- Have you made sure this isn't a firewall/connection problem if it's a
client issue -- perhaps the packets are getting munched by a firewall. Can you get to and from other machines behind your firewall? Can other machines get out through your firewall?
- You don't say whether your problem is global -- you can't ssh at all
-- or to a specific host. Many servers don't use the standard ports, and you need to make sure you are pointing to the right place. Similarly, you need to make sure the server is actually serving. Can you connect with netcat?
- If you are testing your client on your localhost as server, are you
sure the daemon is really running?
- You need to show us what your log files say. Are you having
authorization problems?
Is this a problem all the time or is it intermittent?
Is your problem with standard sitting-at-the-console ssh, or is it
with automatic-with-a-cron-job, or both?
Spammer whisperer!? :)
Shake it for the birds, shake it for the bees Shake it for the catfish swimming down deep in the creek For the crickets and the critters and the squirrels Shake it to the moon, shake it for me girl, aww L.B.
poma
Am 28.03.2013 16:56, schrieb Bill Oliver:
Sometimes its good to try to be helpful even if the person can't take advantage of the kneejerk obvious response. There can be lots of reasons that a person can't upgrade an OS.
For instance, I am closely affiliated with a very large multi-hospital group that is still running Windows XP. Why? The reason is that the healthcare software (case management, automated medical records, etc.) has to be approved by the Food and Drug Administration before it can be substantially changed
and what has this do with Fedora? if you install fedora the life-cycle is known
On Thu, Mar 28, 2013 at 06:21:09PM +0100, Reindl Harald wrote:
Am 28.03.2013 16:56, schrieb Bill Oliver:
Sometimes its good to try to be helpful even if the person can't take advantage of the kneejerk obvious response. There can be lots of reasons that a person can't upgrade an OS.
For instance, I am closely affiliated with a very large multi-hospital group that is still running Windows XP. Why? The reason is that the healthcare software (case management, automated medical records, etc.) has to be approved by the Food and Drug Administration before it can be substantially changed
and what has this do with Fedora?
Bill is trying to explain why the OP might not be in a position to simply reinstall or upgrade.
if you install fedora the life-cycle is known
It may not have been at the time the person installed. Assume good intentions, please. If you are not willing to help further, it's OK to simply move on to another thread. :-)
On Thu, Mar 28, 2013 at 04:18:44PM +0100, Reindl Harald wrote:
In light of that, a friendly reminder that the release is EOL followed by the specific help the OP is looking for might be a more useful response
the OP does not provide any information to help him and 5 identical posts does not add any information
Maybe the OP is a newbie, maybe he is not familiar with email etiquette on mailing lists, there could be numerous other reasons. I think it is always wise to give the benefit of the doubt. If there is lack of information, pointing it out is more useful than getting all worked up about it. Don't you think?
Anyway, I feel this list has become very intolerant lately, maybe even hostile at times. This leads to a very unwelcoming atmosphere. As a community, this does not put Fedora in a positive light.
Just a thought.
-
Frank Murphy -
Paul W. Frields -
poma -
Prashanth Kasula -
Reindl Harald -
Suvayu Ali -
William Oliver