HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Err messages from dmesg
Operating System - Linux
1830244
Members
2006
Online
109999
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2002 08:59 AM
09-19-2002 08:59 AM
portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
lockd_up: makesock failed, error=-5
portmap: server localhost not responding, timed out
lockd_up: no pid, 2 users??
portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
lockd_up: no pid, 3 users??
portmap: server localhost not responding, timed out
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
VFS: file-max limit 8192 reached
nfs: server toaster not responding, still trying
Does any know what this is refering to " VFS: file-max limit 8192"? df seems to hang on me. Why? Thanks.
portmap: server localhost not responding, timed out
lockd_up: makesock failed, error=-5
portmap: server localhost not responding, timed out
lockd_up: no pid, 2 users??
portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
portmap: server localhost not responding, timed out
lockd_up: no pid, 3 users??
portmap: server localhost not responding, timed out
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
VFS: file-max limit 8192 reached
nfs: server toaster not responding, still trying
Does any know what this is refering to " VFS: file-max limit 8192"? df seems to hang on me. Why? Thanks.
Reputation of a thousand years can be determined by the conduct of an hour
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2002 11:52 AM
09-19-2002 11:52 AM
Solution
Some process has too many files open. Try this:
$ cat /proc/sys/fs/file-max
You should see some number there. You can change it by echoing a new one in:
$ echo 32768 > /proc/sys/fs/file-max
When the file descriptor index fills up, wierd things start happening.
$ cat /proc/sys/fs/file-max
You should see some number there. You can change it by echoing a new one in:
$ echo 32768 > /proc/sys/fs/file-max
When the file descriptor index fills up, wierd things start happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2002 09:34 PM
09-19-2002 09:34 PM
Re: Err messages from dmesg
Hi,
Get BAck with results after trying these things
Can you ping to localhost ?
Can you ping to 127.0.0.1 ?
#ifconfig lo
Does it show 127.0.0.1 255.0.0.0 UP RUNNING ?
If not try this
#ifconfig lo up
Check whether this file exists.
/etc/sysconfig/network-scripts/ifcfg-lo
and check it's contents.
Also check this file
/etc/init.d/network
neighbour table full means that ARP table is full and this is caused because of problems in localhost configuration or bad netmask.
regards,
U.SivaKumar
Get BAck with results after trying these things
Can you ping to localhost ?
Can you ping to 127.0.0.1 ?
#ifconfig lo
Does it show 127.0.0.1 255.0.0.0 UP RUNNING ?
If not try this
#ifconfig lo up
Check whether this file exists.
/etc/sysconfig/network-scripts/ifcfg-lo
and check it's contents.
Also check this file
/etc/init.d/network
neighbour table full means that ARP table is full and this is caused because of problems in localhost configuration or bad netmask.
regards,
U.SivaKumar
Innovations are made when conventions are broken
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP