Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, i have a Pentium 4, exactly the same as the CPU in the picture http://i39.tinypic.com/sb7sed.jpg
and sometimes my network go down without reason, at least i don't know why. I know that sometimes it go down because my ping test fails replying
Ping request time out.
But is just sometimes and then a few seconds it come up again....
in that server is running a PBX service and the OS running there is Fedora Core 8. Everything is running well excluding the network device (the network device is integrated in the motherboard)
What you recommend me?
When i run lspci in the command line i get this output
Hi, i have a Pentium 4, exactly the same as the CPU in the picture http://i39.tinypic.com/sb7sed.jpg
and sometimes my network go down without reason, at least i don't know why. I know that sometimes it go down because my ping test fails replying
Ping request time out.
But is just sometimes and then a few seconds it come up again....
in that server is running a PBX service and the OS running there is Fedora Core 8. Everything is running well excluding the network device (the network device is integrated in the motherboard)
What you recommend me?
When i run lspci in the command line i get this output
Hi, look i recently execute this
vi /var/log/messages and i read something like i ave to install nss-mdn
so i download the nss-mdn RPM file...
Now i proceed to execute each command you said...
Hi, look i recently execute this
vi /var/log/messages and i read something like i ave to install nss-mdn
so i download the nss-mdn RPM file...
Now i proceed to execute each command you said...
Look, before i install nss-mdn in /var/log/messages the file content has this lines
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().
Now before installed the nss-mdn RPM file hte /var/log/messages
have this line
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().
Look that the line May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Is not present... and now the ping test don't fail... What you think, is this the nss-mdn the Solution or is just coincidence?
Look, before i install nss-mdn in /var/log/messages the file content has this lines
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().
Now before installed the nss-mdn RPM file hte /var/log/messages
have this line
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: avahi-daemon 0.6.21 starting up.
May 17 19:54:50 TornadoR3 avahi-daemon[2084]: Successfully called chroot().
Look that the line May 17 19:54:50 TornadoR3 avahi-daemon[2084]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Is not present... and now the ping test don't fail... What you think, is this the nss-mdn the Solution or is just coincidence?
are the pings still failing??
mdns uses multicast to find hosts on a small network, so it could have been the problem,but the question is - is ping working ok now?
Yes, for now the ping test doesn't fail anymore.
But i will still testing using more ping tests to be sure that that was the solution to the problem.
Thanks, buddy if me problem still there, i will write to contact you again .
Sorry, I still have the same problem
i make ping for some hours and
Of 8247 sent packages just 8084 was received.
Please, what can i do? In this cpu is running a PBX system and the calls sometimes are dropped by this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.