Here goes the question?

[larryc06]

Here are some comments in my secure log that I do not understand. I have been googling now most of the afternoon and can not find any answers. I hope someone can help me here

How is it that localhost is using 0.0.0.0 I thought it was suppose to be 127.0.0.1?
Jun 19 19:42:57 localhost sshd[2216]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use

What is signal 15?
Jun 21 01:22:43 localhost sshd[1899]: Received signal 15; terminating.

I never sign in as root. I always sign in as my username then go to root when needed?
Jun 21 01:24:27 localhost gdm[2483]: pam_unix(gdm-autologin:session): session opened for user larryr by (uid=0)

Here is a complete showing of what confuses me.
Jun 21 01:23:56 localhost sshd[2017]: Server listening on :: port 22.
Jun 21 01:23:56 localhost sshd[2017]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
Jun 21 01:23:56 localhost runuser: pam_unix(runuser-l:session): session opened for user root by (uid=0)
Jun 21 01:23:58 localhost runuser: pam_unix(runuser-l:session): session closed for user root
Jun 21 01:24:27 localhost gdm[2483]: pam_succeed_if(gdm:auth): error retrieving user name: Conversation error
Jun 21 01:24:27 localhost gdm[2483]: pam_unix(gdm-autologin:session): session opened for user larryr by (uid=0)

Thanks

[ibbo]

Jun 19 19:42:57 localhost sshd[2216]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use

I believe this is caused by IPv4 and IPv6 both been enabled.
vi /etc/sysconfig/network and add/ edit the
NETWORKING_IPV6=no


What is signal 15?

sshd was sent a SIGTERM (task killed) did you end the ssh process by hand?

I would not worry too much about it. It looks fine and is just like my ssh logs.

Ibbo

[larryc06]

many thanks. For your question about ssh; no I did not shut it down. I had not been using it nor, had I been online. I was working on learning and setting up the iptables for that computer. I also noticed traffic from the lights on my switch for that computer that is why I checked my logs. I have learned more since then so I will be able to tell more about the situation. WIRESHARK. :-)